Jump to content

kmax59

Members
  • Posts

    67
  • Joined

  • Last visited

Posts posted by kmax59

  1. On 1/12/2022 at 8:16 AM, Whenmaker said:

    Bonjour Maxime,

     

    i have the same problem on my end. Could you give me a deeper look what MCX is?

    I think we are more and more dependent on helping ourselves with P3D.

     

    Merci beaucoup,

     

    Steffen

    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.

    • Like 1
  2. On 1/7/2022 at 12:19 PM, John Dow said:

    At this time of year I doubt it's a priority item.  Particularly as it is something that appears to have originated in an update by LM. 

     

    Fixing problems like this is not just a matter of running the batch and then uploading the files to Orbx Central.  As is the case in any computer environment, fixes have to be tested under multiple scenarios and users, and if there are multiple fixes they all need to be combined in a patch.

     

     

    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.

    • Like 1
  3. 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 !

    2022-1-5_23-31-16-513.png

    • Like 1
  4. 9 hours ago, Ben McClintock said:

    We do read every single post. Your issues are noted. We have two options: reply to every single post, or actually fix the issues ;)

     

    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.

  5. 3 minutes ago, sim123 said:

     

    ORBX will solve , but give them some time,  I am also bit surprised that it was recognized during beta test, because it is their own product that give issues

    and not third party software. 

     

    but I am waiting that Globase Base will be the default scenery of P3D  so, texture exchange is not neccessary anymore.

     

     

    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.

    • Like 2
    • Upvote 1
  6. 2 minutes ago, sim123 said:

     

    because lots of people start things without reading or knowing what they are doing, If you make a good backup you never have to go from scratch.

    I only went from scratch when P3D changed from 3 to version 4.

     

     

     

    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.

     

    • Like 2
  7. 3 minutes ago, sim123 said:

    Global base , was updated in central V4 without any issue,

     

    this xml structure is only for new sceneries and when LC Asia and Africa will be released I am sure they have solved this issue or there will be an option 

    to install as XML or CFG. 

     

     

     

     

     

    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: 

     

    • Upvote 1
  8. 3 minutes ago, Dust2Dust said:

     

    okay but what if one of your orbx airports, regions or say Global Base or openLC needs an update or reinstall? what do you do then? cause iirc, any type of installation or update in the new orbx central 4 will force you to use the new library system weather you like it or not. correct me if i'm wrong

     

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

    • Sad 1
×
×
  • Create New...