rrohde

The campaign feels very realistic in terms of mission types and procedures used, so thank you for that! Such realistic campaigns are very motivating because their missions force you to learn aspects of the DCS module (in this case, the Huey) you might not yet have mastered, which in turn makes a such campaign a great learning tool. I hope you will continue to make these detailed campaigns down the line as well.

It's that simple indeed. :thumbup: We're just a passionate bunch, and this very passion for our hobby makes us sometimes look like entitled little kids crying for attention. Threads like this amplify this notion. Patience isn't our (as a community) strong suit. In the end, though, ED always delivers the goodness and I - for one - couldn't be happier that DCS exists. Development of complex modules take time, and we all should take a step back and let ED do what they do best without constantly breathing down their necks. :smilewink:

@Strikeeagle345 - great summary, thank you! :thumbup:

I think this falling asleep thing is more of a WMR thing that a specific headset thing, since I experience this as well for some time now with my O+. Rebooting fixes it for me, and if I don't get into DCS in a timely manner, I have to reboot again because by then my headset remains blank due this very issue.

Thanks for the feedback. I have my throttle mapped to an analog axis which doesn't respond until after the engine is running (due to the idle release switch), so I have to remind myself to use PgUp from here on out. :thumbup: Edit: Just wanted to add this useful tidbit from Chuck's Huey Guide to this as a reminder for myself:

+1 :thumbup:

Ok, so I tried something different yesterday - I raised and lowered the collective, and used PgUp all the way, and then PgDown all the way, and now it seems as if I can start the helo in campaign missions 1 and 2. Maybe it's not a fuel issue after all. Could it be that PgDown by itself is not enough?

I can try that when I have some time. Thanks.

It's Open Beta. But then again, I could be doing something wrong on my end, and because of it I went to the Huey Start Up Training Mission that comes with the Huey, and I was able to start the helo there - no problem. Back into your Campaign Mission, and I am unable to start, with the fuel gauge never showing any fuel at all...

Hi, after completing Mission 1, I was unable to start my Huey as it seems to be out of fuel in Mission 2 (even though the mission editor shows 55% fuel available). After restarting the campaign, I am no unable to start the Huey in Mission 1 anymore, either. Is there something I am doing wrong here, or is this a potential glitch? Thanks.

Good to hear that it's a continued effort. :thumbup:

I experience similar things with WMR recently, and it worked quite well before: Launching DCS in VR only seems to work once, immediately after rebooting my PC. Any subsequent launching of DCS for VR ends up with the WMR window minimized to the top-left corner of the screen, the displays of my O+ staying black, but Steam VR is running without error message, and DCS launched in VR mode on my desktop. Seems like maybe one of the recent Steam VR/WMR updates caused this, but I am not sure...

I guess Stadia is aimed at console kiddies (pun intended) and their little games - not for hardcore simulations like DCS.

That's awesome! Thanks for sharing. :thumbup:

+1 Not sure why we haven't gotten our pilot back by now... Can someone please enlighten us?

The engines idle RPMs change after touchdown, but remain higher when you don't move the throttle out of idle briefly, and then back to idle. If you don't do that, you're tracking down the RWY with with RPMs too high for a nominal rollout...

Good to hear, NineLine! :thumbup:

Habe das gerade mal probiert, mit "--high" auf 8192. Wow - was fuer ein Unterschied; absolut klasse. :thumbup:

Well said. :thumbup:

Werde das auch mal testen; war mir dessen nicht bewusst dass man das so entsprechend aendern kann. Danke fuer die Info. :thumbup:

... for the LOLs, right? ;)

Plus AMOLED displays instead of LCD!

Thanks for that, BitMaster. Curious what caused this issue in the first place though...?

Agreed - this is my secondary Gunfighter w/ SCG - now ready for the DCS F-16 Viper :thumbup: The SCG is compact enough for a reasonable throw that's not too large.

As a side note, I haven't been able for a couple of months now to reach the Windows Update Servers during my attempts to update my Windows 10. Is that's a known issue? I believe I am stuck on 1809 - and since then any update attempts time out because of aforementioned issue of not reaching the update servers....