• 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 v6 Still struggling with attach points and effects

DragonflightDesign

DragonflightDesign

Resource contributor
Messages
1,236
Country
northernireland
Thanks to Tom Gibson and Arno I can now set up an attach point to run an effect but... I can't figure out how to control it from code. The effect that is called in the attach point editor appears to be permanently on in the sim (parameter = 0), but if I call the same effect from code (different position in 3D space), it turns on and off as expected.

I've decompiled the default C-130H in MCX to see how it deals with the landing lights effect (fx_landing.fx) but that didn't help.

Can someone tell me what and where I'm missing please?
 
Landing lights are a special case, which is included in the default code.
 
Thanks Tom. I also realised between then and now that the default aircraft can't tell me anything anyway - it has no modeldef file and was reading one of mine. So, my original question remains: what am I doing wrong (or what should I be doing) when trying to drive an effect on an attach point from code?
 
Perhaps you could set up a visibility condition? Perhaps even attach it to a dummy part and have the visibility condition applied to the dummy part?
 
What about attaching a Controller instead of the effect itself ?
The Controller is a powerful feature that lets you create sequences of various effects that can be triggered from one place.
Click to expand...

Just my 2 cents
Gérard
 
Fixed it but not in the way I was trying. Adding No Interpolate=1 to the emitter and Static=1 to the particle and driving the effect directly from code (no attach point) has stuck the flickering flame right where I need it. I can live with it pointing straight up instead of exiting the exhaust at ten degrees of pitch. The problem with adding pitch/bank/heading to the particle is that it maintains that pbh relative to whatever your viewpoint is. There is probably some way of dealing with this but it's not a great sticking point for this application.
 
You must log in or register to reply here.
Back
Top