P3D v4 MCX attached object editor

[shez]

I saw a tutorial on dynamic lights creation in which there was an option of spot light in the drop down of the attach point editor - new. In the current MCX I am not seeing that option and only seeing light. Am I missing something?

 

[Bcars]

Use the Lights option, then in the Edit dialog there is a Type ( SPOT or POINT ) choose SPOT that results in the spotlight

 

[shez]

Thanks! Works.

 

[shez]

Another problem. I exported the Flood Light as a MDL object and when I was working on it I could see the spotlight spikes on the screen and then options in the editor.

I then reopened the MDL and I now cannot see anything like spikes and the options in the editor. See the image.

Also why is there a fx texture file being pulled from my FSX folder?

 

[Bcars]

I have noticed this same behavior. When 1st creating a new attachpoint and setting up as spotlight, it works fine. All the range, inner-outer cones, colors etc are rendered(if the importer option Replace effects by lights: true)
However once the model is saved/exported, and then is reopened ior imported, only the effect name and placement information is shown in effects editor. The EffectType, inner/outer(for spotlight, or light) colors, range, axis etc, no longer appears.
I also notice that the rendering of the light and reflection does not render unless the named fx file ( effect file) is in the same directory as the mdl ( or bgl). Would be nice if MCX searched effects folders like the textures ( the default Prepar3d\effects folder or n the case where using add-on.xml the named effects folder. This could be another parm like the texture paths ( eg effects paths)

 

[shez]

I have noticed this same behavior. When 1st creating a new attachpoint and setting up as spotlight, it works fine. All the range, inner-outer cones, colors etc are rendered(if the importer option Replace effects by lights: true)
However once the model is saved/exported, and then is reopened ior imported, only the effect name and placement information is shown in effects editor. The EffectType, inner/outer(for spotlight, or light) colors, range, axis etc, no longer appears.
I also notice that the rendering of the light and reflection does not render unless the named fx file ( effect file) is in the same directory as the mdl ( or bgl). Would be nice if MCX searched effects folders like the textures ( the default Prepar3d\effects folder or n the case where using add-on.xml the named effects folder. This could be another parm like the texture paths ( eg effects paths)

But adding to this, my fx files are in the same folder as the MDL.

 

[arno]

Hi,

There is an option in the options "replace effects by lights" which will convert the FX files back to a light attachpoint. When you set that option to true you will get all the properties of the light again on import of the object.

 

[shez]

Hi,

There is an option in the options "replace effects by lights" which will convert the FX files back to a light attachpoint. When you set that option to true you will get all the properties of the light again on import of the object.

Great stuff! Works now. Thanks Arno.

 

[Bcars]

I set that parameter to True, and while it shows some subtle glows for ground lighting, the Inner/outer dashed lines that show when you first add a new Effect still do not show up. I only see the basic attach points parameters. (fx name, parm, orientation, position) I am using the P3DV5 sdk with latest mcx.

 

[shez]

I see this.

 

[arno]

Hi,

For P3D you should see both the inner and outer cone. Or do the two cones have the same value?

When exporting to MSFS there is only one cone after import.

 

[shez]

Arno,

By changing this parameter does it have an impact in-sim? or just the MCX viewport?

 

[arno]

Hi,

When you export the model again the changed parameters are put in the new FX file that is created. And when you put that FX file in the sim you will see the changes.

 

[shez]

Hi,

So what does it mean it replaces the effect with a light object?

 

[arno]

If you alter the parameters in the editor MCX will make a new FX file on export that replaces the FX file that was made with the old parameters. If you use the default file name of the effect it will get a different name as well, since the parameters are used for the name,

 

[shez]

Hi Arno,

I am still getting the above mentioned error here. This is with the fix.

1. I build a model with the light attachment and fill in the parameters
2. I export the object, copy the fx file to effects and it works fine
3. When I try and open the MDL file again I lose the spikes on the MCX screen and the extra parameters section of the attachpoint light.

 

[arno]

Hi,

Did you set the option to replace effects by lights to true in the settings? The default value is false and it that case you will only see the effect file after import and not the individual parameters.

 

[shez]

Hi,

Did you set the option to replace effects by lights to true in the settings? The default value is false and it that case you will only see the effect file after import and not the individual parameters.

View attachment 77439

Yes I did. It appears that if the fx files are not in the model folder then it loses the visuals. For e.g. if I am working on a new file the visuals are as expected. But if I close the file and open it a day later there is that issue.

 

[arno]

Let me double check in the code, but I think only the filename is used to get the parameters back. The location of the FX file should not matter.

I assume you are not using the option to specify a custom FX filename, as in that case the parameters can't be derived anymore.

 

[shez]

Let me double check in the code, but I think only the filename is used to get the parameters back. The location of the FX file should not matter.

I assume you are not using the option to specify a custom FX filename, as in that case the parameters can't be derived anymore.

I was using a custom file name.