All Activity

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

If understanding TWS and datalink makes me a hipster, I guess the USAF is the biggest hipster club on Earth.

A couple of thoughts: 1) Because the Americans were there, it was our sector, and the Fulda Gap was the most direct route to get to them. Americans focus on the Fulda because it would have most impacted them after the West Germans. Also US V Corps was headquartered at Frankfurt. That is in no way a short shrift to the units defending the NGP, and I doubt they think a whole hell of a lot about the Fulda Gap. 2) Rhein Main was the huge logistical air hub for the theater. Yes other bases could and did support the logistical mission, But Rhein Main was the primary site for rapid deployment. Again, the Fulda Gap is the quickest way there. I've seen some maps promoting the North German Plain as the primary push with elements circling back toward the Americans. 3.) I just did a couple of drive-throughs of the DCS version of the Fulda Gap, from both directions. I was surprised at the number of very open areas between the border and Alsfeld that would allow for fierce mechanized warfare. It would be a nightmare to push through against determined defender, but maybe that's why the WP dedicated the whole 8th Guards to it. Lot's of areas to plan for alternate routes on the offense and ambushes on the defense.

I'm definitely using the correct buttons to open the radio menu... but still same issue. Even when on the correct channel with the correct frequency set for that channel in the ME, that station doesn't appear when opening up the radio menu. Still can't figure it out. I'll play around with it a bit more. Maybe it was just on the CWG map that the issue arises. Haven't tested any other maps yet.

I believe you also need to ensure you're in the correct flaps config before to button. I'm away from the sim, so someone may need to confirm that statement Sent from my SM-S928U using Tapatalk

Did you post in the wrong part of the forum? The A-10C HUD brightness is a rocker and there's nothing analog about it. Plus the pilot body show/hide keybind makes little sense before they add the pilot body.