pchRage

Hi all, After using my trusty Odyssey for the last year+ I decided to upgrade. Got an O+, returned next day (uncomfortable). Got a Rift S, returned next week (too far outside IPD range). Just got the Index today (beautiful kit!). Setup was easy, updated the software/firmware on controllers/headset. Updated to latest StreamVR Beta Tried out 120hz mode. Adjusted Index IPD and FOV settings to what was comfortable in the "VR House". Kept DCS PD at 1.0, and SteamVR at 170% (same as my Odyssey settings). Felt a bit off on the DCS menu screen. Went to F18 Free Flight. Immediately apparent issues. Super blurry, to the point I had to close one eye to be able to bring up flight menu to exit to desktop. I then went to 90hz and ran it again. Same immediate distortion issues. Then I went to StearmVR and set scaling from 170% to 100%. Tried DCS again.. same issue. I tried flying a bit, and what it really feels like is the LEFT and RIGHT eye screens are not parallel.. light one rendering the picture slightly HIGHER than the other. So its not FOV, not IPD, but something like one eye rendering is maybe 6pixels higher than the other. Anyone seen / reported / fixed this??? thanks!!!

The good news is the RKJXV122400 arrived. Bad news it doesn't looks like it's going to work. 1. the microstick stick itself is about 2-3x larger diameter than the original, meaning the button-hat will not fit. 2. its has no circuit board! I'm guessing i'd have to de-solder the current one and then solder this on. Maybe I can order a board to solve #2, but not sure what to do about #1. Looking at similar models, doesn't seem to have a match...

well bummer. after about a week, decided to return the Rift S. My IPD is too far out of their 64 spec, and the tunnel vision/scuba-mask was annoying, plus eye strain was getting to me. Even with the software IPD adjustment, didn't make much of a difference. And, I gota agree, the audio was starting to become a bother. Ordered and Index, hope it hits the mark!

Ordered a RKJXV122400, will see how the fitment goes!

thanks Sokol1_br When you say, "adapt it". what does that mean? is it too big and needs a bit of trimming with a dremel, or something specific to soldering or wiring? thanks!

Sorry for the play by play. Was able to get those 5 axis to act as one (joy.cpl to the rescue). Was even able to get the microstick working (tubsa is doing insane masking of axis issues). So I'm pretty much in business, BUT I really think I need to get a new microstick somehow... will re-read some of the above recommendations and see where that gets me. Wondering If the Throttle will be ready before or after the DCS module :)

correction. I am able to map buttons, and I can manually assign axis, but it will not auto set. for the thrust, I think the TUSBA min, idle, mil, af, and max sub settings are mucking with DCS ability to pick axis

got the hal kit @Rel4yand installed, super easy and no more axis spikes! I cleaned the microstick with some electrical spray, but unfortunately it isnt any better. maybe with a really smart axis curve and deadcenter config it will be manage-able. BUT... DCS is recognizing the TUSBA and will even show the "default mapped" axis as moving..but when I try to ASSIGN an AXIS..it doesn't recognize it at all! So I have no way to test this thing out! Any ideas on getting DCS to recognize the axis when "moving"? Also, same problem when clicking the buttons, they dont see to want to map either.

