dahlgren

+1 I am also experiencing this problem.

Hi, I also have Reverb G2 and I am using the stand-alone version. To run DCS standalone in VR I do the following: 1. Plug in the headset/start Mixed Reality Portal. 2. Start SteamVR. Normally it starts automatically when launching DCS, but I have on occasion had problems. When starting SteamVR manually everything works well. 3. Run DCS in VR mode. I have set up a shortcut with the command line parameter --force_enable_VR, but this is not necessary.

I would like to see a better "no mouse" option in VR. It is currently possible to put the mouse pointer at a specific place and then move it around by turning your head. In this way it is possible assign mouse keys to the HOTAS and click different buttons without using the mouse. However, since the mouse stays at a fixed position, it is hard to click buttons far down or to the side. For example, to enable the ejection seat in the F-14 you would to turn the head a full 180 degrees. A better option would be to be able to enable a "no mouse in VR" option in the settings. This would work by not have the mouse cursor in a fixed position. If you look up, the mouse cursor would also move up on the screen. If you look right, the mouse cursor moves towards the right side of the screen. In this way, it would not be necessary to completely center the button/switch in the field of view. For example, to enable the ejection seat in the F-14 it would only be necessary to turn your head to get the switch in the corner of the eye to be able to position the mouse pointer over it.

Same here, "Failed to get authorization data" :(

It is unfortunately not possible to switch seats in multiplayer, regardless of server.

It's in the weekend news thread on this forum, see below link. The Persian Gulf map is not supposed to be on free trial until 9-10 april though. I can't check myself since I already own the module. https://forums.eagle.ru/showpost.php?p=4248521&postcount=243

If you are on Steam many modules are free to try at the moment, including the Persian Gulf map. See the newsletter a couple of weeks back for the free trial schedule. Note that there is one separate for Steam and one for the standalone version.

I have noticed the same. Ex. in the F-14 if you approach the head to the mirror it's obvious that something is a bit wrong with the 3d projection. In some modules, ex. the Mig-21 there is no stereo vision at all, the mirror just looks like an LCD screen.

Same issue for me, Oculus Rift CV1.

+1 on this one. I was flying on the Persian Gulf map and tried playing around with the brightness knob and day/night switch, but could almost not make out anything on the radar screen.

I don’t think anyone mentioned that every time you release the trim button, you should quickly recenter the joystick. Unless you use a force feedback (FFB) joystick, or a stick without spring. This is not how it works in the real helicopter, but a workaround for spring centered joysticks that are most common.

I think it's the opposite. Also magnetic changes slightly from year to year so it would make sense to have maps in true so they stay accurate longer.

I believe I have the same issue with the CHT gauge.

Can you attach the track file?

Did you select the bomb racks in the RIO seat, the same switches used for jettisoning?

CTD in F-14, last time just after releasing some snake-eyes. Nothing in the DCS logs. This error in the event log: Faulting application name: DCS.exe, version: 2.5.4.28840, time stamp: 0x5c93ea3f Faulting module name: WorldGeneral.dll, version: 2.5.4.28840, time stamp: 0x5c93a451 Exception code: 0xc0000005 Fault offset: 0x00000000000345a9 Faulting process ID: 0x43ec Faulting application start time: 0x01d4e1b93de6ca08 Faulting application path: E:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\DCS.exe Faulting module path: E:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\WorldGeneral.dll Report ID: cbc49679-ef98-4aa8-b2f6-6438ff47ee58 Faulting package full name: Faulting package-relative application ID:

+1 for either better texture or repeated in the kneeboard, it's impossible to read. If you have the LANTIRN it is repeated there above the laser code. I have added a custom kneeboard page with the texture so I can kind of compare the blur I'm seeing with what's actually written.

I think we are talking past each other. In your Wikipedia quote even you say that a helicopter is statically stable (it will roll back level) but dynamically unstable (increasing oscillations around the statically stable point). I’m not an expert but in a turn you of course have other forces acting such as centripetal force (changing what the helicopter perceives as being the down direction) and maybe gyroscopic precession because of the turn rate that might counteract this statical stability.

The post there seems to be about turning when going forwards, but what about hovering?

Then the Gazelle is also wrong since it seems to have a preference to hover with the skids towards the ground when keeping the cyclic centered (stabilization deactivated). It might drift around a bit, but not start rolling over.

This completely makes sense to me. A heavy helicopter hanging under a rotor with symmetrically angled blades should roll back more or less level. Wish I could up-rep you for your patience.

Good video, was thinking about doing one myself, but am up in the alps away from my computer for some time. When banking in the gazelle if you engage the magnetic brake (trim), keeping the cyclic left, but centering your joystick you get a similar result as keeping the cyclic left in the mi-8. No rolling over.

Same here. The tanker is set to 44Y, but I have to tune TACAN to 44X, otherwise I only get the bearing and no DME.

Paragraph 23.9.34 in the manual says that the ground track should change between magnetic and true depending on the OSB selection "TRUE". This leads me to believe that the current behaviour is incorrect. And it makes no sense to have ground track pointing in the wrong direction on the EHSD.

Did you try the module at least? I have no problem with the Gazelle being sensitive on the controls, twitchy, etc. with minimum cyclic input. What I am talking about is that any input from the joystick (your computer joystick, no matter the position of the cyclic) causes an accelerating rolling behaviour. A small experiment to show the problem: while hovering, use either magnetic brake or trim hat to trim the position of the cyclic forward. The helicopter will start to accelerate forward as expected. The helicopter will not keep rolling forward, no corrections are necessary with the joystick. Instead of allowing the helicopter to accelerate, recenter the cyclic to the starting center position through joystick deflection. You will then get the accelerating rolling backwards as long as you apply a joystick deflection. The behaviour is the same wether SAS is enabled or not. That being said, this is nitpicking and I still think the Gazelle is a blast to fly. And as some people say it seems that Polychop are working on improvements so hopefully this will be resolved at some point.