MrSauga

Finally found the issue. For whatever reason the sim.cfg file located under inibuilds-airport-klax-losangeles\SimObjects\Landmarks\noolaero VDGS KLAX\ had to be removed/renamed. Even though I was not using the VDGS(disabled in iniManager) the file was still being called, or accessed. At first I just removed the line entry for Gate 62 in the sim.cfg file: [fltsim.63] title=noolaero VDGS KLAX GATE 62 model=T2-18 vdgs_features=stand_number, startup, local_time vdgs_nose=33.941842395472136, -118.4016367104799, 261.696 vdgs_stand=62 vdgs_screens=GUIDANCE "noolaero VDGS KLAX T2-18 guidance", STANDBY "noolaero VDGS KLAX T2-18 standby", STARTUP "noolaero VDGS KLAX T2-18 startup" Once I did that then only gate 62 allowed the marshaller to be visible. All other gates had the marshaller invisible. Renaming that sim.cfg file so it wasn't used fixed the other gates.

No, I’m not frustrated at all. There’s plenty of other options to use instead of a marshaller. As I mentioned, I’ll need to figure out what is wrong. I can’t really see it being the scenery, but something the OP and myself obviously have in common. Whatever the issue, as soon as I figure it out then I’ll update this thread. Thanks for the support and looking into the matter.

Thanks, but I did this before I posted the issue I was having. Clearing the scenery indexes and reinstalling the scenery did not help. It's the first scenery I have purchased from iniBuilds. Nice scenery, but I think that will be my limit until I find out what the reason is for the issue I am having.

Could only upload the three above. Had to start a new reply.

Thanks for testing. I'm using the latest build of KLAX and also GSX (3.1.6) Here's images from Gate 62. I didn't try your gates, but the rest was the same. You can see in the GSX editor that the Marshaller is not there. He/she flickers when moving around the parking area, but never stays visible. I never checked over at GSX. I just assumed the issue was the scenery based on the OP. Although the original official GSX profile was installed through the iniManager, as soon as I modify it the name changes. So, you may not see the same .ini file in one of the pics.

Yes, same thing happens with me. Makes no difference if I make a custom profile or use the klax-inibuilds profile, the same issue as mentioned above exists.