• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

P3D v4 Transparent texture not showing in P3D V4.4

Messages
104
Country
pakistan
Hi , so i have been trying to export my Gpoly to P3D but i am getting this issue I can not see the taxi lines in p3d 4.4
-I have latest dev release of MCX.
-I have set it to translucent object in Prepar3d materials.
-I have set to default transparent.

The texture of taxi lines show perfectly how it is supposed to look but when i goto P3D it does now show the lines there but instead the lines are somehow under the asphalt or concrete base that i made even though i have set its layer higher than both Asphalt and Concrete

I have attached below SS_1 from MCX and then after export how it looks in P3d in SS_2.

Any help would be appreciated
 

Attachments

  • Screenshot_1.png
    Screenshot_1.png
    1.1 MB · Views: 419
  • Screenshot_2.png
    Screenshot_2.png
    2.6 MB · Views: 492
Try unticking 'group polygons 500m' and also 'optimise reference point location'.

I have had this issue with large area GP's and only using 'slice polygons 100m' solved it.

Also, you want to put your airport altitude in the altitude box, so MCX can make round earth calculations.
 
Try unticking 'group polygons 500m' and also 'optimise reference point location'.

I have had this issue with large area GP's and only using 'slice polygons 100m' solved it.

Also, you want to put your airport altitude in the altitude box, so MCX can make round earth calculations.
Roger I will try that and let you know
 
Try unticking 'group polygons 500m' and also 'optimise reference point location'.

I have had this issue with large area GP's and only using 'slice polygons 100m' solved it.

Also, you want to put your airport altitude in the altitude box, so MCX can make round earth calculations.
Unfortunately this doesnt work , the lines are still hidden under the whole polygon
 
So I kept investigating the issue further on, and I'm seeing a strange issue. When I use the P3D v4.4 export with the PBR materials, I originally set layers in positive and increasing upwards as per the SDK, but when I reimport the converted .bgl file back into mcx, the layers have a minus sign with them. This causes everything to hide below the base asphalt layer

For test, I converted the .x file directly to .bgl bypassing the Ground Polygon Wizard and this time everything showed up perfectly and also the layers were correct this time.

These are the layers before the export
Screenshot_19.jpg


And this is the result and the export
Screenshot_20.jpg


Hoping to hear more on this issue.
 
I'll check, only when there is no PBR material the negative layers should be used.
 
Hi,

I checked the code, but PBR materials should always get a positive layer.

Do you have a file to test maybe?
 
Thanks for the file, I have found the bug now. It will be fixed in the next development release.
 
Well, I tested with the latest version and can confirm that the issue is resolved. Thanks!
 
Back
Top