Jump to content

Recommended Posts

Posted

I have assigned one of the rotary to throttle. When you ramp start the rotary don't work until I manually page up. I don't know it is a bug or it should work like that.

 

Any one have this issue plz confirm.

 

Note: I have synchronized my controls in DCS settings

Thx

Win10, Intel 3rd Gen. Core i7 3.8Ghz, 20GB ram, Nvidia Geforce 1060 6GB Opentrack (Download it from HERE), PS3 Eye, Saitek x52-pro Joystick,

DIY Rudder Pedals,

Google Cardboard with DCS World

English is not my native language

Posted

How did you sync your controls? After sync, throttle started to work in ramp start?

 

My throttle (corrector) is assigned on "slider", and still can't get it work in ramp start. I need to press PageUp (or something) to get it out from initial point, or do that by mouse.

Intel i7-14700@5.6GHz | MSI RTX4080 SuperSuprimX | Corsair V. 64GB@6400MHz. | Samsung 1TB 990 PRO SSD (Win10Homex64)
Samsung G5 32" + Samsung 18" + 2x8"TFT Displays | TM Warthog Stick w/AVA Base | VPC MongoosT-50CM3 Throttle | TM MFD Cougars | Logitech G13, G230, G510, PZ55 & Farming Sim Panel | TIR5 & M.Quest3 VR
>>MY MODS<< | Discord: Devrim#1068

Posted
How did you sync your controls? After sync, throttle started to work in ramp start?

 

My throttle (corrector) is assigned on "slider", and still can't get it work in ramp start. I need to press PageUp (or something) to get it out from initial point, or do that by mouse.

The problem is with the ramp start It don't work until manually use page up. Actually what is the point when you do manually. So I think it is a bug

Go to options and then Misc and check Synchronize Controls with HOTAS controls

 

attachment.php?attachmentid=110518&stc=1&d=1419931541

Screen_141230_142233.thumb.jpg.f7f59efb59c8c1a8cc059e34a253a137.jpg

Win10, Intel 3rd Gen. Core i7 3.8Ghz, 20GB ram, Nvidia Geforce 1060 6GB Opentrack (Download it from HERE), PS3 Eye, Saitek x52-pro Joystick,

DIY Rudder Pedals,

Google Cardboard with DCS World

English is not my native language

Posted

I have a TM warthog and have the same issue when the corrector is set to my left throttle.

 

DESCRIPTION OF BUG:

 

When doing a cold start from the ramp, the corrector twist grip WILL NOT move, regardless of what position your throttle is in, until unlocked with a mouse click or keyboard command.

 

REPRODUCTION STEPS

 

Load a mission with a cold ramp start. Attempt to adjust corrector with your throttle input. corrector will not move.

 

Click the twist grip in the cockpit and rotate it that way, or use the keyboard command, the twist grip becomes unstuck, and will from then on respond correctly to whatever throttle inputs you give it.

 

Does not seem to be limited to the X52/

Practice makes perfect.

Posted
I have a TM warthog and have the same issue when the corrector is set to my left throttle.

 

DESCRIPTION OF BUG:

 

When doing a cold start from the ramp, the corrector twist grip WILL NOT move, regardless of what position your throttle is in, until unlocked with a mouse click or keyboard command.

 

REPRODUCTION STEPS

 

Load a mission with a cold ramp start. Attempt to adjust corrector with your throttle input. corrector will not move.

 

Click the twist grip in the cockpit and rotate it that way, or use the keyboard command, the twist grip becomes unstuck, and will from then on respond correctly to whatever throttle inputs you give it.

 

Does not seem to be limited to the X52/

 

Yes your steps for reproducing this bug are correct and it should be synchronized with the HOTAS bound axis as the mission loaded.

 

I have a question. Is it called corrector or throttle? as in manual it is called throttle friction control

Win10, Intel 3rd Gen. Core i7 3.8Ghz, 20GB ram, Nvidia Geforce 1060 6GB Opentrack (Download it from HERE), PS3 Eye, Saitek x52-pro Joystick,

DIY Rudder Pedals,

Google Cardboard with DCS World

English is not my native language

Posted

I'm using the term Corrector to refer to the digital twist grip in the game, and throttle to refer to my physical throttle. The controls config screen lists it as the corrector, but I don't know if thats what a pilot would call it. I just wanted to use 2 different words to make sure it was clear which throttle I was talking about. It would be confusing if I called them both "the throttle".

Practice makes perfect.

Posted
Uhm, guys, you are aware that there is a thing called "Idle Stop" at the throttle grip? Check back at the manual if not ... ;o)

I know about this. I tried already but without any luck. Is it working with you?

Win10, Intel 3rd Gen. Core i7 3.8Ghz, 20GB ram, Nvidia Geforce 1060 6GB Opentrack (Download it from HERE), PS3 Eye, Saitek x52-pro Joystick,

DIY Rudder Pedals,

