FSDS V3.5.1 compile log

[aerogator]

Hey guys, hope someone can help.

When I compile a model using FSDSv3.5.1, if it fails to compile, I do not get a compile log showing the errors like in FSDSv3. Is there a setting that needs to be changed or is this normal and if so, how do you track down the error, especially if its a multi-LOD model?

And also, the compiler starts without letting me check any settings like: "has reflect map" etc. It seems to compile all of the LOD's without me having to add them in manually like in FSDSv3. Is this normal and does it know there is a reflective texture without me telling it?

[nickblack423]

Jake.

You need to go in and change the two files in your main FSDS folder

MakeMdlAircraftParms

MakeMdlSceneryParms

make them

xMakeMdlAircraftParms

xMakeMdlSceneryParms

This will stop MakeMDL autocompiling and cure your problem.

Nick

[Weescotty]

Noticed something esle as well with FSDS 3.5

For the reflective canopy -
As long as you have the glass material (settings as per previous posts) assigned to the part, and the bitmap has an alpha channel you don't need to check the "Has Reflective Texture" option during complie.

Seems like generally -

If the material assigned to the part has a specularity value AND the texture has an alpha it's treated as reflective.

If there is no material, or a material without specularity assigned to the part and the texture has an alpha its treated as transparent.

Big benefit -
No more transparent part sorting problems, as you don't use the Transparent option for individual parts.

[aerogator]

Thanks guys, seems to be working for one model but when I try to compile another one I get the MakeMDL dialog box just like in FSDSv3, but when I click on the LOD tab, delete the temp.x, and click 'add', I get the next dialog box showing the _temp_exterior_ files that I am used to adding but THEY ARE FOR A DIFFERENT MODEL (the model that compiled correctly).

The model that compiled correctly showed a dialog box with the _temp files already in it so all I had to do was click 'start'.

Sorry to be such a pain, but I've just started compiling using v3.5.1. and I'd really like to be able to use it.

[Weescotty]

Happened with me at first also.

Now have to manually select the LOD files also.