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

P3D v4 MCX attached object editor

OK, so in that case that is the issue. The parameters are derived from the default filename, if you have that option to go from effects to light set to true.
 
OK, so in that case that is the issue. The parameters are derived from the default filename, if you have that option to go from effects to light set to true.
So if I have my custom fx name (false for autogenerated name), and leave that custom fx file in the models folder, the display should be OK every time I open again?
 
No, you will only see the light beams parameters when you use the default filenames. With custom names you will just see it as an effect instead of a light in the attached object editor.
 
No, you will only see the light beams parameters when you use the default filenames. With custom names you will just see it as an effect instead of a light in the attached object editor.
Got it. It displays because the name of the autogenerated fx file has the code which is read by MCX the next time the MDL is opened.

Very interesting though that even after I delete the fx file from the MDL folder MCX is still displaying the effect. Where is it reading the code from?
 
The name of the FX is still stored in the MDL file, so the code for generating the light object can still derive all data without needing the actual FX file.
 
Arno,

Quick question related to this. If I have already attached a lot of lights to a model and saved the MDL, and now I have to make some changes to the base MDL, how can I retrieve the light placement data from the previous MDL? If would be a nightmare otherwise to place all the lights again to a complex MDL.
 
Hi,

You could load the MDL with the light and remove everything except these lights. Then save that to a new MDL file. Then you can merge that lights MDL with your modified base MDL.
 
Hi,

You could load the MDL with the light and remove everything except these lights. Then save that to a new MDL file. Then you can merge that lights MDL with your modified base MDL.
OK so the merge would happen within MCX? Or just a placement in ADEX?
 
It would happen in MCX, I assume you want them as one model in the end
 
There is a merge object editor where you can merge different files together.
 
Back
Top