jaxx_za

I actually quite liked the cover - different take on the original - less anger, more sad. *Let's see how this flamesuit holds up*

Nothing of value to add, other than WOW! Now that my jaw is off the ground, how well would a physical cockpit layout work in VR? No criticism intended, just wanted to know your thoughts around getting VR to align with actual reality. I fly the mi-8 in VR as well, and am hoping hand tracking like in the Oculus Quest comes to the rift, to allow interaction with the cockpit.

Yes, you would need to use the Saitek profiler SW to program different functions across modes. Also remember that you would need to load the profile and keep the Saitek app running in the background, before starting DCS.

Welcome down the rabbit hole... Before long you will be tempted by the Huey module, reading Reddit posts about the visual improvement of the Rift S over the 1st gen, and crawling Amazon and eBay for specials on the TM Warthog Hotas[emoji16] But it's worth it.

I removed the guard after 2 minutes as I found it a little ticklish. In my case, without the guard there is enough of a gap to see the keyboard. But even if this weren't the case, the improvement in resolution is really massive from the CV1, so if your IPD is in range don't hesitate - you will not regret it.

Just did the same a week ago, and it's a massive step up. Do it - you will not regret it (provided your IPD is within range) Sold my CV1 today, and before shipping I gave it one more go in DCS - while the CV1 still holds its own, it feels previous gen in comparison to the S. In the CV1 @1.7 pixel density, everything inside the cockpit looks crisp (excluding text), but outside of the cockpit the jagged edges are really apparent. With the Rift S, other than the text being completely clear, the outside of the cockpit appears as clear as the inside does in the CV1 - if this makes any sense at all. The image also appears to pop more in the S - color just seem more vibrant. Screen door effect is so much better that I hardly notice it at all. Audio is not nearly as bad as its made out to be - after a week I don't feel like I'm missing out on much. Somr have complained about the black levels on the S - I didn't find it to be a problem at all. Same for the 80hz refresh rate - I cannot tell the difference. Comfort wise, I find that halo style band much better. It doesn't put as much pressure on your face as the CV1 does, which makes longer sessions much easier. I did remote the nose guard as it was somewhat ticklish. Many reviewers have criticized the S for not being a generation up from the CV1 - I tend to disagree, as the improvement is significant. I finally feel like VR has matured with the S, and for the first time I can say that I'm content with where my VR experience is right now.

Thanks for the feedback - could be interesting if the HUD is only partially visible in real life too. I'll give the IPD settings a bash. Sent from my Nexus 5X using Tapatalk

Thanks, does this also correct the HUD readout size? At preset I cannot see the full HUD text unless I move the viewpoint forward, but then I'm sitting too close. Sent from my Nexus 5X using Tapatalk

Sir Yes Sir[emoji2], just completed both BFT03 and 04. Guess my Xplane habits of banking at 30' had to change. Thanks. Sent from my Nexus 5X using Tapatalk

Just experienced the same - flying out to sea at 300... Will try the quick turns as you suggest, but also a little dissapointed as it is turning out of be a really good training tool. Sent from my Nexus 5X using Tapatalk

[emoji106] Sent from my Nexus 5X using Tapatalk

Thanks - been wondering about this myself. Also wondering if there's any means of triggering different graphics profiles for VR and non-VR via command line ?

Hi, I'm no expert, but it depends on what you are trying to bind the axes as... If you are trying to assign as an axis in DCs, I don't see any reason why they shouldn't work ( that is, you click on assign axis, and then move the slider or rotary to assign). If on the other hand you are trying to assign to a button, then you would need the SST SW to output a keypress based on the slider / rotary position, and then assign that keypress in DCS. Perhaps share what you are trying to assign to the axes ? Sent from my Nexus 5X using Tapatalk

Yes, PoV hat 3 is configured as the throttle designator, and the scroll wheel depress to lock. Sent from my Nexus 5X using Tapatalk

Thanks for bumping this :thumbup: I've been looking for good missions / campaigns for the A10C, but as the module has been out for a while it's difficult to find the good content that stilll works. This seems very interesting - can't wait.

Here is my profile for the hornet, if you'd like to give it a try. (Note that this is a lua file to be loaded directly in DCS, and not in the Saitek SST SW) https://forums.eagle.ru/showthread.php?t=210359 Sent from my Nexus 5X using Tapatalk

