-
There seems to be an uptick in Political comments in recent months. Those of us who are long time members of the site know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religious comments out of the forums.
If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.
Please note any post refering to a politician will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment among members. It is a poison to the community. We appreciate compliance with the rules.
The Staff of SOH
Orbx trees in Prepar3D v2. HUH?
- Thread starter OleBoy
- Start date
YoYo
SOH-CM-2023
Check this: http://www.sim-outhouse.com/sohforums/showthread.php?83655-Dhaenens-scenery . It looks like similar problem. Maybe its a good idea to put this on FTX Forum too. I have too same and use ORBX tree in FTX Global.
gman5250
Charter Member
What you are seeing are building textures being applied to trees. Bowerman has not been updated yet by the ORBX team.
The only thing ready for P3D V2 is FTX Global Base 1.1. The rest of the regions and airports are being updated and the new installers are being created for the V2 application. At this time the P3D 1 Migrator tool does not work with V2, but the new Migrator Tool is on the top of the priorities list.
Here's a direct link to the Master List page at ORBX. This will be updated as the updates are completed.
http://www.orbxsystems.com/forum/topic/68566-master-list-of-all-p3d2-ready-orbx-products/
The ORBX team are working hard behind the scenes to make the V2 integration happen. Keep checking at the update page periodically.
The only thing ready for P3D V2 is FTX Global Base 1.1. The rest of the regions and airports are being updated and the new installers are being created for the V2 application. At this time the P3D 1 Migrator tool does not work with V2, but the new Migrator Tool is on the top of the priorities list.
Here's a direct link to the Master List page at ORBX. This will be updated as the updates are completed.
http://www.orbxsystems.com/forum/topic/68566-master-list-of-all-p3d2-ready-orbx-products/
The ORBX team are working hard behind the scenes to make the V2 integration happen. Keep checking at the update page periodically.
Last edited:
Crusader
SOH-CM-2022
Looks Like a FTX Global 1.2 in near future
Happen to come across this today at the ORBX Forums : http://www.orbxsystems.com/forum/to...e-issue-with-p3dv2-landclass-with-ftx-global/
I too was experiencing some very weird textures (especially in Hawaii), also around the KLHQ(Lancaster) and KCMH(Columbus) were large areas of bare ground . I still have P3D 1.4 loaded and when I compared the same area(with FTX Global 1.0) they were all filled in with no other structural problems(trees) but P3D 2.0 and FTX Global 1.1 had many . Hopefully the upcoming FTX Global 1.2 update will cure at least some of the textural bugs some of us ORBX users are experiencing in P3D 2.0 . No doubt in my mind most of the 2.0 problems with get ironed out with LM , ORBX and other developers in time .
Rich
Happen to come across this today at the ORBX Forums : http://www.orbxsystems.com/forum/to...e-issue-with-p3dv2-landclass-with-ftx-global/
I too was experiencing some very weird textures (especially in Hawaii), also around the KLHQ(Lancaster) and KCMH(Columbus) were large areas of bare ground . I still have P3D 1.4 loaded and when I compared the same area(with FTX Global 1.0) they were all filled in with no other structural problems(trees) but P3D 2.0 and FTX Global 1.1 had many . Hopefully the upcoming FTX Global 1.2 update will cure at least some of the textural bugs some of us ORBX users are experiencing in P3D 2.0 . No doubt in my mind most of the 2.0 problems with get ironed out with LM , ORBX and other developers in time .
Rich
Daube
SOH-CM-2025
Some simmers reported that sometimes, when autogen textures don't load well like this, a workaround is to jump into the graphic settings of the game to modify the maximum texture resolution (the one where you can choose between 1024, 2048 and 4096). Set it to any different value than what you currently have, and confirm. That solves the bad texture loading for a lot of people. Then you can revert to your original setting.
Thanks everyone for the attempted resolutions. The issue with the trees is just one of the bugs I'm seeing. As for any temporary fix, I tried them all. And beyond all I've read elsewhere or what's been mentioned here. I went to the extent of turning all my sliders down to minimums, and turning off every feature I could while trying to find the culprit. Nothing helps.
Back to v1.4 for the time being. I'll be watching for an update from the sidelines.
Back to v1.4 for the time being. I'll be watching for an update from the sidelines.
Last edited:
Navy Chief
Senior Member
will any of the freeware Orbx airports work with V2?
gman5250
Charter Member
I've tried ORBX CBB7 but most objects don't display properlysame for CEJ4
ORBX has established a priority list for resolving P3D V2 display issues on the P3D support forum.
http://www.orbxsystems.com/forum/topic/68566-master-list-of-all-p3d2-ready-orbx-products/
First is Global, then regions and then airports. Tipella won't display correctly without PNW installed. None of the regions have re-approved for P3D V2 yet, so you won't have much luck with regions or individual airports.
From what I am seeing, the anomaly is a result of the autogen GUID assignments. I can hand annotate (IS3) a tree grouping and it will display correctly, but if I assign the same tree grouping in Annotator I'll the GUID address may call up a building texture on a tree. Building textures don't have an alpha transparency channel embedded, so the tree will display this solid texture.
This is a relatively straightforward issue to resolve, but due to the size of the autogen libraries it will be a chore to hunt down the culprit or culprits. Once this is sorted out the autogen libraries will be updated and the fix should work globally in all regions and airports. We're talking about two massively complex platforms in P3D V2 and ORBX so the potential for conflict is very high.
IMHO: There are a lot of links and fixes out there that may or may not work....I've tested quite a few of them and ended up re-installing P3D V2 three times as a result. Personally I'd wait for the various developers to certify their products and use the approved revised software to avoid any problems.
I've been flying photoreal in P3D V2 with default autogen with no problem. The ORBX regions and airports will be coming on line as they are resolved.
This is one magnificent simulator. Hang in there...the wait will be worth it.
P3D V2 w/default autogen and hand placed vegetation & scenery objects. Note the lighting on my hanger and DAK.
DAK cockpit with P3D V2 shadowing. High def PR terrain with hand annotated autogen.
Last edited:
Yes you are right, Oleboy.
The more I look the more I see. Autogen is a problem.
If I could get rid of the "hand" textures (I get a photo of someone's hands instead of a tree or something) it would be a great start but there will be more to go after that.
I am staying with P3D on the basis that I have utterly ravaged my FSX in order to install to P3D so have no choice!
gman5250
Charter Member
Chief, the freeware airports are dependent on their regions and the ORBX libs to display correctly. The only thing approved by ORBX at this hour is FTX Global which has been revised with a new installer.
The beta team worked with LM right up till the launch, but it appears that something in the LM code was tweaked at the last minute that caused the ORBX display problems.
It will all get straightened out and all of the regions and airports will be updated. Same for the freeware.
I got my trees back
Hey everyone.
I've been doing some reading on the LM site and tinkering with settings in Prepar3D v2, and on my PC. I got the trees to display as they should, with almost all the sliders maxed out.
I turned Tessalation all the way down.
It seems that P3Dv2 needs to have Windows "Aero" turned on. This removes the bug in the menus lagging. Once I turned on Aero and went back in P3D, I went immediately to the "texture" sizes and turned it down to 1024x1024 and went back in the sim. The trees were there. And surprisingly, the 1024 size textures looked real good. All the buildings, AI aircraft, everything looked nice. Then I went back to the texture sizes and bumped them up to 2048 and tested. Everything was still as it should be, and still looking good. I maxed my out to 4096 and everything is displaying correctly.
From that point I started cranking things up. Almost every setting is far right and it looks GREAT!
Try it.
Right-Click/View Image
If you need help finding where to change the Aero settings, go here for a bit of reading. http://www.mydigitallife.info/how-to-turn-on-and-enable-aero-in-windows-7-enable-aero-peek/
Hey everyone.
I've been doing some reading on the LM site and tinkering with settings in Prepar3D v2, and on my PC. I got the trees to display as they should, with almost all the sliders maxed out.
I turned Tessalation all the way down.
It seems that P3Dv2 needs to have Windows "Aero" turned on. This removes the bug in the menus lagging. Once I turned on Aero and went back in P3D, I went immediately to the "texture" sizes and turned it down to 1024x1024 and went back in the sim. The trees were there. And surprisingly, the 1024 size textures looked real good. All the buildings, AI aircraft, everything looked nice. Then I went back to the texture sizes and bumped them up to 2048 and tested. Everything was still as it should be, and still looking good. I maxed my out to 4096 and everything is displaying correctly.
From that point I started cranking things up. Almost every setting is far right and it looks GREAT!
Try it.
Right-Click/View Image
If you need help finding where to change the Aero settings, go here for a bit of reading. http://www.mydigitallife.info/how-to-turn-on-and-enable-aero-in-windows-7-enable-aero-peek/
Last edited:
YoYo
SOH-CM-2023
For P3Dv2 Aero must me turned on all the time but it isnt a solution. People & me have it too same with Aero On.
If You will have symptoms like this - take settings - change resolution to 512 pxt, back to sim - will be ok, next change resoluttion for 1024 or more again.
Its a problem of textures of trees.
If You will have symptoms like this - take settings - change resolution to 512 pxt, back to sim - will be ok, next change resoluttion for 1024 or more again.
Its a problem of textures of trees.
BTW Yoyo, I watched your Hughes racer video on Youtube recently again.
Fantastic job man, best youtube video for FSX ever!
gman5250
Charter Member
I did some follow up on the Aero fix.
Aero is one element that needs to be running, but does not completely resolve the autogen display issue.
After checking Aero "on" the texture resolution fix may provide a correct display for the current session. ORBX is recommending going to 512 then back to higher resolution. This may give you working trees in one session. Looks like the best thing at this time is to create a saved flight at 512 resolution and spawn into your questionable areas in that setup, then change resolution. Bottom line is that the new installers have to be created for each region and airport. Until that happens there appears to be no absolute fix.
Global is stable with a few vector lighting issues. Expect to see missing vector street lights and some other vector possible vector related anomalies. The ORBX site has a P3D v2 support page that can keep you up to date.
Aero is one element that needs to be running, but does not completely resolve the autogen display issue.
After checking Aero "on" the texture resolution fix may provide a correct display for the current session. ORBX is recommending going to 512 then back to higher resolution. This may give you working trees in one session. Looks like the best thing at this time is to create a saved flight at 512 resolution and spawn into your questionable areas in that setup, then change resolution. Bottom line is that the new installers have to be created for each region and airport. Until that happens there appears to be no absolute fix.
Global is stable with a few vector lighting issues. Expect to see missing vector street lights and some other vector possible vector related anomalies. The ORBX site has a P3D v2 support page that can keep you up to date.