January 16, 201313 yr Question regarding some FlyTampa scenery. It would appear as though the ground textures of their San Diego scenery flicker when I am flying the 747. It appears to be a height related issue, as I have tested this with several aircraft, including several 747s. Allow me to show you. First test was with the Project Opensky ERJ-145. As you can see, it works fine. Next was the Project Opensky Boeing 737-800. Works fine. Getting a little bit higher off the ground with the QualityWings Boeing 757-200. A little higher with the Project Opensky Boeing 777-300ER. Higher up in the PMDG Boeing 747-400. As you can see, runway texture starts disappearing on the left side of the glareshield. Project Opensky Boeing 747-400 was worse. Any ideas? This problem also occurs in Miami. Strangely enough, I didn't have this issue with San Francisco or any other FlyTampa airport scenery that I own. I tried asking on their forums, but no response from them. Edited January 17, 201313 yr by firehawk44 Images removed. Far exceeded 400KB weight limit. Captain Kevin Air Kevin 124 heavy, wind calm, runway 4 left, cleared for take-off. Live streams of my flights here.
January 16, 201313 yr I've found some of these issues in some Virtualcol airports. I'm not sure if it's just placebo, but what if you "sink" the airport 1-2 centimeters? I mean, I reduced the airfield altitude about 0.01-0.1 ft (the lowest decrease AFCAD/ADE allows) and then I can't recall seeing ground textures flickering anymore. Hope this helps. Best regards,Luis Hernández Main rig: self built, AMD Ryzen 7 5700X3D (with SMT off and CO -50 mV), 2x16 GB DDR4-3200 RAM, Nvidia RTX 5060Ti 16GB, 256 GB M.2 SSD (OS+apps) + 2x1 TB SATA III SSD (sims) + 1 TB 7200 rpm HDD (storage), ID-Cooling SE-224-XTS air cooler, Viewsonic VX2458-MHD 1920x1080@120-144 Hz (G-sync compatible), Windows 11. Running P3D v5.4 (with v4.5 scenery objects as an additional library, just in case), FSX-SE, MSFS2020, MSFS2024 and even FS9! Lossless Scaling for all my sims. What a godsend...Mobile rig: ASUS Zenbook UM425QA (AMD Ryzen 7 5800H APU @3.2 GHz and boost disabled, 1 TB M.2 SSD, 16 GB RAM, Windows 11 Pro). Running FS9 there .VKB Gladiator NXT Premium Left + GNX THQ as primary controllers. Xbox Series X|S wireless controller as standby/mobile.
January 17, 201313 yr Author Yeah, that didn't fix the problem unfortunately. Captain Kevin Air Kevin 124 heavy, wind calm, runway 4 left, cleared for take-off. Live streams of my flights here.
January 17, 201313 yr Your screenshots are not visible any more, but one idea might be conflicting scenery? Did you have any other San Diego scenery installed before? If so, check it was really removed / deactivated properly... A few times I have noticed when there were extra sceneries installed the ground bitmaps cross over or flicker and it often has a critical altitude. Geoff
January 18, 201313 yr Author Your screenshots are not visible any more, but one idea might be conflicting scenery? Did you have any other San Diego scenery installed before? If so, check it was really removed / deactivated properly... A few times I have noticed when there were extra sceneries installed the ground bitmaps cross over or flicker and it often has a critical altitude. Geoff I don't have any other San Diego scenery other than default. Captain Kevin Air Kevin 124 heavy, wind calm, runway 4 left, cleared for take-off. Live streams of my flights here.
January 18, 201313 yr I see you have posted your question at the FlyTampa forum too and so far they have no solution for you. If you have MyTraffic, it has AFCAD's for KSAN and they might be conflicting with the FlyTampa scenery especially if MyTraffic (or any AI program) is located above FlyTampa KSAN in the Scenery Library. I recall this happening a lot in my FS9 days. I also remember installing MegaScenery SoCal in my FS9 installation and I saw this problem with the default scenery. MegaScenery finally issued a fix. Since this is happening at another FlyTampa airport, you might make sure your FS9 settings are set as recommended by FlyTampa. Play with the Texture resolution slider. I think you will have problems if all sliders are set to max. Best regards, Jim Jim Young | AVSIM Online! - Simming's Premier Resource! Member, AVSIM Board of Directors - Serving AVSIM since 2001 Submit News to AVSIMImportant other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS) I7 8086K 5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10
January 18, 201313 yr Author I see you have posted your question at the FlyTampa forum too and so far they have no solution for you. If you have MyTraffic, it has AFCAD's for KSAN and they might be conflicting with the FlyTampa scenery especially if MyTraffic (or any AI program) is located above FlyTampa KSAN in the Scenery Library. I recall this happening a lot in my FS9 days. I also remember installing MegaScenery SoCal in my FS9 installation and I saw this problem with the default scenery. MegaScenery finally issued a fix. Since this is happening at another FlyTampa airport, you might make sure your FS9 settings are set as recommended by FlyTampa. Play with the Texture resolution slider. I think you will have problems if all sliders are set to max. I do not have MyTraffic. Only AI I have is World of AI, although I've had this problem with San Diego even with AI turned off. The settings were set to recommended settings. San Diego and Miami are the only two airports I've had this happen to. I don't have this problem at Boston, Seattle, St. Maarten, or Kai Tak. Captain Kevin Air Kevin 124 heavy, wind calm, runway 4 left, cleared for take-off. Live streams of my flights here.
January 18, 201313 yr Then you have covered almost every possible avenue for fixing your problem. You'll either have to live with it or remove it and find another scenery for San Diego. To me it is surprising a fix has not been discovered as this really is an old, old program and it worked well for others running FS9. I could find no one else having this issue through a Google search. Make sure KSAN is located at the very top of your Scenery Library. That will eliminate any possibility of any other scenery or utility causing a problem. You can also delete it and install a freeware scenery program for KSAN - http://www.freewarescenery.com/fs2004.html (unless FlyTampa comes up with a fix of course). You can also download an AFCAD editor - http://www.airportdesigneditor.co.uk/ and load the KSAN AFCAD and check the elevation. You might be able to raise or lower the scenery's elevation a few feet. Best regards, Jim Jim Young | AVSIM Online! - Simming's Premier Resource! Member, AVSIM Board of Directors - Serving AVSIM since 2001 Submit News to AVSIMImportant other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS) I7 8086K 5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10
January 18, 201313 yr Author I tried lowering the elevation last night upon Luis's suggestion, but that didn't seem to do anything. I haven't tried raising it yet, I'll give that a try later when I have more time. Thanks for your help. Captain Kevin Air Kevin 124 heavy, wind calm, runway 4 left, cleared for take-off. Live streams of my flights here.
January 20, 201313 yr I'm not sure if this is related (just speculating), but can you check if all your San Diego (and Miami) texture files are all mipped? Alpha Searcher can check this; MipMap Manager can fix this if needed. Best regards,Luis Hernández Main rig: self built, AMD Ryzen 7 5700X3D (with SMT off and CO -50 mV), 2x16 GB DDR4-3200 RAM, Nvidia RTX 5060Ti 16GB, 256 GB M.2 SSD (OS+apps) + 2x1 TB SATA III SSD (sims) + 1 TB 7200 rpm HDD (storage), ID-Cooling SE-224-XTS air cooler, Viewsonic VX2458-MHD 1920x1080@120-144 Hz (G-sync compatible), Windows 11. Running P3D v5.4 (with v4.5 scenery objects as an additional library, just in case), FSX-SE, MSFS2020, MSFS2024 and even FS9! Lossless Scaling for all my sims. What a godsend...Mobile rig: ASUS Zenbook UM425QA (AMD Ryzen 7 5800H APU @3.2 GHz and boost disabled, 1 TB M.2 SSD, 16 GB RAM, Windows 11 Pro). Running FS9 there .VKB Gladiator NXT Premium Left + GNX THQ as primary controllers. Xbox Series X|S wireless controller as standby/mobile.
January 20, 201313 yr Author I'm not sure if this is related (just speculating), but can you check if all your San Diego (and Miami) texture files are all mipped? Alpha Searcher can check this; MipMap Manager can fix this if needed. Might be a while before I can check that. Events that occurred yesterday afternoon pretty much put me off flying in the simulator for a while, as I'd tried to fly earlier tonight, but wasn't able to get it together and ended up aborting the take-off. Captain Kevin Air Kevin 124 heavy, wind calm, runway 4 left, cleared for take-off. Live streams of my flights here.
Create an account or sign in to comment