045

I can confirm that the throttle potentiometer in the digikey link DOES work. I have just replaced that part in my TWCS. The digikey pot has a 243 degree range so you will need to adjust the x saturation and deadzone for throttle axes within DCS itself. Thanks for posting this. It has saved me close to $100 so far.

This is completely independent of the wind, which has always been relatively minor. As I said the flight path marker and pitch ladder appear latched onto the original, incorrect heading that the jet had. I also said it only occurs after doing an In-Flight Alignment. If I could attach a track I do not think you would think this is correct behaviour. If you turn your aircarft enough, the pitch ladder and marker will be completely out of view. I should have mentioned that before.

I am unable to attach a track yet as they're all too large, but maybe someone else has encountered this as well. This has happened to my brother and I both now. We first noticed when trying to keep combat spread we noticed my heading was wrong. We then flew a close trail so I could try an In-Flight Alignment, entering the correct heading. Once the process was complete, my pitch ladder rotated off to the side, almost as if it was facing the original heading that my jet incorrectly reported. We have noted that this bug also occurs with the bug already reported concerning gross waypoint distance errors. When it occurred for me we hadn't noted my incorrect heading tape until well into our flight. When it happened for my brother, we noted his heading after INS alignment was wrong right from the ramp start. Multiple attempts at realignment, using both stored heading and normal alignment, and ensuring we weren't rearming or moving during the process failed to correct the heading. He then entered the correct heading during alignment, which lead to the pitch ladder problem. I will attach a track file if we can reproduce in one that isn't too large. So far it has only occurred on the Hoggit Georgia at War server. Sorry that this is sort of a double error post, but without an appropriate track I can't narrow it down further. Hopefully someone has a track they can contribute.

Is that SA-11 site inside of static object revetments or are the revetments part of the terrain?