Just been through the entire thread (:thumbdown: Photobucket for messing up and otherwise perfectly documented build), and I have to say well done - you must be very proud of what you have accomplished in two years. I hope you don't mind a request : I would love at some point to see a video of you playing a 30 min or so mission from the below angle (where both the cockpit and screen are visible) - to watch how you interact with the cockpit throughout a quick mission.

Open up the Saitek SST SW with the default profile, and have a look at what is programmed by default for the scroll wheel - I suspect there is a mouse wheel function programmed to it. Reason I say this, is that the scroll wheel is just 2 buttons ( check out the default windows calibration for the x52 - it only sees 2 push buttons for the wheel). If you delete whatever is coded to the scroll wheel, then save as a new SST profile, and activate for the x52, DCS should start recognising the wheel up/down as push buttons, and hence you can program it as mentioned initially. I had this issue with the little push button next to the mouse pointer on the throttle - I use it for VR zoom, but had to do as described above before DCs would recognize it. I have also programmed the scroll wheel for the f-18 antenna elevation and DCS recognizes the wheel up/down as separate button presses. Sent from my Nexus 5X using Tapatalk

You're welcome, and thanks for the feedback [emoji106] Sent from my Nexus 5X using Tapatalk

I cannot recall now, but in DCS under the key bindings, is there no single button call for zoom in and zoom out? If yes, then you should be able to assign the scroll forward and back to these functions, an scrolling the wheel generates a single joystick button press in each direction. Sent from my Nexus 5X using Tapatalk

Chances are that you will experience motion sickness when you first try VR, but you should overcome it in a few days. I started with Assetto Corsa and experienced motion sickness for the first 3-4 days, after that none. So we do adapt quickly. From another perspective, the first time I demo'd the rift to my wife, she spent less than 5 mins driving around in Assets Corsa and felt so sick that she had to lie down for the next hour. Fast forward a month or three and I was impressed with the IL-2 BoS experience so I had to show it to her. She flew around for 15mins without any motion sickness - this after not having touched the rift since the previous experience, and only her second experience with the rift. The problem with the try before you buy is that chances are high that you would get motion sickness, and this could put you off it before you get the chance to adjust. Assuming you are happy with what VR has to offer, I'd say go from it rather, as the odds of you not adapting is slim. Sent from my Nexus 5X using Tapatalk

Try right shift + right Ctrl + num pad keys to adjust you position. I think the / and * zooms in/out. Sent from my Nexus 5X using Tapatalk

Hi all, Just thought I'd share my X52 profile for the Hornet. Note that this has been configured directly for DCS (ie. no SST SW profile included/needed, but you will need the SST SW to enable the PINKIE switch as a button in DCS as explained below). I haven't had to transfer DCS profiles between PCs before, but I believe the below should work. If it doesn't, hopefully someone with a better understanding will assist. Prerequisites : - for DCS to recognize the PINKIE as a button, we need to remove the shift states in the SST SW: https://forums.eagle.ru/showthread.php?t=83215 - for DCS to recognize the clutch buttion ("i" button), we have to enable as a actual button, and not as a shift state as follows : Control Panel->Devices and Printers-> Right-click X52-> Game controller settings->select X52 and click Preferences->MFD Tab->Remove the tick at ENABLE CLUTCH MODE->click Ok- - you will also need to add the Pinkie Switch as a modifier in DCS, as follows (please name the modifier as "PINKIE" in order for my profile to recognize it): DCS Controls > Click the "Modifiers" button at the bottom left > Click the "Add" box > Under "Device Name" choose the X52 HOTAS > Click the Pinkie for it to be recognized as a modifier > Change the "Modifier Button Name" to "PINKIE" https://forums.eagle.ru/showthread.php?p=3183147 Hope this works :doh: DCS FA-18C X52 Profile.diff.lua

Had the same issue when i cancelled the update mid progress - I had to run the dcs_updater again, which then downloaded and installed the missing files. Once DCS started again, the module downloaded just fine. So I suggest try running the dcs_updater app to make sure you are on the correct release (2.5.2.x), and if that doesn't work try closing DCS, then launching from DCs.exe as opposed to auto launching from dcs_updater. One of the two should result in a further update and restart of DCs, at which point you will be able to install the hornet. Sent from my Nexus 5X using Tapatalk

No need to download the beta version from scratch - you can: - upgrade your existing install to beta quite quickly (and downgrade at a later time), or - make a copy of your current install, and upgrade that to beta Have a look here: https://forums.eagle.ru/showthread.php?t=114030 Sent from my Nexus 5X using Tapatalk