Rob Ainscough

I can understand if Orbx can't justify the work effort to bring their products to "use" V6 features rather than just be "compatible" ... ROI. But if the ROI is really that bad, why not make P3D airport source files available to end users and we can do the adjustment work for them and make the products work with V6? It is frustrating that Orbx would rather just hold onto the source files ... what's the purpose behind that? With that said 6.x still has some work to do and I fear some key visual issues are not going to be address in V6.x series. The biggest being: Bloom Odd color visibility layer that doesn't blend (this visually looks horrible) Shame, because P3D V6.x has some very nice other new features, but is held back by just two major visual issues. Cheers, Rob.

It would probably make more sense to use existing MSFS products to replicate for P3D V6 since they'll already be updated with PBR materials. Slightly different workflow in 3DSMax, but not drastically different. But understand it's hard to justify from strictly financial aspect ... maybe toss us a bone for decades of service? Cheers, Rob.

What about v6.1

Didn't get time to do any video, here is a quick document that includes Orbx migration process (based on Larry's info and my testing): https://drive.google.com/file/d/147aBWl1AOQEc0PbsUwJIPclpgLlvYUQi/view?usp=sharing I included a few other .CFG and shader adjustments in the document, some familiar some new.

I'll post some video when I get a chance ... but real world work has me swamped (as usual). The latest P3D V6 build (6.0.33.30992) is very significant as it fixes a major issue with lighting the scene at all times of day/night. You'll want to use Tone Mapping also. I operate VRR and Unlimited with Vsync OFF ... very smooth. Unfortunately OBS and my video capture card can't record VRR, so I have to operate at locked 30 or locked 60Hz which isn't my smoothest experience. I don't use external limiters. Larry's method worked for me so long as one uses Library approach. Cheers, Rob.

Still working on the code, as always I have a bad habit of expanding a project scope to include other key features to help with visuals in V6. There are still pending items from LM that need to be addressed: brown tint haze line that doesn't blend over saturated bloom dawn/dusk transitions V6 has lots of potential, but these need to be addressed. Cheers, Rob.

Agree, absolutely the best and easiest way to do V5 to V6 and no replication needed. I'm actually amazed at how easy it was to get everything reference, even HiFi ASP3D6 network setup was easy. No worries Nick, all good now. Now that I have ChasePlane for V6 installed and all working correctly, it's video time.

Anyone having issues with Orbx Central connecting to servers for product downloads?

That's the planar reflections slider, see my settings images above. I use Ultra because it presents the most accurate reflection of all objects otherwise it looks weird with building reflection but no land mass reflection. It would be nice to be able to reduce the reflection detail, they seem a tad over reflective on water ... tends to be over dramatic from common real world situations where water surface aren't smooth as glass.

Will do, probably will not be this week as I'm going to be on a mini-vacation, July 13th to 16th. Cheers, Rob.

I think I'll make a desktop app, take a little longer to do, but can auto detect paths via registry settings and json config files from Orbx. Batch file is a bit primitive. That way I can also expand on my app with other 3rd party add-on migrations to V6. Most are pretty easy, but hate to have people typing in long paths manually if it can be automated. Plus I can add backup/restore option just in case something goes south. It will be "As Is" and "use at your own risk" and NOT sanctioned or supported by any 3rd party vendors.

I can provide a batch file and/or app that will do the "tweaking" for you, it's pretty simple ... it's why LM introduced the "Add-On" process going way back. Global and OpenLC work.

Here are the V5 v. V6 graphics differences: In my test, using as close as I can get to V5 setting using V6, I saw an FPS increase. FPS items to watch out for: Mesh Resolution V5 - 1m V6 - 7cm SSAO V6 only (GPU loading) Shadows V6 all shadows types are enabled Cloud Dynamic Lighting (melt that GPU especially with Vol Clouds at Ultra) Cube and Planar Reflections TAA, it's not bad, but I prefer SSAA which isn't supported now in V6. Cheers, Rob.

Yes ... couldn't do that until very recently due to bug in V6. To be honest, there needs to be another patch release to fix some issues like: Can't get white, suffering from the brown tint problem XP12 has Clouds are get blown out (too white) They clouds also changed from prior builds, seem too consistently "flat" base. I've been trying to adjust Tone Map, Saturation, etc. but I can't get rid of the brown tint. But so far most of my add-ons work Orbx and AIG and others. Videos will be coming, but probably not until next weekend.

Recommend you post graphics setting from both V6 and V5 ... V6 has a slew of additional graphic settings not present in V5 that can and will have a performance impact and it will vary based on how good of a GPU you have. l recommend checking TAA (enable) and then set MSAA to None ... I'm running 4K res so this works very well. The Auto update working well also and fixed those issues you listed today.