• 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.

Recent content by hek293

  1. hek293

    [MSFS] Emissive values not exported

    I think that was the best workaround-thanks as always Arno!
  2. hek293

    [MSFS] Emissive values not exported

    Yes, correct
  3. hek293

    [MSFS] Emissive values not exported

    That would be very useful ! I think there is a performance benefit for instances, especially for larger chunks, which also need curve correction. simpler workflow :)
  4. hek293

    [MSFS] Emissive values not exported

    I think we tend to use the emissive values often for MSFS, so leaving the default MCX settings of the .glTF writer to 'false' could be an idea. Btw, speaking of exporting, i also noticed the instances are being lost ? I havent checked the actual code but I judge from the size of the resulting...
  5. hek293

    [MSFS] Emissive values not exported

    Aha...wasnt aware this existed! thanks Arno
  6. hek293

    [MSFS] Emissive values not exported

    Hey Arno, I just noticed that the emissive values (RGB or emissive factor) are not exported on .gltf for some reason. Upon re-importing the altered .gltf, the emissive values are always default (255,255,255).
  7. hek293

    MCX startup hang - fixed

    *fixed by deleting old configurations
  8. hek293

    MCX startup hang - fixed

    Hey Arno, I have an issue with MCX (tested development and stable versions), which i never encountered before. When running the program, i get a brief shell ('starting ModelConverterX'), and then the MCX window starts and hangs indefinitely. From the event viewer, not much information is shown...
  9. hek293

    Unwanted glTF material property?

    Pretty sure not in this case. Unless a single object in the whole export (perhaps missed it), can mess up other objects too?
  10. hek293

    Unwanted glTF material property?

    Hi Arno, I noticed strange shading on some polygons while reading a .glTF (exported with bablyon from MSFS SDK) on MCX. When re-exported the .glTF from MCX, this exact shading issue was replicated in MSFS in-game (essentially black polygons). If the same .glTF is compiled directly (without using...
  11. hek293

    Prepar3D v4 support

    Thanks for the recent p3dv4 release Arno..done it again! eternally grateful as always
  12. hek293

    P3D v3 Flickering with ground poly

    even better! :)
  13. hek293

    P3D v3 Flickering with ground poly

    Thanks Arno, i know it's possible to give zbias a negative value; what i was thinking is if MCX would automatically assign that minus sign in front of zbias value when reading a fs2k poly, which would save some time i guess. Currently, when fs2k poly bgl files are loaded into mcx the zbias...
  14. hek293

    P3D v3 Flickering with ground poly

    Hey Arno, correct me if i m wrong but shouldn't MCX be reading the z-bias values in reverse? For example, if i load a ground poly BGL into MCX, the z-bias values are exact copies of the layer numbers which are stored in the BGL, ie 4-8-12..etc..But z-bias works the opposite way, ie those layer...
  15. hek293

    FSX Ground Poly heading

    That will depend on how your polygon is set up and exported from your 3D program. A screenshot from your 3D program, and then a screenshot from FSX would be useful.
Back
Top