Weijs Posted February 12, 2020 Share Posted February 12, 2020 HI After flying some minutes the scenery is vague, is refreshing too slow or is not refreshing anawhere quick enough. Frame rates are around 50, but FXS is not running smoothly. See pictures below. To solve the problem I did apply Holger Sandmans "resolving rapid ground texture", verified libraries and Open LC Europe and I have tapped FSX-libraries in setting FSX. But that does not help. Besides I noticed the scenery-order in FSX seems to be wrong: 1 - 9 Open LC Europe, 10 Open LC America 2, 11 FTX ARBX LIBS, 12 - 31 ORBX- airport, 32 - 55 ORBX regions, 56 FTX-22-Global Airport, 57 - 66 Aus vs 2, 67 FTX-22 OLC Fixed APT, 68 ORBX Open LC Europe lights, 69 - 71 ORBX LC Europe 1, America 1, 2 BASE 72 - 92 ELPB en other non-ORBX airport and scenery, 93 addon scenery, 94 - 114 Edwards and parts of the world, 114 - 118 Vector, 119 BASE. I have no idea how to fix. Can somebody help me? I'am running FTX Central v4. OS: Windows 10, Simulator FSX SE. PC: Intel Core i7 4790, 3.6 Quad-core. NVidia Ge Force GTX 970. Link to comment Share on other sites More sharing options...
Doug Sawatzky Posted February 13, 2020 Share Posted February 13, 2020 Hi I would go to settings/help and run the Sync Simulator function. Then you can go to settings/Insertion Point and set them like this. Ensure all of your 3rd party non Orbx addons are at the top of your scenery library and above your FTX entries. Then in Orbx Central Insertion points "Orbx Airports and Regions”, put your last non Orbx 3rd party listed in your scenery library addon in the INSERTED BELOW window. Then for the "Orbx Global openLC” ensure the Orbx Airports and Regions are in the INSERTED BELOW window. Link to comment Share on other sites More sharing options...
Weijs Posted February 16, 2020 Author Share Posted February 16, 2020 Hi Doug Thank you. I did some flying around. The textures are better, but are at distance still vague: see picture. Is there something to do to fix? Harry Link to comment Share on other sites More sharing options...
Smudger Posted February 16, 2020 Share Posted February 16, 2020 42 minutes ago, Weijs said: Is there something to do to fix? Hello Harry, it is to do with the LOD radius, in FSX.cfg that is set at [TERRAIN] LOD_RADIUS=4.500000, this is an aid to help VAS on a 32bit program. You could set it larger in the FSX.cfg but at a cost to Virtual Address System, causing an OOM quicker. P3Dv4.cfg is set to [TERRAIN] LOD_RADIUS=6.500000, clearer for further, but this is a 64bit program, without VAS concerns. Link to comment Share on other sites More sharing options...
Weijs Posted February 18, 2020 Author Share Posted February 18, 2020 Thank you. I also set filtering to anisotropic and ticked the anti aliasing. Now everthing seems te be fine. Harry Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.