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

[SmokeSystem] always on?

Messages
201
Hello!
the SmokeSystem effects are shown only if the aircraft engine/s is/are on and running.
Do someone know is there is a way to bypass this and make the smokesystem effects always visible, even with engine off?
I'm developing in P3D v4 bytheway.
Thanks a lot!!
 
Thanks!
I see, it must be hardcoded.
Did a few tests in FSX-Accell. Same problem.
The SmokeSystem vars themselves aren't affected (so with all engines Off you can still control the SmokeSystem vars On/Off) but the switched effect is suppressed.
And since nothing in an .fx file can be set making it dependant on "engines state", it must be hard-coded.

This hidden "feature" isn't illogical, given the reason why the SmokeSystem originally was implemented.
But awkward if you want to use the SmokeSystem for another function then "smoke".

Tip: try to switch the effect on/offwith a "light"switch, which isn't depending on engines-state.

Rob
 
Hi Rob, thanks for your answer!
I don't get your tip: the .fx effect is anyways in the [SmokeSystem] tag, so whatever i recall it, no matter of what switch type, it doesn't work with engines off.

Code:
<PartInfo>
        <Name>TEST_REC</Name>
        <AnimLength>100</AnimLength>
        <Animation>
            <Parameter>
                <Code>
                    (L:testrec, bool) 10 *
                </Code>
                <Lag>50</Lag>
            </Parameter>
        </Animation>
        <MouseRect>
            <Cursor>Hand</Cursor>
            <CallbackCode>(L:testrec, bool) ! (>L:testrec, bool)
            (L:testrec, flags) 0 > if{ 1 (>K:SMOKE_ON) } els { 1 (>K:SMOKE_OFF) }
            </CallbackCode>
        </MouseRect>
</PartInfo>

Get what i mean?
 
I don't understand your purpose using smoke, but I do work with smoke variable. it always work with or without engine ON.

this sample

Code:
    <PartInfo>
        <Name>osprey0514</Name>   
        <Visibility>
          <Parameter>
            <Code>(A:AVIONICS MASTER SWITCH, bool) 1 == if{ (A:SMOKE ENABLE:11, bool) }</Code>
          </Parameter>
        </Visibility>
    </PartInfo>
 
Hi Rob, thanks for your answer!
I don't get your tip: the .fx effect is anyways in the [SmokeSystem] tag, so whatever i recall it, no matter of what switch type, it doesn't work with engines off.
Get what i mean?
Yes, but I ment something else as "tip":
In the aircraft.cfg, define the .fx file not in the SmokeSystem section but in the Lights section (for an unused Light switch like Cabin, Wing, Recognition or whatever is unused).
And then in the mdl code, switch that light On/Off instead of the Smoke.
By the way, you should never use code like
Code:
  "condition"
   if{ 1 (>K:SMOKE_ON) }
   els{ 1 (>K:SMOKE_OFF) }

Because that will continuously issue either a SMokeOn or SmokeOff event at every schedule of the code ....
Instead, used code like
Code:
  "condition"
   if{ (A:SMOKE ENABLE:1,bool) ! if { 1 (>K:SMOKE_ON) } }
  els{ (A:SMOKE ENABLE:1,bool)  if{ 1 (>K:SMOKE_OFF) } }
So you only issue an event when the smoke switch actually needs to be changed.
Later:
While typing this, I noted another problem in your code, problably causing the smoke switch never to be set Off:
Code:
   (L:testrec, flags) 0 > if{ 1 (>K:SMOKE_ON) } els { 1 (>K:SMOKE_OFF) }
There is a space character between "els" and "{" , which is a syntax error ...
Rob
 
Last edited:
I don't understand your purpose using smoke, but I do work with smoke variable. it always work with or without engine ON.
this sample

Code:
    <PartInfo>
        <Name>osprey0514</Name>  
        <Visibility>
          <Parameter>
            <Code>(A:AVIONICS MASTER SWITCH, bool) 1 == if{ (A:SMOKE ENABLE:11, bool) }</Code>
          </Parameter>
        </Visibility>
    </PartInfo>
Hi Maryadi,
The problem isn't in the Smokesystem variables (they can be switched off/on OK even with engines off), but in the display of the .fx files you switch: when engines are off, they won't be displayed anymore.
To see what I mean, try this the MV22B:
Temporary disable the gauge V22RotorwashControl.xml, so the smoke.1-8 aren't controlled anymore.
Observe the V22 in spotplane (with engines ON) and type "I" to enable the Smokesystem.
Now all 4 rotorwash effects are visualised intermingled .....
Now set both engines OFF, and try again.
"I" still toggles the smokevars, but the rotorwash smokeeffects themselves disappear.... and cannot be made visible anymore untill you start the engines again.
That is: this is what I see in FSX-Accell, and this "feature" probably hasn't changed in P3D

Rob
 
oh... ok, I didn't use any fx file when using smoke variable. it for visibility and animation model. thanks Rob for clarification
 
Yep indeed, i was writing it.
I was talking about .fx effects. I know the smoke system is working, but the effects related simply does't show up with engines off.

@Rob thanks for the coding tips
yep in P3D is the same :(
 
Back
Top