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

SCASM exclude autogen

  • Thread starter Thread starter GHD
  • Start date Start date
GHD

GHD

Messages
12,244
Country
england
Is there any way to prevent SCASM models from excluding autogen?

I ask because MCX cannot read the correct textures so cannot convert to FSX models.
 
Hi,

You could try the same empty reference point trick. It might work.

What's the bug with MCX, maybe it's easy to solve.
 
It doesn't convert the textures properly. They are defined as 8.3 and MCX stops reading at the first space.

If I change the textures to .PAT or .BMP, it does convert, but the mapping is wrong.

It would be nice to have an FSX library since nothing is displayed in P3D.

Files attached.
 

Attachments

Ok, I'll try to reproduce.
 
I see what you mean. It is a very weird way to put spaces between the filename and the extension in the BGL. I doubt that FS can read this correctly. I'll see if I can improve the BGL decoder.
 
I have fixed the bug in the BGL decoder, so that the space is no longer an issue.

But MCX still can't find the textures, because a file "VOD00 .PAT" doesn't exist.
 
Sorry for the omission, files attached.

FSX does display the objects correctly using the original bgl.
 
That's interesting, so FS trims spaces at the end of the filename and doesn't treat filename and extension as one string. I can probably let MCX do the same.
 
MCX is now getting the filename and extension, but it keeps the trailing spaces in the filename so doesn't find the textures.
 
Yes, I fixed the bgl decompiler so now it's read correctly. But I still have to update the texture searching logic to trim the spaces.
 
Hi,

I have added it now, but wait till tomorrow, because in the current build a small bug has slipped in that gives a crash in some cases. I have just fixed that and in the next development release it should be OK.
 
Thanks Arno.

I have had a couple of cases today where it fails with "invalid character in name".

I did "phone home" ;)
 
I have been almost flooded with those reports. But it should be fixed in the next development release.
 
Not sure, it was reported about 10 times in my bugtracker within an hour. There's also a thread in the MCX forum.
 
You must log in or register to reply here.
Back
Top