CrimsonGhost

If this has been a known bug since before the last patch is there any reason it has not been fixed, or at least marked confirmed? This is a frustrating bug for MP servers and makes buddy lasing impossible with preset drone lasing like found in the 4YA servers.

I know there are plans to eventually go back and bring some of the oldest modules up to modern standards but while we wait I would love to see an update to the anti collision beacon. Currently it’s just a big red ball of antiquated lighting. I know this is a small “bug” but it I can’t be be the only one that finds this annoying. I believe the Mi-8 has the same issue so could be a “two birds, one stone” thing for those of us that love logistics flying.

I am ashamed to admit that I never realized there was a push action on the hat switch you mentioned. I did switch the radar elevation control to button mode in the WinWing software and tried to use that as suggested but for some reason it always returns to the up position in DCS instead of centering like it should, and shows it’s doing in SimAppPro. I’m just using the keyboard commands for the Coolie Hat and will see how that goes. Thanks for your help in this as it has helped me get everything mapped. It is much appreciated.

Sorry for the late reply. Are you referring to the hat switch on the throttle or stick? I use the one on the throttle for SRS and comms and have that bound the same across all modules as that makes it simpler as I own every DCS module. For the stick I swap out my TM Hornet grip back to the TM warthog grip when flying the A-10 or F-16. Thanks for your input.

Hello all. About a year or so ago my beloved TM Warthog throttle died and I replaced it with the Orion 1 stick and throttle. Ever since then the throttle has been great for everything except my favorite aircraft, the upgraded A-10C. I have not been able to find a binding solution for the China Hat and the Boat Switch that I can comfortably use. I do use the top hat switch on the right throttle for coms and SRS and prefer to keep bindings the same (as much as possible) across all modules. With that out of the way, does anyone have a decent throttle binding set for the Orion 1 that they would be willing to share? I don’t need anything for the stick as I use a Virpil WarBRD base and swap between the TM Hornet stick and the TM A10/F16 stick depending on what I am flying, but mainly use the Hornet stick. Any help of advice would be greatly appreciated. I want to get proficient in the Hawg again but have not been able to. Thanks all. Edit- I have been looking at the new F-15 grips as those would give me the buttons I am looking for but am not in a position to be able to pickup the Orion 2 with those grips. And using the grips on the Orion 1 really limits their use.

Is this bug report and all the provided data just being ignored at this point?

Do I need to submit anything for this one?

Any chance of the "Missing Track File" tag being removed? Feels like a scarlet letter.

Upon further investigation with guidance, from Hoggit's own Lazyboot, it seems that the Autostart script is bugged. Attached are 2 screenshots of the section of the Macro_sequencies.lua file. The stock lua entries are 0.1, but when changing them to 0.0 the wipers no longer start on their own. This of course breaks the IC making the fix unusable in MP. The 0.0 entry was tested in SP and the wipers remain in the off position. Another test was done with putting the wipers in the low position PRIOR to beginning the Autostart and the script correctly moves the knobs to the off position. Track files for fix testing are attached. Current Lua file attached as well. SP Autostart Script Edit.trk SP Autostart Script Edit Test Low to Off.trk Macro_sequencies.lua

Track files attached for both MP and SP. Same issue in both scenarios. SP Autostart.trk MP Autostart.trk

For further info, this is encountered during Automated Starts. I frequently use this in the Apache as it gives me time to work on waypoints and other system setup during engine start. I normally avoid auto starts as I am one for immersion and systems depth but this is an exception as the CPG would be doing most of what I work on during the Auto start.

Curious If anyone else has been experiencing this issue since the last update. Not a huge problem but as there is already enough to do to get the Apache ready to fly from Cold and Dark, it is an inconvenience to have to hop into both seats and turn off the wipers.

I wonder if this is why I have been having one hell of a time getting George to find targets after the patch. Typically George will find targets when I point my Pilot HMD que where I want him to search and tap up on George wheel. Last couple of days it’s been like he got a solid visor on his helmet and is blind as a bat. Using the K Hellfires all I see from George is the occasional “all tracks deleted”.

Just found out about this amazing tool and have been loving it! Do have one question/suggestion. As the F-15E has Waypoints and Target Points, is it possible for the tool to ask which type of point we are trying to set up and then program accordingly? The difference in the 2 types of points being a "." at the end of a target point and needing to be at ground level. So "6" would be waypoint 6, and "6." would be target point 6. This would be very useful for slewing the TGP and A/G radar onto target points. If this is something that could be added to this already fantastic tool it would be much appreciated. Thanks.

