laertesson

I am using the Reverb with motionvector reprojection. I basically use your VR settings plus high terrain textures and no shadows. I have been considering trying 70% render resolution or something. Frametimes are high on the GPU while CPU seems to keep up okay. I could try low terrain textures but according to some of the settings comparisons people have posted it doesn't make that much of a difference. I'm also playing on Syria a lot lately, so that never helps getting good performance. i7-9700K @ 5.1GHz RTX 2080 Ti 11GB 32GB 3000MHz DDR4

mod seems to work on the new patch. not 100% sure though. anyone know any way to get rid of stuttering? i get fine fps but the game still stutters consistently. and been getting worse with each patch.

Yep, I just use the dispersion from the weapons mod for SP. So much better and the cannon is actually usable that way, not a shotgun.

I think this problem is my fault, no bug.

The JF now features baked-in reflections on the canopy, HUD, and MFD screens, these are not well liked in DCS VR community and ED has now added “special” options to turn them on and off. Is there any chance DEKA will follow suit. There are mods available on userfiles for the HUD and canopy already but there’s no mod to fix the MFCD reflections (they are integrated with the dirt/fingerprint textures which look great any way you consume DCS)

IMO they’re doing a HELL of a lot better than heatblur in 2020. F-14 and viggen state is disappointing compared to where they said everything would be in late ‘20. DIS is the new god in my eyes.

How is this going? Afterburner is still very sad.

Razbam’s behavior and actions in this train wreck of a thread (not to mention throughout the life of the Harrier and this forum) have ensured they’ll never get another buck from me. I think they’re in over their head in many ways (except of course artwork and new models, they’re sure good at that, but that’s not why we play DCS.)

Since it’s ED’s feature I hope it undergoes fixing soon. Definitely doesn’t seem like a finished feature but still anything’s worth improved performance.

Frustum culling + this shader mod has allowed me to play the new Syria map at acceptable framerates, thank you.

So I have been trying to hit tanks in mountainous terrain with CCIP. It is inaccurate with DTSAS. Bombs always fall slightly short or far. The solution is to use the data rocker to input target altitude. My question is, how do I know when I am using HOT and when am I using DTS? I am assuming once you switch off a steerpoint that has been manually edited, DTS turns back on? But I truly have no idea, I would really appreciate an explanation.

It’s clearly not drag and drop. And all Vulkan implementations aren’t created equally, so I’m thankful ED appears to be taking their time to do due diligence. Another part of me hopes it’s coming soon, because VR performance is still such a rough subject.

Every time, and if I destroy more than one ground unit in a certain area, frames really tank

Hi, this issue is really bad in VR and has only gotten worse lately. Are there any settings I can change to make this more bearable?

Sort of unrelated, and I’ve probably missed most of this conversation, but should we expect to see new flight model of laser rockets anytime soon?

I wonder if there is a way to modify the FAB100s so they have a drop “chunk” sound, they are silent now. Either way I very much enjoy and appreciate the new options. TERs look amazing on the JF-17.

Id be happy to use simplified warning light shaders mode for VR. They look fantastic if you have the performance headroom but I don’t think DCS VR users almost ever do. I’ll double check it once I extinguish them all if the frames go back up when supersampling, but the startup process almost makes me sick the FPS is so low when PD > 1.5.

I can totally confirm that when running very high supersampling, the JF has HUGE frame drops as soon as I turn on the battery. If the battery is off, runs butter smooth. When SS is turned down and MSAA is on, I don’t notice it. I should add that I have no problem running even higher supersampling in modules like the F-14. I recommend trying a VR setup with high resolution to reproduce . I doubt there is an issue otherwise.

EDIT: ive finally narrowed it down to a binding issue, not a WMD7 issue. When I lock target using the keyboard, or my Warthog throttle, it works. But I cannot lock target using my Warthog stick. At least the nightmare is somewhat solved. It looks like it was just some very complicated double bindings, and I will have to delete my config folder. It's incredibly annoying because if I press the button in adjust controls, it says its bound to lock target, but doesnt work in game.

Thanks for the video, that surely is the sound I'm talking about. It's a bit like the WIP sounds we're hearing now to me, just needs a bit of refinement.

Yeah I did, I saw the change log but did not click the link to get the picture for more info, now I understand.

Hi, I flew JF last night for one of the first time in 2020. I turned on oxygen valve and connected hose as always, sealed the canopy and turned on ECS. When I flew over the target zone I pulled turns 4.5-6G, and blacked out. I’m wondering if I was overheating because of PG temps? Is there a new feature im missing? Edit: apparently yes, sorry about the redundant g suit question, I believe I found out why it’s happening at the least

This point is fully negated by the fact that they’ve been advertising MC as a Huey feature forever.

I so hope a bit more time is spent porting NS to different modules. I’d imagine it would actually be pretty good money for Aerges to add it to UH-1 especially, using the knowledge gained with this C101 implementation.

Same here, apologies if it’s in a thread somewhere but I did not remember hearing anything since then.