zero2005

Yea, still a thing for me, though - it doesn't do it when I use Oculus link, or rather, it doesn't do it enough to effect actual frame times, the green line does blip in link, but not above the 72hz frame limit. HOWEVER in Virtual Desktop, its completely broken... I've defaulted to not using VirtualDesktop for now for other reasons (24h2 broke h264 for it, among other things), but I'm also kind of burned out on trying to troubleshoot DCS's minor problems...

Newest patch actually broke it for me... Logitech GPro Superlight... Haven't had this issue for a long while, but now its back for me... its random though, usually on first launch it causes the lag with movement, but if I select an option that force restarts DCS (ie full screen on/off or Vsync on/off) sometimes it makes it go away?

So, I've been doing some testing for VR for some other issues, but this popped up today for me as I was checking something in 2d/chasing down other bugs: Hind has 3 states for mirrors, "on" and "enabled", "on" but the reflective view is "disabled", and completely removed. When they are completely removed, they have the same frame rate hit/impact for me when they are on and enabled, which in 2d was about a 10% or more hit. at 4k and my VR settings (but again, in 2d flat panel), I would hover around 250-260 frames in the hind freeflight mission which starts you in active pause after you press OK, with the mirrors either on/enabled or completely removed. when having them in view, but the reflection turned off -> immediately shot up to 290-300 frames. Can we please get some optimizations for the hind? Can we get an option to disable rendering the front gunner seat completely or something, if we don't plan on using it? there's something else in the forward view that's causing additional load that doesn't seem like it needs to be.

I noticed this in the past, then it was fixed, but the most recent 30 sep patch brought it back with a vengeance... I'm using a Logitech G Pro Superlight, both wired and wireless it does it *horribly* in the menu, especially in VR. However, I also have a Logi M570 trackball, and that doesn't do it or at least its not noticeable (when in actual flight, I do see a minor burble, but it doesn't effect frames) Intel 14700k. I've tried with and without the old MT.lua (btw, what is going on with that?), i've tried with and without E-cores on, with and without hyper threading. with and without HAGS. I've tried disabling any and all overlays (Steam, Discord, RTSS). It does it both using Link and VirtualDesktop. I recently just reinstalled DCS, and this is a fresh install of Win11 24H2. my 14700k is brand new as of like 2 weeks ago, as I RMA'd my previous one, and I have set the power limits to intel standard (253w/253w/307a) and stock clocks. My questions are: is the MT.lua supposed to be used still? it does not come with a fresh install of DCS... If I don't use MT.lua my core 0 [aka, first core] seems to becomes the main thread and gets the highest load. using MT.lua moves it from core 0 to a random other core, but it still stays pegged at 100% or nearly 100% and the issue remains... also, why hasn't the in-game frame limiter slider been adjusted so we can use it with actual numbers instead of limited to 10's and 5s? I want to limit frame rate in game to 72 but cannot, editing the options config to 72 manually doesn't work, RTSS is a pain in the ass to deal with, and setting a limit in NV control panel is not ideal.

Having weird issue where the mirror texture and the "glass" texture that seems to have been applied over the moving map. There's also a few switches that have "missing texture" bleeding through on the left panel.

Baked in reflections need to die a horrible horrible death, or be optional. They look even more awful in VR than flat panel.

Can only hope, Deferred is terrible for VR, just a fact. Its not 2013, no reason to be using Deferred any longer, at least not in DCS which isn't even using the main benefits of going deferred shading in the first place. The shader bloat is real, just dig through the bazar folders. MSAA would benefit by going back to an optimized forward pipeline.

IIRC DCS switched to Deferred some years back, Can we please go back to strict Forward Rendering, at the very least for VR?

I took a bit of 1000 grit sandpaper I had lying around and gave it a bit of a buff and the roughness seems to have given it a bit more friction, then I applied a drop of lucas gun oil I had laying around and it seems to have got it to the point I find it acceptable. its like the angle is just so damn flat and the plastic is extremely smooth. to give some perspective of how easy it was to push through the detent (assuming I could even feel the initial contact point) was less than the pressure it takes for me to press the air brake button forward. If I ever get around to it I still want to 3d print a new design.

Yea it feels like the right throttle is just arbitrary when it hits the stop. always feels like I'm a few % off. The left seems fine. I've tried disassembling it and reassembling it a few times, tried tape on the detent. I don't like the shape of the detent to be honest, if someone were to design it to be more positive, like a "wing" shape like the TM Warthog detent I think that would give it more of a positive stop. Possible the spring isn't as strong as the left spring, but just looking at it, it seems like a HUGE pita to take apart to change that tiny ass spring. Overall I'm not impressed by this one feature so far, everything else is amazing, but the AB detent is kind of something that should have been nailed down in the early design phase. I'm going to try putting some Nyogel on it to see if that can help, but I think I might have to just redesign a new detent that looks more like the leading edge of a wing instead of this flat angle they have.

Just got my Orion 2 Stick/Throttle (F-16EX stick, F-15EX throttle) with the finger lifts. My only real annoyance right now on initial impression is the afterburner detent is not very positive, I've tried the different positions and it just seems like I can't bump against it and know exactly where mil power is, which is frustrating. Is there an aftermarket detent that is more "positive" in nature? or is there a way to increase the tension on the finger lift mechanism to have a more positive mil-power stop? I still want push through, but its like the friction to push through, especially on the right grip, is basically nil. I tried even putting a few pieces of scotch tape on it and it kind of helped until it started to wear down.

Then we can have a bunch of missions with the 10 getting Consol'd by 135s, just to offload 6klbs to an A-10 9.5 hours later. lol Also, accurate oven model for booms to bake dick shaped cookies when?

Any chance we can get the DLSS option "unlocked" somehow? so that we can push REAL FSR2 through the DLSS option? (The current iteration of FSR is *not* FSR2, its FSR v1.2 with TAA locked and not the same, unless you are doing some sort of black magic hiding the FSR files...) I'm able to run DCS through a vulkan compatibility layer via DXVK, and have replaced the dlss files, however there's no way to select the DLSS option. IF I were able to force select the DLSS option, it would be interesting to see how actual FSR2 runs... The above method is the same way Cyberpunk and other games were modded into using actual FSR2.

Got a mk IV, wanna see some of you out there with damper setups. I have a set of 3d printed "dry clutch" that go on the bearings between the pedals, and they're OK but not stiff enough for just removing the spring.

So, I noticed that in the cockpit of the Hind, I'm getting a weird frame limitation, usually around 60fps, I am in VR (Reverb G1 @ 2800x2800 using the OpenXR mod, 12700kf @ 5.3ghz and Powercolor 6900xt @ 2700mhz) Most other modules, getting a pretty solid 90 fps offline. The I hop in the cockpit of the hind and it suddenly drops to 60 frames. I go external and its back to 90 frames. I've tried the optimized English cockpits from Sundowner, but to no avail. I've tried several other aircraft and haven't run into any issues: F-14, Mig-21, F-5, Huey, and Hip all run great. I suspect this is likely due to it not being optimized? Unless someone has any other suggestions. I tried clearing out FXO/Metashaders already (I do this often anyways). But I also don't see anything listed in the bug report?