Baggy MacDouche

I believe Alt+Enter to go into fullscreen mode eliminates this.

I think some people have gotten so used to the update cycles of cell phones that they mistakenly think to equate it with this kind of new technology. It's nowhere near the same boat. I wouldn't be surprised at all if HTC says absolutely nothing about any new advancements other than stuff that has previously been talked about at dev conferences and such. It's more likely that they are just having a presence to continue to show off their current product as it is still so new. The things that need upgrading are no simple obstacles to overcome, at least to justify a completely new HMD. There will never be a modular system any more than you could just upgrade the cpu/gpu of a console. Everything needs to be precisely integrated in order for it to work properly. Fact is, we are all extremely early adopters, even at the CV1 level. Just the fact that we are at where we are now is a monumental achievement that took years to accomplish. We just have to be patient and give them the time they need to improve and do it right. I wouldn't hold it against them for keeping information close to the chest in this emerging competitive market either.

For some reason I thought that the Steam and non-Steam module versions were incompatible(i.e. a module purchased through Steam would not work with the non-steam version and vice versa). If that's not true, or used to be true but changed, then sorry for any confusion.

Hmm, maybe this is the key.

The main reason I want certain snap views is because I have a lot of trouble getting my head/vive to view extreme angles of the cockpit that allow me to click on certain things. For example, I can't seem to get the center of my view when tilting my head down to look at the radio or lighting controls, because they are so close to the seat/body. So, if I'm looking down and there are still controls at the bottom of the screen, I can't physically move the mouse cursor over the control as it gets stopped by the "edge" of the screen. Everybody is different and maybe others don't have this problem, or maybe use a wider FOV? Ideally, if I had a couple of sticky snap views for say, the two left/right side & rear quarter panels, that would allow me to easily click on things. I wouldn't be doing those things during engagements so I'm not concerned about losing situational awareness. CDU would be nice too though. I don't even feel like I need snap views for the MFDs as I can see them pretty well actually. I'm still trying to understand what you posted though. Is the RCtrl+KP0+KPx combo an actual sticky version of the snap view? I don't think I tried that full combo. But, I'm still unsure of how to actually position and save a particular view to one of those combos. It's also a PITA to try and do this with the keyboard and the vive on, but I realize that it just may be the nature of the beast. If I get it right, I should only have to do it once.

I tried following the instructions in the video link posted above, but for the life of me I still can't get snap views to work. First off, he's using a TIR and normal zoom keys to get the view he wants, which is not possible with VR. Secondly, the snap view keys(LWin+Numpad-X) need to be held down to keep the view up. I'm only referring to the default ones, as I have been unsuccessful in actually saving any new ones. It's not practical at all to have to hold down the keys(or stick bindings) if you want to be able to interact with the panels in view. I mapped the Cockpit Panel View Toggle to a stick bind, which just snaps me to a wide view of the entire cockpit. Then going to a snap view just goes to that as long as I hold it, but then reverts back to the default view when released. If anyone has gotten snap views to work in VR, meaning you can assign several views to different key binds, which are sticky, then please advise on the process you used, as well as the appropriate controls commands used. Assume I would like to do this in the A-10C to start. Thanks. *edit* Maybe I should mention I'm using a Vive? I don't know if that has anything to do with this, as there are differences in support between the Rift and Vive(i.e. Vive just recently got zoom support).

That is a separate issue that I'm aware of, but not what is causing me problems. I experienced this ever since I started using VR, before the latest patch which bugged the mouse cursor. It's still a problem for me, even if I do the open comms menu workaround.

Don't overlook the Vive either. I know there are a lot of Rift folks here, and it was the first supported HMD, but there are plenty of valid reasons to choose a Vive, beyond just using it for DCS. Another nice feature of the Vive is that it has a built-in forward facing camera on the front and if you double-tap a button on the side of the HMD, it overlays a view of the outside world. It's not 1:1 picture and looks more like something out of Predator, but it's good enough to be able to look down at your keyboard or controls and get a good sense of where things are at. Can be pretty darn useful and saves you from having to pop up the headset at times. Also, understand that there's a bit of a trade-off right now when it comes to VR and sims like DCS, and that's visual quality. If you're coming from a pretty decent highrez monitor, you may be a bit disappointed at first that things are not nearly as crisp. But in my opinion, the sense of presence and immersion with VR makes up for that. I could never play on a flat screen again.

Thanks gents. Got it working now. It's a little weird, but I'll take it. I was getting quite used to it in the short time I played around with it.

I think you may have misunderstood me. First, thanks about the zoom feature. I did see the other thread and I finally got it to work. Secondly, I'm not having any issues with visual quality and actually reading instruments/labels, etc. I'm just having trouble actually clicking on things that are within a certain field of view. I'll be specific: Let's say I want to tune the radio, switch flight plan modes, set TACAN, turn on lights, all that kind of stuff that is to the sides and close to the edge of the seat. When I look down at those things and try to get the mouse cursor to hover over them, I just can't get it to some locations. It's as if the cursor hits the edge of an invisible wall. While seated in my normal position, I just can't look down and to the side enough to get the control into the center of my FOV. I hope that makes sense.

