Su-33 extremely low thrust (cannot T-O/fly)

[Bourrinopathe]

Even on full afterburner, the Su-33 has a very low thrust.

It's impossible to take-off or maintain a leveled flight (with or without any weapons).

 

I noticed this issue on my system (w/ OB 1.5.0.45655) with the AI diving into the sea instead of landing on the Kuznetsov in a custom mission.

I created two test missions variants with a player-controlled Su-33: I barely reached 100 km/h on the runway and couldn't maintain a stable flight (reproduced several times).

I also checked the brakes (efficiency and keybinding) and my thrust axis commands (nothing wrong).

 

Two tracks attached (airborne + runway).

 

[bourrinopathe_system.nfo]

OB 15 Su-33 low thrust.rar

[Deano87]

Very odd...

 

I have had no problems with the Su33 in 1.5,

 

Maybe something Fubar with your install?

[Bourrinopathe]

My 1.5 beta is untouched so that's weird indeed. I'll try a repair pass and report back if it fixes that issue.

Thanks for the info!

[Stuge]

My 1.5 kept constantly crashing. Repair wouldn't fix the problem. Then I completely eradicated it from my hard drive, and made a clean install. No more crashes..

[Slazi]

I had the same problem on release of 1.5.

[DarkFire]

My 1.5 beta is untouched so that's weird indeed. I'll try a repair pass and report back if it fixes that issue.

Thanks for the info!

 

Make sure your thrust axis isn't bound to multiple devices. For some reason by default DCS thinks the trim wheels on my CH Fighterstick are extra thrust axes which causes all sorts of issues until I un-bind the wheels from the axes. Might be worth checking that your throttle is only bound to your actual throttle.

[Bourrinopathe]

FIXED!

 

Ok. Thanks to your top-notch Sukhoi engineering skills (+rep ;)) I managed to fix the issue.

 

That was a weird behavior nonetheless.

 

I checked the thrust control bindings and I was using two virtual joysticks (w/ VJoy) for another joystick (not connected) - those two virtual joy were bound to the (single) thrust command (my X55 is bound to the separate L/R thrust axis). I cleaned that up.

The thrust was normal during a first test mission, then I went back to the controls menu to clean up the whole virtual joysticks bindings as well as the Razer Orbweaver (programmable keypad) I use (for good measure).

Back to another test mission: same issue. Absolutely no other thrust axis bound at this time.

And even if the in-cockpit throttle position and instruments were correct (full AB), the thrust was wrong for both the player-controlled aircraft and the AI aircraft (both loosing speed).

 

I finally uninstalled VJoy, Joystick Curves (a response curves software I was using with my Logitech Extreme3D pro, for Elite Dangerous a while ago), and it removed the two virtual joysticks in my system and DCS World.

No issue since. I triple checked the AI aircraft and the player controlled Su-33 with custom missions.

 

I have no idea why it was only messing with the Su-33 but it seems VJoy was the issue (and why the AI couldn't accelerate despite the full AB).

(all the other aircraft I tested with the 1.5b AND the two virtual joysticks default config were fine: P-51D/TF-51D, Su-25A, Su-25T, Su-27, A-10C, MiG-15Bis, MiG-21Bis, MiG-29, F-15C, F-86F and the helos)

 

I hope this thread will help with similar issues. :joystick:

Happy flying everyone!

 

[EDIT: I also removed the Orbweaver from the devices list (Human Interface Devices) (Windows 10) to ensure it won't appear in DCS anymore.]

Edited October 16, 2015 by Bourrinopathe
dealt with wild letters flying everywhere

[DarkFire]

He he cool, glad you managed to find & fix the problem :)

[iFoxRomeo]

I had this problem too. But I don´t have VJOY or Orbweaver. So this doesn´t seem to be connected to this.

I whiped the chategory for the throttle(Joystick), altough i had no other devices connected to the throttle(game function). That solved the problem for me.

 

Fox

[serega071079]

The issue has been solved just by reinstalling the drivers for my Logitech Force 3D Pro.