April 4, 201610 yr Looks to me as being antennae, I can see the red and white areas. Intel(R) Core(TM) i7-10700F CPU @ 2.90GHz (8 cores) Hyper on, Evga RTX 3060 12 Gig, 32 GB ram, Windows 11, P3D v6, and MSFS 2020 and a couple of SSD's
April 22, 201610 yr Hi Guys. Something to check for you: Today i found out, that my blurries was caused by a wrong scenery library order list. I put the Open Lc over the Vectors. By coincidence i found this misfortune. I tried out all affinity masks and other tweaks like or TextureMaxLoad before. Nothing seems to fix it. The evil was a bagatelle. Blurries are at all events history in my P3D. Here is the hint: http://flightx.net/index.php?thread/80512-installation-von-ftx-global-ftx-global-vector-und-open-lc-europa/ Stefan Mühlemann
April 23, 201610 yr Paul, unfortunately no amount of deleting shaders or cfg`s or useless tweaks will fix what you see, that`s the limitation of LOD for P3dv3, its max range is set to 6.5 and cannot be increased because it will cause a string of other issues, also LM have locked it there to increase the other performance gains they made, a simple search on the LM forums will confirm this because Beau has explained several times why it`s like this, 11 nm in front is the maximum range for autogen draw.
April 23, 201610 yr They are in fact antennas, but something is messed up initially I thought it was SLI or nVidia drivers screwing up things... guess not! These shots were taken with Prepar3D v3.2 default settings. When cracking all the slides to the right [max] I was unable to reproduce the same vertical sprites which is odd. The thing is... How the world am I going to solve this... My terrain.cfg is full of addons "crap". Check pics and look at the airfield (center of the image) with antennas over taxiways parking and runway lol. Best regards, Luís SYSTEM (build date july, 2023): Case: Lian Li Lancool III | Motherboard: Asus ROG STRIX Z790-E Gaming WIFI | CPU: Intel® Core™ i9-13900K Processor @ 6.0 GHZ | RAM: 128 GB Corsair Dominator Platinum RGB @ 4800 MHZ | MVMe 1: 4 TB Crucial T700 PCIe Gen 5 | MVMe 2: 4TB WD Black SN850X PCIe Gen 4 | Cooler: Corsair iCue H150i Elite LCD XT | PSU: Corsair HX1500i | GPU: Asus ROG STRIX Gaming 4090 OC | Microsoft Windows 11 x64 Pro
April 23, 201610 yr Hi Guys. Something to check for you: Today i found out, that my blurries was caused by a wrong scenery library order list. I put the Open Lc over the Vectors. By coincidence i found this misfortune. I tried out all affinity masks and other tweaks like or TextureMaxLoad before. Nothing seems to fix it. The evil was a bagatelle. Blurries are at all events history in my P3D. Here is the hint: http://flightx.net/index.php?thread/80512-installation-von-ftx-global-ftx-global-vector-und-open-lc-europa/ What do you mean? Are you saying that vector should be on top of open LC? FTX automatically layers vector under the rest. The link you provided doesn't work. Shanan ASUS Z170 PRO, I7 6700K @ 4.85ghz (HT ON), ZOTAC AMP EXTREME 1080TI GTX (OC), 16 GB DDR4 G.SKILL TRIDENTZ RGB @ 3230MHZ CL 16-17-17-33 (OC) 4X SSDS : WIN 10 (NVME 960 EVO) + P3D + OTHER GAMES, 2X WD BLACKS RAID 0 + 1 SEAGATE BARRACUDA, CORSAIR AX860i PSU, CORSAIR 760T CASE (BLACK), 27 INCH IPS PREDATOR GSYNC 165HZ 1440p + 24 INCH IPS DELL 1080p, THRUSTMASTER HOTAS FCS THROTTLE + FCS16000M CORSAIR K95 RGB + CORSAIR M65 RGB + CORSAIR MM800 POLARIS RGB, CORSAIR H115i v2, CREATIVE GIGAWORKS 7.1 + ASUS D2X XONAR
April 23, 201610 yr What do you mean? Are you saying that vector should be on top of open LC? FTX automatically layers vector under the rest.this may help http://www.orbxsystems.com/forum/topic/113226-ftx-insertion-point-airport-multiple-layers/ I7-8700k,Corsair h1101 cooler ,Asus Strix Gaming Intel Z370 S11 motherboard, Corsair 32gb ramDD4,, gtx 1080ti Card, RM850 power supply Peter kelberg
April 23, 201610 yr What do you mean? Are you saying that vector should be on top of open LC? FTX automatically layers vector under the rest. The link you provided doesn't work. Vector should be below OpenLC, there's no doubt about that cf. Page 38 of the setting guide that you can open in FTX Central. Dominique Simming since 1981 - [email protected] GHz with 16 GB of RAM and a 1080 with 8 GB VRAM running a 27" @ 2560*1440 - Windows 10 - Warthog HOTAS - MFG pedals - MSFS Standard version with Steam
April 23, 201610 yr Vector should be below OpenLC, there's no doubt about that cf. Page 38 of the setting guide that you can open in FTX Central. Hmm then that was the case for me all along. I thought you were saying that it should be the other way around. But I didn't know scenery misconfigurations would cause blurries. Thanks I have: Addon scenery FTX global airports FTX libraries FTX global FTX openLC Europe FTX openLC base Default stuff FTX vector More default stuff Seems correct no? Shanan ASUS Z170 PRO, I7 6700K @ 4.85ghz (HT ON), ZOTAC AMP EXTREME 1080TI GTX (OC), 16 GB DDR4 G.SKILL TRIDENTZ RGB @ 3230MHZ CL 16-17-17-33 (OC) 4X SSDS : WIN 10 (NVME 960 EVO) + P3D + OTHER GAMES, 2X WD BLACKS RAID 0 + 1 SEAGATE BARRACUDA, CORSAIR AX860i PSU, CORSAIR 760T CASE (BLACK), 27 INCH IPS PREDATOR GSYNC 165HZ 1440p + 24 INCH IPS DELL 1080p, THRUSTMASTER HOTAS FCS THROTTLE + FCS16000M CORSAIR K95 RGB + CORSAIR M65 RGB + CORSAIR MM800 POLARIS RGB, CORSAIR H115i v2, CREATIVE GIGAWORKS 7.1 + ASUS D2X XONAR
April 23, 201610 yr Hmm then that was the case for me all along. I thought you were saying that it should be the other way around. But I didn't know scenery misconfigurations would cause blurries. Thanks I have: Addon scenery FTX global airports FTX libraries FTX global FTX openLC Europe FTX openLC base Default stuff FTX vector More default stuff Seems correct no? so have you fixed your problem? i have ftx global and vector which comes first? Ahmad Kalbouneh
April 23, 201610 yr It doesn't cause blurries... whatever is going on with your system/install, it wasn't the library order. Vector should be below almost everything else.
April 23, 201610 yr Vector should be below almost everything else. agree I7-8700k,Corsair h1101 cooler ,Asus Strix Gaming Intel Z370 S11 motherboard, Corsair 32gb ramDD4,, gtx 1080ti Card, RM850 power supply Peter kelberg
April 23, 201610 yr It doesn't cause blurries... whatever is going on with your system/install, it wasn't the library order. Vector should be below almost everything else. What I thought initially. Stefan had me thinking otherwise. Oh, well. Shanan ASUS Z170 PRO, I7 6700K @ 4.85ghz (HT ON), ZOTAC AMP EXTREME 1080TI GTX (OC), 16 GB DDR4 G.SKILL TRIDENTZ RGB @ 3230MHZ CL 16-17-17-33 (OC) 4X SSDS : WIN 10 (NVME 960 EVO) + P3D + OTHER GAMES, 2X WD BLACKS RAID 0 + 1 SEAGATE BARRACUDA, CORSAIR AX860i PSU, CORSAIR 760T CASE (BLACK), 27 INCH IPS PREDATOR GSYNC 165HZ 1440p + 24 INCH IPS DELL 1080p, THRUSTMASTER HOTAS FCS THROTTLE + FCS16000M CORSAIR K95 RGB + CORSAIR M65 RGB + CORSAIR MM800 POLARIS RGB, CORSAIR H115i v2, CREATIVE GIGAWORKS 7.1 + ASUS D2X XONAR
April 23, 201610 yr That has nothing to do with the "Scenery Library Configuration" which is to be found page 38 of the manual ! Anybody following your advice would mess up their scenery rendering big time. Dominique Simming since 1981 - [email protected] GHz with 16 GB of RAM and a 1080 with 8 GB VRAM running a 27" @ 2560*1440 - Windows 10 - Warthog HOTAS - MFG pedals - MSFS Standard version with Steam
April 23, 201610 yr When i look at this picture i think vector has to be first. Where did you get that picture? The second one to be exact. I think its gonna confuse a lot of people, myself included. It's the opposite from whats in the FTX manual. Shanan ASUS Z170 PRO, I7 6700K @ 4.85ghz (HT ON), ZOTAC AMP EXTREME 1080TI GTX (OC), 16 GB DDR4 G.SKILL TRIDENTZ RGB @ 3230MHZ CL 16-17-17-33 (OC) 4X SSDS : WIN 10 (NVME 960 EVO) + P3D + OTHER GAMES, 2X WD BLACKS RAID 0 + 1 SEAGATE BARRACUDA, CORSAIR AX860i PSU, CORSAIR 760T CASE (BLACK), 27 INCH IPS PREDATOR GSYNC 165HZ 1440p + 24 INCH IPS DELL 1080p, THRUSTMASTER HOTAS FCS THROTTLE + FCS16000M CORSAIR K95 RGB + CORSAIR M65 RGB + CORSAIR MM800 POLARIS RGB, CORSAIR H115i v2, CREATIVE GIGAWORKS 7.1 + ASUS D2X XONAR
Create an account or sign in to comment