Which command are you actually mapping and where? As stated previously, I tried mapping the VR Zoom command in the UI Layer section(do not see any other VR related commands anywhere else). Also not sure what it is supposed to do, since it just says VR Zoom. Is this a toggle enable/disable for use with other zoom commands?

I don't want to be that guy(despite my namesake), but how does something like this get missed in internal QC, even if something could have gone awry in compiling? Code update, fire up VR, try to use mouse, hmmm...

I was just playing around with the new patch(trying to) and can concur that mouse use is definitely broken badly. But, how did you get zoom to work? I tried using all the relevant keyboard commands, as well as mapping in the VR section of UI Layer. Nothing worked.

Utterly broken now. :(

Hey folks, looking for some advice here. I'm using a Vive(not sure that matters), and I primarily fly the hawg right now. The problem I seem to be having is after my view is centered and I try to look/interact with the side panels(especially with controls closest to the cockpit seat or rear quarters), I just can't seem to comfortably get my view targeted on the control I want to interact with. It's like I can't lower my actual head enough. I'm using mouse control too, instead of center view, and the mouse will just sometimes not be able to reach the control and/or jump around too much. I basically have to move my seat around just to get a better view, which is a pita, and not something I'd like to do in-flight. Anyone else having this problem in VR and if so, what are your solutions? I've never messed with snap views and not sure how that all works in VR.

Not for me. Removed DCS folder from Saved Games and while it does recreate the folder, it still hangs on the loading screen at 5%.

I just wish I had the equivalent controllers with the same touch/feedback as the real thing. It's hard to tell with my Warthog and tweaked axis settings.

I agree with you MadCat. I will only add that I think it should be an option that you can toggle on/off like head shake. I think that would be the best of both worlds for the people who want that visual feedback, as well as those of us who prefer a more accurate visual representation, regardless of the lack of physical feedback.

Thanks for the replies and it confirms my suspicions. IMO, if this is going to be the most realistic simulation of the Huey possible, then it shouldn't have these added effects just to make up for a lack of "seat of your pants" feeling. When it comes to things like this, I am a big fan of making it a option that can be toggled. I understand that some people may like the effect as a visual aid, but I don't think it should be forced on those who prefer a more true to life simulation, despite the lack of the physical feedback.

Sorry if a rehash but I did try to find an existing thread but gave up. What I'm talking about here is when you startup the Huey and the rotor starts to spin up, the airframe begins to rock side-to-side quite a bit. It's very visible both inside and from outside. Not that I know a lot about the real Huey nor have I spent any time around them IRL, but it just seemed odd to me. Then I found a video on youtube(will post link if I find it again) of someone videoing a Huey startup on the ramp from not very far away at all. Close enough to tell that there was almost no visible shake while the rotor spun up. The tail boom did vibrate very slightly a bit until the RPMs got higher. I don't know if this is a bug or a feature. Is it something that is supposed to be fixed? I mentioned this to someone and they seemed to be under the impression that Belsimtek did this on purpose to simulate the lack of "seat of the pants" feeling. I'm not sure why you would need this on startup.

Been on both those servers. Was actually on the HueyDrop last night having some fun. I gotta get better at controlling the door gunner to try and help clear the area for insertion. Keep forgetting the mouse toggle key. :p Most times I can't get on till late and don't recall seeing the HueyDrop server up. IDK if it runs 24/7 or not.

Thanks for the reply TK. Yeah, guess I'm just looking for a "Huey friendly" environment with cool stuff to do without the threat of fast movers. :) I downloaded Wolle's MP/SP CSAR mission and played around with it a bit last night. Had to figure out how to use the ADF which wasn't too hard. Was fun but still got to work on my landings and straffing technique, but most of all how to deal with AAA without being turned into swiss cheese. Having a blast though. Will stay on the lookout for Huey servers. I'm often on at odd times though, even for PDT.

Are there any good open servers that cater to the Huey? Seems like all the servers I've tried out don't have any real roles for the Huey. I'm still noobish to the Huey but getting much better all the time. Still, I feel like I'm just fodder for enemy defenses.

If this latest patch is indeed a rollback, how do you use the autoupdater to rollback to the previous version without having to download anything? The download is going at snail's pace of 70-80KB/s. Come on! I've got a 50+Mbps connection. Tell your hamsters to run faster! :D

Has the procedure for repairing a damaged airframe changed at all recently? The way I have always understood it was come to a stop anywhere off the runway or on the ramp. Turn on ground power and then cut engines. Countdown timer to repair should start. The last couple of times I have tried this I got no countdown and it never repaired. Now I can't recall which airport I was at at the time and I do realize that there are some that don't allow repairs. That's why I wanted to double-check to see if anything had changed or if I am simply doing it wrong. TIA