Cowboy10uk

So it looks like a lot of you, are having teething issues with the new S, while from what I can gather, the display clarity is a significant update would you say it’s actually worth me hanging fire for now with my purchase until the issues get sorted? From what I can see from both here and the Rift forums, the main issues are Display doesn’t turn back on, after first use. Tracking is inconsistent, if you require to use the controllers close to your face, when firing a gun or using a bow. ( granted that’s not an issue for DCS but still ) Display flickers and gets white static after a while Sound is pretty much useless ( hardware issue that’s unlikely to be fixed this generation, completely wrong design call by Oculus ) Battery’s is controllers run down extremely quickly due to not turning off. ( workaround is to remove battery when not in use ) Battery cover comes lose during gaming Audio drivers crash during certain apps Tracking crashes during certain games Headset crashes during certain games, although that might just be the same audio crash that’s reported differently All in all, that’s a fair list of issues, and although I appreciate its early days and it’s fair to expect gremlins with new products, quite a few of them could be seen as game stoppers. I am seeing quite a few who are now returning their S for refunds due to these issues. Now realistically I only use VR for DCS and project cars, so a lot of the controller issues shouldn’t be too much of an issue for myself, and likewise I’m planning on using a headset, so long as it fits over the halo for my sound as I believe full immersive sound is a big thing when it comes to VR. I want to be transported away from my RL, not still listen to it while gaming. So again the audio issues I’m not overly concerned about. But if you guys had a choice, between getting the S when you did a few days ago, or waiting for the issues to be fixed, which I’m sure they will be in time, would you have still got the Rift when you did, and is the increase in clarity worth putting up with the current bugs? I’m unlikely to be able to get one till next week at the earliest anyway due to stock and being away on holiday, but I’m torn between grabbing one to better my DCS VR experience sooner rather than later, or hanging on and seeing how Oculus handle the current issues and what fixes they manage to come up with.

Sadly showing out of stock everywhere now. Not an issue, I’m sure it will turn up again soon. Thanks for the advice

Strange, I’m away at mo, but will grab some screenshots next week when I’m back online for you. Having simshaker error out on a few aircraft and Xplane at the mo. No idea what’s wrong. It’s always worked fantastic before.

So after reading the reviews here, thought I would bite the bullet and grab the Rift S, only to find it’s blooming out of stock everywhere. Dooohhh. Although for a VR point of view, that is great as it does mean it’s selling well. Hopefully will be back in stock in a few weeks. Is anyone finding any issues with the inside out tracking though? I’m reading fairly mixed reviews on different forums, with some stating it works great and others stating that it loses tracking with the controllers fairly easily, especially if you move them towards the headset in FPS and boxing games. Also how’s the head tracking feel? I know my CV1 is the best head tracking I’ve ever experienced, so I really don’t want to lose that

