Woody01

Multiple guys reporting this at Choppa Tuesday last night.

Glad to see this thread. Our dedicated server missions are pretty heavy and now I just cant use F10, it will crash the Reverb as described by the OP pretty much every time.

Yes this is happening too me a lot! It seems way worse when I plug the headset in the USB on the motherboard, if I run it through the powered USB hub its not as bad. I thought it was just part of my borked Reverb dying but seeing this thread now I'm not so sure...

Yes that was a bit of a shame I think, taking fuel in the FA18 off the KC135 was a hoot! And the touching tips jokes never got old...Plus they can for real, albeit with a short drogue out of the boom, but it was at least doable before.

I would say your chocks were in. Glad to see this bug sounds like it is resolved. When you spawned in on one of the cats your chocks were in and there was no way to remove them. So this could give you the impression that salute was broken as everything looked normal otherwise.

Yes trying to get too the bottom of this for the Speed & Angles server. I dont think its the mission, the exact same mission runs fine on The Flying Kiwis server but the mission in question is on Syria. Hardware configuration? Server setting? So far Ive seen a few threads like this but no answers, very annoying for sure.

Im glad to see this thread! I thought I must have done something weird to make this happen. This is on a brand new build it is happening to me on, I totally rebuilt a mission from scratch because of this. Yes a fairly major bug.

Honez we are not seeing this issue. The Kiwis do a lot of refueling and it is very consistent for us, we routinely cycle large groups of aircraft through the tanking phase and dont see the problems you are. Not really sure what to suggest but just wanted to let you know its fine for us. We are running our missions on a dedicated server.

Thanks Grimes! :thumbup:

The mission sometimes, sometimes not crashes with this error during the mission cycle which is 9 hours. I dont have access to the logs as its run on another PC in another country. It may well be connected too uncontrolled aircraft awakening via the F10 menu.

Can anyone understand what might be happening with our server when we get the following message after it crashes? Anything you could point me too would be a great help. It doesn't happen every time but is fairly common. It seemed to start after the last update that changed the way everything was named, but if you can read into it and give me any clues that would be awesome. Thanks.

If your in the Australasian region and love yourself a good ole bit of choppa action you may want to pop your head into the TFK Discord channel. Every Tuesday we fly a dedicated choppa mission (always with fixed wing support) and it would be one of our most popular nights in our weekly flying schedule. Weather we jump on our dedicated server and make something up out of the bozillion options we have or we run a one off mission. Although the Huey is by far the most popular aircraft there is always the Gazelle, the Hip and sometimes even the Ka-50 available if that's your poison and all the usual suspects for fixed wing support where you will find CAS, CAP and SEAD roles commonly required to help out the choppas. We enjoy a lot of banter and shit talking and have a heck of a lot of fun, don't take ourselves too seriously but we fly pretty hard out and give as good as we get. Several of our guys stream the missions also. If it sounds like you might be a fit come say hi and get amongst it. https://discord.gg/r6y2fx

I'm seeing this as well, has done it on two different missions lately and I'm pretty sure I have the missions setup correctly (The same way it has worked in the past).

I have spent today updating everything I could, flashed the motherboard BIOS, updated motherboard drivers, big windows update (2004), checked everything else was up to date. Annnnnd crash to desktop. Before the last DCS update it was CTD every time I jumped in any cockpit, after the last DCS update it was not crashing to desktop and I was able to fly, then a steam update and now its back to unusable again. This is all on a system that is only a few months old, 32 gig RAM, 2080 Super, 17 8700 etc...

Same for me, 4 crashed in a row tonight as soon as I log in, didn't try after that as I was afraid of punching the headset through the wall. The sad thing is it was doing this before the last update, then the latest update made it so I could jump in the cockpit without crashing, then steam released an update today and now its crashing straight away again. So over it. dcs.log-20200830-080109.zip

Cant help you with the Australian part but check out The Flying Kiwis. We have a great bunch and a very busy server with lots and lots of Australians flying with us.

Yes sorry twells555 I didn't get an answer back to you. Im in New Zealand and we have a law here called the Consumer guarantee act, it covers consumers regardless of what any warrantees say. if the product does not live up to your expectations you are entitled to either repair, replacement or refund at your discretion. I could have pushed for a refund but they were getting the G2 in anyway (The local shop I brought it off) so I opted for a store credit and that way I shouldn't miss out. Also several of the guys I fly with are either on their second Reverb or about to be, a lot of it from the same issue, it cant hack it after about 30 mins and shuts down. I too really hope Valve has had a positive influence on HP from a reliability point of view.

I'm just waiting for the G2's too arrive in the country now. The second unit they sent me was a referb or demo model or something, they did admit after a while it was not new. I got a refund in the end that is in the form of a credit with the shop I brought it off, will be spent on the G2. Other guys in my outfit are also having issues with their Reverbs, similar to what happened with mine. Such a shame really as when it works its great, it just seems they cant handle it in the long run.

Yes awesome feature, thank you!

Yes, my door gunners are acting weird, I cant get them to engage targets for more than a single burst.

I use illumination bombs triggered by the F10 menu, works awesome and you can see them for scores of miles.

Ive had my Reverb for about 8 months and it died, it would just shut down (crashing me out of DCS) after about 30-60 mins. HP replaced it with a unit that is WORSE! And the lenses are not even aligned! I think it is a refurbished unit as the foam padding is already 'bedded in' to the shape of a human forehead, just not my forehead! So pursuing a refund now and I don't think I'll bother with the G2 after a reviewer said it would shut down as well. "But HP said it will be fixed in the production model" Yea right! Not holding my breath! When it works its pretty good, but in my case the product has not performed to expectations so going for a full refund.

Thanks you for listening ED! We are happy Kiwis now :D

Unknownaussie, as Shu said we might have something of interest for you, though we are The Flying Kiwis you will find near on a 50/50 mix of Aussies and Kiwis. We run the server out of a Sydney data center so pings are great for you guys, good for us and the pipe is pretty big. We fly new missions every week and have 3 main flying days, Choppa Tuesday (with fixed wing support), Training on Thursdays and our main mission is on Sunday night. We cater for most common aircraft types. our discord channel is https://discord.gg/YkWcxX

Yes for me it turns out a repair fixed a number of issues, I can now see the target diamond again! Still having trouble with the bloody pod slewing everywhere except where I want it but managed 7 out of 8 hits with GBU-12's (one missed because I forgot to flick the laser back to on) L MAVs also working again. Thanks guys! Thought I was going crazy!