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

FS2004 Custom N1 Animation??

Messages
141
Country
peru
OK, this was supposed to be the simplest thing, but no. If I use prop0_still/slow/blurred, they are linked to N2 RPM... But I want the fan to respond to N1 as it should...
using the N1 variables will only make the the fan behave like an RPM indicator...!!!
multiplying it by ABSOLUTE TIME,SECONDS makes it jerky and snap per-second... and all sorts of issues at start/stop. Anyone has a fan animation linked to N1 that works properly?
 
Unfortunately, I can't help you, but I'm sure someone else will be able to.

I'm replying because I'm quite curious as to what you're working on. Are you planning a new update for the P-180, which I've been using since it was released, or are you working on something completely new?
 
Unfortunately, I can't help you, but I'm sure someone else will be able to.

I'm replying because I'm quite curious as to what you're working on. Are you planning a new update for the P-180, which I've been using since it was released, or are you working on something completely new?

Glad you like the P-180!

This is a completely new aircraft model. A Dassault Mercure 100!
 
Wow! Something I can fly the length of my street with! Interesting choice, my experience with the Tinmouse should let me transition to this one fairly easily, as they seem quite similar.
 
So far the FDE work (with fairly advanced techniques including DATCOM, AVL and other cryptic aerodynamic predictors) revealed a pleasant flying aircraft, and the more mach tables I dropped in for the sake of detail, the smoother it got! It is an oddball aircraft:

Takeoff feels underpowered, but once the wheels are off, climbs happily at 3500 fpm!
Flaps are uber effective, full out stall at 110KIAS! (official manual data)
nice roll rate ("Le Chasseur D'Air Inter" as it was called by it spilots, must have been for a reason)
aero derivatives and proper MoI values make it feel more fluid than most aircraft. No "On Rails" feeling, but it performs nice and stable! This aircraft is a fine lady, be gentle and it responds with elegance. Get rude on the controls and it will protest all over the place.
I also programmed stall behavior to be gentle until forced too much, then, flat spins with no recovery possible!

With respect to the great TinMouse it compares! also, same engines used here... although all engine tables were re-calculated to reflect proper RPM and thrust... now you can leave your throttles safely at MCT N1 and do a max perf climb, N1/N2 will stay at proper values instead of going all over the place as most FS engines do!
 
What DATCOM tool did you use? This one?
http://www.holycows.net/datcom/
And AVL is here, right?
http://web.mit.edu/drela/Public/web/avl/


I still can't quite see what you mean with "proper N1 animation". N1 is closely linked to N2 via table 1505, so all you're ever going to see in a N1 animation is the relation between N1 and N2.
Also, N1 is just low pressure spool RPM presented in a form that's easier to read from an analog indicator.

FSX offers an animation tags for N1. Maybe you can convert them to FS9 sysntax and work with them.

Code:
<PartInfo>
  <Name>N1_0_still</Name>
  <Copy>prop_anim</Copy>
  <AnimLength>100</AnimLength>
  <Visibility>
  <Parameter>
  <Code>
  (A:ENG N1 RPM:1, percent) 6.25 &lt; if{ 1 } els{ 0 }
  </Code>
  </Parameter>
  </Visibility>
  <Animation>
  <Parameter>
  <Code>
  (A:ENG N1 RPM:1, percent) 0.01 &gt;
  if{ (A:GENERAL ENG RPM:1,degrees per second) (E:ABSOLUTE TIME, second) * 360 % 3.6 / }
  els{ 0 }
  </Code>
  </Parameter>
  </Animation>
  </PartInfo>
  <PartInfo>
  <Name>N1_0_slow</Name>
  <Copy>prop_anim</Copy>
  <AnimLength>100</AnimLength>
  <Animation>
  <Parameter>
  <Code>
  (A:GENERAL ENG RPM:1,degrees per second) (E:ABSOLUTE TIME, second) * 360 % 3.6 /
  </Code>
  </Parameter>
  </Animation>
  <Visibility>
  <Parameter>
  <Code>
  (A:ENG N1 RPM:1, percent) 6.25 &gt;
  if{
  (A:ENG N1 RPM:1, percent) 12.5 &lt; if{ 1 } els{ 0 }
  } els{ 0 }
  </Code>
  </Parameter>
  </Visibility>
  </PartInfo>
  <PartInfo>
  <Name>N1_0_blurred</Name>
  <Copy>prop_anim</Copy>
  <AnimLength>100</AnimLength>
  <Animation>
  <Parameter>
  <Code>
  (A:GENERAL ENG RPM:1,degrees per second) (E:ABSOLUTE TIME, second) * 360 % 3.6 /
  </Code>
  </Parameter>
  </Animation>
  <Visibility>
  <Parameter>
  <Code>
  (A:ENG N1 RPM:1, percent) 12.5 &gt; if{ 1 } els{ 0 }
  </Code>
  </Parameter>
  </Visibility>
  </PartInfo>
 
Hmm... I can probably FS9-ize these easily! Thanks a lot!

(Yes, that datcom+, and AVL, well, I have a special version that cannot be re-distributed...)
 
Code:
prop_anim_ratio=0.2

Enough said to adapt N2 RPM to N1 during start for the animation... should have thought of it before attempting this unfruitful animation coding... the above animation results in jerky motion... after all, visually discerning between 13500 RPM and 8800RPM at high power settings is impossible unless you have spider eyes :D (you could see the difference, but in FS5 graphics detail :p )
 
Back
Top