Galinette

Hi, Is it possible to assign keyboard controls for the U/VHF controls?(0-9 and VLD, mostly)? These are used a lot in campaigns, and I would like to assign them to my keypad, as it's super painful to click on these in VR. However, I can't find anything in the M2000 controls. Thanks!

Hi, Is it possible to uncage the HUD vector on the M-2000C? For hardcore low-level sharp turns, this would be very useful in order to avoid impacting the ground or climbing too much, as well as for crosswinds landing.

Hi, I checked some documentation about how the distortion is applied in the Link pipeline. You can read in many places that "Low" is the best setting, however it's more complex than this. The distortion pass has been added before compression on purpose for increasing the pixel density at the center, while decreasing pixel density on the edges. This means it actually improves the perceived image quality for low encoding resolutions. So unless the encoding width is set to something very high, setting distortion on "Low" will decrease perceived quality in the center (and improve in the edges). Is there a rift app for testing perceived resolution? Such as something with resolution scale bars.

I don't think so: That's a nasty one, I was overcorrecting! When I wanted 26 ft I was compensating manually to 86 in order to display 26...

Hi, When I try to make an INS update, either by overfly or radar ranging, I can mark the point, the deltas show in the INS display, it's less than 15nm and VAL & REC buttons light up, but, when I press VAL, it seems nothing happens, because the reference waypoint does not move to the marked object. Am I doing something wrong? Also, when entering an DeltaAlt (offset mode) in feet (left screen) the results gets converted to meters. For instance, entering -00086 on the left results in -00026ft and -0008m while it should be -00086ft and -0026m. I guess this is a bug. Cheers!

Thanks, this works. The tutorial is wrong, it says to attack from 1500-3000ft AGL

Hi, I gave a try to CCIP bombing today, using the supplied tutorial, in TAS mode. I have the "RELEASE NOT SAFE" cross in the HUD showing anytime I am below 6000 feet AGL, and at those altitudes the CCIP pipper is about 70-80° down which is impratical... If I dive from 3000 feet at 500kts, I have the pipper at 20-25° slightly above 1000 feet AGL, and everything works, except the "RELEASE NOT SAFE" warning, always showing. Is this a bug from current version?

Don't forget the neck joints warmup before every VR session, it really helps! And subscribe to a yoga class if you are too stiff :) This plus a swivel chair for a few extra ° of rotation, and I'm OK. I would be OK for 10-20° more FOV in the headset, though.

Hi, I'm quite new to the mission editor. I would like to create ILS landing scenari. Is there a way to set ILS frequency in the mission editor? I can find the radio channels, but not the ILS. Is it possible to preset a player slot so that when opening the mission, it's ready with the "FLY" button, instead of showing the slot list? Thanks!

I have the feeling that the 8KX will require a RTX 3080 Ti for running smoothly. Given that a Reverb is already at the limit with a 2080Ti, and 8KX has 16M pixels vs 9M for the Reverb, I hope that a dual 3080Ti is not necessary... I think I will wait Occulus to release a Rift with a resolution similar to the Reverb, to keep the Touch controllers, the adjustable IPD, and perfect software and hardware quality that Occulus provides. I hope I don't wait too long...

Since the last Quest FW update, you can use a USB2 cable as well, such as the one supplied with the headset. Technically no difference since the stream is still 100Mbps over the USB cable. However, a Quest for a dedicated DCS use is a bad choice. While under daylight the quality is very close to the Rift S, at night time you see ugly compression artifacts with the Occulus Link.

Another observation for those who want to buy the Quest for DCS use : if by daylight the quality is very close to the Rift S, for night flights, the compression used by Occulus Link is absolutely ugly. You see huge banding with big compression blocks.

There are some news, with the new 17.x Quest firmware you may use USB2, this means the cable provided with the Quest works. I just tested, there is absolutely no visual difference or lag with USB2. Just equivalent to USB3 or official Link cable.

