MatzWarhog

It would be handy if the default was "Option 2" for now and you could use the "Option 1" "Hardcode" if you wanted to. At least then, we wouldn't have to be going into old missions and cleaning out all the FMs now created in them. All the same, your solution worked great! Many Thanks!

Ok... so we figured out how to create "Groups" in ME allowing us to identify each other via Datalink... but how is this going to work on public servers and all of the multitude of missions we already fly as a squadron? Basically, from what I see now, our group has to be built into the mission, or we can't use the datalink that we rely heavily on. Am I missing something?

We're not seeing anyone in our Group on the Datalink in the A-10C II. No other A-10C IIs are showing up blue on the TAD. On the TAD we can hook each other and see SPI shares, but other A-10C IIs in our Group do not show blue, nor are they identifiable with our HMCS. It's as if we have the Datalink, it's just not visible to ID each other.

FYI... found this same issue in an ED Forum search in which the same issue was popping up with a previous Update in the past. I followed the solution there, and in ESET, when you go into "change the cleaning method (https://help.eset.com/eis/16/en-US/work_avas_realtime_cleaning.html) to "Always ask the end user", below that setting, check "Exclude From Detection" and the it skips past it entirely, and now Combined Arms shows Authorized and works as normal. Hopefully it's not a virus! LOL

I experienced the same issue with ESET and did as suggested above and got a full update, However, my Combined Arms does not show up, and says it is not authorized.

This does appear to be the cause and solution to the issue. I just now recreated the unstickable "stuck key" error, by clicking both mouse buttons on an OSB at the same time and then trying to click any other OSB. The OSB's descriptor became highlighted in purple and would not respond to clicking "Ack" to clear the error message. Clicking the same OSB again with both mouse buttons removed the purple highlight and resolved the problem.

Interesting! It's entirely possible that I did that at the time. I'll try and recreate that! Thanks!

Ditto! For the first time ever, I just received a "Stuck Left MFD Key" message at the worst possible time. Ended the mission, and spawned back in, it's gone. Is this a modelled in failure if you accidentally hold an OSB down too long? Update: I went back into the mission and used the mouse cursor and intentionally held different OSBs down until the "Stuck Left MFD Key" or "Stuck Right MFD Key" message appeared. However, when recreating the error, I was able to cure the problem simply by clicking "acknowledge". I'm not sure why it would not clear the error in the mission, but the problem is gone. I even went back and recreated it using my Cougar MFDs, and was able to clear it with "Acknowledge". Strange thing that I've never seen this before, just curious why the "Acknowledge" didn't clear it in the mission. It happened at a very inopportune time.

I was comptemplating using the same... how is that working out for you?

I've decided I want to experiment with the Harrier as well, and I'm also using a TM Warthog. I was looking at Chuck's Guide, and he advises to bind the Nozzle to an axis. Just curious what others have used as the axis on the HOTAS Warthog?? TIA!

Ditto! I even posted on the color abnormalities in the "Unknown Bugs" forum after it occurred during our squadron mission, which in the middle of, we had people's DCS crashing, and others with VR questions about green hangers and framerate drops. The entire "Halloween Easter Egg" event would have most likely gone by with nothing but laughs and seen as a really cool thing ED had done... IF it wasn't 4 days following the update from 2.7.xxxxxxx to 2.8.xxxxxx, one of the biggest updates in months, and one full of actual Bugs. It was poor timing, and some of us actually did spend a lot of unnecessary time trying to troubleshoot the colors. Time to let this subject fade away and learn from it, but seriously, stop dissing the people who had events disrupted and spent time trying to fix the "2.8 Update" because of it.

Just NOT 4 days after a major update that has the vast majority of players still troubleshooting framerates and and other graphics issues. There was a lot of wasted time trying to fix a green sky post mission last night.

Pumpkin runway lights... fine. A unexpected green lit sky during a squadron mission night over snow in the late afternoon sun... not alright. I can appreciate some fun, but after suffering through green skies, and then post mission, spending quite a bit of time trying to troubleshoot why my freshly installed open beta update that everyone is still dealing with framerate and graphics bugs and suddenly looks worse... gotta say the timing was poor. Nice gesture, poor timing.

Same green sunlight at 13,000 as well. If this was my trick or treat, then haha... not.

The green tint seems to be coming from the ambient light/sunlight. After you mentioned the Halloween thing, I jumped in at Kutasi and screenshot this. Now that is some serious green light coming from somewhere!