I always have keys bound to Zoom In Slow and Zoom Out Slow, along with Zoom Normal. This lets you zoom in to read the digits. My question is what do you do with the window once you have set your desired code. Granted, I didnt have much time and was just looking at new features so I never actually started the jet. Does it auto hide on engine start?

OMG thank you! I came back here looking for a solution and stumbled on this thread, which I totally forgot creating. You made my day.

Not sure if this is the right place to post this but I need some help. I have run DCS Open Beta in a borderless Window for years as I run 3 monitors. This is great for keeping maps and docs like Chucks Guides open while playing. In the last few months DCS has started to minimize itself whenever I click on anything off of the monitor DCS is running on. Is there a setting somewhere that I can use to prevent this from happening? Obviously this is less than ideal and I have been meaning to ask about this for a while now. Thanks.

I noticed that in Mission 1 it took Biff forever to get airborne. I was about 5 miles from the Turn waypoint when I noticed he had just taken off. Cut the power and orbited at 190 KIAS until he caught up.

FWIW, I just completed Mission 1 and I think I burned more fuel waiting for Biff to land than I did during the flight. Biff made 3 missed approaches on 21R, and another on 21L before finally coming around and landing correctly on 21L. Very cool to finally be flying these missions for real after helping out with some very early testing and a voiceover or two. Seeing as how I don’t remember my lines it should be a shocker to hear my voice if my lines made the cut. Thank you BD for finally giving us a proper training campaign for the Hawg.

Hello all. I wasnt really sure where to pose this question and I figured with the amount of TM Warthog owners that play DCS, this seemed like a logical place. I have been using the TM Warthog as my go to HOTAS for a number of years now, with the throttle mounted to a Monstertech desk mount that stays in place when not in use as it is not in my way. All of my flightsim gear and other USB hardware are plugged into a powered USB 3.0 hub under my desk and nothing gets unplugged in between uses. Last week, my computer was making the normal Windows sound that is made when a device is unplugged and plugged back in, rather frequently throughout the day. Nothing appeared to be changing, and the LEDs on the throttle remained illuminated. The following day when I turned my PC on, I noticed the LEDs on the throttle were off and sure enough, it was not showing up in the Windows settings nor in DCS. I began troubleshooting by swapping out the USB hub for a known good device which did not help, no matter what port I tried it on. My next step was to plug the throttle directly into my PC and when doing this, it is detected and works fine. Unfortunately this is not a permanent solution as the PC is too far away for the cord to reach. I ordered a couple of USB extension cables to see if this would rectify the issue, but it does not. So now I am stumped. If I plug in the throttle to the front panel ports on my case, it works fine, but any other connection method only leads to the LEDs flickering a few times and the throttle is not recognized. If anyone has any suggestions or ideas, I am all ears and would greatly appreciate it. I am reasonably hardware savvy and build all my own PCs, but the functionality of USB is not something I am all that familiar with. Thanks and I look forward to some feedback.

Educated guess based on all the other topics asking this same question, is that we can expect no news or updates in the foreseeable future. PC is still at it as shown in the recent updates to the Gazelle yesterday. As much as I would love to get my hands on the Kiowa I am not expecting anything for quite a while. I would love to be the scout element for the upcoming Apache finding and lasting targets but this seems to be something much farther down the road than originally hoped. I wish the folks at Polychop nothing but the best and look forward to a great future with them.

FWIW I noticed the same thing in the “Cockpit Familiarization” training mission report when I completed the mission.

Could you share a little more info on this SAR server? Sounds pretty interesting and was one of my favorite activities back in the days of Mirknir’s Open Conflict server, and would love to find another server to perform the SAR role. Thanks!

Hello all. Like many others I have recently got back into the Mi-8 in anticipation of the upcoming Hind module. While relearning the techniques and procedures for the Hip it reminded me of something I noticed in the past but never thought to bring to the forums. So on to the question. I use the TM Warthog Throttle for my Collective input, specifically the right throttle, although I keep them locked together and have the axis curves and saturation set up as recommended in Chucks wonderful guide. For the most part this works out great but I have noticed that more often than not the amount of input required at the “sweet spot” to either maintain straight and level flight, or to descend at a safe vertical speed in order to prevent entering VRS, is extremely small. I know that using such a short travel axis is nothing like the fine input that can be achieved with a proper collective, but has anyone come up with axis settings for the Warthog that might give a little more “granularity” or precision in the middle part of the axis? I imagine there is a sweet spot in terms of X or Y saturation that may achieve what I am looking for but I can’t seem to wrap my mind around how to make this work. Has anyone else ever had this thought, and figured out a solution? I would love to hear the thoughts and ideas of the community. Thanks all!

Wow, this is awesome! I will check it out today with a few friends and see how it goes. You might be on to something here.