ShaunX

Fantastic little app which I can't believe I've only just discovered ! I do have a question.. Does anyone know if it's possible to change the keyboard output such that it writes to whatever might have the input focus rather than the scratchpad ? So I mean for the scenario where I finish a mission and while still in VR I want to save the track file, and name it something appropriate, or where I might want to pop into the ME and change mission start time or a waypoint altitude. Not laziness honestly, just that my VR Pit don't have no screen or keyboard VR Pit

I think ED made the point in their Marianas FAQ with their recommended VR requirements (for which I think we can read MINIMUM requirements) " RECOMMENDED VR SYSTEMS REQUIREMENTS (VR graphics settings): OS 64-bit Windows 8/10; DirectX11; CPU: Core i7-9700 / AMD Ryzen 3700X or better; RAM: 32 GB; Free hard disk space: 120 GB on Solid State Drive (SSD); Discrete video card NVIDIA GeForce GTX 2080 Ti / AMD Radeon RX 5700 or better " ..and those are the recommendations for the "VR" preset in system options, which are pretty low settings ! (I suspect they also do their VR testing with that preset too!) If I adopt the VR preset settings with my 5900X/3090 then sure, I get perfect locked 45 FPS low across Guam. But that rather defeats the reason for having a G2. I've done some testing this morning and and with my rig and regular high settings, CPU frametime is aound 8-9, which is reasonable, but GPU frametime is 18-19 (compared to 12-13 on Syria and sub 10 on Caucasus) I've tried starting with the VR preset and upping settings one at a time. I'm finding the biggest killers are Visible range, water and ansiotropic filtering (which is odd). I've set those first 2 those to medium and last to off against my regular high settings and the map over Guam is playable for me with MSAA x 2 (& Steam SS 80%). Reasonably well locked at 45 (though not while rolling). If you're struggling I'd suggest starting with the VR preset and see what you can add. Also, try setting up a basic mission flying out of an airfield on one of the Northern islands. There are far less terrain objects up there and the islands are still stunning.

When you defined the waypoint did you set its altitude correctly? In the mission editor you need to put 0 in the altitude and dcs will correct it automatically to whatever ground level is at that point.

I thought I had that exact issue this morning when I ran the instant action hornet mission on Marianas. Couldn't understand it until I realised that the mission is started on Active Pause so you have to press space bar to release it.

I've just tried the instant action again and even with no MSAA I can't get above 36-37 over Guam. However, with my home made basic mission I can get 45 most of the time so there's something up with the instant action. Worth a try. Also try taking off from the Northern islands' bases as they're much less demanding. I have to say once you get stable the terrain is really really nice on all of the islands.

We already kinda do. If you set shadows to low and terrain shadows to flat and then install Mustangs Flat Shadow Removal mod it removes ALL terrain shadows, but leaves you with cockpit shadows and your aircraft shadow ONLY, which is a realy nice compromiose.

Interesting - assume you mean WMR for Steam VR ? I've kept to the stable version of that for weeks now since an update screwed me up.

That IS disappointing for your spec, particularly with the mods you're running. Did you delete FXO/Metashaders 2 etc and allow to rebuild after the update ?

