HoMeBoY

The video presentation is amazing... You (Heatblur) set a new level of quality when it comes to DCS modules. If the F14 was already unrivaled in terms of experience, the in cockpit manual and the pilot customization together with the Jester 2.0 are something on another level. These features should be a "standard" Also looking forward to use the Shrike missiles on an official module (only tried them on the A4E) Obviously I already pre-ordered the Phantom.

This issue is due to the ghosting artefact DLSS generates. Most MFDs (eg radar, tgp) are affected The best solution would be todo as they do in MSFS for the Fenix A320 for example, where the MFD are rendered separately and without DLSS I know it's hard as especially a HSD/Datalink needs to integrate and show info coming via the network and from the server at all times and I guess it's pretty in the depth of code of each module

Confirm it happens in VR. They look very big. Even adding the line to the cfg file doesn't fix it for me. I think there is proper bug for when the plane is in front of clouds and at that point the dot is rendered at full scale and full opacity no matter the distance

They advertised it in the video and there was no mention in the video either. Also instead of graying the options out (that makes it look like it's not supported by your card) they could have added a note saying "* requires running MT version" Small stuff that makes the UX better

Update: I tested without any DLSS and without any AA and it happens the same. I tried disabling the "new spotting dots" by adding the line to my autoexec.cfg (I don't know what they are but I thought it could be that) but no luck. Still a big square when the plane is far away

But it's not mentioned here https://www.digitalcombatsimulator.com/en/news/changelog/openbeta/2.9.0.46801/ where I guess most people read the changelog

Settings are grayed out if you are not running the MT version of DCS exe

When I enable DSLL (either quality or balanced) in VR, as soon as an airplane becomes visible on the horizon appears as a big black square (de facto making it very easy to spot and almost like a cheat). When entering approx 8nm range, the airplane comes back to a normal perception of a silhouette. I imagine it's the DLSS up scaling trying to recompute a plane from very few polygons but it completely breaks the immersion. I would prefer to see nothing than a big black square flying towards me

Can confirm you need to run MT version of DCS or won't have those options. Make sense to an extent

I am yes. Is that only for MT?

Same here. I have a RTX 4090 FE with latest NVIDIA drivers 545.84 and the DLSS/DLAA options are all grayed out both when running 2D on monitor and in VR

1) If I map the Radar Antenna Elevation to an axis the antenna doesn't map 1:1 to the current axis position, but instead keep accelerating towards FULL UP or FULL DOWN based on how much off the axis is from the middle position...and it's super sensitive. Also most axis on a throttle do not self center. (eg: the flap level on a Warthog or Virpil thottle). Same issue if I bind it to a rotary slider. 2) If I map the Radar Antenna Elevation to 2 separate key buttons instead, the same bug appears, the antenna elevation keep increasing indefinitely until it reaches the full up position and it's impossible to move 3) the only binding I found working is if I bind the antenna elevation to the tiny slider I have on my Virpil CM3 , that is some sort of short axis , almost like instantaneous axis, with a small detent in the center position. That works like if I move the slider off centre, the antenna starts moving (up or down) and if I move it back to the center position the antenna stop moving. Can we have the antenna elevation bindable to a proper axis like we have on the F16 module or having it bindable correctly to 2 push buttons like we have on the Hornet and Mirage module? Thanks

I like this topic. Also we should point out at Aerges team that while the AI piloted F1CG can have 4 AIM9 mounted (but only L or Juliet), if we select the base F1EC flyable by humans (Client) you can only install 2xAIM9 (and you car correctly mount the P). The CG skin is available but it doesn't affect the loadout. Will we have a specific F1CG a human can pilot? If not can we please add the option di have 4x AIM9P on the F1EC? Thanks

@dmatsch The device removed error in my experience is caused by the Nvidia driver being loaded with test or debug settings enabled and it tries to assert or crash instead of just ignoring when the GPU takes some long calculation and it hangs. When it loses contact with the GPU is because it crashes thinking you got stuck You can fix it or try fixing it by changing the TDR level in you registry. Here a couple of links https://youtu.be/C8-EgUcrwOs https://www.nvidia.com/en-us/geforce/forums/game-ready-drivers/13/127945/tdr-fix-here-for-nvidia-driver-crashing-randomly-i/ https://docs.nvidia.com/gameworks/content/developertools/desktop/timeout_detection_recovery.htm https://manual.notch.one/0.9.23/en/docs/faq/extending-gpu-timeout-detection/

@BIGNEWY Why did you remove OpenXR from the auto search list? Also it's not science fiction to have a prompt that ask you how you want to launch the game (similar to what steam does). something like: - Run DCS on Screen - Run DCS in SteamVR - Run DCS in OpenXR (WMR) - etc... Why we always have to hack our way into the game to get some decent frame and VR?