Automatic Low RMP F 14 A/B/D Exhaust smoke

[Nesu]

Engines_smoke_effect _for_IRIS_Pro_F14
Test version ,easy Hit button 'I' than Enjoy . Tested ! I'll do an Automatic Low RPM smoke effect in tha Future . You can
use it for Dino's F14 too .


​

Hello ,
i am ready right now with my small project Automatic Low RPM exhaust smoke effect ,what i planed in September 19th, 2009 .
I say it's a beta but u would test it .
I hope u Enjoy '


Its work fine between 20 n 40 percent of RPM automaticly ,u dont need push any button or something else .

I know ,i mean ,many off you can make better accessories or you made it already ,but i don't find after web search something like so .

If you are interesting of it post reply with your request plane and special question .I'll try to do my best for it .

in next i give an effort make it separate working engines exhaust smoke . i hope u dont need wait so long time with this small special kind off virtual experience .



Here is the link :
http://www.sim-outhouse.com/sohforum....php?catid=118

Best regards
N3su

Video in next ...
​

 

[rcbarend]

Hello ,
i am ready right now with my small project Automatic Low RPM exhaust smoke effect ,what i planed in September 19th, 2009 .
I say it's a beta but u would test it .
I hope u Enjoy '


Its work fine between 20 n 40 percent of RPM automaticly ,u dont need push any button or something else .

I know ,i mean ,many off you can make better accessories or you made it already ,but i don't find after web search something like so .

If you are interesting of it post reply with your request plane and special question .I'll try to do my best for it .

in next i give an effort make it separate working engines exhaust smoke . i hope u dont need wait so long time with this small special kind off virtual experience .



Here is the link :
http://www.sim-outhouse.com/sohforum....php?catid=118

Best regards
N3su

Video in next ...
​

Hello N3su,

Out of curiousity, I had a look at your xml file, but your code makes little sense
Like, when N1 is over 40%, you give 3 consecutive Smoke events (Off., On, Off) in one run of the gauge.
And repeat that every 55 msec, inducing the "continuous event" problem. Causing all kinds of multi-keystroke sequences to fail, multiplayer servers overflooding, etc.

Assuming that what you want is: Smokesystem ON when N1 is between 20 and 40, and OFF otherwise, use code like:

<ELEMENT>

    (A:Turb eng1 N1, percent) 20 > (A:Turb eng1 N1, percent) 40 < &&
    if{ (A:SMOKE ENABLE,bool) ! if{ (>K:SMOKE_ON) } }
    els{ (A:SMOKE ENABLE,bool) if{ (>K:SMOKE_OFF) } }

</ELEMENT>
That's all ..

I hope you understand the difference...
I.e: at each schedule of the gauge, you test:
- What the new state of the Smokesystem should be, based on N1 ..
- If it should be ON: first test if the current state is OFF; only if so, give a SMOKE_ON event.
- If it should be OFF: first test if the current state is ON; only if so, give a SMOKE_OFF event.



Regards, Rob

PS: There's a big problem with the Code tagging in this forum ...
Somehow, the code is interpreted instead of just displayed...
Like the sequence "Ampersand l t ; " is replaced with a "less-then" sign.
And "ampersand a m p ; " is replaced by a single "ampersand" character...
But I hope you get the idea....

 

[Nesu]

Hi , Rob :salute:

many thax for reply n teaching ,
my english isnt so good as many thinkin about ,so can be true .
I look for it to change ,i noticed this problem ,already .But , u were faster then me .

THX

Best regards
N3su

Hello N3su,

Out of curiousity, I had a look at your xml file, but your code makes little sense
Like, when N1 is over 40%, you give 3 consecutive Smoke events (Off., On, Off) in one run of the gauge.
And repeat that every 55 msec, inducing the "continuous event" problem. Causing all kinds of multi-keystroke sequences to fail, multiplayer servers overflooding, etc.

Assuming that what you want is: Smokesystem ON when N1 is between 20 and 40, and OFF otherwise, use code like:

<element>

    (A:Turb eng1 N1, percent) 20 > (A:Turb eng1 N1, percent) 40 < &&
    if{ (A:SMOKE ENABLE,bool) ! if{ (>K:SMOKE_ON) } }
    els{ (A:SMOKE ENABLE,bool) if{ (>K:SMOKE_OFF) } }

</element>
That's all ..

I hope you understand the difference...
I.e: at each schedule of the gauge, you test:
- What the new state of the Smokesystem should be, based on N1 ..
- If it should be ON: first test if the current state is OFF; only if so, give a SMOKE_ON event.
- If it should be OFF: first test if the current state is ON; only if so, give a SMOKE_OFF event.



Regards, Rob

PS: There's a big problem with the Code tagging in this forum ...
Somehow, the code is interpreted instead of just displayed...
Like the sequence "Ampersand l t ; " is replaced with a "less-then" sign.
And "ampersand a m p ; " is replaced by a single "ampersand" character...
But I hope you get the idea....

 

[Nesu]

update 1.01

<tbody> </tbody>

<tbody>
</tbody>

Hello ,

its an update releasd for Automatic low RPM exhaust smoke effect ;

Its work fine between 35 n 73 percent of RPM automaticly ,u dont need push any button or something else .
Some the .xml code and words are changed in .cfg's .

Best Regards
N3su

 

[Nesu]

update 1.02 releasd

Hello ,
its an update 1.02 releasd (October 18th, 2012)for Automatic low RPM exhaust smoke effect ;
Its work fine between 35 n 73 percent of RPM automaticly ,u dont need push any button or something else .
Separate working of N1 ,N2 Engines , SooN


Best Regards
N3su