• 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 05 release

Status
Not open for further replies.

arno

Administrator
Staff member
FSDevConf team
Resource contributor
Messages
32,883
Country
netherlands
Here is a new version again. This time mainly some bug fixes:

  • MDL exporter now works with paths with a space
  • Fixed crashes when running for the first time due to some settings not set to default values
  • Fixed texture name problem in OpenFlight exporter
  • Some improvements in the SCASM reader so that more macros are read correctly now

I have also started implementing some new features, like night textures, but that is not fully working yet. So for that you will have to wait for the next version.
 
Last edited:
Messages
130
Country
scotland
Hi Arno

Many thanks for latest version.
Happy to report that exporter now working for me. Also now got the texturing problem sorted out in preview.

Can also advise that the .x files produced will compile with MakeMdl from FS2004 gamepack. I have an .asm and _0.asm file plus .mdl and also have been able to run the mdl file through MdlTweaker2 and apply new condition.

Thanks again

Iain
 

arno

Administrator
Staff member
FSDevConf team
Resource contributor
Messages
32,883
Country
netherlands
Thanks Iain, good to know it also works with the FS2004 MakeMDL, guess I should also write a MDL exporter for that one.
 
Messages
1,360
Country
scotland
Hi Folks

Arno -
Nice work sir.

Couple of points -
- Batch export as x file, all have the extension . (X
- Texturing, although being called correctly, displays the light maps instead.
- Wheels appear to be missing last segment.
- Some models only show half their sides, (as if they'd originally been mirrored).
- Errors indicate some commands not supported.
e.g.
Unsupported command IfVarRange
Unsupported command Dwx
Unsupported command Dbd
Unsupported command Dbx
Unsupported command IfVarAnd
Unsupported command LineColor
Unsupported command DotPt
Unsupported command Dot
Unsupported command DrawToPt
Unsupported command MoveToPt
Can supply api's if required, (please PM your email address).

Lastly, for a future version please,
for a single x export,
could the source filename be populated automatically.

HTH
ATB
Paul
 

arno

Administrator
Staff member
FSDevConf team
Resource contributor
Messages
32,883
Country
netherlands
Hi Paul,

- Batch export as x file, all have the extension . (X

Found it, stupid little bug indeed. I did only test MDL and FLT batch until now and they work fine.

- Texturing, although being called correctly, displays the light maps instead.

Are you seeing this in FS or in the preview? I did some (not yet finished) work on getting night textures working again, but did not expect it to work like this :).

- Wheels appear to be missing last segment.
- Some models only show half their sides, (as if they'd originally been mirrored).

These two are probably related to some trouble with the normals, I am still working on the last issues there. Do you see the polygons on the other (wrong) side? I'll send you a PM so that I can look at the model.

- Errors indicate some commands not supported.
e.g.
Unsupported command IfVarRange
Unsupported command Dwx
Unsupported command Dbd
Unsupported command Dbx
Unsupported command IfVarAnd
Unsupported command LineColor
Unsupported command DotPt
Unsupported command Dot
Unsupported command DrawToPt
Unsupported command MoveToPt

Most of these I already know:

Lines: will probably not be supported soon, as FSX does not know this kind of object in the MDL. Would have to convert them to polygons in some way then.

Dwx/Dbd/Dbx: these are codes to write hex BGL codes directly. They are high on my list to implement next, especially as FSDS uses them a lot (so that they could keep using an old SCASM version).

IfVarRange: conditions are not possible in the MDL format, so for the moment this command is ignored. Maybe I should hide the warning if I decide to hide them myself :).

Lastly, for a future version please,
for a single x export, could the source filename be populated automatically.

Good suggestion, wrote it down. Will probably be in next alpha :).

Thanks for this useful feedback,
 
Messages
1,360
Country
scotland
Hi Folks

Arno -
Excellent news all round.

re: Texturing
Only in preview,
as I hadn't tried in FSX yet.

Can supply texture set to match APIs if required.

re: Lines
I've maybe misunderstood, (being a non-modeler),
but thought from wiewing some older ODG platforms
that FSX already handled these.

re: IfVarRange
I'd assumed it was a conditional.

Please do not hide the warning.
Better to know there's a possible issue.
Maybe include a notice in the readme.

re: Do you see the polygons on the other (wrong) side?
I think you may have identified the issue there
will check again tomorrow.

Look forward to the next version.

Email of APIs to follow shortly.

PS
Not sure if it's my source files,
but seeing 'black borders'
from what looks like -
a ~2px vertical displacement downwards,
and 1px lateral displacement leftwards,
of all textures applied, (in preview mode).

HTH
ATB
Paul
 
Last edited:
Messages
130
Country
scotland
Hi Arno

I can advise having placed and viewed converted objects in FSX and see no problems with the texturing apart from the night lighting which we are aware you are hoping to add in a future version.
Now I have the paths set up also for textures in the preview screen they are also appearing as expected.

Iain
 

arno

Administrator
Staff member
FSDevConf team
Resource contributor
Messages
32,883
Country
netherlands
Hi Paul,

re: Texturing
Only in preview,
as I hadn't tried in FSX yet.

OK, will see if I can reproduce this problem here and debug it.

re: Lines
I've maybe misunderstood, (being a non-modeler),
but thought from wiewing some older ODG platforms
that FSX already handled these.

Yes, the engine can display them (backwards compatibility), but using the new FSX MDL files you can not define them.

re: IfVarRange
I'd assumed it was a conditional.

Please do not hide the warning.
Better to know there's a possible issue.
Maybe include a notice in the readme.

Agreed. I think I should just read them and then let the export say it can not save them. Other exports might be able to handle them, so the data should not be lost.

Email of APIs to follow shortly.

Got them, thanks.

PS
Not sure if it's my source files,
but seeing 'black borders'
from what looks like -
a ~2px vertical displacement downwards,
and 1px lateral displacement leftwards,
of all textures applied, (in preview mode).

Haven't seen that before. Will try with your APIs to see if I can reproduce this.
 

arno

Administrator
Staff member
FSDevConf team
Resource contributor
Messages
32,883
Country
netherlands
And again a new release, so I'll close this thread.
 
Status
Not open for further replies.
Top