=Panther=

You don't have to rush, the AI takeoff on script and will despawn and respawn when you are at certain positions along the flight path.

Paper ones are still there.

I do believe more support for handicaps are needed. Seems it get lost that although this a simulator, but most who enjoy the game are not pilots. Some which may not qualify to be a pilot, which includes health related issues, like vision.

Roll back to previous patch or wait for the next patch and pray it fixes the issue.

Not a bug, it is to grab the attention that the system isn’t operating.

Especially the Tank Inerting switch.

This thread may help those with the combined controllers and or the long delay. https://forums.eagle.ru/showthread.php?t=232737 In short Microsoft Windows Store is a culprit most of the time. There are a few ways to handle the store, depending on what you want to accomplish e.g. uninstall, kill it until restart, etc.

You're not alone.

DCS can use either or, not just Oculus. Yes I use SteamVR with an Oculus headset playing DCS.

The strobe gets power from the generator after the engine is spooled up, exactly like is in real life. Military (USA, maybe not all but most) fighter aircraft don't have power to the lights until at least one engine is online.

Yes, allows for better solutions when streaming to Twitch while in VR.

What is the confusion?

Version: 2.5.6.49314, Standalone Testing system used: Win 10 x64 GTX 1080TI i9-9900k 32GB Ram DCS installed on M.2 VR system: Oculus Rift S (using steamVR SS=199% for pure testing purposes) Prior to this patch I was receiving horrible FPS in a vfw mission: <15 FPS with several stutters and black displays in the HMD. It was the first time since going to VR that I lost all motivation to fly, it was just awful. Patched to the latest version as indicated above and decided to try out the new adjustments. Using same configuration as prior to the patch with the MSAA off I saw FPS locked at 40FPS. MSAA to 2x: 40FPS (Mask 1.0) MSAA to 4x: 40FPS (Mask 1.0) Adjusted mask value had no affect on performance of FPS but did see it actually working. A lowest value of .10 I could see a tiny clean box in front of my view. I adjusted the MSAA Mask while in the jet (it is live and adjustable from in the jet while in options menu). I slowly brought the value out to .45 which is where the jagged lines disappeared to the left and right of my rift s. Throughout the test FPS remained 40 both reported by DCS ingame counter, and the Steam fpsVR. Here is example of my VR configuration, note this is only VR and graphics, not the entire config.lua. ["VR"] = { ["bloom"] = false, ["box_mouse_cursor"] = true, ["custom_IPD"] = 58, ["custom_IPD_enable"] = true, ["enable"] = true, ["hand_controllers"] = false, ["interaction_with_grip_only"] = false, ["msaaMaskSize"] = 0.45, ["pixel_density"] = 1, ["prefer_built_in_audio"] = false, ["use_mouse"] = true, }, ["format"] = 1, ["graphics"] = { ["DOF"] = 0, ["LensEffects"] = 0, ["MSAA"] = 2, ["SSAA"] = 0, ["SSAO"] = 0, ["SSLR"] = 0, ["anisotropy"] = 4, ["aspect"] = 1.7777777777778, ["chimneySmokeDensity"] = 1, ["civTraffic"] = "", ["clouds"] = 1, ["clutterMaxDistance"] = 0, ["cockpitGI"] = 0, ["effects"] = 3, ["flatTerrainShadows"] = 2, ["forestDistanceFactor"] = 0.3, ["fullScreen"] = false, ["heatBlr"] = 0, ["height"] = 1080, ["lights"] = 2, ["messagesFontScale"] = 1, ["motionBlur"] = 0, ["multiMonitorSetup"] = "1camera", ["outputGamma"] = 1.2, ["preloadRadius"] = 60000, ["rainDroplets"] = true, ["scaleGui"] = 1, ["shadowTree"] = false, ["shadows"] = 0, ["sync"] = false, ["terrainTextures"] = "max", ["textures"] = 2, ["treesVisibility"] = 6000, ["useDeferredShading"] = 1, ["visibRange"] = "High", ["water"] = 2, ["width"] = 1920,

Glad it is sorted. Regarding size of track, most use a cloud to upload it temporarily.

I don't have a solution, but I'll add myself to the list who has an odd issue when taking the headset off mid-game. My issue is a little more severe than the OP, I lose the ability to interact with the game at all. So I have to go to desktop and force close via task manager. No clue why, but I think Oculus is the issue, because I have multiple installs of DCS (including 2.5.4) and this is new across all versions.

A trk file would help. There is no "INS Bug" the actual issue is redair doesn't use GPS for alignment. So the manual mode to align is highlighted in post 49 and several other post in this thread. If your waypoint data appears to be frozen as you're flying, then you didn't align manually as instructed. However, we don't really know without a trk file. Fly the mission, and when you get the issue, exit out and hit the save track option on the debrief screen. Share it here for others to review and try to duplicate the issue.

Just set the middle screen as the default primary screen in your monitor configuration in your windows control panel.

I think that is the problem, the code for the lights is (I don't know, only assuming) shared between all. So for one to be brighter, the others also grow brighter.

There is no MWS on the Viper in DCS.

W.A.G.... x, y, z values. YMMV and I can be completely wrong. so good luck. }, [13] = {--default view viewAngle = 54.176285,--FOV hAngle = -1.233092, vAngle = -9.922364, x_trans = 0.021000, y_trans = 0.091809, z_trans = -0.004051, rollAngle = 0.000000, cockpit_version = 0, },

A track would be helpful, because the RWR also makes beeps. However there is no audio associated with the laser or gbu delivery.

If they are compatible you can just browse to the saved games/dcs folder that you have them saved via the load mission window. Another option is to copy/paste the missions over. If you want to carry over your progress, that is found in your logbook, which is also in the saved games directory.

Looks to me the altimeter wasn’t set per the mission weather.

So are we getting coordinates on TPOD?

They say it isn't a thing. https://forums.eagle.ru/showthread.php?t=256326&highlight=bump