• 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 v2 Prepar3D v2 support

Hi Arno,

Wow, P3D v2 support already, this is great! And you have a version of FXE for v2 also, can't wait to try these out. For some reason all my previous attached lighting effects do not work in v2, and the effects tool in the v2 SDK works only on the sample effect (on my machine at least). So P3D v2 support will be so helpful.

Thanks again for all your work,

Larry
 
Hi Larry,

I haven't tested FXEditor very deep yet, so if there are changes on which effect files work and which don't, that might not be fully supported yet. The changes I made now are mainly to make the GUI aware of P3D v2.
 
A first quick report Arno; I've not yet tried a model compiled using the P3D v2 option in version 2 yet (it's dinner time) but I did discover that if I open an existing FSX .bgl model with MCX and save / replace the existing file in FSX using the P3D v2 option, it is no longer visible. So maybe models compiled for P3D v2 will not be backwardly compatible. Not that I really care that much now that it looks like all the tools I use will soon be compatible with P3D v2.

And I briefly checked the P3D v2 option for FXE, and found that it displays those effects as I would hope. Why some work in the sim and some do not, I have no idea, but it may be related to the off-loading of particle and extrusion effects to the gpu in v2. Or maybe it's related to a bug I notice you had mentioned on the MCX wiki page regarding attached objects in FSX. (??) I guess it's wait and see....

Larry

[Edited to add] results so far; an export using the P3D v2 option is visible in v2 but not in v1 and not in FSX. But you probably knew that. :-) Using my tough test case model (4096 textures and a lot of transparencies) and the v2 export option, textures look substantially better in v2, more like what I see in SU when I'm making the model and using the 'nicer' setting for transparencies. Some of the transparent textures flicker however, even close up. I'll experiment with resizing the textures to 2048.
 
Last edited:
You must log in or register to reply here.
Back
Top