SneakyBastd

I cannot figure out DLSS in MSFS. Prior to SU12, turning DLSS (with frame gen) on would make a huge difference. I went from 80fps to 120fps over new york @ 3440X1440. But after SU12 something totally broke DLSS. No DLSS setting makes any difference now. I'm stuck at the base frame rate. HAGS on/off, REBAR on/off, drivers, complete re-install, etc. Tried it all. I only play it in VR now, but a few more frames from DLSS would be nice.

Gunfreak, 850w is plenty for a 4090. I have 850w myself. Even if it set to 110% power limit it handles it fine. At about 70% power limit you draw 330-340w or so, which is about the same as my 3080 did.

I haven't messed with voltage curves, just set my power limit to 72% and mem to 12000. It barely drops any performance and uses 100w less power. I might try what you suggest later though.

Loving my crystal with 4090 so far. Quad views DFR is fantastic. Running high graphics settings at high framerate. The image is beautiful, deep blacks and good colours with a clean picture. It still has some problems though, namely audio delay and mic is basically not working. Both are being worked on by pimax I believe. Doesn't really bother me much, because a small audio delay in DCS isn't noticeable. It is when watching a movie though. And I use a modmic 5.0 wireless anyway.

Fwiw, I still use MSAA 2X. Just to get rid of the worst shimmer. I tried raising render res instead but it didn't fix it. There is still a slight shimmer, but better than what I had on the VP2. The shimmer is now minimal enough that I am not bothered by it anymore.

My 2c. I'm trialling a friends crystal while he is away. It is awesome. I'm coming from a vive, then 5k+ (tried a G2 also), and now a vive pro 2 (which is hobbled on 40x0 gpus). The vive console software is horrible (frequent random view stutter/hitching), and steamVR hinders performance. Ditching that for openXR is awesome. My 4090 can stretch its legs now. Pros: Visuals are as impressive as you've heard. Clear across almost all the FOV. FOV is about same width as VP2, but clearly more vertically. The panels are higher res, but it is the lens that steal the show. So clear. HLAlyx is seriously impressive. So sharp, so much detail in everything. Virtual Desktop showing my monitors, is like looking at 1440p monitor for real. Very clear. DCS runs a bit strangely. I have settings a little lower to hold 90fps. But when it dips below, even slightly, the view stutters when turning the plane. Not sure what is happening there. Lower fps shouldn't stutter like that. I think DCS will need smart smoothing (not working atm) to lock it at 45. Then we can raise details. Still, it's very good even now. Don't need labels anymore for aircraft. Cockpits are clear and easily read without zooming in or leaning forward (finally). MSFS runs really well. 67fps (feels pretty good, smooth enough) with highish settings native res. Very pretty game in the crystal. OpenXR doesn't have dynamic eye rendering yet, but it isn't far away from what I hear. That will also be an amazing addition. I can also use OpenXR Neck Safer now. Just having it installed would stop my VP2 from running DCS for some reason. Another great benefit of using openXR now. Cons: The headset is heavy. Not too bad to wear, but definitely some weight to it. Inertia when looking around. Not great for fast pace frantic games, but fine for sims. Batteries last just fine atm. Sound is good, having speakers off the ear is nice. The microphone is non functional atm. Smart smoothing is "coming". Also, the price... ouch. Can't run some games like Apollo11 VR. Not sure why, don't have time to fight with it. Flight sims are my priority atm. I have to return it on Saturday, but I'm convinced and ordered one for myself. A worthy upgrade from VP2/G2 class headsets for sure. Running 12700KF/64GB DDR4 3600/4090.

I also had to uninstall necksafer in order to get MT to run. Bummer.

@Voyager many people are complaining that 40x0 series GPUs on Vive Pro 2 is stuttering and laggy, unplayable. Are you not getting any of those problems??? I have VP2 and reluctant to upgrade to 4090 if I'm only going to get problems! For reference: https://forum.htc.com/topic/14223-nvidia-has-changed-the-render-pipeline-framedrops-on-vive-pro-2-rtx-4090/page/21/ Thanks.

I used vrPerfKit but it stopped working with this update. The force_steam_VR switch fixed it again, so all good. But I have VivePro2 which needs to use steamVR, so not sure why the switch is needed?

Yeah I don't get it either. Are they using VR??? When I went from 1080Ti to 3080 it was a huge jump.

No, that's working correctly. After you drop all your TOO1, you need to change each station to TOO2 so the remaining bombs know where to go. As far I understand it anyway. It would be cool if it switched the station to TOO2 before stepping automatically, but I have no idea if that's accurate IRL or not. Are you using QTY? If so I describe how that is working differently than in PP mode.

