phrozen

Hmm ... Doesn't look like it's been fixed to me, I just tested. Not sure if you bound the cargo door, possibly closed the wrong one? see my screenshot. You need to arm the gunner, then attempt to close the cargo door FWIW. So, the initial bug I reported is very much still there.

Would the answer solution, then be, to implement the ability to close the cargo door on whichever side the gunner is applied too?

What happened that resulted in the issue? Equip the gunner, close the bay door What were you doing that caused, or seemed to cause the issue? I equipped the gunner. Could you reproduce it? Yes What module where are you using, and does it happen with others? The hind. A screenshot: See attached

Running into this recent weirdness (if any one else has run into this) Only until yesterday I'm geting auth failed notices that I only actually saw after removing the -norender flag for my servers. Not sure why it took about a month for this message to finally pop up and give me issues, but apparently I need licenses for all of these (which were done away with since 2.5?) ... Couldn't figure out why my servers werent showing up, but this apparently was the issue... Tried reinstalling the server client and redownloading all assets to no avail, anyone have any ideas? Thanks! **EDIT** So, re-enabling the -norender flag avoids this message, however my servers do in fact show up in my dcs.com /personal server list - ports are good and are visible (windows firewall setters are OK) to the outside world, however the server isn't in the main list in game, and I can't connect to it locally "server is offline" shows. The docs in the open beta server client say it checks for updates, but it appears that this is a DCS version issue? Trying to figure out why my server client is apparently not updating if that's the case... Anyone run into this? **EDIT** The server does indicate the right version ... so now I'm pretty baffled as to why they're suddenly not showing up at all