All Activity

so FFB is working correctly now?? excellent. i can try this bird out again

So. There are multiple problems with this idea. The core problem is its not NVGs. its the fact the COCKPIT, that has to be modified to work with them. 1: Soviets didn't have gen2 or much less gen3 NVG's operational anywhere in the relevant time frame of the 9.12 like not even remotely 2: Cockpits have to be modified for NVG's to even work at all in them. ED has historically done a terrible job in this regard, failing on every level to acknowledge this basic fact. Its well documented. 3. Even if you had some "western modified" "9.12" it wouldn't really be a 9.12 anymore and even then there is no evidence of NVG mods of that.

AH-64 (the whole reason I got into DCS all those years ago), A10CII, F-16. Recently discovered the new UH-60L v2.0 mod and been really enjoying that.

The chart is in my video above There really aren’t many for Fulcrum “fuel flow per speed and altitude” charts, though there are more for “fuel used for climb/descent with xx payload”

I don't have force feedback but I just checked & the force feedback option was checked. I unchecked it & will see if it has any effect.

I've been struggling with AA recently, my solution which looks hugely better is using reshade and the TAA shader along with MFAA 4 and turning MFAA related stuff on in nvidia panel.

The real-world Luftwaffe manual has much more understandable wording for explaning this system: In TAC the remaining flight distance is calculated based on current fuel flow and ADC data. In OPT the remaining flight distance shows the max possible range "with an optimized calculated fuel flow." I believe this would be referenced through charts, however my manual is incomplete and missing said charts.

About our beloved sim, seems to reveal a distinct lack of game design on behalf of ED. This is perhaps obvious but is there any discussion around this topic? Why not allow the community to build the 'game part' of this sim? As much as i love DCS i find that my experience on it today is much the same as it has always been going way back to lomac. Pretty disheartening. Regards

Two of those logs show you've added Quad-Views-Foveated, recommend removing OpenXR Toolkit if you're running that in general. The logs don't show a crash itself so it's more likely that Windows is killing the process. Can you run the Windows DxDiag tool, save the output, and then attach it here as well. I'd highly recommend you remove your mods, run a repair, and delete your Saved Games\DCS\fxo and metashaders2 caches. Mods can cause issues so may be something conflicting with that module and not others. Additional items: You can remove the "force_OpenXR" parameter from your shortcut as the game is entirely OpenXR. I'm assuming your other params are so you can have both VR and 2D shortcuts? You have core parking enabled. You can use the ParkControl software to disable core parking for your power management profiles. Having this enabled can cause stutters. I'll wait for the DxDiag report as that will likely have more info re: system issues and if/why Windows is terminating this.

For those that can’t remember everything Wags says like me

I agree, I was confused when manual said 1100 kmh limit for MPRF. I thought perhaps this is some computer limit not a “drop lock limit.” The speeds max out at 2200 kmh for rear aspect MPRF and 2500 kmh for front aspect HPRF, meaning rear aspect targets near Mach 2 couldn’t be locked and front aspect targets above Mach 2.3-2.5 couldn’t be locked.

M-60 M-48 Personally, I would also really like the Soviet 2S7M Malka, I would be very grateful. I think that cannon is still in use.

I had terrible frames the other night and IC fails, the solution was to reduce the visibility distance slider thing... Now it runs smooth.

What do you mean by this? Windows Mixed Reality (WMR)? Can you clarify what you mean by that. Not sure what you're trying to do, there's no reason to send it back.

Happens 100%, every flight, including training missions, on my system (7800X3D, 4070Ti Super, 64GB DDR5, all SSD).

Target could also be falling within MLC of a spectral line and the scenarios in your tracks are set up just right that the closure rates fall into it. Theoretically there shouldn't be a hard maximum detectable velocity limit with MPRF signal processing but soviets seemed to have always done things differently. Could be many reasons why they imposed one.

I did end up changing the stick grip and getting an extension.

Instant action, 4 stingers LastMissionTrack.trk

Eh... not all landings are good, especially when after engagement you end up with 1 damaged engine and then you're trying to land on very short runway, adding to problems drag chute when released rips off on release which does not help with breaking and stopping the airplane

Neither. Helios does not "generate" the exports. Neither is WW or other software. The exports are pure from ED/DCS and are defined in the monitor.lua, in which you have to edit to have exports in VR. Helios, WW etc software can help you generate that file, but not for VR. That's why you need to manually edit it. Cheers!

Doesn't exist. You must manually change the Snapviews.lua. I believe the view is 2-3° downward by default. Which is extremely irritating when one has a headtracker. Cheers! Sent from my SM-A536B using Tapatalk