Hi, I just started editing an airport project this morning. Yesterday I
installed the latest SDK. Performance of selecting and moving things has
gotten SUPER slow. I think what’s going on is it’s doing a consistency check
of the airport with every single change. It was not like this last week with
the previous SDK version Scenery editor. I’m just trying to move points of a
taxiway around, and it’s super frustrating and taking me forever. I have to
pick and repick points, then I have to wait several seconds before I can
select either the point or the plane of the triad I want to move, and then I
have to wait again before I can begin moving it. It’s not a big airport, just
a small GA airport in Maine with a single runway, some parking spots, a
vehicle spot, and a fuel parking spot. Is anyone else noticing this? Edit: I
think what’s going on is, every time I make an edit to a taxiway or apron,
it’s regenerating the trees nearby and this is taking a lot of compute. Is
there any way to freeze the trees? Hmm, maybe if I just add a temporary tree
killer polygon over the whole area far away from where I’m working, that will
help. Edit 2: That didn’t help Edit 3: Is it perhaps related to the top down
camera? When it really slows down, and it slows down over time, all of a
sudden the top down camera goes crazy, if I touch the wheel, it zooms all the
way in, I just touch it again slightly back and I’m a mile above the airport.
And it just keeps going, if I try to move, it skips by a mile. The only fix is
to switch to developer camera and then back again. If I try to use Developer
camera to do apron/taxi/polygon work, it goes crazy because it doesn’t like to
look straight down. It’s getting extremely frustrating. I tried exiting out,
rebooting my computer, then getting back in again, and it was ok for a while,
but then it got super slow again. But I was working on a different area of the
airport at first, so I don’t know if it’s location based (i.e. near
vegetation), or if there’s a memory leak, or what.
The problem with DevMode editor slowing down over time, seems to be related to
rearranging the whole nodes hierarchy each time you move something. Initially
it seems to work fine after a simulator restart, but if the airport is
complex, in a few minutes it starts to degrade again. When it happens, the
amount of RAM taken by the sim as reported with Task Manager, gets
considerably higher than when starting editing. I made all possible tests,
like setting the graphic to the absolute minimum, turning off online data so I
would be working on synthetic landclass scenery, and it didn’t do the
slightest difference, neither did switching from DX12 to DX11, and trying all
sort of graphic settings, from the highest to the lowest one, tried to disable
the visibility for everything except the object I was editing, but nothing
helped. I even tried with placing or not a copy of the scenery I was editing
in the Community folder, or not placing it, no difference either. This, added
to noticing during the slowdowns, no issues are reported on the GPU
performance graphs in the DevMode fps display, but the Main Thread gets an
abnormally high latency, like 200-300 msec or even more, it seemed to indicate
the problem is not graphic. What seems to be a good solution, is to not use
the “Legacy Hierarchy”. If you place things in custom groups, the editor seems
to perform way better, even on very complex airports and it’s possible to
crack up all graphic settings again, with no issues. With no hierarchy at all,
it’s even faster, although you might get lost finding things. This has been
reported in another post, which I read and apply this suggestion has saved me
from the big headache of having to work on an extremely large airport with the
editor working so badly.
Thanks, I’ll try that. Thing is, this is a really simple airport - KIWI in
Maine. The airport definition file is only 92KB, there’s hardly anything in
it. This is new behavior to me. Just last week, everything was fine working in
other airports, now, with this airport and my first time in the latest SDK (I
just started working on it today) it’s unusable. I’ll attach the source file.
I just started rearranging things and setting it up, so it’s a bit of a mess.
But if moving apron and taxi points was moving at rates it was moving just
last week, I’d be almost done by now.
Answer for me: Create your airport project. Make some edits to the airport in
the scenery editor. Create a package of the airport. Exit MSFS. Put the
package of your project in your Community directory. Restart MSFS and go back
to the scenery editor and all should be fine. Apparently the Scenery Editor
has a tough time editing a project over a default airport or something? I’m
not sure, but this fixed it.
Ok, in your case the XML file was fairly small, so it doesn’t seem to be the
same issue as mine. I have a 5MB XML file, with about 50K lines in it, so the
node processing seems to be significant, when they are in a Legacy Hierarchy.
It’s much better if they aren’t.