Cannot move a point "Fire on point" and the similar points until you select the task in the panel of tasks - fixed This is mentioned in the DCS 2.5.6.49798 change log. I am not certain if this refers to the issue I demonstrated in my original post. Just in case it does, I wanted to state that I am still able to reproduce the problem every time. Again, Triggered Action Fire at Point is immovable (instead moves the point's vehicle group) until an Advanced Waypoint Action Fire at Point is placed. When Advanced Waypoint Action point is removed, the problem reappears. I was going to record another video showing the problem again but my OBS is malfunctioning. I will try further if necessary.

Upon initial placement, ground vehicles are spawning and moving inside of FARPs. When the vehicles leave the point at which the FARP edge meets the ground they roll briefly, and upon driving back to the FARP they climb atop as normal. FARP Noclip.trk

In Mission Editor for ground vehicle groups, a Fire at Point Triggered Action cannot be moved. Upon selecting the Fire at Point triangle icon, the group is instead selected and moved with the cursor. This is fixed by also adding an Advanced Waypoint Action Fire at Point task. With this added, the Triggered Action Fire at Point is moveable as normal. Removing the Advanced Waypoint Action Fire at Point again creates the bug. Advanced Waypoint Action Fire at Points are always moveable (as far as I have seen). Attached is a video recording, demonstrating the issue. DCS 2.5.6.47404 Fire at Point Bug.zip

My brother and I have both experienced this on our two ELINT trials. Has it been determined what is going wrong? Or what we might be doing wrong?

I have it working, what issue are you having?

Oh excellent, that is definitely a fix I can do. Thanks Grimes. And yes that is an awkward way of doing it.

Good call Grimes, that'd probably explain why my check in doesn't play but JTAC still responds initially. It doesn't know what to send for them. Time for me to dive into the lua to see if there's a fix. If only it was something other than the cannon and Sidearms, two of my favourites!

I'm not sure if it is fully repaired. I have been unable to get the JTAC to relay remarks on any of my missions. I made the attached mission as an example. JTAC Remarks Test.miz

An instant download for what will hopefully be my Christmas present. Great work as always Devrim!

Just wanted to say how happy I am you made this mod. I'm using the D-30 as a stand in for all towed artillery pieces and it's added a great deal to my campaigns. My players and I thank you.

-All menu items visible on all resolution settings -Helicopters placed on appropriate pad rather than centre icon of FARP -Sort option working for Trigger Zones -Mouse wheel scrolling only affecting the menu that the cursor is over. *Kind of a feature request. But headache inducing in a big campaign. -Hide engagement and detection zones for units, either selectively or globally

Airplane Group Default Task Unchangeable Since the current Open Beta update (17th of July, 2019), a fault seems to have developed, forcing the default task for an airplane group in the Advanced Waypoint options. It seems to re-add or overwrite the default task (so white text in advanced task), as soon as the group is deselected or reselected. For example, if the group's task is CAP and I delete the Default tasks (CAP), the CAP task will always reappear when the group is reselected. It appears to be overwritten as any changes made to the CAP task disappear (stop conditions, etc.). This applies to all the default tasks. A SEAD group will always regain its SEAD and Allow Abort Mission tasks, CAS groups will always regain their CAS task. This has applied to both existing missions as well as newly created missions.

First time I opened DCS to record the track it didn't inform me of the update today so I just patched it and recorded another track on the new version of Open Beta. The stutters occurred while the NAVterrain page was selected, the panel did not have to be open for them to occur. I admit I did not test every page in the track as I have other things I need to take care of right now (bad science, I know), but hopefully this gives the developers a place to start. NS-430 Framerate Stutters 2.trk

[REPORTED]Frame Rate Stutters While Powered On I first noticed this using the NS in the A-10A so I recorded the track on the same mission but in an air start F-5. The stutters in frame rate occur only when the NS-430 is powered on. The pop-up panel does not need to be on the screen for them to occur. If the panel is visible but the NS is powered off, there are no stutters. I did not suffer stutters when testing this on a mission that is empty except for my aircraft, so I suspect my computer, old as it is, is able to cope with whatever the problem is. This problem with the NS powered on has also been noted on my brother's far superior computer, though I do not have a track from that machine that is small enough to be uploaded. Hopefully tracks are able to demonstrate the problem, I am unsure if they work on performance issues like this rather than control issues. NS-430 Framerate Stutters.trk

I will look through my control schemes again. I use MSI Afterburner to optimize my GPU, but I am pretty certain I adopted that after noticing this problem. I am going to try it out with the program off and if it's still present, I think I will also turn off my Thrustmaster DDIs as I notice sometimes they automatically get assigned controls if I turn them on while DCS is already open. If none of those yield results I think I will fully redo my inputs in Saved Games before uploading another track. Thanks for the extra help. :)

So I wonder why I am unable too, because it's definitely an issue on my machine and has been since TOO mode was introduced. I've tested it with all my mods uninstalled. It seems unlikely to be a malfunction in my throttle button ONLY when TOO mode is active. I'm racking my brain to try and think what other things I've done that might cause the problem. I don't suppose it could be related to graphical settings either, as that's the only other difference between our machines that I can think of. Perhaps drivers? Just to confirm NineLine, you were able to toggle Sparrows on/off of LOFT mode with the cage/uncage button while TOO mode on HARM is active? Same with caging/uncaging the Mavericks?

And sorry Harker, I forgot I mentioned the RAID/FLIR issue on this thread. Yes I did indeed have the HARM display as SOI, that was a good idea.

So if ED is unable to reproduce, should I provide more tracks? How can I provide more data?

This is in regards to the cage/uncage button use for things other than the HARM. In the track I demonstrate how I am unable to use it to switch Sparrows to & from loft mode. Maverick caging is also not possible using the button so long as the HARM is in TOO mode.

The attached track shows me being unable to use the cage/uncage button while I have my HARMs in TOO mode. The rest of the track has me trying to reproduce the inability to shift HARM targets using the RAID/FLIR FOV button. I have a track that shows the problem but it is too large to be uploaded so if anyone knows how to shorten a track, or has encountered this problem please let me know. HARM TOO Cage-Uncage.trk

Thanks for the info Tholozor.