Missing Vehicles **SOLVED**

[crab453]

Hi, I'm using this in P3D v3 and the PMDG 777 and am having issues with vehicles missing. I'll have cartons entering/exiting the bay with no loader, missing stairs, etc. Some of these are at FSDT sceneries. I'm curious if it has to do with the vehicle update installs. I did try and install all of them, but all but the last two (which open and install normally) close shortly after opening without action. I'm not sure if they're all even needed, but was too curious if that issue (the installers closing early) had anything to do with me using Windows 10. Any ideas?

[virtuali]

You must have a problem with the update installers (as indicated in your message) and/or downloaded the wrong ones (not correct for the date of the full installer you have).

Just use the latest full GSX installer, it should fix every problem with missing vehicles.

[crab453]

I was just about to edit my post that I did uninstall/reinstall without success. I'll download the newest version I can find (I downloaded my current on 10/23) and install clean. Will I need any vehicle update files after that?

[crab453]

I did a full reinstall and noticed something I forgot before...Right now I have all vehicles showing up except the front container loader. Nothing is there, and no cargo is moving.

Edit: I'm only seeing this at KJFK at American's gate showing as 846. So may just be something with that location.

I guess my remaining question is just with downloading the latest version from your page, will I still need any vehicle update files, and if so, which?

Thanks again

[virtuali]

Edit: I'm only seeing this at KJFK at American's gate showing as 846. So may just be something with that location.

Some vehicles have parking spot radius restrictions.

I guess my remaining question is just with downloading the latest version from your page, will I still need any vehicle update files, and if so, which?

The full installer is always fully updated with everything.

[crab453]

Excellent. Thank you for the quick replies.


Another question if I may. I see previous questions referring to the PMDG 777 and the fact that P3D's jetways attach to L2. However, GSX requests door L1 to be opened. Replies guide us to edit the cfg file to swap the doors and this has worked for people. When I use the editor, I see it is sourcing the aircraft info from the internal GSX database, and no cfg file exists in the aircraft's folder. Is there another file I should be looking into, or is there a newer method?

[virtuali]

When I use the editor, I see it is sourcing the aircraft info from the internal GSX database, and no cfg file exists in the aircraft's folder. Is there another file I should be looking into, or is there a newer method?

You can swap the doors in the editor, by exchanging their parameters. When you save the file, a GSX.CFG file is create in the %APPDATA%\Virtuali\Airplanes folder.

The aircraft folder it's normally used by airplane developers if they want to supply a GSX configuration file that has less risks to be destroyed by user mistakes because, when you use the "Reset" button to undo all your changes, it will remove ONLY the file created by *you* in the %APPDATA% folder, NOT the one in the aircraft folder (which is supposed to be provided by the airplane developer), so you don't have to start from scratch, but from the configuration supplied by the airplane developer. Assuming there IS one, of course...

[crab453]

When I use the editor, I see it is sourcing the aircraft info from the internal GSX database, and no cfg file exists in the aircraft's folder. Is there another file I should be looking into, or is there a newer method?

You can swap the doors in the editor, by exchanging their parameters. When you save the file, a GSX.CFG file is create in the %APPDATA%\Virtuali\Airplanes folder.

The aircraft folder it's normally used by airplane developers if they want to supply a GSX configuration file that has less risks to be destroyed by user mistakes because, when you use the "Reset" button to undo all your changes, it will remove ONLY the file created by *you* in the %APPDATA% folder, NOT the one in the aircraft folder (which is supposed to be provided by the airplane developer), so you don't have to start from scratch, but from the configuration supplied by the airplane developer. Assuming there IS one, of course...

Understood, worked perfectly. Thanks again for all the help!