Hi,
I upgraded to P3D V3.3. Every airport works fine except CYYZ. The ground textures and AFCAD don`t work. All the taxi lines and runway markings are blurred out.
http://imgur.com/a/IjMFy
P3D V3.3 Texture
Re: P3D V3.3 Texture
Having the same issue. Really weird.
ROMAN78
ROMAN78
- george[flytampa]
- Site Admin
- Posts: 3868
Re: P3D V3.3 Texture
Some things to try.
Any terrain addons that could be conflicting? Try disabling them in the scenery library.
Check for a duplicate afcad for Toronto.
Move Toronto to the top of the scenery database.
Re-install Toronto.
Any terrain addons that could be conflicting? Try disabling them in the scenery library.
Check for a duplicate afcad for Toronto.
Move Toronto to the top of the scenery database.
Re-install Toronto.
Re: P3D V3.3 Texture
Hi,
Its a fresh install of P3D V3.3. Nothing installed besides Toronto, Montreal and the new Memphis from FSDT. Software from ORBX and ASN is not compatible anyway at the moment so that isn't installed. I have tried re-installing Toronto, even re-installing P3D. Still same result.
Update: Looks like something on P3D's end. Several posts on their forum about this
Its a fresh install of P3D V3.3. Nothing installed besides Toronto, Montreal and the new Memphis from FSDT. Software from ORBX and ASN is not compatible anyway at the moment so that isn't installed. I have tried re-installing Toronto, even re-installing P3D. Still same result.
Update: Looks like something on P3D's end. Several posts on their forum about this
Re: P3D V3.3 Texture
Hi,
Tried a fresh install multiple times with your suggestions. No change. All other FT sceneries are displaying fine.
ROMAN78
Tried a fresh install multiple times with your suggestions. No change. All other FT sceneries are displaying fine.
ROMAN78
Re: P3D V3.3 Texture
Good Morning,
Any possible fix? I know it's still usable just wondering if anyone found anything that helps. Thanks!!
ROMAN78
Any possible fix? I know it's still usable just wondering if anyone found anything that helps. Thanks!!
ROMAN78
- george[flytampa]
- Site Admin
- Posts: 3868
Re: P3D V3.3 Texture
Was it working in P3D V3.2 or earlier?
Re: P3D V3.3 Texture
Good Morning again,
Yes it was working perfectly..
ROMAN78
Yes it was working perfectly..
ROMAN78
Re: P3D V3.3 Texture
Hi,
yes it was working before in 2.5, 3.1 and 3.2.
yes it was working before in 2.5, 3.1 and 3.2.
- george[flytampa]
- Site Admin
- Posts: 3868
Re: P3D V3.3 Texture
Okay, I confirm its an issue with 3.3. Looking into it.
- armchair_pilot
- Posts: 13
Re: P3D V3.3 Texture
I apologize for posting this here but the issue is basically the same for a few other airports. So far I've noticed the problem in Sydney and Vienna. In Sydney the textures vanish at times during takeoff roll, in Vienna they are not present or totally blurred out. As for the other 2 airports I have (TNCM and OMDB) I haven't noticed any issues, except that for TNCM they are also a little washed out but I think that's normal. Can't exactly remember how they looked before.
Re: P3D V3.3 Texture
I can confirm I have the same thing using p3d v3.3
completely new install.
completely new install.
- firefly_80
- Posts: 12
Re: P3D V3.3 Texture
Look here:
http://www.prepar3d.com/forum/viewtopic ... 15#p136926
OK Folk's here the whys and whats all about this problem.
Beau Hollis wrote:
Exact replication of the draw order generated by the legacy dx9 rendering system is not possible in the new system. We've done our best to fix specific issues as reported, but there will eventually be cases where fixing one add-on by modifying sort orders will break other add-ons. We posted a couple years back that we were dropping official support for the fs2002 routines for this vary reason, and encourage developers to stop using tools that rely on them.
We made some major performance improvements in 3.2 which relied in part on changes to optimize some draw order sorting routines. These changes caused issues with a few add-ons which had worked in 3.1 and we addressed those issues in 3.3. We also fixed a bug in the sorting routine which made draw order non-deterministic in certain cases. We believe the sort is stable now and would prefer not to modify it again. Please keep reporting these issues, as we do appreciate the feedback, but also understand that we may not be able to investigate and respond.
As you can see fixing one issue with the now standard z-bais ordering of scenery layers has broken something in the older ASM Method. So it's a point in the evolution of P3D that breaks a lot of older addons or even new addons that are compiled in the old way. The best you can hope for is that the developers will eventually update their software to be P3D compliant.
This is nothing new to developers as I'm sure they are aware from v1 days about the transfer of compiling methods. LM have no plans to remedy this now as it will break the fix for their preferred method. Its now up to the Developers if they want to upgrade their now incompatible software.
http://www.prepar3d.com/forum/viewtopic ... 15#p136926
OK Folk's here the whys and whats all about this problem.
Beau Hollis wrote:
Exact replication of the draw order generated by the legacy dx9 rendering system is not possible in the new system. We've done our best to fix specific issues as reported, but there will eventually be cases where fixing one add-on by modifying sort orders will break other add-ons. We posted a couple years back that we were dropping official support for the fs2002 routines for this vary reason, and encourage developers to stop using tools that rely on them.
We made some major performance improvements in 3.2 which relied in part on changes to optimize some draw order sorting routines. These changes caused issues with a few add-ons which had worked in 3.1 and we addressed those issues in 3.3. We also fixed a bug in the sorting routine which made draw order non-deterministic in certain cases. We believe the sort is stable now and would prefer not to modify it again. Please keep reporting these issues, as we do appreciate the feedback, but also understand that we may not be able to investigate and respond.
As you can see fixing one issue with the now standard z-bais ordering of scenery layers has broken something in the older ASM Method. So it's a point in the evolution of P3D that breaks a lot of older addons or even new addons that are compiled in the old way. The best you can hope for is that the developers will eventually update their software to be P3D compliant.
This is nothing new to developers as I'm sure they are aware from v1 days about the transfer of compiling methods. LM have no plans to remedy this now as it will break the fix for their preferred method. Its now up to the Developers if they want to upgrade their now incompatible software.
Re: P3D V3.3 Texture
I know LM will be posting a hotfix, but I'm reverting back to 3.2 since its was the most stable with great VAS
ROMAN78
ROMAN78