It seems the Marianas map is somewhat more demanding than Syria.. perhaps because it utilises features in the new EDGE 2.7 Engine ? With my rig and G2, optimised to @speed-of-heat's test 26 settings, I can't maintain 45 FPS flying low over Guam (whereas I can easily over Syria), and so I'm getting a lot of stuttering looking sidewards. The compromise for me is to loose MSAA and I can just about hold 45 FPS. Dropping Steam SS to 70% solidifies it but I don't like the image quality drop and increased aliasing. (I do still have reshade for VR enabled as I'm addicted to the clarity now). It's certainly worth the MSAA drop as the terrain is far more detailed than Syria. Another compromise is to keep MSAA x2 but just fly out of the Northern islands which are far less processing intensive and the tiny Farallon de Medinilla island North of those (situated in the bottom right hand corner of CT97 in the ME) is a handy official US bombing range. Hopefully there's optimisation to follow but still definately worth flying for me with a little compromise. Interested if others are having a similar experience ?

Just found it myself..Bottom right hand corner of CT97 in the ME. However, it has a large population of frigate birds, boobies, terns, and other species. The US DOD was ordered to cease bombing exercises on Farallon de Medinilla until they became compliant with the Migratory Bird Treaty Act. ..so make sure you turn birds off in settings before you level it

Same experience with my G2 rig. Can't maintain 45 FPS over land (over Guam at least, the lesser islands are better and managed to land on Tinian at 45 fps). I thought it might be the instant action mission so created a basic one for the Hornet, with clouds OFF and no A.I. Still couldn't maintain 45 FPS over Guam. It's a shame because the map looks excellent, but frankly uncomfortable with a G2 without motion smoothing below 45fps, and my rig is still buttery smooth flying low over Syria. ...just realised that sounded a tad ungrateful considering this is an entirely free map.Thanks ED for what looks like a beautiful map. Here's hoping it can be optimised a little for us ever complaining VR folk

Wow, if I wasn't on the wrong side of the pond I might be tempted to grab one as a backup at that price !

Hey @speed-of-heat ! Haven't done any testing for a few weeks now and thought I'd run your performance.trk this morning following the Windows and Nvidia updates. Unfortunately it no longer behaves the same way for me. Does the initial roll then instead of NOE flying it heads skywards and eventually dives into the dirt ! I've had this happen before to me with my own tracks across the initial 2.7 upgrade so I'm assuming some update since then has sent this out of whack. Or is it just me ? (BTW, sorry to hear about your throttle - fixable or RIP?)

Thanks, I've installed both this morning. No adverse effects. Is DCS smoother...you know, I think it just might be...

Bummer. Perhaps report the issue in that thread.

That's because you need the IC pass version of the mod for MP. See this thread ..

The answer is both really. Ideally you want to set up 2 profiles within OVGME using the "new" button at the top right, 1 which points at your saved games DCS folder and the other which points at your DCS installation folder. Then create a seperate mods folder in each of those profiles. Mods such as this one should be placed in your DCS installation mods folder, and you use the DCS installation ovgme profile to access and apply them. Other mods, such as aircraft and liveries mods, go in the saved games mods folder, and you used the saved games ovgme profile to access and apply them there. It's usually apparent which mods go where - saved games or installation, but you can always ask. Make sure that the mods you place in either of those mods folders have the correct folder structure. Their root folder should be the name of the mod, then below that the structure should match their target folders. So for example, this mod has the folder structure.. DCS VR Shaders mod for 2.7.0.4625 bazar shaders deferred enlight Materialfactory.. ..etc, because it writes files to the deferred, enlight and Materialfactory sub-folders in your DCS installation folder. ..so in this instance, all you need to do is place the "DCS VR Shaders mod for 2.7.0.4625" folder in your DCS installation ovgme folder. When you run that ovgme profile, you'll see that mod name listed and all you do is select it and click apply and you're done.

I started getting exactly the same issue following a 2.7 OB update, but changing input switching to manual has completely resolved it for me. I should have probably had it set to that in the first place.

You might also try going into WMR settings and change input switching to manual..

I was thinking about buying a new gaming seat to replace my old chair to give my aging bones a little more comfort. Then it occurred to me that the most comfortable I am when sitting for hours, is in my car. So I found and purchased an old Ford Galaxy passenger seat from a breakers yard on eBay. The chair cost £40. I stripped off the plastic fairings and angle ground the metal fittings off it. I also bought an 8’ x 4’ sheet of 18mm MDF for another £30 to build the frame. The base has 2 blocks to raise the seat to a comfortable height and as solid supports to attach the side panels.. Side panels are a simple ribbed construction, bolted onto the support blocks. I had a USB keyboard controller and some buttons and switches leftover from other projects so I made a button box.3 x 3 way momentary switches at the front and 5 additional buttons spaced to be easily located in VR.. Arm rests taken from an old office chair and throttle screwed in place.. Seat bolted onto the blocks using insert nuts. The seat is on it’s original rails so can me moved forward and backward as it would in the car. Seat back tilt and lumber support adjustment are also functional. Pedals fixed to the base and cable hidden.. Right panel bolted on. I added a table with a surround to the stick platform for a G2 controller and mouse. On reflection I should have made this bigger and will probably replace it. Actually don't really need a mouse as I have a wireless trackball hot glued to the stick, which is all I need to supplement headset pointer tracking in VR. Very happy with the end result, so much more comfortable and ergonomic than my old setup, and with all sundries included it was still only around £100 to build, so somewhat cheaper than a new gaming chair. (That's my G2, hanging from a hook on the side panel) Very easy build, though I do have a workshop with tablesaw, bandsaw etc. (For any woodworkers out there – I used a small amount of 18 mm birch ply which I already had for areas needing strong support for screws/insert nuts, such as the top layer of the blocks, as MDF is pretty useless in that respect. Ideally I would have done the whole build in birch ply, but sheet price in the UK has rocketed with Covid - £110/sheet from my normal supplier vs £30/sheet for MDF from B&Q) The paint job is just black emulsion with 4 coats of water based poly for protection. Doesn’t look great but hey, I can’t see it in VR anyway

Nice one

I think you meant to add those tests to your 3090 settings thread rather than here. I get very similar results and agree that the standard setting appears to be the way to go for now. Even that setting is a definite improvment over what we had, better contrast and definition and the wobbling has gone (though I also agree there's some major edge shimmering on them when looking towards the sun). Baby steps I guess.

I'd be pretty sure it's the known x570 mobo usb issue. Some boards work on all ports, some on just one or two, some work with a PCI-E card. My G2 wouldn't work with any port on my x570 (Asus Prime X570 Pro), nor would it work with an installed PCI-e USB card. Then I plugged an external, unpowered USB 3.0 hub into a mobo port and the G2 has worked flawlessly through that ever since. Even then I believe it's somewhat of a lottery as there are reports of even external USB 3 hubs not helping. Apparently the issue relates to certain x570 mobos with PCI-E gen 4 enabled. Some users have solved the problem by reverting to gen 3 in the bios as a workaround Table of x570 mobos reported with and without G2 issues.. https://airtable.com/shrhQQFoy4SQKIrjZ/tblvehlveGY2s7cu5

I don't see any performance hit and I never fly without them. Worth noting that with VA you can also define all of the 2 and 3 way warthog switch positions that DCS doesn't handle. I see we have very similar rigs. Have you turned Ryzen Master PBO on ? I get a measurable performance bump with it in DCS.

Glad you like it. The app is purely for creating standard DCS kneeboard images. You don't run it while you're flying. So yes, the created kneeboards are accessable in VR with the G2 by bringing up the DCS kneeboard as usual from which the kneeboard images can be paged through. Personally, I use it with the interactive kneeboard which is part of Viacom Pro which I'd highly recommend for VR.