Yes! This was the other button. I confuse but the documentation, the controls settings, and your post all give different names to HOTAS buttons, so it's confusing :) The documentation says about INS overfly update on HOTAS: "Magic Unlock / Position update" The controls settings have these two entries in HOTAS: "Magic Slave/AG Designate/INS Position Update" "NAV Update/Magic Unlock" You wrote that the two buttons are: "Magic Unlock / position update" "Magic Slave / INS désignate" That's a big mess... Maybe they should have kept the french names.

Hi, I know how to align the INS by flying over a known waypoint, using the REC / VAL buttons. The documentation says : This button is assigned on my flight stick, however it does nothing (the waypoint doesn't move and REC/VAL do not light up). Does it work only in some master mode? Thanks

Well, I ended up Signing in and purchasing 220$ worth of modules (before discount) on Steam just to get the discount... leaving 33$ off ED's pockets.

No, what's strange is having a discount on steam last longer than at ED store. In my case this will make me move to steam and they will loose the 30% steam income vampire drain. For sure I should have better read the news...

Damn, I have read the news to quickly and I have waited the trial end to order a few modules with 50% off... Now I have to install Steam just for this :( That's a strange policy from ED, as this will force people to purchase through Steam, where they loose a 30% of the income.

Hi, I have tested, this doesn't affect VR controllers. I believe this is for FF sticks. The VR controllers vibrate all the time on clickable cockpits, this can't be disabled either in DCS or Occulus settings. Please add a setting to disable it in the VR settings!

I confirm this is still the case with 2.5.5, it vibrates all the time on clickable cockpits.

Hi, I'm testing VR with Occulus Touch Controllers. It's really usable and you can now access every single cockpit button in a few seconds, without having to bind a ton of controls to the keyboard. But, the vibration is super annoying. Every time you just point at a button, without even activating it, it vibrates. So it basically vibrates all the time, which is distracting, and kills the battery. I emptied a new battery in 30 minutes of heavy cockpit interaction, while they usually last 6-7 hours of VR gaming. We should be able to disable it. Or maybe, it should vibrate only : - When a switch is actually triggered? Less disturbing, but not so useful - When a switch failed to be triggered. For instance, when trying to switch on something which is already on. This would really help : in the Mirage 2000 for instance, the switches are quite small, and you don't always see well if they are on or off. Thanks!

Hi, I have looked everywhere, there is no such feature. Also on this Occulus forum I found: https://forums.oculusvr.com/community/discussion/69874/how-do-i-turn-off-oculus-touch-controller-vibration Someone reports the same issue with DCS. I will suggest this to the wishlist... As the vibration is likely triggered by DCS when pointing at a cockpit control, there should be an option to switch it of in DCS VR settings.

For a dedicated use, I would definitely not recommend the Quest. The Rift S is not much more expensive and best suited. The quest uses video compression to send the video signal through USB3, using about 100mpbs bandwidth. It's hardly noticeable, but sometimes dark areas slightly blocky. Also, for use in DCS, you need a USB3 cable (not supplied). The official one costs about 100$, this makes the total price very close to the Rift S. A cheap USB3 cable works, but is not super comfortable. However, for mixed use with some VR games, the Quest is fantastic for the price. Wireless VR is a game changer, pun intended.

You can basically use any USB3 to USBC cable. Just plug it into any motherboard USB 3 port. The official Occulus Link cable exists because: - USB3 only works up to 3 meters because of attenuation, and 3 meters is too short for stand-up VR. Occulus Link cable uses fiber optics, with a converter at both ends. - Occulus link cable is super flexible, reducing constraint on the headset - The angled connector is more convenient. I have a regular USB3>USBC 3m cable. Video quality is perfect, but clearly it's too stiff, and with the straight connector it makes the cable heavy and not super convenient to manage.

Hi! I'm testing the Occulus Quest with DCS. The controllers are really usable with clickable cockpits, much more precise than the mouse. But : every time you point at any cockpit switch, without clicking, it vibrates. So basically, when doing your checklists, it vibrates all the time. That's somewhat disturbing, but more importantly, it destroys battery life. Is there any way to disable it in DCS? Regarding the headset itself, it is surprisingly good for the price, tracking is awesome, resolution is not the best on the market but is really usable, similar to the Rift S. Definitely not the headset you would choose for a dedicated use, but as a 450$ toy its capabilities on DCS are impressive.