Wizard1393

+1

If I didn’t miss news about its completion, TERM guidance settings for JSOW and JDAM is still not implemented/completed. Sounds about right that it would then also apply to the SLAM/SLAM-ER.

I don't use Windows Defender, I have it completely disabled so that's not an issue for me. It seems to me that something does not "unload properly" when going back to cockpit. But I'm no game developer so this is just guesswork of mine really. My hardware setup are in my sig if that helps at all... Good to know you're tracking the issue at least.

Too bad F10 map is still unusable in VR. Still halves the FPS / makes it all juddery when going back to cockpit. Other than that, great patch!

Still having this issue myself. Started a long time ago. I avoid using the F10 map alltogether. Most times (not always) the issue can be corrected when alt-tabbing out of the game for 5-10 seconds, then back again. This tells me there should be something that can be done code-wise how the game unloads recourses loaded when bringing up the map...

Still having this issue myself. Started a long time ago. I avoid using the F10 map alltogether. Most times (not always) the issue can be corrected when alt-tabbing out of the game for 5-10 seconds, then back again. This tells me there should be something that can be done code-wise how the game unloads resources loaded when bringing up the map...

+1 to MP campaign possibilities!

If you've followed all instructions correctly, persistence (state saving) is done automatically every 5 minutes iirc.

I'm on a Reverb G2 100% and PD 1.0, and I like the new spotting dot system overall, but sure it can be tuned a bit. Here's my take on it: In my opinion they are drawn too far out. They could definitely start to fade in at a closer distance, perhaps around 15 miles, starting at 100% transparent going to fully visible at around 7 miles. Then they could fade out from 7 miles to perhaps 3 miles where the actual model is about the same size as the spotting dot. The dots could also be reduced in size by 25-50 percent. I especially don't like that there's a sharp "cutoff-point" where the dot disappears at what I estimate to roughly 5 miles and makes me loose tally. I would like the dots to be more gradually drawn, going from transparent at range, to solid mid-range and then back to transparent when in close and dot size ~= model size instead.

my bad mate. I thought I did. Must've thunk it and not wrote it xD

I was under the impression that this wasn’t needed when spawning in Hot/In Air.

SOI the HMCS, designate a target, SOI TGP and refine target, TDC-depress to redesignate/update target, go in on a gun run, the target designation box in the HUD will not be on the target, making it very hard to spot your actual target. Is it supposed to be this inaccurate, or am I doing something wrong?

Still having this issue also. Can't use the F10 map anymore, it always lowers FPS to ~20 and will not return to normal after going back to F1 view. Have to restart DCS to resolve the issue.

I don’t know, but my guess is they will still make a difference VRAM wise. I don’t think ED has done much with textures for this patch though I’m unsure how much of a difference their work on LOD’s does for VRAM usage. I just enabled the mod in my mod manager and ran with it. Haven’t done any proper testing.

Yes. Still works.

So I find myself still struggling with understanding the details around the following: Does anyone know if there's a difference between downscaling with OpenXR Custom Render Scale or using in-game Pixel Density? Is there a quality or performance difference between them, especially when used in conjuction with the new DLSS setting?

To clarify further, the number on the HUD is the laser rangefinder "cooldown" timer. Do not fire another missile or range a new target until this counter has come to 0 and disappears, otherwise you risk overheating the laser and damaging and degrading it's performance.

+1

I have this issue with my Reverb G2. Reprojection has always been off. Latest DCS, no mods. Specs in my sig. The same issue sometimes also occur when switching to another aircraft type in the same mission. Sometimes, ALT-TAB once or a couple of times helps, but not always.

Yes. Same as this thread:

Yes, noticed. I've got a Reverb G2 running Open XR without Steam. My headset goes completely black during any kind of loading.

I have this issue aswell. I've been flying mostly on Syria and with the F-14/18 and Apache. This issue has been around for quite a long time for me. Long before the MT release. It happens often when checking the F10 map and going back to F1 view, the whole rendering is very weird and stuttery and won't go away. It also happens very often if killed and/or respawning in a new slot, same Aircraft type or not. Pretty much always avoiding the F10 map for now due to this. Complete DCS restart is the only thing that helps.

Thanks for the feedback HB!

So I just had a go at this mission. I got moved to CAP station south, went 10 or so passed between the new WPT2 and WPT3, then I got "final MiG splashed" and got vectored to tanker. But it seemed like the tanker was already on its way back to Incirlik because I was barely closing in on him at all. Steered to home plate instead and when passing overhead the base, Jester told me to switch air source and extend the probe. I ignored this and landed normally on the base. The tanker was already there in it's spot. I got mission failed since something must have gotten borked.

Ohhh, I was under the impression that this was no longer an issue for anyone with WMR and OpenXR. I stand corrected then I guess.