I tried replying via email, but something went wrong and it got bounced back as undeliverable...
First, the proverbial "Good News" is that your landing light works perfectly! I suspect however that it's falling over dead because you are using MCX to compile the model. I have no idea, but does MCX even
parse the modeldef.xml file when it compiles a .mdl file? If not, then that's why your light isn't turning on/off. The <Visibility> conditional XML script doesn't get read and added to the compiled .mdl file.
You can easily verify if this is the case by loading your .mdl file in Notepad or Notepad++ and checking the very last entry in the file:
Code:
attachpt_landing_4 ATTO„ | i fx_landing attachpt_landing_4
I used the Prepar3D v1.4 export module and then compiled the .x and .xanim files using the Prepar3D v1.4 xtomdl.exe compiler. I tested this as a substitute for the default C172 and aside from contact points, and .fx light positions, and a totally opaque canopy glass, it looks just fine. I recompiled using the Prepar3D v2.2 xtomdl.exe compiler and tested in Prepar3D v2.2.1. It appears just as it did in FSX/A.
Here are some practices you need to correct moving forward:
1. The export module really doesn't like Material names that begin with numbers, such as 01-Default. While the exporter will add an X in front, it's a massive pain in the butt to get pestered with popups when exporting.
2. All your materials are "Standard". You truly do need to create new "FSX Materials" so that you can configure the advanced properties afforded, otherwise your massive 4096x4096 textures (rather much of an overkill for a plane this tiny!) will be wasted.
My suggestions would be to take care of the above issues, then learn to use the XtoMdl.exe compiler supplied with the Prepar3D v1.4 SDK.
It's a real shame I can't save this project back to a Max7 format, but Max2012 won't support that option. I can only 'back-port' two versions: 2010 and 2011.