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

ModelConverterX alpha 08 release

Status
Not open for further replies.
arno

arno

Administrator
Staff member
FSDevConf team
Resource contributor
Messages
34,450
Country
netherlands
Here is a new alpha version of ModelConverterX, this new version mainly brings a lot of small improvements to the SCASM reader. Here are the main changes:

  • Improved handling of polygon normals
  • Night textures now supported (for LoadBitmap and TextureList commands)
  • Direct compilation to FS2004 MDL added (using FSX X file)
  • Transformations with rotations now work correctly
  • Default scale of an API macro is read and applied from the comment in the file
  • SCASM automatic texture mapping options supported
  • Triangulation of polygons improved, so complex shapes should now be shown correctly
  • Option added to show the vertex normals in the preview window
  • Option added to save the preview image to a JPG

My next big issue to work on now is the correct support of transparent textures. And also creating a manual for the tool, for which I already made a little start on the Wiki.

Any feedback is welcome again of course,
 
Last edited:
Hi Folks

Arno -
Cheers for the latest version.

Having problems opening several files
all of which ISTR opened previously.

All failing at DBD commands.

Will have a closer look over the next couple of days.

HTH
ATB
Paul
 
Hi Paul,

Those warnings for binary commands have been in this tool since version 1. That is still on the todo list to support as well. But for most objects this should not hinder the loading of the model too much. If you have one that really fails, please send me the source code so that I can use it as a test case for future developments.
 
Hi Folks

Arno -
Apologies,
mean't to update the last post, but been tied up with IRL matters.

DBD is the last command listed before the lockup,
but is not nescessarily the cause.

Please see your PMs.

HTH
ATB
Paul
 
Hi guys,

I found the issue, the triangulation code failed if the input polygon was not correct (for example a polygon with no area). Here is a quick fix for this issue.
 

Attachments

Illegal Characters warning / Freeze

Arno,

I get a message about 'illegal characters' with many files. Please see fmsams10 as an example.

The second one - cfs2hang - sends the program into nirvana, I have to close it with the taskmanager.

Any idea :)

Cheers,
Martin
 
Last edited:
Hi Arno

This screenshot may be the same as reported in previous message. I am getting similar type error messages on quite a few attempted imports.
Thanks for adding the night-lighting, it's working well:)

Iain
 
Last edited:
OK, I will try to reproduce it with the objects Martin attached. Hopefully I get the same errors here :).
 
Hi,

The illegal character error is caused by the quotes around the texture name. I have found and fix that in the code.

The other API seems to have a triangulation problem, I still have to debug why this polygon keeps the triangulation in an endless loop.
 
New version is available that should solve the bugs mentioned here.
 
Status
Not open for further replies.
Back
Top