Colmillo

No problem, I'll do

This is the update that solve the problem (in my case) Windows 11 Insider Preview 10.0.22622.290 (ni_release) Cheers

Nice!! But... since last windows 11 update Magic!! Now the problem is solved.... (until next update hahaha) Thanks for the tips

Ok, I just understood the situation. Indeed, the keybindig is not necessary, in fact I eliminated them (RShift + F and RCtrl + F eliminated), it is enough that it is associated with the accelerator action. Then the throttle goes from Stop to Idle position and vice versa. But the caging lever doesn't move, it stays in the cage. In this condition, ignition is possible, a situation that on some occasion did not allow me to start the engine (I probably did not execute the procedures properly) I thought the caging lever MUST be uncage for the Start process, as stated in the JF-17 manual (page 20), and the Chuck manual (page 86). So the position of the caging lever doesn't matter. Thanks for your time

Thanks for checking, but I don't know if I understood you correctly that the throttle doesn't move if it's not uncaged, and it does. The problem is that if it is not uncage it is not possible to start the engine. (Reason why I realized the problem) I include an image of the binding: Please see the description of the video where I indicate the steps executed and how the problem occurs: 00:05 Just RShift + F (Keyboard) 00:11 Repeated Rshift + F (Keyboard) 00:13 RCtrl + F (Keyboard) 00:15 Throttle moved from Stop to Idle (See the uncage stay caged) 00:21 Using mouse to uncage Thank you

1. I have the Orion Throttle Base II controls and the Base2 Joystick (for F-16) 2. In the DCS configuration of the JF-17 "Throttle uncage:Stop to idle" the accelerator is configured to generate the command "RShift + F" that automatically detects the JOY_BTN31 (I have also tried manually with JOY_BTN30) 3. The problem is that when I move the throttle from Stop to Idle, the throttle moves correctly but the Throttle Idle/Stop Caging Lever doesn't uncage. So I have to click on it to uncage or press RShift + F on the keyboard to make it do it. The throttle is supposed to send that command and it doesn't. It is the same principle that the F-16 uses without problems, but in the JF-17 it does not. I created a partial solution with Voiceattack by assigning the same RShift + F command to the throttle when I take it from Stop to Idle, but I think there must be something better to solve this problem. If someone has this problem and has solved it, I will be attentive to try it. Thank you

I ask this query first in this forum because probably someone who flies the Thunder and has the winwing controls has already figured out how to solve it. If I don't have an answer, I'll try the winwing forum. 1. I have the Orion Throttle Base II controls and the Base2 Joystick (for F-16) 2. In the DCS configuration of the JF-17 "Throttle uncage:Stop to idle" the accelerator is configured to generate the command "RShift + F" that automatically detects the JOY_BTN31 (I have also tried manually with JOY_BTN30) 3. The problem is that when I move the throttle from Stop to Idle, the throttle moves correctly but the Throttle Idle/Stop Caging Lever doesn't uncage. So I have to click on it to uncage or press RShift + F on the keyboard to make it do it. The throttle is supposed to send that command and it doesn't. It is the same principle that the F-16 uses without problems, but in the JF-17 it does not. I created a partial solution with Voiceattack by assigning the same RShift + F command to the throttle when I take it from Stop to Idle, but I think there must be something better to solve this problem. If someone has this problem and has solved it, I will be attentive to try it. Thank you

Thanks! I will check

Oh, found it...

Hi I saw this info (Radial angle and Speed). Is that a mod ? I'm looking on setting and I just find the over g's Thanks

Hi, I can't make it work on multiplayer, only in single player. Is that right? Thanks

Hello I remember that something similar happened to me with some buttons on the central MDF. I fixed it by changing the keyboard combination assigned to that key. for example if button U2 requires left + ctrl + 2 , I changed it to shft + 2 and then assigned control to it. I hope it helps you

Hi!! Installing the probe requires power off (engine and electricity), and I imagine that most users rearm with airplane energized. Cheers

Hi!! Any news?? The problem persist... EDITED Sorry, I did not see the "WIP"

It has happened to me three times. In all of them I have been with AG1 load, low level and have applied maximum g's. But in all of them, I was able to recover the engine with an inflight start. I have not tried the condition that you indicate.

FYI Solved with the last update. Thanks

This is new... I just tried it and it doesn't fix the problem Thanks anyway

Good day I recently acquired the Orion2 HOTAS F-16EX combo (Absolutely recommended), which has generated the problem of this topic. Before starting this query, I have searched many places how to solve this problem. I have made all the changes that have been presented to me, and I cannot find the solution. Previously, I was using the Warthog controllers and had this problem too, but changing the device manager option to allow the computer to turn off this device "sometimes" fixed the problem. But not now, the only way for windows to act correctly is by disconnecting the USB controls (from the motherboard). If anyone has found a solution, I would appreciate it. cheers Intel(R) Core(TM) i9-10900KF CPU @ 3.70GHz 3.70 GHz ROG STRIX Z490-E GAMING RAM 128 M.2*2 2T total SSD*3 2.5T total GeForce RTX 3090 Orion2 HOTAS F-16EX Saitek Pro Rudder

Tested with last update. Good job Thanks

Nice!, unfortunately is not IC

Good day everyone Since the last update I have noticed a strange behavior of the LD-10 I have tested it in several scenarios, at different heights and in 95% of the times when I launch the second missile, approximately 10 miles from the target it deviates its trajectory to stall and fall vertically. I've never seen that glitch before. I attach all the files. Thank you dcs.log LD10_BEHAVIOR.trk JF-17 TESTS-CAUCASUS.miz

Another video, with failures for clarify: 1. Before TO 2.After landing Cheers

That is the point... I did several tests, the worst: raise the landing gear on the ground, and there is no repair, there is only repair if I have flown. In the video after landing there is no damage, and the system allows repair. Thanks for the tip hahahahah, I use VR, but for the recordings I make the track in 2d.

1. Cold, I try to repair and I only receive the confirmation (Copy) 2. Hot, the same as the previous point. 3. Air/Ground transition, and in this case there is repair. I made this recording without causing failures, (I already did the test and the result is the same). As I also did the test to start up, take off and land immediately and like point 3, there is a repair. I hope I have been clear. Greetings

I discovered the problem. In this plane the repair function is activated only if you have been in flight. And the tests that I did were all COLD. Perhaps, it would be good if this were modified because if I suffer any inconvenience on my departure, the only way to solve it is by entering in a new plane. C.