Fargengru

I can confirm I am not using any third party input tools. I use a cheap "pro pedal" i got off amazon for my rudder pedals, a T16000m thrustmaster for my stick, and the accompanying thrustmaster throttle. I have as a result 3 inputs for my rudder, but my twist is broken on my joystick so that's disabled, and i don't use the rudder pedal things on my throttle (which are by default in a neutral position) so that's also disabled. I would be glad to post the track file, I found it, but it is a little long. How would I go about cutting the file so you don't have to sit through like 40 minutes of nothing? To mention to @BIGNEWYas well since you mentioned it. I also haven't been able to replicate this. This was a one time problem that appeared during this flight and since I haven't had any rudder malfunctions. It's why I think this may have been some sort of rare bug or something. In any case, if anybody would be so kind as to tell me how to cut down my track file, I'd gladly provide you with it. Edit for extra information: I do use a third party software, but the only one I use is SRS, the radio tool. So I don't think that should interfere with this. That is as it stands the only third party software I run in DCS as it stands. (unless you want to consider plane skins third party software, but even then I don't have many.)

Promised update has arrived, the video is now functional though not yet HD. Again: i apologize in advance for my profanities. But you should get a clear picture of what my problem I described was. The video is overly long but it covers all the bases, there's no input error on my end.

No, this was recorded yesterday as an afterthought, but no. It had continually yawed left. I was initially flying due west. I looked away to watch a friend flying I believe it was and when I came back I was significantly off course with extreme hard rudder. I also do not believe the rudder yaws hard left within the cockpit. The pilot's legs should show you that. I apologize if it isn't uploaded yet. The video itself is ~4 minutes of me complaining and showing the issue, whenever it finishes uploading and such I will make an update.

I was on the Persian Gulf At War server on 1/7/2022 and I found that the rudder was hard left rudder with no letting up. I am unsure of the cause of this problem as I had not done anything out of the ordinary. In the video provided I will show that I have no glitches on the part of my control scheme. I disable all inputs to the rudder in their entirety, not even keyboard rudder controls are enabled, yet it continually yaws hard left. I have not been able to repeat this problem and even a simple respawn solved the problem in my next Hornet. I am totally unsure as to what could have caused the problem but this is clearly a bug in the game as my inputs had no malfunctions on my end. Will be glad to provide any and all files you could need, to start I will provide a recording I made of the problem. I apologize in advance for my colorful language, I did not realize my microphone was working on recordings again. If anybody requires anything else do not be afraid to ask and I'll provide if able.

Hello, I shall preface this with the fact that my tacview is installed incorrectly so unfortunately I don't have a tacview of the current instance of this issue, however I have an old one. I had not made a track file as this was multiplayer and I didn't think to. But I still have recordings of it happening. The Issue: Some harpoons fired will simply climb until they kill themselves at 50,000 or higher. Current record of the two harpoons I've witnessed doing this is 66,000 feet. This all occurred on the Syria at War server on multiplayer, Syria being the map. However I should point out I have experienced this bug once prior on the Persian Gulf map as well on Persian Gulf at War, so map doesn't seem to be relevant to the bug. Process: What I did was I loaded up two harpoons on the 2 and 8 rack pylons and I flew off the carrier. Once airborne I began timing out the Harpoons on the stores page and I activated the SEA radar to find my target, which I did and locked onto successfully. I switched the Harpoons to the R/BOL mode and they successfully displayed the target information I was wanting, I set them both to fly at medium altitude with a skim setting for the terminal. Both missiles read the same information. I then launched from 60nm at a broadside stationary destroyer. Pylon 2's missile proceeded to pull up and climb to about 53,000 feet before its engine cut off, whereas pylon 8's missile flew properly at 15,000 feet for the journey and struck the target dead on. The video is unlisted on my account for you to see. I do not have any better way of providing evidence of it happening and unfortunately I had pressed the record button too late to demonstrate my own cockpit footage. However I hope that my description of what I had done should assist in figuring out the issue. DCS Harpoon Bug Video.zip.acmi