Jump to content

Autostart Sequence Fails (NOZ POS)


Sierra99

Recommended Posts

Autostart intermittently fails.

 

Appears to be related to "NOZ POS" indication. All other engine indications appropriate.

 

Track and Photos attached.

Screen_191013_163540.thumb.png.ed6b352529bd8f30fe6f4b521db72d52.png

Screen_191013_163721.thumb.png.8d44d4894bb02f7ecaebe054102f12ee.png

Autostart Fail.trk

[sIGPIC][/sIGPIC]

Primary Computer

ASUS Z390-P, i7-9700K CPU @ 5.0Ghz, 32GB Patriot Viper Steel DDR4 @ 3200Mhz, ZOTAC GeForce 1070 Ti AMP Extreme, Samsung 970 EVO M.2 NVMe drives (1Tb & 500 Gb), Windows 10 Professional, Thrustmaster Warthog HOTAS, Thrustmaster Warthog Stick, Thrustmaster Cougar Throttle, Cougar MFDs x3, Saitek Combat Rudder Pedals and TrackIR 5.

 

-={TAC}=-DCS Server

Gigabyte GA-Z68XP-UD3, i7-3770K CPU @ 3.90GHz, 32GB G.SKILL Ripjaws DDR3 @ 1600Mhz, ZOTAC GeForce® GTX 970.

Link to comment
Share on other sites

  • ED Team

Thanks for the track Sierra99

 

I was not able to reproduce, the aircraft starts fine for me in your track until you stop the autostart.

smallCATPILOT.PNG.04bbece1b27ff1b2c193b174ec410fc0.PNG

Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status

Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, HP Reverb G2

Link to comment
Share on other sites

Thanks for the track Sierra99

 

I was not able to reproduce, the aircraft starts fine for me in your track until you stop the autostart.

 

BIGNEWY I didn't stop the autostart...it stopped itself after the "Engine Parameters Failure" message. I was getting a cup of coffee...:smilewink:

 

The only thing out of kilter seemed to be the Nozzle position indication. Gauge indicated 82%, Externally the Nozzle appeared to be full open. It did it 3-4 times in a row then seemed to be fine...then did it again. Just did an autostart and it worked fine.

 

Meh...I know things are being tuned. Just wanted to post it in case it was related to something else.

[sIGPIC][/sIGPIC]

Primary Computer

ASUS Z390-P, i7-9700K CPU @ 5.0Ghz, 32GB Patriot Viper Steel DDR4 @ 3200Mhz, ZOTAC GeForce 1070 Ti AMP Extreme, Samsung 970 EVO M.2 NVMe drives (1Tb & 500 Gb), Windows 10 Professional, Thrustmaster Warthog HOTAS, Thrustmaster Warthog Stick, Thrustmaster Cougar Throttle, Cougar MFDs x3, Saitek Combat Rudder Pedals and TrackIR 5.

 

-={TAC}=-DCS Server

Gigabyte GA-Z68XP-UD3, i7-3770K CPU @ 3.90GHz, 32GB G.SKILL Ripjaws DDR3 @ 1600Mhz, ZOTAC GeForce® GTX 970.

Link to comment
Share on other sites

  • 2 years later...

Can confirm this still occurs. This happens when the throttle axis is ALMOST at full idle, but forward enough that the nozzle position changes ever so slightly. The "Throttle must be at idle" check passes, but the other non-specific tests fail. 

For me, this was rectified by changing my Thrust axis dead zone from 13 to 14. I have it set to 13 as below that are startup/cutoff virtual buttons, and physical shutoff detents on my Virpil CM3. 

I could also get around the problem by actively pulling the throttle back against the detents during this check, but that was irritating and easy to fail. To be clear, the difference in throttle position was about 7/16384ths.

 

Link to comment
Share on other sites

  • BIGNEWY changed the title to Autostart Sequence Fails (NOZ POS)
  • ED Team

Tried to reproduce this again and I am not seeing any issue, as Masque mentions maybe the throttle position was the problem. 

thanks

smallCATPILOT.PNG.04bbece1b27ff1b2c193b174ec410fc0.PNG

Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status

Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, HP Reverb G2

Link to comment
Share on other sites

  • Recently Browsing   0 members

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