FlyAgi

The sam.xml is in the scenery main folder of the scenery you want to modify, for example "Aerosoft - EDLW Dortmund - 1 - Airport". If a scenery has multiple folders, check the 'airport' named folder, there you should find it. If there is no sam.xml in any of these folders, the scenery does not have a sam configuration and is not using sam at all (but you can create a sam.xml yourself and add jetways from the sam library in wed if you like).

Before you can edit a scenery (that already has a SAM configuration) you have to unlock it for editing first: Go to your scenery folder Open SAM.xml in a text editor Change the line including 'locked=true' to 'locked=false' Save file and try again. Then, in the authoring tool, you have to choose the scenery to work with in the first tab from the left. There you find a drop down menu and you should now find your unlocked scenery in this list so select that one and save, then start working on the configuration. If the scenery does not have a sam.xml yet you can create one using the same menu you select the scenery with. There should be a button 'add sam to scenery' to create a new sam.xml file.

Well, we got it sorted by now. In fact, the fps issue is caused by XP itself having issues with PNG textures in rare cases (one of the XP devs told me) and this should not happen in theory but we can fix this in the scenery by converting all textures to dds - which is the recommended method anyway and also improves loading times dramatically and also reduces file size of the scenery significantly. In the end your first impression was right, this was actually an optimization issue - but it will be fixed soon. 🙂

Another update on the situation: After wasting all day with this I finally found the issue and an update should be coming soon (the actual developer has to check if I did not mess anything up with my fix before we can publish the update).

I got it reproduced, it's happening to me too - still investigating but this might take some time, it's a really weird issue and it's hard to find what is actually causing this. I also noticed that, when this happens, all my CPU cores are fully utilized and this is totally abnormal behaviour, never seen this before.

Well... I just found there's indeed another issue caused by objects - that's a hard one, because objects usually don't cause any fps issues when not on screen but here I got fps drops when flying out of the airport, looking mostly at sky and clouds and not a single part of the airport is see on screen.

Please try the patch attached. To install, copy the 'Earth nav data' folder from the zip into your scenery folder and confirm file overwrite with yes. This should give normal performance as to expect (CPU and GPU frametimes are completely normal on my machine, before the GPU times got very high and this can also cause some fluctuation on CPU side because of waiting for the GPU I think). And please report back how that works for you. AS_LIME_Bergamo_V2_XP12_FPSFIX.zip

Update on this: You are right and the scenery is very performance heavy on the GPU side - I figured out how to fix this and an update will be published ASAP. 🙂

Isn't the XP12 version coming with an XP11 version as well? And was this a free update? I'm not sure if your XP12 version is the same as the XP11 one because the current scenery is a V2 version of the airport and when an Aerosoft airport is labeled with this kind of version number in the product name it's usually a completely new airport with new modelling - so if you are comparing the old V1 version with the new V2 then difference in the fps are to expect but then the V2 version should also look much more detailed. Anyway, I will try to get the files from the developers so I can see if the fps are reasonable or not.

You mean, the XP11 version runs faster? That's weird because they should be the same basically aside from some XP12 related optimizations... seems I need to check for myself with the actual product but this will happen monday at best. Meanwhile you could try the XP11 version in XP12 and see how that works in terms of performance.

I got some information from the Bergamo developer team and they don't know of any performance issues regarding Bergamo XP12 so the scenery should work with reasonable performance according to beta testing but they also stated that using SimHeaven might tank your fps significantly - maybe you can give it a try with this disabled and see if it makes a difference?

Okay... if Manchester works that much better, then I guess there might be an issue with the scenery but I don't have it right know so this has to wait until tomorrow to see if there actually is an issue. Judging by the screenshots it should not be much worse than Manchester, but the modelling at Bergamo is more detailed and it's a newer scenery so it can be more fps heavy for good reasons. Also have in mind that at Manchester there is only the city northern to the airport while Bergamo there is autogen all around the airport and this might also contribute to worse performance (similar to Manchester when approaching from the south looking at the city).

What CPU are you using and how did you set up your XP graphics options? XP12 is still very CPU bound and detailed airport scenery can have an impact on the framerates, especially when there are very high polygon objects involved (Madrid also cost some frames on the CPU side for me) - and this effect is stronger on weaker CPUs than on faster ones. Finally, SimHeaven is also taking some CPU performance away from you compared to default XP scenery.

Das hatte ich schon vor zwei Wochen oder so geändert, als ich die ersten Hinweise dazu bekam, im aktuellen Download sind die Pisten seitdem korrekt umbenannt vorhanden.

That's great, you got it. 🙂

That looks weird indeed. You did not accidentally reduce vegetation density to lowest levels in XP options? But there might also be an issue with scenery order or some other package is overriding your trees somehow with placeholders... Anyway, please upload a log.txt file so we can investigate this. 🙂

Ja, das ist klar, und diese Mesh-Kachel sollte mit der Freeware nicht verwendet werden, da sollte dann einmal die Kachel neu generiert werden, was theoretisch auch mit der Standard-Mesh-Quelle von Ortho4xp funktionieren sollte (jedenfalls gab das mit der XP11-Version keine Probleme, sollte mit der XP12-Version also auch funktionieren).

Super... und danke für die Rückmeldung. 🙂

Die Szenerie hat ja kein eigenes Mesh mehr, somit muss für Ortho4xp auch nichts deaktiviert werden - ein eigenes mesh würde hier aber auch nichts ändern, da die Probleme durch das ortho-mesh entstehen, welches wohl irgendwie anders erzeugt werden müsste. Wenn das nicht klappt kannst du aber noch ein Flatten in die apt.dat des Flughafens setzen: Öffne die apt.dat mit einem Texteditor (die Datei liegt im Flughafenordner unter Earth nav data) Füge die zeile "1302 flatten 1" unter "1302 transition_alt 5000" ein und speichere die Datei ab Damit sollte dann der ganze Flughafen flach gezogen und alle Meshprobleme innerhalb des Flughafens behoben werden.

Technisch wäre das jetzt nicht so schwer (ich hatte mal den EDXE portiert vor Jahren), nur braucht es dazu jemanden, der das macht, ich hab da derzeit nicht die Zeit dafür und persönliche Motivation auch nicht, da ich den MSFS derzeit nicht selbst nutze. Wenn da jemand Lust drauf hat, kann er sich aber gern bei mir melden und bekommt dann, was er dazu braucht).

Du siehst gar keine Objekte außer Jetways und Bodenfahrzeuge? Klingt nach einem falsch platzierten Mesh in der Scenery-Packs.ini, die Meshes, inklusive Ortho4xp müssen nach ganz unten, darüber dann Flächensezenerien (SimHeaven X-World) und darüber die Global Airports als Trennung - und über diese Global Airports dann alle Flughafen-Szenerien. Hier nochmal in übersichtlich übersichtlich: Airports Global Airports Flächenszenerien/SimHeaven Meshes/Ortho4xp Falls das nicht klappt schick mir bitte eine log.txt um zu sehen, wo der Fehler liegt.

Dann lade bitte nochmal neu herunter, ich hatte das geändert und aktualisiert.

Die wurden für die Szenerie bereits umbenannt. 🙂

Ja... rüste ich nach... ... erledigt. 🙂

Well... that means, Jetway are not visible at all or they don't work as expected? The scenery uses standard XP12 jetways which have to be connected manually. Anyway, I will check the scenery and upload again, just in case that the jetways were disabled for some reason in the current version, please download again in half an hour (counting from the time of this post, I have to upload a new version which takes some time) and check again.