Greetings,
Came across this issue today; ORBX LC et al all installed with prio on top.
Add-on airport sceneries below ORBX.
I have a 4K monitor and settings to medium.
This flickering only appears when I am in P3D; when I click the toolbar (ie. Windows Explorer) the P3d becomes stable.
Could be a load issue with textures, or graphics? Anyone have an idea please. Thank you!
P3dv5 HF flickering and texture load issues
-
- Posts: 16
- Joined: Fri Apr 29, 2022 11:58 am
Re: P3dv5 HF flickering and texture load issues
Your add-on airports should be above ORBX.
If they aren't, what is the purpose of having them?
Jorgen
If they aren't, what is the purpose of having them?
Jorgen
System: i5-12600K@4.9 GHz, ASUS ROG STRIX Z690-I motherboard, 32 GB 4800 MHz DDR5 RAM, Gainward RTX 3060 w/ 12 GB DDR6 VRAM, Windows 10 Pro.
All views and opinions expressed here are entirely my own. I am not a Lockheed-Martin employee.
All views and opinions expressed here are entirely my own. I am not a Lockheed-Martin employee.
-
- Posts: 1
- Joined: Fri May 19, 2023 4:24 am
Re: P3dv5 HF flickering and texture load issues
I don't know why we should change their positions. Normally, ORBX always take precedence at the top.JorgenSA wrote: ↑Sat Feb 18, 2023 7:16 am Your add-on airports should be above ORBX. shell shockers 2
If they aren't, what is the purpose of having them?
Jorgen
Re: P3dv5 HF flickering and texture load issues
Basically, the priorities in your scenery configuration library should be like this:
Add-on airports
Sceneries - like city sceneries
Photosceneries
Landclass
Mesh
Base
In other words, add-on airports at the very top.
Jorgen
Add-on airports
Sceneries - like city sceneries
Photosceneries
Landclass
Mesh
Base
In other words, add-on airports at the very top.
Jorgen
System: i5-12600K@4.9 GHz, ASUS ROG STRIX Z690-I motherboard, 32 GB 4800 MHz DDR5 RAM, Gainward RTX 3060 w/ 12 GB DDR6 VRAM, Windows 10 Pro.
All views and opinions expressed here are entirely my own. I am not a Lockheed-Martin employee.
All views and opinions expressed here are entirely my own. I am not a Lockheed-Martin employee.