Jump to content

Recommended Posts

Posted (edited)

f5_engine_behavior_bug.miz

 

f5_engine_bug.trk

 

Edit: I realized the track attachment was INOP

 

Engine thrust, FF, ITT, nozzle are all affected by most recent minimum or maximum stabilized throttle position.

 

This issue has been present since DCS:W 1.5 and first became apparent during formation rejoin. Pulling IDLE after a MAX take-off to prevent overshoot on rejoin, then resetting Ng to match lead would yield reduced thrust vs the lead aircraft who pulled from MAX to cruise power (i.e. 90% Ng). In many circumstances, the wingman could not catch up using MIL power, while the flight lead was still set to ~90% Ng.

 

In my view of the submitted track, the engines start at either parameter, with similar NG but different FF, ITT and Nozzle Position on the left vs. right engine.

 

These photos are not from the test track, but show identical behavior at higher altitude and I believe the Dec 2018 version of DCS Open Beta.

 

IDLE power

Screen_181214_215221IDLE.png

 

Resumed cruise from IDLEScreen_181214_215237idle2cruise.png

 

MAX power

Screen_181214_215258MAX.png

 

Resumed cruise from MAX

Screen_181214_215419max2cruise.png

Edited by COLTROGUE
Posted

Wow, I'm surprised how flawed this moduel actually is!! What the hell?? :mad:

 

I was able to fully reproduce the bug. Track attached.

 

@Coltrogue: nice catch!

F-5 engines oddities.trk

Windows 10 - Intel i7 7700K 4.2 Ghz (no OC) - Asus Strix GTX 1080 8Gb - 16GB DDR4 (3000 MHz) - SSD 500GB + WD Black FZEX 1TB 6Gb/s

Posted

I sent a PM to Nineline about this, maybe they didn't see it.

Windows 10 - Intel i7 7700K 4.2 Ghz (no OC) - Asus Strix GTX 1080 8Gb - 16GB DDR4 (3000 MHz) - SSD 500GB + WD Black FZEX 1TB 6Gb/s

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...