getting that error after about 20 mins flying on all my aircraft and in Xplane as well. as soon as it turns up my simshaker stops working. Did you ever find a fix? im still getting it in the latest build :(

Damn this is a rather interesting thread. Before I read it, I wasn’t at all interested in upgrading to the S, as I wasn’t convinced it was a big enough step forward in the clarity. Given what I had read on other sites. However after reading all the posts on here, you sods are gonna cost me money me thinks. :smilewink::smilewink: I love the CV1, but only use it for transit flights or just messing about in the Huey as I just cannot read any mfds or spot any targets whatsoever with it. But by the sounds of things, it does sound like the S has solved this issue or at the very least significantly improved it. That in itself is enough reason for me to upgrade. I’m a huge believer that VR headsets are the future of our hobby, but we are just waiting on the resolution and clarity to become usable. It also sounds like my other main concern about them using internal tracking only, is a none issue. Certainly it sounds like it’s working as well as it did with the external sensors for you guys, apart from the annoying requirement of now having to have a light on. I always game in the dark. The sound is meh, I never use the internal speakers of the Rift anyway, so as long as I can still wear my 5.1 headset I’ll be happy. Only issue is, it’s sold out everywhere around me, but it just so happens to be in stock, where I’m off on holiday tomorrow. :pilotfly: Think my bro will be happy as well, as he will suddenly find himself with the option of using VR in DCS, as he Inherits all my old sim stuff.

:thumbup: thanks for that. Some great info there. Think I understand now.

Thankyou for that, so in a nutshell, The A8 is a ground attack version of the D9 that we currently have, or at least more suitable for ground attack than the D9. Appreciate that’s probably a very over simplistic way of looking at it, but that’s certainly the impression I’m taking from your very in depth description of the differences.

Hi guys, just wondering with the new pre order that’s just com won’t, what exactly are the differences between this version are the new one that went on pre order today, and is it worth getting both the if you already own this version?

So u know when you’re at the Thrustmaster booth in a few weeks, Wags. It might just be worth, giving them a nudge in the right direction for a rerelease, revamped model. :thumbup::thumbup::thumbup:

Sounds like this could be linked to my issue with the Rio eject sequence ejecting both crew members no matter what position the cmd ejection handle is in in the Rio seat. Sounds like the switch isn’t syncing https://forums.eagle.ru/showthread.php?t=240171

Hi guys, Im having a slight issue with the cmd ejection handle in the rios cockpit in MP, the one on left hand side of cockpit. If i select it backwards, then i understand it should eject both crew members on ejection from Rio seat, which it does. However if i select the handle forwards, I understand that if the Rio pulls the eject handles, then only HIS seat should fire and the pilot stays in the aircraft. At the moment it appears that whatever direction the handle is moved in, BOTH crew members will eject no matter what. Track file is avalible on request, but the forum wont allow me to upload due to size

Simple, you’re as addicted as the rest of us. :thumbup: I own every single module, I’ve flown about 4 of them. :huh::huh:

Nope quite a few of us with the issue. Hopefully now Razbam have stated they are cracking on with the harrier, it will get fixed soon.

Yep, been ongoing for a while now sadly. https://forums.eagle.ru/showthread.php?t=230394

Sadly am I the only one who reads that 2nd link as it ain’t coming. If after all these years of patience and waiting, Belsimtek still only assigns it as a third degree of importance to an already busy Dev. Then realistically there’s bugger all chance they are gonna get the time to do it. The previous excuse was always because Multicrew wasn’t working in DCS, well know the F14 has blown that argument out of the water, so surely it’s time to get that advertised component working.

Have a family friend who owns a Huey, so have fired across the questions to see if he can help.

Cheers mate, will have another look later today. That may be the issue, as my Kneeboard is that small I can’t actually read the writing on any of the airfield maps. Was looking for the info on a nav page.

Yep completely stuck there as well. Can’t see anything to add on the Kneeboard, and no idea how to do so, if I do find it

I tend to start switching to STT around 50 miles. No idea if it’s the correct procedure, but I do find it does help me tracking the different aircraft.

Nope we always wait in the lobby and join together. No one touches anything until we are both in the cockpit and state we are ready for the prestart checklist. Although this isn’t the only issue we are having in MP, as a Rio I can’t see any of the light checks my pilot does, the fuel light always shows low in the back, and IF we eject,only the canopy jettisons if I fire the seats, or if the pilot fires them, he ejects but the canopy and myself stays in the aircraft on my sim. I’m assuming it must be a sync issue, I have since uninstalled and reinstalled the module, so I’m hoping that may fix the issues we are see8ng. Sadly I can’t check until weds as I’m working nights at the moment.

Strange, ok well I will uninstall the F14 and reinstall her then. Maybe it’s a install issue or possibly a desync issue with the MP

Yep, mentioned this a few times. As a Rio it doesn’t matter what I do, when I eject only the canopy blows off. We still stay with the aircraft. When my pilot ejects, I stay in the aircraft and it didn’t show the canopy separating from F1, in F2 it appears to be blown as normal. Assuming it’s a desync issue

Yep I get this on every MP flight. Cold and dark startups on each one with a full aircraft. Caution panel always shows low fuel.

tried again today in MP, Rio initated ejection both on ground and air, only fired canopy. when my Pilot ejected, he ejected, my canopy and myself stayed in the aircraft????