So I think it is actually working ok. I think I selected QTY for all stations with jdam, making 2 bombs go to a single point. I thought it would drop from each station selected, but still keep their independent targets. Nope. So I have to drop each bomb in turn. Pickle twice, select TOO2 each station, pickle twice. Then they target correctly. I just tried this with the same setup, but manually typed in the coords for each bomb using PP. And I CAN use QTY with both stations selected to drop, and each bomb still goes to its individual target. So I think TOO and PP behave differently here - perhaps that is the bug.

Using todays patch, I have 2 pylons with 2xGBU38 each. TOO on both. I use TGP to designate target coords for TOO1 and TOO2. Switching between them, the coords seem ok. Step to the other station. Designate TOO1 and TOO2. Again, seems ok. Step back to the original station, check TOO1/TOO2. They have now changed to the coords from the last designates. That is, TOO1 coords are the same on both stations. TOO2 coords are the same on each station. Dropping all 4 bombs, 2 bombs each hit the same coords. This seems like a bug, or is my process wrong? Thanks. Update: maybe a bug - QTY behaves differently with TOO/PP When using PP drops, you CAN use QTY. Each bomb guides to the coord you enter When using TOO drops, you can NOT use QTY. Multiple bombs will guide to one coord, no matter what you put in the TOO for each one.

It doesn't use WMR, it's vive software and steamvr. Thanks though.

Can I use this openXR with a vive pro 2? I don't know how it works, but it seems openXR means you no longer need steamVR right? But when I launch the Vive Console software, it opens steamVR automatically. Has anyone done this with VP2? Thanks.

Perhaps check preload radius. It was set to max on mine, I don't remember doing that myself. No other modules seemed to care, but apache frames went to hell. With a low preload radius value, my normal fps is back and it runs very well.

First flights with apache gave me horrible FPS. Turns out my preload radius was set to max. I don't remember putting it that high myself, but who knows? It did not cause problems with any of my other modules. Anyway, check that maybe. With a sensible value fps went back to normal.

Does anyone know of a 3D printed file for the black part with the 3 bolt holes in it? I can make one up in some cad software, but figured why reinvent the wheel if someone else has done it. I'm doing this from sourced parts, as shipping made it very expensive (DHL only for a 600g package!).

Thanks, but I have only ever used Broadcast Parallel. VOIP control remains on broadcast parallel, with all of its options unchecked.

Tried turning it off. All it did was make the radio menu appear in game. Only every second voice command would work then. I'd press transmit, the menu would disappear, and then the voice command worked. When no menu was visible, pushing press to talk made the menu come up, and then the voice command was ignored.

Thankyou for your suggestions. I'll try that over the next few days. VAICOM already has broadcast parallel selected. SRS Allow VAICOM TX Inhibit is currently ON - I'll try turning that off as you suggest.

After more experimenting, it seems it is SRS that is causing issues. I can have SRS running and just do a custom mission or freeflight, and VA commands work perfectly all day long. But as soon as I join a multiplayer server that uses SRS, I start getting strange button behaviour. I can hold down the radio PTT button on my hotas, but it cuts out half way through me speaking a command - that is, I can see VA stop listening even though the PTT button is still held down. This does not happen when DCS is closed, or when DCS is in an offline mission.

Hi guys. I've got a problem with VA. In DCS, I can press the listen button, say a command, and release the listen button. The command works just fine. Maybe this works a few times, maybe 20 times. But sooner or later, it hears something it doesn't recognise, and from that point on the "listening" icon in VA with the headphones has the red crossed out circle on it. Pressing the listen button again will never remove the red crossed circle. So it can never action anything I say again. Sometimes, after waiting awhile, I can say commands again (it starts to listen) but mostly it is just dead until I restart VA. Please note that this only happens to VA when playing DCS. If I don't open DCS and just press to talk, issuing commands to VA, I can do it all day long without issue. It recognises everything I say, and even when it doesn't, I can just immediately try the command again. The red crossed out circle ALWAYS goes away when I press to talk. Any ideas why VA cracks it and refuses to listen after an unrecognised command in DCS only? Thanks.

dcs.20220129-042214.dmpdcs.20220129-042214.crashserver-20220129-151118.trkHi. I made a multiplayer training miz for my mates to teach them slamER steerpoints. It crashed the game for each client connect the moment I pickled a slamER. My game kept running no problem, but everyone else DCS crashed. Server track and log files attached. We set up 1 slamER each, with 5 steerpoints, individual altitude per steerpoint, and then designated a waypoint for the final target point. Doing this same mission file in single player, it works without a problem. dcs.log

Agree with Taz. Get 32GB 3200/3600MHz and whatever GPU you can afford. Wouldn't hurt to overclock the CPU also. Check link below. You can see that even with my recent upgrade, GPU is still far and away the limiting factor. The CPU overhead is nice to have - it helps to smooth out frame drops, but a faster GPU is always going to help more.