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

FS2004 aircraft mdl export

tgibson said:
The right magneto lever in the original FSX model uses a stock animation tag, it’s MCX that uses a custom tag instead.
Click to expand...
Let me check the default FSX model first then.
 
I checked the default DC-3, I see these two mouse rectangles and no custom one:
  • switch_ignition_magnetos_dc3
  • switch_ignition_magnetos1_dc3
 
This FSX model uses the same tags. It's only after conversion to FS9 that MCX creates the custom tag.
 
There is no mention of a No Smoking tag in the FS9 MakeMDL SDK. MCX would need to create its own custom tag. I use a 2D no smoking switch in my VC's, so I don't need such a tag.
 
Copy, I see what goes wrong now, let me try to fix it.
 
tgibson said:
There is no mention of a No Smoking tag in the FS9 MakeMDL SDK.
Click to expand...
I could not find it either, I am not sure if the event ID are maybe listed in another SDK.
 
arno said:
Copy, I see what goes wrong now, let me try to fix it.
Click to expand...
I have found and fixed the bug for the magneto mouse rectangle now.
 
arno said:
I could not find it either, I am not sure if the event ID are maybe listed in another SDK.
Click to expand...
I had a look in the Panel SDK, in the gauges.h file are the ID are defined. But the FS2004 version has no no smoking ID, while the FSX version has. It seems to be this one has been added with FSX only.
 
Agreed, I used a custom L: variable for that in my No Smoking gauges. No stock EventID.
 
Hi Tom,

I checked the issue with the material editor updating the wrong material you reported for the DC-3 VC. I can't reproduce it here. Can you check in the next build if you still see this issue?
 
I have tried to repeat it with the 1/4 build and could not make it happen. I had made many changes along the way and it must have been some odd (and hopefully unlikely) combination of things that caused it.
 
What's more, I have been able to make the VC cockpit windows partially transparent by first applying Set Default Transparent to the "reflection" material in the FSX model, setting the diffuse color to 50,255,255,255, and then converting to FS9.

The only anomaly is when I import the converted model back into MCX, the diffuse color of that material is again 255,255,255 and even when I set it to 50,255,255,255 the cockpit windows in the display never become transparent (even though they are transparent in FS9). I don't think MCX takes the diffuse alpha into account when displaying FS9 models? This is with the complex or simple shader activated.

I guess this makes sense since FS9 planes are converted to FSX format when imported into MCX and the diffuse alpha does not control transparency in that sim.
 
Last edited:
Test 5: FS9 CV-340 to FSX
The slow and blurred props are completely transparent, not visible at all (except their shadow).
I changed the Alpha Test Level from 100 to 1 (my new standard) and the props became visible.
Control surfaces flip back to center in one direction.
I wanted to use the FS9 night textures, so I changed all the Additive properties to MultiplyBlend - look OK.

Test 6: FS9 JBK DC-4 to FSX
Control surfaces flip back to center in one direction.

Test 7: FS9 B377 to FSX
Control surfaces flip back to center in one direction.
 
Last edited:
Hi Tom,

Thanks for reporting, I have added these two issues to my list to check.

The list has been flooded a bit after Martin and his team also started testing, so it might take a bit longer before I have the time to check this.
 
Using 1/18/24 version of MCX.

Test 1: FS9 DC-6B to FSX
All appears correct, no errors in visibility or animations.

Test 2: FS9 JBK DC-4 to FSX
The control surfaces flip back to center at one point.
 
Hi Tom,

Thanks for testing. The last build mainly had some issue fixes in the material editor, I have not made big changes to the export of the aircraft. I am about to push some changes that will help with the AI model conversion.
 
Hi Arno,
Any known issues with converting attachpoint based landing lights that would be on a gear leg no going off when the gear retracts, but do go off at the FS9 preset 10000ft?
 
Weescotty said:
Any known issues with converting attachpoint based landing lights that would be on a gear leg no going off when the gear retracts, but do go off at the FS9 preset 10000ft?
Click to expand...
The FS2004 aircraft export does not export any attachpoints with effects, MakeMDL does not seem to like it. So they are removed on conversion. Is this on a model exported with MCX?
 
You could add a visibility condition to the landing light effect. I don’t think there is a default one for gear down but you could create one in the FSX (I.e. P3D 1.4) SDK modeldef file and apply it before conversion. I have one if you need it.
 
Using 1/27 release

Test 1: FS9 DC-6B to FSX
Everything seems OK, as it was before. So this new release did not break anything for this plane.
 
You must log in or register to reply here.
Back
Top