March 12, 201610 yr Pete, I assume that you have systematically disabled all of those other products (ORBx FTX Global/Vector etc) to see if the "rogue grass textures" disappear? As for screenshots, just press the PrtScn key when you want to take a picture, paste it in MS Paint, and then save it. Christopher Low AMD Ryzen 7 9800X3D CPU / 64GB DDR5-6000 RAM / 12GB Nvidia RTX 4070 Super GPU / Gigabyte X870E Aorus Elite Wifi 7 / 1+2TB Samsung Evo Plus M2 Nvme UK2000 Beta Tester
March 12, 201610 yr Without going through all the pages in here once again, what were the negative sides again if you reinstall the content pack like things you might end up having to reinstall etc? Or was it mainly when reinstalling the texture pack you were required to reinstall things like FTX Global?
March 12, 201610 yr Next I might try re-enabling the UT layers. Tomorrow though. I'm whacked for the day ... I'd start with uninstalling UK2000 EGLL first, then UTX (verify manually also). I don't run UTX and Orbx together (I've never been successful doing this despite the claims) ... just for diagnostics, not suggesting one is worse or better. You may also want to delete "SceneryIndexes" under ProgramData... And of course delete your shaders. Yes, good news is that it's solvable ... just have to identify culprit. The downside to having an "open system". Cheers, Rob.
March 12, 201610 yr Without going through all the pages in here once again, what were the negative sides again if you reinstall the content pack like things you might end up having to reinstall etc? Or was it mainly when reinstalling the texture pack you were required to reinstall things like FTX Global? See here: http://www.avsim.com...-out/?p=3386995 And scroll down to my post. [email protected] ∣ Asus ROG Strix B650E-E ∣ 64Gb@6000MT ∣ NVidia 5090 FE
March 12, 201610 yr I noticed in any case that all of the ORBX changes are additional entries, it doesn't appear to change any existing lines. ORBX installers used to change the entries listed in the file below (it's from my old FSX post related to the anomalies at Aerosoft Tegel). Affected lines are in bold. These "tweaks" caused problems with layering at some airports. As I'm away from my flightsim PC, I cannot say if it's still the case... https://www.dropbox.com/s/ok9mn104nd8dfg7/terrain.cfg.right.values.pdf?dl=0 Cheers, Roman Heriban
March 13, 201610 yr Commercial Member I'd start with uninstalling UK2000 EGLL first, Actually, there's really no point in that. UK2000 sceneries are VERY well behaved, and all contained in their own folders. Once switched off there is absolutely no way they play any part at all. I know this, I've been using them ever since Gary started writing them.. In fct none of them were "installed" on this PC in any case, their folders wewre copied over and the paths simply added to the SCENERY.CFG, so disabling or removing them from the CFG is the same as uninstalling them. I just wish all sceneries were so well behaved. then UTX (verify manually also). I don't run UTX and Orbx together (I've never been successful doing this despite the claims) UTX hasn't been installed at all in the Prepar3D 3.2 installation, which is completely new -- I uninstalled P3D v2 completely beforehand, including all folders. It was installed and its layers removed on the FSX-SE installation. You may also want to delete "SceneryIndexes" under ProgramData... And of course delete your shaders. Well, I'll try that, but isn't it odd that a virgin P3D3.2 installation suffers the same as a long added-to FSX-SE one? The only common thing that both have suffered in the last three days is OrbX layers installed. Yes, good news is that it's solvable ... just have to identify culprit. At present I've a mind to completely uninstall P3D 3.2 and start again, and maybe change to a completely non-Orbx solution. I'll possibly try Orbx once more at most, but it seems to have too much going on for FS health. Thanks Pete Win10: 22H2 19045.2728 CPU: 9900KS at 5.5GHz Memory: 32Gb at 3800 MHz. GPU: RTX 24Gb Titan 2 x 2160p projectors at 25Hz onto 200 FOV curved screen
March 13, 201610 yr Commercial Member ORBX installers used to change the entries listed in the file below (it's from my old FSX post related to the anomalies at Aerosoft Tegel). Affected lines are in bold. These "tweaks" caused problems with layering at some airports. As I'm away from my flightsim PC, I cannot say if it's still the case... https://www.dropbox.com/s/ok9mn104nd8dfg7/terrain.cfg.right.values.pdf?dl=0 Thanks. Those all check. In fact I did a comparison with the original and all the changes Orbx did were NEW (added) lines, pretty much all adding new landclass numbers. Pete Win10: 22H2 19045.2728 CPU: 9900KS at 5.5GHz Memory: 32Gb at 3800 MHz. GPU: RTX 24Gb Titan 2 x 2160p projectors at 25Hz onto 200 FOV curved screen
March 13, 201610 yr Thanks. Those all check. In fact I did a comparison with the original and all the changes Orbx did were NEW (added) lines, pretty much all adding new landclass numbers. Bad news! I remember those old golden FSX days when I had to check terrain.cfg after each ORBX install. P3D is so boring in this respect, not many puzzles, at least on my setup. Will probably buy this Heathrow to have some fun again... ) Cheers, Roman Heriban
March 13, 201610 yr Is ASN working on v3.2? They've updated it, good to go.. Regards,Pivoti9-10900k * 64Gb Ram * MSI RTX 4070 Ti Gaming X Trio * Steel Series Arctis Pro Wireless Headset * Win11 Home x64 * Beam ET * TM Warthog Combo, Honeycomb Alpha & Saitek Pro-Rudders
March 13, 201610 yr I'll possibly try Orbx once more at most, but it seems to have too much going on for FS health. I was going to suggest check Terrain.cfg next but sounds like you already have ... only other thing I can suggest is open up FTX Central, switch to some other region (if you have any installed), then switch back to Global region (uncheck hybrid mode before you do this). Does your FTX Central prompt you for V2.x or V3.x even though you only have v3.x? Cheers, Rob.
March 13, 201610 yr See here: http://www.avsim.com...-out/?p=3386995 And scroll down to my post. Super thanks!
March 13, 201610 yr Located here ► Computer ► Local Disk (C:) ► Users ► your user name ► AppData ► Local ► Lockheed Martin ► Prepar3D ► Shaders http://www.avsim.com/topic/479630-where-to-find-my-shaders-folder-prepar3d/ Thank you for your answer, needs to delete what exactly ?
March 13, 201610 yr Thank you for your answer, needs to delete what exactly ? The folder called "Shaders" Simmerhead - Making the virtual skies unsafe since 1987!
March 13, 201610 yr So you can delete the folder itself, rather than just all of the files inside the folder? Christopher Low AMD Ryzen 7 9800X3D CPU / 64GB DDR5-6000 RAM / 12GB Nvidia RTX 4070 Super GPU / Gigabyte X870E Aorus Elite Wifi 7 / 1+2TB Samsung Evo Plus M2 Nvme UK2000 Beta Tester
March 13, 201610 yr Commercial Member I was going to suggest check Terrain.cfg next but sounds like you already have ... only other thing I can suggest is open up FTX Central, switch to some other region (if you have any installed), then switch back to Global region (uncheck hybrid mode before you do this). Does your FTX Central prompt you for V2.x or V3.x even though you only have v3.x? I only have Global and OLC Europe installed for P3D. I can turn the hybrid mode on and off -- makes no difference. And, no, FTX Central only offers choice of FSX or P3D v3. Here's a link to some screenshots. There are three each of the same view with UK2000 and Aerosoft Heathrow's. UK2000 is correct. I also disabled both EGLLs and took an overhead of the default, after changing to a default SCENERY.CFG file with only default layers. ScreenshotsAtHeathrow.zip It looks to me like the default layout and texture is being shown as well as the Aerosoft ones. STOP PRESS IMPORTANT FIND: Whist having NO scenery layers other than default and the two Heathrows, I checked Aerosoft's Heasthrow again -- no problems with textures! So whatever is doing it is definitely to do with one or other of the layers. I thought I'd tested without all those recently added, but maybe something Orbx installs affects another layer that those which are obvious. Either that or I made a mistake whilst trying to eliminate them. So now I'll just add a few layers at a time. I have 400 additional layers, over the defaults, so I'm not doing them singly initially! ;-) Some progress towards a solution at last! Pete Win10: 22H2 19045.2728 CPU: 9900KS at 5.5GHz Memory: 32Gb at 3800 MHz. GPU: RTX 24Gb Titan 2 x 2160p projectors at 25Hz onto 200 FOV curved screen
Create an account or sign in to comment