Rift to O to O+ to Rift S..Wow! Decided to try the Rift S before I go all $1k in on the Index. Microsoft store 30 day policy is awesome, why not! Picked up the Rift S and put in about 3 hours tonight. TL;DR: == Wow! To be honest, I wasn't expecting much more than another trip back to the store in a few days to return. I expected that the Halo band would be about the same. I expected the resolution and sweetspot would be about the same. I expected that the software-only IPD would be worse. I expected the "directed" audio would be subpar. I was wrong on pretty much all counts. With the O, I was typically always locked in at 45fps, so I expected 40fps for this device... which is what I got. Even with "5 less fps", its performance is better! It truly has more clarity than the O (and O+). Compared to the O: Its lighter Its more comfortable Its more clear/crisp Tracking is better Plane tracking/ghosting is much less (not eliminated, but much better) Was literally able to track a phoenix as it smashed into my poor plane :-) Cockpit is just visually sharper/clearer Text is clearer, still not great, but say, 10-15% better (ie SA page trying to read the cursor BRAA info is still guessing unless I zoom in). Still need to do plenty of tuning, the only settings I changed were: PD from 1.6 (SteamVR beta controlled) to 1.3 (DCS controlled) MSAA from Off to 2x (DCS Controlled). With those two changes, was still able to lock the ~40fps both offline and online. Will probably do more A/B tests over the next 30 days to decide if I return it and stay with O, keep it, or return it and go to the Index. Now I need to deep dive through 160+ pages of the Rift S thread here!

Been using VR-only for at least the last year. Got a Rift, wasn't too impressed. Got an Odyssey 5 days after the Rift to compare and immediately returned the Rift. Probably have several hundred hours in the Odyssey by now over the last year++. With the recent discount sale prices of the O+ thought it may be worth a minor upgrade till the Index comes down in price with future competition. Two hours later with the O+ and I'm boxing it back up and plugged back in the v1 O. For me - the fit and comfort are worse. - way more light through the nose area - sde seems the same even though the O+ has some sort of filter - all the pros (and cons) of the O are still present in the O+ Anyway, that's my experience, YMMV. I think I'm really over the "halo-head-band", and need to jump on the Index bandwagon.

@EchoBravo, how did you go about cleaning it. Did you just take it out from the throttle and clean the outsides/leads? Did you take apart the actual microstick control? thanks!

thanks for the info! Looks like I have some work cut out for me!

Got the TUSBA for independent use of my Cougar throttle to use alongside by TM Warthog (no intention of using Cougar stick). The TUSBA works as advertised, BUT... Within an hour or two, the throttle pot gave up the ghost and its min/max are shot. I hear the HAL kit is now unavailable??? Other options?? (TM oem pot only?) And, apparently the microstick is shot too. Any options for that? At least the Ant and Elev controls I soldered in a few years ago still seem ok! Feels like its going to be a race between getting this controller up to spec and ED's F16 EA :-) Thanks in advance!

thanks cofcorpse. this at least tells me its my problem and not a settings issue. I've tried re-centering the vr both on my noggin and in game. at best, i can "look" down and center vr to get it "closer", but then I lose the heading tape at the top of the HUD.

thanks cofcorpse. While looking through the lenses in VR, it is definitely level (perceptually anyway). Perhaps the desktop view is able to capture the full vertical res vs the VR field of view is clipped? Anything else I can try? faux vr center? pilot seating position, some lua tweak? thanks!

Long time reader of the forum, here is my first post! I've seen a few questions asked regarding the horizontal offset of the JHMCS in VR, which seems mainly due to a left/right eye issue. My issue is slightly different: the vertical offset My issue has been consistent since the first Open Beta build with JHMCS and up to the latest. With the ability to set "both eyes" now, I am able to take a screenshot (from left eye perspective projected on desktop) that shows the offset. When flying level, and focusing directly on the 0 degree bar in the HUD, the JHMCS is offset what feels like ~15 degrees high. I have to "look down" towards the UFC to be able to get the JHMCS to center in the hud and "disappear". This happens regardless of whether I set to right, left, or both eyes. I've worn out the VR reset button on my Hotas attempting to get a perfect alignment. I have zero issues in VR except for the JHMCS alignment. I have the DCS IPD set to 60 (tried 50 thru 65) and pixel density is set to 1.6x Doesn't matter if its Instant Action, Mission, or Multiplayer. I use a Samsung Odyssey for VR, GTX1080, DCS Open Beta. Have the latest WMR firmware, latest Steam VR software, latest Nvidia drivers, and latest DCS Open Beta.