AhSoul

Tried with the link cable and ASW 45 (with the headset on 90). Definitely felt smoother, though the graphics looks muddier compared to VD, so I assume I need to play about with the Oculus App and Debug settings. Weirdly it doesn't seem to be running OpenXR like it does with VD though. I've used the OpenComposite tool to make OpenXR the default, and in the Oculus app it says the Oculus Runtime isn't the default, and Steam VR isn't running, but I don't get the OpenXR overlays. So I assume it's using Oculus?

Yeah I'm probably getting confused - so many tools to mess with....

But he's setting his FOV Multiplier to 0.65, so must be cropping a massive chunk of the view???

This guy also has a 3080ti, and isn't using DLSS or ASW, and his game seems to be on higher settings than mine with no visible stutter and a solid 72fps. ok his CPU is and i9900 and he has 64Gb of ram though....

Also should I use ASW in Oculus Tray Tool or OpenXR?

I tried ASW at 72 (so halved to 36) and got weird artifacts and stuff. I'm sure when I tried VR ages ago with my Quest 2 ASW gave me crazy ghosting e.g. aircraft or buildings to the side of me. Would things be different at 45/90?

How much VRAM do we need???

I'm wondering about the 4080 Super about to come out. It's like 1/2 the price of the 4090 and I guess can't be thaaaaaat far off in terms of power? Someone on Reddit suggested I shouldn't use VD but use the link cable. Do we know that the cable is definitely the better option? It looks worse to me when I try it....

I've done most of that (I think I still have the clouds on 'standard') - pretty much changing one at a time to see what makes a difference. Kinda feels like I've gone as low in terms of detail as I want to get - I don't want to play in VR if it looks <profanity> I guess Maybe hardware is the only solution - just not sure which thing to change first. Feels like there's so many variables though.... Very useful! Just thought, I don't have vsync on - it's still off from when I was playing on my Gsync monitor. Should I turn it back on again for VR?

Wouldn't that make my framerate worse, given there's no upscaling?

I recently got a Quest 3 and am dipping my toes into DCS VR. My specs are Intel 12600KF 32Gb DDR4 at 3600 3080Ti I'm running MT DCS, Virtual Desktop (it looks nicer to me than link cable, I guess due to the better codec?) and OpenXR, and with DLSS on I'm just about hitting 72FPS in Instant Action missions on Caucasus (I don't want to use ASW). I'm not able to keep it to 72 though if there's a lot going on, smoke etc. Other maps like Syria reduce my FPS, some modules get me better FPS than others too - the Apache for example seems to be a lot more taxing. I'm also getting stuttering even when at my target FPS - if I look forward the ground looks smooth, but if I look to the side the ground seems to 'jump'. I'd prefer not to use DLSS - it makes everything less clear even with sharpening on - so I'm trying to work out whether I need to upgrade everything or just my GPU so I could stop turn it off and use MSAA instead. The FPS monitor in DCS seems to suggest I'm CPU bound (main thread?) but then the OpenXR Overlay seems to suggest I keep running out of GPU headroom. So I'm not entirely sure which direction to go in first!

I'm starting to think it might be 'broken' in the module itself. That switch seems to generally have some interesting behaviour: https://www.reddit.com/r/hoggit/comments/nfwjsm/f16_autopilot_3_position_switch/

Thanks @bones1014 I might see if I can find some difference between how the Roll button (3014) has been coded vs Pitch (3013).

Anyone using the SD with the F-16 and having issues getting the Autopilot Pitch switch to behave? I can set the Roll switch to either of the 3 values (-1,0,1) fine but the Pitch one just doesn't seem to work. If I try and set it to 1, it moves. If I try and set it to 0 it doesn't, and sending -1 sets it to 0

@Trigati all seems to be working from my quick testing. Thanks so much

OK will give that a go now

I'm not seeing any of the fuel or engine readouts either.

Interestingly the SD buttons still push the UFC buttons, so it seems to be just the outputs that changed. @Trigati are you still the best person to fix the lua?

Has today's DCS patch broken the UFC output for everyone? Or just me?

I'll ping you in discord

Ahhh I thought the overheating was in. Cool, will turn it off

@skypickle I did wonder about doing a 'start' page in my profile as you say. However you could do that with my profile now - wouldn't be too hard to just move the buttons around (or duplicate them) to a new page. I'm pretty sure on my pages you'll find everything you needed. I've done the cold start training mission with it.

https://www.digitalcombatsimulator.com/en/files/3331753/ F-15E Pilot and WSO profiles. Mostly just text buttons, easier to read (for me) than lots of graphical switches etc. Couple of example screenshots....

If we all think it's better in the long run to not have the 2 sets of outputs in the file (labels and raw), then we should remove them. We only suggested them originally as it seemed a pretty simple thing to do that would help some people, but if it's going to make it harder to maintain and/or cause a performance hit... It's just the fuel and engine sections right?

@Trigati works for me. It's the only one that has lbs in the label anyway. Might bother people that want it exactly like the text in the cockpit but I'm fine with it