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

Insert a precise execution delay in XML code

Assuming the N1 / N2 meters aren't crossed by mistake: in the Catapult gauge code, replace (A:ENG1 N1 RPM,percent) by (A:TURB ENG1 N1,percent) ... Or more in line with current FSX syntax: (A:TURB ENG N1:1,percent).
That probably works more accurate for turbine engines.

Rob
 
Keep in mind that N1 is read directly from the FDE engine, but aircraft instruments may be coded to display other figures to make up for any deficiencies in the engine simulation.
 
rcbarend said:
Assuming the N1 / N2 meters aren't crossed by mistake: in the Catapult gauge code, replace (A:ENG1 N1 RPM,percent) by (A:TURB ENG1 N1,percent) ... Or more in line with current FSX syntax: (A:TURB ENG N1:1,percent).
That probably works more accurate for turbine engines.

Rob
Click to expand...

Rob, Bjoern,
Thanks for your help with this. In a debugging gauge i use I created L:vars for ea of the below to monitor N1 and N2

(A:ENG1 N1 RPM,percent)
(A:TURB ENG1 N1,percent)
(A:TURB ENG N1:1,percent)
(A:TURB ENG CORRECTED N1:1,percent)

and

(A:ENG1 N2 RPM,percent)
(A:TURB ENG1 N2,percent)
(A:TURB ENG N2:1,percent)
(A:TURB ENG CORRECTED N1:1,percent)

and got this
Eng_Lvars.jpg


there seems to be some wires crossed some place.

I left a note for Mike over at Lotus Sims but that site is pretty much a ghost town these days. In the mean tiime, since at the end of the day the culmination of the work I'm doing is suppose to end up being a custom panel/HUD that i can use in several of my aircraft with minimal alteration, i created L:vars to hold the proper N1 and N2 values and added them to a Aircraft specific "ini" gauge that i use to hold L:vars that are used across all gauges in my panel. I then modded the above code to use my L:Eng1_N1 for it's launch trigger.

Thanks again for you time.

Joel

BTW Rob, I yesterday got my email returned as undeliverable, I had apparently typed in "planet.net" instead of "planet.nl", my bad, force of habbit.
 
I never heard back from Mike at Lotus Sims but I did a through search of the forum there and found a discussion of some engine parameters In the L-39 and saw this quote from Mike ...
"Also N1 values in code are read as N2 on the gauge in the plane, and vice versa. Don't ask, it's a long story."
So.... I think it's that way in the aircraft and I'll just have to live with the work around above. it all works and the sound is playing as desired so I'm moving on to the next thing on the list. Thanks All

Joel
 
Joel,
Your data tells me the airplane turbofan engine is idling at close to sea level. This is because the N1/2 values are close to the Corrected to ISA Sea level values CN1/CN2.
Table 1502 must have an entry for CN1 of 32.49% when CN2 is at 56.5% or if those specific values are not used directly then that is what is obtained through linear interpolation.
Which value is gauged is up to the designer. Typically Thrust is related to N1, engine condition is more a N2 thing.
Roy
 
jdhughen said:
I never heard back from Mike at Lotus Sims but I did a through search of the forum there and found a discussion of some engine parameters In the L-39 and saw this quote from Mike ...
"Also N1 values in code are read as N2 on the gauge in the plane, and vice versa. Don't ask, it's a long story."
So.... I think it's that way in the aircraft and I'll just have to live with the work around above. it all works and the sound is playing as desired so I'm moving on to the next thing on the list. Thanks All

Joel
Click to expand...
That clears it up then ...
Not sure if you want any other improvements for the catapult launch sound, but I can think of two things:

- Play a different sound (or use a different volume) depending on the view you are in (Spot or VC). Very easy, since Dougs sound gauge contains a view-status Lvar.

- Make the sound duration depending on the actual travel duration of the catapult shuttle.
This duration isn't fixed (usually between appr. 2 and 4 sec), and depends on desired aircraft airspeed at the end of the shuttle range.
IRL the steam pressure is calculated for this, based on desired airspeed (depending on aircraft type, actual weight, speed of the carrier and longitudinal windspeed).
This is already calculated in the gauge, but isn't used yet for the sound duration.
One way of doing that: when the shuttle is at the end of it's range (which is a fixed distance), fade out the sound (== reduce volume to 0) quickly.

Depending on the realisme you like to achieve ... LoL

Cheers, Rob
 
Roy Holmes said:
Joel,
Your data tells me the airplane turbofan engine is idling at close to sea level.
Roy
Click to expand...

Roy,
Thanks for the info. I guess parked on a carrier deck is close to sea level. I didn't know how "corrected" was connected to regular N1-2 values. So would using the "Corrected" value be the best to display in an eng gauge ?

Joel
 
FYI All,

I did get a response tonight from Mike at Lotus Sims and the values are indeed switched....

RE: N1 and N2 values switched ?? Hi Joel. Yes the N1 and N2 values are switched. The real L-39 runs a higher N2 than N1 rpm (If I recall correctly, it's been awhile!) but it wasn't possible to set that up in the .AIR file. Engine wouldn't respond properly no matter how much I messed with the values, so I just ended up switching the visual needles so that the image matched reality... I think.;)
Click to expand...

So Roy does that go along with what you were talking about ?
Bjoern, I noticed tonight that you did worked on a version of the L-39, did you run into that same issue ?

Joel
 
Borked the flight dynamics on mine trying to get it in line with the real specs and so far did not find the motivation to go on.
 
You must log in or register to reply here.
Back
Top