Google Cardboard with DCS World

English is not my native language

Posted

I am not sure that I understand exactly what you already tried. But perhaps this might help:

The trottle grip does not move if you use an analogue axis until it is moved past the idle stop. To move the trottle past the idle stop, you have to use the keyboard function (or map it to a button). Once the throttle ist past the idle stop, the analogue axis will work as expected. This is implemented that way so the whole range of the analogue axis is usable and no "dead space" is wasted just for the range past the idle stop.

If you want to twist the throttle back to idle, you have to use the keyboard functions again - as the analogue axis does not go past it. Therefore you need to press PGDown AND RWin+T (or the respective buttons that you have mapped). You need to press both - this is to replicate the fact that you need to apply a bit pressure so that the idle stop button "catches".

Posted (edited)

Flagrum. That is inconsistent with what the manual describes, and the idle stop button has zero effect on the problem. I just tested it now, as the idle stop was not implemented when I remember not having this issue. The Issue is NOT the idle stop, and I'll prove it.

 

1. Turn on the Controls Indicator by pressing [RCTRL + ENTER].

2. Throttle – Set for start. Position the throttle as near as possible (on decrease side) to the engine idle stop position. To do so:

a) Roll the throttle fully left (increase) (Figure 9.1) from FULL CLOSE (Figure 9.2, 1) to FULL OPEN position by pressing and holding [PgUp].

b) Roll the throttle back to the right (decrease) by pressing and holding [PgDn] until the idle stop (Figure 9.2, 2) is reached and the throttle cannot rotate further past the detent.

c) Press [RWIN + T] to engage the IDLE RELEASE switch on the collective control box.

d) Press [PgDn] to roll the throttle just right (decrease) of the idle position. The throttle will now be set as near as possible (on decrease side) to the engine idle stop position as required for engine start.

e) Press [RWIN + T] again to release the IDLE RELEASE switch on the collective control box.

Figure 9.1. Direction of rotation of the throttle

[PgUp] roll left (increase)

[PgDn] roll right (decrease)

Idle release

 

Step 2A requires rotating the corrector to full, and step 2B requires rotating the corrector back down to it's idle stop.

 

So you exercise the full range of the corrector axis in the cockpit before ever touching the idle stop release, but you can only do that by clicking on the corrector in the cockpit. You can't do that from your joystick axis. If the corrector is locked in place by design without pushing the idle stop release, why state in the manual to run it through its range of motion before pressing the idle release, and why does clicking on the corrector in the cockpit override this detent, instead of the idle release button, which does nothing?

 

It's obviously broken, and its operation is completely inconsistent with the manual. Test it yourself.

Edited by Socket7

Practice makes perfect.

Posted (edited)
I am not sure that I understand exactly what you already tried. But perhaps this might help:

The trottle grip does not move if you use an analogue axis until it is moved past the idle stop. To move the trottle past the idle stop, you have to use the keyboard function (or map it to a button). Once the throttle ist past the idle stop, the analogue axis will work as expected. This is implemented that way so the whole range of the analogue axis is usable and no "dead space" is wasted just for the range past the idle stop.

If you want to twist the throttle back to idle, you have to use the keyboard functions again - as the analogue axis does not go past it. Therefore you need to press PGDown AND RWin+T (or the respective buttons that you have mapped). You need to press both - this is to replicate the fact that you need to apply a bit pressure so that the idle stop button "catches".

I do understand what you mean but this is useless as you have to use your hands for pageup and pagedown etc. then what is the point of using joystick axis. I don't want my hands off from my HOTAS. I think only one button should be mapped with corrector is the idle stop. When it is pressed the corrector should work with HOTAS.

 

Note: Why you can move throttle with your mouse without even using idle stop

Edited by sniperwolfpk5

Win10, Intel 3rd Gen. Core i7 3.8Ghz, 20GB ram, Nvidia Geforce 1060 6GB Opentrack (Download it from HERE), PS3 Eye, Saitek x52-pro Joystick,

DIY Rudder Pedals,

Google Cardboard with DCS World

English is not my native language

Posted
I do understand what you mean but this is useless as you have to use your hands for pageup and pagedown etc. then what is the point of using joystick axis. I don't want my hands off from my HOTAS. I think only one button should be mapped with corrector is the idle stop. When it is pressed the corrector should work with HOTAS.

 

Note: Why you can move throttle with your mouse without even using idle stop

You can map the functions to buttons on your hotas. But I understand what you are saying, yes, it is a bit cumbersome. But again, the idea is that you can use the full physical range of your analogue axis for operating the (relevant) range of the throttle.

 

And you can use the mouse to move the throttle from idle to fully open in one go, yes. But that is because the mouse has no fixed range axis - you can drag the mouse or scroll the wheel forever - there is no need to restrict the range at all. But you still have to depress the idle stop button if you want to twist the throttle back to idle, even if you use the mouse.

  • Recently Browsing   0 members

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