kmax59

Bonjour Steffen, MCX is for ModelConverterX, with this tool you can change the material properties of a 3D model (and do many other things) but normally you should not modify Orbx files, it was just for test purposes and confirm the theory.

Hi there, As a dev I am aware of this and of course it's not just a matter of making the fix. I just wanted to get some feedback from someone who worked on this, if there could be any downside and if a fix will be looked at.

Hello there, Anyone?

Hello there, I'm surprised nobody reported this yet but an annoying issue with trees appeared with v5.3: trees edge are visible through fog when sky is directly behind trees (please see attached picture). This seems to be linked to this issue: I've been able to solve both issues by editing the material of the trees with MCX as a test and used the same parameters as default P3D trees (that were updated). The required parameters are these: Destination blend=zero Source blend=one It seems to add a bit of shimering but it's definitely better, than seeing trees that are 5km away through fog. If any developer could look at this it would be great, fixing the model is quite quick using batch convert. Thanks by advance !

Hello again, Not sure why but after many attempts, it seems to work again...

Hello there, I'm having a weird issue with Orbx central for a few days, the scenery configurators do not take effect anymore in any scenery and do not enable/disable features correctly (the setting itself shows as changed in central but the associated bgl file is not changed). Any idea?

There are recommended HDR settings to use with Envshade to prevent such results...

There's indeed no need to reply to every post, but acknowledging the issue somewhere is a good idea and it took 5 days to get a confirmation the issue was noted, but anyways, glad you are aware of the issue I've found.

They have the time and globally I think userd here are pretty patient, if you read my topic you’ll see that I’m just trying to help. What I don’t appreciate is the fact nobody from the dev team bothers reading or answering while some major flaws were discovered.

There are indeed users who do not read. But there are a lot of others who read. Some have several hdd/ssd and prefer to keep their sceneries on a separate drive, some others simply like flexibility. It’s not because you are often reinstalling from scratch that you do not read. As a dev I often reinstall P3D from scratch to test different versions of P3D, or lately because orbx central still had a bug that left a lot of indesirable files in the p3d directory, creating duplicate files with the migrated products. There are a lot of advantages of installing addons externally for some users, for some others it’s useless. That said flexibility and choice is always a good thing.

That's a solution, but only a temporary one.

You can't migrate Global base when it's installed, so it actually remains the same as FTX Central v3, thus it does not create issues. However if you start from a clean P3D install without Global base and you install it from scratch using Orbx central, you'll surely start getting issues. It's been confirmed by several users:

You're much probably right as the australian airports updates for AUv2 were released on Orbx central v4 but not on FTX Central v3

That may be why, it seems that the migration is what is creating issues