General Category > General Discussion
Strange problem rendering buildings
skwaL:
Maybe someone besides support here would have some general idea on what is going on, here is the issue. When I load ANY FightBeam or FSDT airport some buildings show up.....some dont. And the building that don't show up generally will show up if I fly close to them, the screenshots attached are essentially the break down of my problem. Now every time I will load the sim and any of the FSDT or FB Airports every single time, the buildings that show and the buldings that dont are different. It seems like my rendering distance at all these airports is being stupidly short.
What I have tried so far:
- Reinstalled the airport
- Reinstalled addon manager
- Both couatl and addon manage menus show up in the sim
- Updated Visual C++ Libraries
- Updated graphic drivers, deleted and created fresh FSX.CFG
- Tried both DX9 and DX10 settings (I generally run DX10)
- Tried changing settings in NVidia Inspector
- Changed Antipopup and AltitudeCulll values
Couatl seems to be working fine so does the addon manager.
Any suggestions are welcome
P.S. I have posted this topic on both FSDreamTeam and FlightBeam forums in hope that someone would be able to help me out.
Thanks,
Konstantin
virtuali:
--- Quote from: skwaL on September 17, 2015, 02:55:54 pm ---And the building that don't show up generally will show up if I fly close to them
--- End quote ---
Already discussed here:
http://www.fsdreamteam.com/forum/index.php/topic,10296.0.html
and here:
http://www.fsdreamteam.com/forum/index.php/topic,2794.15.html
skwaL:
I saw those posts. But my sim initially always had the HIGHMEMFIX in the fsx.cfg and I never changed compatibility settings.
braindamage02:
I've just upgraded my PC (all new hardware) and installed a new copy of Win 10 Pro 64. I was previously running Win 7 Home 64 with zero issues with FSDT or Flightbeam airports. Now with FSX (Deluxe + SP1 & SP2) reinstalled, I have this same issue of some buildings missing. Here's what I've done:
- Confirmed everything I've installed has been as administrator.
- Confirmed Windows Defender was off for both download and install (I do not have any other anti-virus software installed).
- Confirmed no FSX related programs, including FSX itself, are running in compatibility mode.
- Followed these steps from http://www.fsdreamteam.com/forum/index.php/topic,2794.0.html
--- Quote ---- Uninstall the scenery. Reply YES when asked if you want to remove the Addon Manager and the Couatl Engine. Reply YES to both questions.
- TURN OFF your antivirus. Don't just exit from its interface, but turn off the real time protection. Actual wording changes between products, however, it's the option to scan every file that gets open in real time, without user intervention.
- Reinstall the scenery with the Antivirus TURNED OFF. Don't launch FSX yet.
--- End quote ---
and
--- Quote ---The only possible explanation, is that another addon is clogging Simconnect with so many commands, that our own are received with a delay. It might be worth trying to disable *every* other 3rd party module in DLL.XML and EXE.XML, by setting the <Disable> tag to True, then trying one by one, and see if it makes any difference.
--- End quote ---
Even with the Addon Manager being the only module running, I still have missing buildings that only appear after getting very close to them. The buildings that are missing are usually different with every launch.
The OP also posted in the Flightbeam forums and stated that the determined solution was to install Acceleration. If the airports worked perfectly on my Win 7 install but not on Win 10, I fail to see how changing the sim I use is an acceptable solution. Any other input would be greatly appreciated.
virtuali:
--- Quote from: braindamage02 on March 14, 2016, 09:33:31 pm ---- Confirmed everything I've installed has been as administrator.
--- End quote ---
The installers automatically install themselves with admin rights so, it's not something that could be wrong, and it won't cause this issue anyway even if they didn't.
--- Quote ---- Confirmed Windows Defender was off for both download and install (I do not have any other anti-virus software installed).
--- End quote ---
The antivirus doesn't have anything to do with this. If you had an antivirus problem, one of the modules won't run, so you won't see ANY buildings, not even when getting close.
--- Quote ---Confirmed no FSX related programs, including FSX itself, are running in compatibility mode.
--- End quote ---
I'm sorry, but I stil think this is the most likely explanation. Every user that ever reported this issue, had the Compatibility flag checked either for FSX or for some other 3rd party program that starts with it.
--- Quote ---Followed these steps from http://www.fsdreamteam.com/forum/index.php/topic,2794.0.html
--- End quote ---
None of these are relevant. See the explanation about the antivirus. If you see the buildings only when you get close, it means the software IS RUNNING CORRECTLY.
--- Quote ---- Uninstall the scenery. Reply YES when asked if you want to remove the Addon Manager and the Couatl Engine. Reply YES to both questions.
TURN OFF your antivirus. Don't just exit from its interface, but turn off the real time protection. Actual wording changes between products, however, it's the option to scan every file that gets open in real time, without user intervention.
--- End quote ---
Same as above. The software is running. These steps are ONLY needed when it's NOT running, so you don't see anything, not even when getting close.
--- Quote ---Even with the Addon Manager being the only module running, I still have missing buildings that only appear after getting very close to them. The buildings that are missing are usually different with every launch.
--- End quote ---
So, the only explanation left is the Compatibility mode enabled.
--- Quote ---The OP also posted in the Flightbeam forums and stated that the determined solution was to install Acceleration. If the airports worked perfectly on my Win 7 install but not on Win 10, I fail to see how changing the sim I use is an acceptable solution. Any other input would be greatly appreciated.
--- End quote ---
There's no difference between FSX SP2 and Acceleration, regarding this problem. The user probably THOUGHT it was "fixed" by changing the sim, because when doing this, he got either his Compatibility settings reset (FSX install with all of them off by default), or the FSX.CFG has been reset.
In fact, you don't say if you tried to rest the FSX.CFG, and apply ONLY the HIGHMEMFIX=1 fix, and nothing else.
Navigation
[0] Message Index
[#] Next page
Go to full version