-
Please see the most recent updates in the "Where did the .com name go?" thread. Posts number 16 and 17.
Texture bleed-through in scenery problems
- Thread starter Navy Chief
- Start date
Navy Chief
Senior Member
Navy Chief
Senior Member
I've never seen anything like that before Chief! I wouldn't even hazard a guess as to what might be causing that.
HOWEVER. . .after looking again. . .you can always try dumping the shaders and reloading the Sim.
Only seems to be happening with payware addon scenery; best I can tell thus far. I had tried dumping shaders a few days ago, reloading, etc... No fix. Also made sure Orbx stuff is lower on the list, because when Orbx scenery at top of list, none of my NAS sceneries show up; only stock scenery. I am perplexed. Pete
The insertion point tool in FTX Central is very important- see this-
Navy Chief
Senior Member
I haven't checked the info at the link that Penzoil listed yet, but yes, the texture problems seen so far are with payware P3DV4 scenery. NC
Are you using Tacpack? If so, try turning Tacpack off and see if the problem goes away.
Your screenshots look exactly like the problems I was having with Orbx's YBRM Broome airport, and the cause turned out to be
Tacpack. Something to do with a conflict between the way Tacpack and certain Orbx airports handle runway boundaries. The Orbx
website is down at the moment, so I'm not able to find and link to the Orbx thread about it.
Fortunately, it doesn't seem to be all Orbx airports, and the solution is not to have Tacpack on when using the effected airports. Tacpack
has a setting that will ask if you want it on or off when you start P3Dv4.
- Rob
Your screenshots look exactly like the problems I was having with Orbx's YBRM Broome airport, and the cause turned out to be
Tacpack. Something to do with a conflict between the way Tacpack and certain Orbx airports handle runway boundaries. The Orbx
website is down at the moment, so I'm not able to find and link to the Orbx thread about it.
Fortunately, it doesn't seem to be all Orbx airports, and the solution is not to have Tacpack on when using the effected airports. Tacpack
has a setting that will ask if you want it on or off when you start P3Dv4.
- Rob
Navy Chief
Senior Member
Rob,
It appears you are correct about Tacpack being the culprit. Once I turned it off, then no more texture problems. But is there a workaround? I can't use Tacpack with these sceneries installed? Not cool. NC
It appears you are correct about Tacpack being the culprit. Once I turned it off, then no more texture problems. But is there a workaround? I can't use Tacpack with these sceneries installed? Not cool. NC
no probs with orbx broome and tacpack here both are working fine
For a fact the problem with YBRM Broome did not exist with FSX and Tacpack. And I can't recall seeing the problem
with P3Dv4.1 and the 4.1 compatible version of Tacpack (but I also can't recall whether I actually visited Broome
during that time)..
Where I first noticed the problem was after I upgraded to to P3Dv4.2 and the compatible version of Tacpack v.1.5.0.3.
I've never found or read of a solution, other than disabling Tacpack when flying at the airports effected. I've tried different
settings in the Tacpack manager. And I did try changing the P3Dv4 client back to 4.1. But I didn't know how to change
Tacpack back to the earlier version.
This is the thread in the Orbx forums:
https://orbxsystems.com/forum/topic/150300-ybrm-broome-problem/
The reason for the conflict is provided in one of the sub threads listed:
The reason the DLL causes this weird texture/terrain anomaly is because VRS has it's own terrain avoidance and crash detection system built into it which is more
accurate than the sims could ever portray thus creating this effect we are seeing with the textures and terrain. When you want to fly the VRS all you have to do
when that prompt comes up is say yes and you will load the VRS as normal. If you select no to the prompt understand you will not be allowed to use any TacPack
products correctly until you shut the sim down and restart and selecting yes at the prompt screen. Hope this help some out in the future.
From the various threads, the problem also seems to have existed in P3Dv3.
- Rob
with P3Dv4.1 and the 4.1 compatible version of Tacpack (but I also can't recall whether I actually visited Broome
during that time)..
Where I first noticed the problem was after I upgraded to to P3Dv4.2 and the compatible version of Tacpack v.1.5.0.3.
I've never found or read of a solution, other than disabling Tacpack when flying at the airports effected. I've tried different
settings in the Tacpack manager. And I did try changing the P3Dv4 client back to 4.1. But I didn't know how to change
Tacpack back to the earlier version.
This is the thread in the Orbx forums:
https://orbxsystems.com/forum/topic/150300-ybrm-broome-problem/
The reason for the conflict is provided in one of the sub threads listed:
The reason the DLL causes this weird texture/terrain anomaly is because VRS has it's own terrain avoidance and crash detection system built into it which is more
accurate than the sims could ever portray thus creating this effect we are seeing with the textures and terrain. When you want to fly the VRS all you have to do
when that prompt comes up is say yes and you will load the VRS as normal. If you select no to the prompt understand you will not be allowed to use any TacPack
products correctly until you shut the sim down and restart and selecting yes at the prompt screen. Hope this help some out in the future.
From the various threads, the problem also seems to have existed in P3Dv3.
- Rob
Navy Chief
Senior Member
Many thanks for your reply, Rob. I guess I will simply deselect loading Tackpack if I plan on flying out of certain sceneries. Not a huge deal. NC
Navy Chief
Senior Member
UPDATE:
Adiemus in the forums at VRS suggested the following: Turn off the D3D Experimental Features in the Tackpack Manager. That fixed it! No more problem! NC
Adiemus in the forums at VRS suggested the following: Turn off the D3D Experimental Features in the Tackpack Manager. That fixed it! No more problem! NC