February 5, 201214 yr I have in my aircraft collection a few airplanes that are using the FSX weight module to add and remove loadouts. Notably the ukmil Tornado, and Skysim Mirage.After not flying these for a while, the other day I going to do a quick flight in the Tornado. After loading the aircraft I entered the Fuel and Payload menu and added my weights and fuel. Pressed ok and returned back into the sim. The loadout displayed for a few seconds before disappearing again. I returned to the Fuel and Payload window and saw that they had returned to the initial setting. I have checked with other aircrafts, and it applies to all, so it's not just a Tornado problem. It did work before, so there is something that has changed or have been broken in my config.I have search all over the web for information about similar cases but came up clean. I've tried deactivating FSUIPC, since I just got a registered version of it. I've tried changing the ownership of the folders, but nothing has worked so far.My fightsim version is Acceleration.OS is Win7 x64Any hints, tips or solutions would be really appreciated. Edited February 5, 201214 yr by F16_Driver
February 5, 201214 yr I could explain the fuel thingy, if you are close to a fuel spot on that airport. You should see some fuelling station close to you, but that's not the actual trigger. But this should not affect your payload, only your fuel will always reset to 100% when being too close.
February 5, 201214 yr Author Yeah, it's not that. I happens where ever and whenever. Also the fuel is going to 0% not 100% in the tanks affected.
February 5, 201214 yr And the realism settings are checked? There's an unlimited fuel option. Just in case.
February 5, 201214 yr No, that would be too much work for this one. Maybe reset your fsx.cfg and look if some FSUIPC option or another addon of yours triggers that fuel and payload issue. I mean, you would want to know, right? Otherwise you reinstall stuff and get the same error.
February 5, 201214 yr Author Problem solved. :) Turns out it was some miss behaving dlls from the Beta SP1 release of Milvis's F-15E. :) Edited February 5, 201214 yr by F16_Driver
Create an account or sign in to comment