davidp57

I have added this to Config\Input\UiLayer\joystick\default.lua and to Config\Input\UiLayer\keyboard\default.lua : {down = iHeadTrackerZoomToggle , value_down = 1.0 , name = _("VR Zoom IN") , category = vr}, {down = iHeadTrackerZoomToggle , value_down = 0.0 , name = _("VR Zoom OUT") , category = vr}, I didn't try in VR yet but it works in the Controls Edition window

Same here

I'll repeat here a question I asked in another thread : do you guys know what Lctrl7 and Lctrl8 do ? They do something, only when in VR, that's for sure... There's a "device (dis)connected" sound and the display freezes for 2-3 seconds. Any idea ? Anyone tried ?

"Posting images, file links, and file sharing links" ; no mention of excerpts, is it ? ;)

I ain't got no tracks but I'll record one and report here.

You could also try switching the INS switch to IFA (In Flight Alignment) where the GPS will be used to align the inertial system. Usually it takes about 5 minutes (even when flying) and then the HUD shows up. If not, you may have another problem than the INS (maybe the HUD as suggested by Mecrutio)

Hi there, On the latest release version (but it already happened before) we noticed that, when taking off from the Tarawa, whenever we land on ground (on a runway, on a farp, wherever) the plane starts to bounce off the ground to a 500-1000 ft altitude and then go down to the same altitude underground, repeating this process until it is destroyed eventually. It usually starts when slow enough to turn, but sometimes it waits till we're fully stopped. We made some tests : - start from Tarawa (cold) → bounce on runway (Kutaisi) - start from Tarawa (cold) → no bounce on Tarawa - start from runway (Tbilissi) → no bounce on Tarawa → no bounce on runway (Kutaisi) Could you please add this to the bug list ? Thanks ! PS : love this bird !

Thanks ! I tried it (lite version) and it worked, although I've got a problem that required uninstallation. Let me explain... Hopefully someone will step in and provide his/her experience. TL;DR : not sure it worked at first, my FPS were the same in the end ; also had to uninstall but don't know why. Here's what I did : 1. installed the mod and cleaned up the shader cache (both in terrain and saved games/fxo, saved games/metashaders2) 2. started up the game with MSAAx2 (previously I didn't use MSAA) and after about 20 minutes (yeah that's long) it generated almost 400 metashader files for 140MB, then started 3. noticed that FPS were good, as good as without MSAA before ; decided to crank up MSAA to x4 ; noticed that the mod was up (I think) because of a black ring around the FOV in the 2D screen mirror (but not in the HMD) 4. modified the setting, restarted the game 5. waited (main loading screen) forever, the log saying that a few shaders needed recompiling (having a MSAA4 in their name so I gathered it was because of the MSAA change) 6. gave up after 10 minutes with no progress whatsoever (nothing in the log, no change in the shader files) 7. restarted : same difference 8. reset to MSAAx2 : again, stuck 9. deleted all metashaders and restarted : stuck 10. got back to no mod and cleared shaders : worked after a few seconds 11. tried MSAAx2 without the mod : does not change FPS significantly. Any idea what went wrong ? Was the mod correctly installed ?

Wrong forum then buddy...

Was there a response to this post ? Didn't see it; I'd like to know, too, please.

Try this way : - activate DMT on the right mfd (using the mfd buttons) - click the left-top mfd button that reads "code" - enter a code (e.g. 1688 ) on the UFC and press ENT - kill stuff with laser guided ordnance ;)

Is there wind ? Anyway you'll have to watch your wind vane (just in front of your windscreen) to make sure you land into the wind ; then it's only a matter of training, gentle corrections, and avoiding pilot induced oscillations. Train, train, train and then train some more. Also, try this with a very light bird at first (1500lbs fuel, no pylons)

Just wanted to add (sorry for highjacking this thread) that when using the MFD export keys in VR it shows the image of the selected MFD as if projected on a big screen to the upper right of your cockpit ; I love that ;)

I read a good tip on mfd/keyboard usage with VR : stick a tiny bit of velcro/heavy tape to strategically chosen keys to help you find the buttons/keys you want easily...

I can confirm that when the Touch controllers are enabled in DCS, the mouse cursor disappears (latest release version)

Chaff used to be deployed in previous versions when using the dedicated Chaff Release button...

→ this

Hi there, I'm paraphrasing another thread in order to get this bug (behavior?) some visibility and (hopefully) to put it on Decoy's list. We spent a lot of time understanding what happened to us on our rented server, but the quick rundown is this : when DCS is started on a server without a sound card, or through Remote Desktop while not choosing "Play sounds on remote computer", the Harriers in the game make everything lag after a few minutes. The effect can be monitored on the CPU usage graph ; here's an example : Legend : 1: a Harrier has been chosen in the Roles window 3, 4, 5 : each spike (downwards) correspond to a huge lag as seen by the players 2: the player in the Harrier returned to the Spectators I post this here because it only happens with the Harrier and, while it has now a well-known and documented workaround, it may hide another, deeper bug. Decoy, what do you think ? I'm available to help in whatever way you want. I just have to restart our servers in the "wrong" way and join a flight with a Harrier...

Hi guys ! Thanks OP for this excellent thread, good idea to have it pinned. I've got a question : while experimenting with Oculus and DCS (vanilla version, not Steam) I noticed that the LeftCTL+KP7 and LeftCTL+KP8 did something : the oculus image froze, there was a sound like a device was disconnected, and the image moved again as if nothing happened (also the FPS changed). Are these new shortcuts added to Oculus to complement the CTL+KP1/2/3/4 ? What did it do ?

+1

Sorry Wags but I don't understand your answer (in context). Other than that, we also have this problem (sometimes, not always) in our MP missions.

Speed is probably not the same, too ; I don't know if this has an effect on radar...

I'd suggest to bind it to a keyboard shortcut (in the Control Options) ; it's very frustrating to start up a Harrier, line up the navigation system, then try and click on the "parking brake" but only succeed on hitting the fuel cutoff (which is right beside it) and shutting everything off :P

This works for me : I'm on a Acer Predator 34", 100hz GSync monitor, with an additional 12" 1080p 60hz for MFDs. If I turn GSync off, my Predator runs at 100hz and the MFDs at 60hz, with no visible stutter (to which I'm quite sensible, so I'd have noticed). If I turn it on, of course the Predator refresh rate adapts itself to the game fps, and the MFDs stay at 60hz ; still no stutter. I'm on Windows 10 with all the latest updates, Geforce 1080Ti (11GB) with the latest Nvidia driver, the Predator plugged on DisplayPort and the 12" on a DVI-HDMI adapter.

You need to trim when your speed changes, or your weight (e.g. when refueling, or dropping ordnance). Other than that it should not be necessary. You can also use autopilot ON, then OFF for a quick auto-trim