mrprime

What's unfinished on FC3 planes?

Also noticed this and would also like to know if it's intended behaviour or not, I would assume it's not correct as regardless of whether you're on or bypass the pilot would want to know their CM levels.

OP pretty much reflects my experience with the Spit to date. I appreciate the majority of consumer sticks have nowhere near the throw of the stick in the spit, but I have a Virpil WarBRD base with no extension and find the spit uncontrollably twitchy without heavily desaturating the pitch/roll axis. There's very little feedback in the aircraft for when it's about to do something crazy. Dog fighting with wake turbulence enabled really exaggerates these issues where flying through the trail of an aircraft a couple hundred feet ahead of you can flip the spit upside its head. I understand the need to 'git gud' but I really think this module is asking too much of the user when compared to other WW2 modules that don't suffer these issues. Seemingly everyone uses aggressive curves as a necessity, and requires that we can maintain the flight envelope with no significant audio/visual feedback for what the aircraft is about to do. In real life you'd have a better sense of the wind, the vibrations in the pit and through the stick, we get none of that and it's pretty tough to fill in the gaps.

+1 DCS really should have native OpenXR support. With then release of headsets like the Reverb G2, and the increased effort from MS on OpenXR with improvements and new features for MSFS and Squadrons, it would seem like we're missing out a bit. Having SteamVR in the loop adds a whole layer of unnecessary abstraction for WMR users who have to run two VR apps simultaneously to get DCS to run. If DCS is going to take VR seriously there really should be native support for the major headsets.

Sorry I'm not sure how, I removed all the assets and that just leaves a skybox by default. I wouldn't recommend making the change considering the bug it produces currently, but I'd be all in favour for a 'blank' VR environment if anyone else knows how.

This is more of an oddity and (to my knowledge) can only be hit by fiddling with .lua files, but it's an oddity that suggests to me that something's not quite right. Also this behaviour is quite recent, not sure exactly when as I've only recently gotten back in to VR but it wasn't an issue 6 months ago when I was last active. I don't like the default VR hanger so I removed all the geometry in the lua file, which just gives an empty sky box. The VR hanger is used as the background when doing the F10 map. When I go back to game from the F10 map, lighting effects from the hanger continue to be visible. This is most noticeable at night, but also during the day (I thought it was some new visor effect initially!) First screenshot: In game, everything as it should be. Second screenshot, F10 map with my minimalist background Third screenshot, returned to game after being in F10 map - lights from the environment persist To reproduce this issue: Download 'sceneVR.lua' to your DCS World OpenBeta\Scripts\DemoScenes folder Open DCS in VR Go in to any mission (ideally a night mission where this is most obvious) Hit F10 to bring up the map Hit F1 to return to pilot position >> Graphical effects from the VR environment continue to be visible Obviously the solution here is to not mess with the default VR environment, but it seems odd that effects in that environment aren't being cleared up when switching from F1/F10 so I wonder if that is causing other, more subtle issues. sceneVR.lua

Adding to this - I get it most commonly in WW2, for me this is 100% reproducible in the Spitfire 'Fw 190 A8 Dogfight' instant action mission in The Channel, the first few frames there'll be at least one 'flash'. It gets progressively worse as time goes on, not sure of any rhyme or reason. I've attached a short track. I've uploaded a quick clip of what I see during that track: You can see the first few flashes right at the start of the mission, then again it starts happening at 04:23 - captured and attached a still image. I'm on a 2080 with the latest nvidia drivers at time of writing (457.30) WW2Flashing.trk

+1, there is nothing worse than having the cross over something but the actual cursor is AWOL

+1, rwr volume is something I frequently bind in all modules because it’s almost always something that bugs me and I want to quickly adjust in the air, I don’t think I know of any other module where this isn’t bendable.

Start-up as normal and switch the middle MFD on and set your INS knob to 'GND'/'CV' as appropriate. Once that's done, on the HSI page on the middle MFD you'll see a new option 'STD HDG' along the bottom row. Box that, and you'll get the 90 second align (it takes a couple of seconds to get going)

+1 on this, coming from multiplayer to singleplayer I find this really jarring and unnecessary - please make it optional.

You can't throw money at these problems and expect them to go faster, 9 women can't deliver a baby in a month, stuff takes time. I worked on a project based on UE3 codebase that ported to Vulkan and it took well over a year, full time, of a very experienced programmer who specialised in rendering, and while UE3 wasn't the greatest game engine, there was at least support and places he could turn, I should imagine doing this work with proprietary tech is.. daunting.

Did you ever find a happy setup? I have exactly the same stick/base and am struggling to get find decent settings.

+1 on this, it's impossible to adjust the lighting in the cockpit to not have crazy glare in the NVG, I'm not sure if this is realistic or not but considering it's the same effect as other NVG's in the game that do have gain settings, this seems like something that should be available.

Fixed for me also on latest OB, hopefully this makes its way to stable soon.

+1 on this, don't have a track but I've been in RWS to STT and unable to drop lock because the unlock button keeps switching target like it's in TWS. Very very annoying. Had to turn cold on targets in order to break the radar out of wanting to bounce between locks.

I've attached a track to help with diagnosis, Single player mission, cold start on ramp Connect external air, Power up left and right engines, Turn on external lights and cockpit lights (all work correctly), Turn on taxi lights - nothing happens F5_NoTaxiLights.trk

As you have an nvidia card you're best off setting the frame rate limit in the nvidia control panel - attached a pic of where to find it. I've also attached a picture of my OBS recording settings, I have a very similar system to you (i9-9900k + 2080 non-ti).

Open task manager while playing and look at your GPU load, if GPU is hitting 100% that will confirm the problem. Windows allocates system resources based on the selected app, so when game is selected it's being prioritised, and vice versa. You could add a frame rate cap to DCS or lower settings to free up GPU time for OBS, but considering you have vast amounts on CPU resources not doing anything I wouldn't recommend that. x264 with CPU profile of fast/medium (or below) will give superior results anyway, so you have nothing to lose.

What encoder are you using in OBS? hazarding a guess if you're using NVENC, your GPU is getting completely saturated and so the OBS encoding is getting depriortised when the window doesn't have focus. Regarding happening after you upgraded monitor, the higher resolution will put more demand on GPU, and if you used to fly with vsync then with 120hz there'll be even more asked of it. Given your system I'd recommend using the x264 (CPU) encoder, rather than GPU. Because DCS doesn't scale on threads/cores, you've got masses of CPU time not contributing, whereas I'm guessing the GPU is maxed out.

You're absolutely right :thumbup: I had an old install in the base game directory from 2018, didn't even remember trying it back then! thanks for the assist, works like a charm.

That's where I installed it.

+1, can't get taxi light to work at all

Trying to get this working on 2.5.6.49718 (never tried it previously) and I'm hitting warnings when I open DCS, Tracking back up the log, there's a couple of interesting lines, and later, Any ideas? tried removing options.lua but to no avail

Strong agree on WW2 asset pack, perhaps it made sense at the time but I think that's changed. Imo, with the Channel map coming, new WW2 damage model, P-47 etc, WW2 in DCS is really shaping up. I believe it'd be a long term benefit of WW2 in DCS to use this opportunity to ditch the asset pack and include it in the base game, and for those who already shelled out, give them the relevant discount on the Channel map. Sorted.