mhe

I will try it out asap and get back to you with results, thanks again!

Thanks for the quick reply, I'll try that then!

I have this weird issue when I try to use the Reshade Sharpener and the Kegetys Shader Mod simultaneously, my loading times go through the bloody roof, I have to wait several minutes for anything to load. Any ideas what causes this? As soon as I remove either, things go back to normal.

Hab den ReShade VR Mod auch am Laufen, der absolute Wahnsinn wie viel Unterschied das macht. Und Performance leidet null drunter.

A man can dream: Being able to manipulate the controls like that in DCS (sans HOTAS, since we have hardware for that) would be a dream.

What firmware does your stick run? I remember on mine that a when I ran firmware from a long time ago, it would get a different USB device ID every time it was connected, making re-binding everything necessary. So update your stick to the latest firmware first and see if it goes away.

Any chance you got the stereo parser tweak activated in your autoexec.cfg?

Even if I have a CM3 throttle running with idle cutoffs and afterburner detent perfectly tuned for my go-to planes, it would still be very nice if DCS offered this capability, just like BMS does. It sure isn't rocket science, but it would go a long way for people who don't want to spend hours messing about with firmware configs, deadzones etc. In the end, if you have better or same capability with a lot less friction in usability, your product will be superior for it.

Downgrading to PCIE 3.0 Setting should stop being necessary once your particular mainboard gets the next BIOS update that includes the newest AGESA version.

It's Friday, give it a few hours!

I recently got around to watch a nice interview with ED's Simon Pearson that is a few months old right now: At 47:17 Simon says "Of course we're doing the mission editor, we're doing all the ground units as well and we're doing the weather and we're doing the voice chat and we're doing the new Earth module." Anybody know what he was referring to? I don't think he meant the Apache that got announced at the end of the year in the trailer, as I would think he'd rather call that a ground warfare module or something similar. I don't want to start a hype train here, but the way it was called is indeed intriguing. Maybe some kind of procedural generation terrain engine that can later be refined with handcrafted high detail terrain areas, similar to what that other big civilian sim does? @BIGNEWY maybe can clarify for the curious bunch that we are?

Thanks gents, I learned something today.

What is an ASPI if you don't mind me asking? I have a lot to learn on Apache systems.

Came across a video where somebody tests the Gazelle FM against flight data logged by the military tests. Maybe it has been posted before, but I couldn't find it even when searching for the substrings of the video link, so I guess it might still be news to people here.

So do we all, especially the VR users will rejoice with any performance improvements that can be had. I had the pleasure of occasionally experiencing 90fps without reprojection in very particular situations in DCS and it was something to behold. Having that buttery smooth performance without having to dial down your visuals so much would be pure joy. Flying through those new clouds in VR with framerate so stable that it could be real life, it would be mesmerizing to say the very least.

Yes, which is why ED is not only switching to Vulkan, but also overhauling the threading system of the engine, so it finally uses more than one (well, technically two) CPU cores. It is correct that Vulkan alone doesn't help much unless you also get rid of other bottlenecks. But the multihreading overhaul is on the roadmap for Q3 just like Vulkan is.

@BIGNEWY I know you have no news to share with us, but maybe these news shared with you and the team might be helpful: https://store.steampowered.com/news/app/250820/view/3044967019267211914 tl;dr: SteamVR 1.16 brings full OpenXR compliance into SteamVR. Since Oculus also does that, you could start migrating to OpenXR and only have to maintain 1 API instead of the current 2 (SteamVR and Oculus). That would also be super helpful for the people running WMR headsets since the performance gain should be substantial by just utilizing OpenXR alone (WMR via SteamVR copies the framebuffer between the 2, not the most elegant solution).

@BIGNEWY Mesh Shading is available in Vulkan. Hence the question. Any statement on that? Of course it is not supported by all the graphics cards dating back to the stone ages, but as an option it would be tremendously helpful, especially for the VR players as they tend to run cards that can make use of it.

This would be a dream come true and tremendously help frames, especially in VR. And timing is just right since Vulkan was announced for later this year. Does the dev team have Mesh Shaders on their radar? @BIGNEWY

Okay, I got it to work occasionally, but it is really nowhere near the reliability of the Hog's system. And it seems to like to look down from higher up, with flatter angles it doesn't seem to work that reliably. Also, seems like it is much easier to pick up marked targets than just marked points in the terrain, does DCS model laser reflectivity?

Have to admit I have noticed the FOV selector key for the first time today, for that alone you have my thanks already! So, I'll play around with it a bit, let's see if I can make it work.

So you mean I have to slew it to the rough target area already to get a lock? Or can I also boresight it by slaving it to the FPV and aim in the rough general direction with the HUD?

I tried anything from 10nm down to being directly overhead 1000ft above the lased target. The LST mode on the pod didn't work, but I was able to have all my weapons guided by the other people's designations. I just can't think of what I did wrong, the codes did match (as was verified with the weapons), the pod just can't spot a laser for some odd reason in my case.

Tried again today with a friend and no joy with the pod, but buddy lasing with Mavs did work. It is really odd.

OpenXR instead please. Little point in doing all APIs directly when OpenXR provides a pathway to ALL of them, including the ones not even invented yet. How efficient it is handled by each API will remain part of the companies that do provide their API and their respective OpenXR implementation, but it makes it a lot easier on ED's side to maintain it.