paulferris

Now got it to show K - but required me to also change to override and use latest preset on DLSS-FG and DLSS-RR

Thanks sleighzy. It looks like it may have sorted itself after another Windows restart, at least partially. It's now showing v.310.2.1 - albeit, curiously with preset C, as shown below. That doesn't change even if I set it to another specific preset. Tried it in both the DCS Black Shark and the Global profile, and now using the latter. Changes were applied. Never used DLSSTweaks, although - given the various methods described - I had tried DLSSSwapper. However, I reset the dlls in that to the original.

Can anyone please suggest what I am doing wrong? I have an RTX 4090 I've done a clean install of Geforce 572.42 drivers I have installed Nvidia Profile Inspector 2.4.0.16 In Nvidia Profile Inspector, I have set 'DLSS - Enable Override' to on, and 'DLSS Forced Preset Letter' to always use the latest However, using the 'show DLSS indicator' reg tweak in 2D (it won't display for me in VR), it shows that DCS is using 'Render Preset C - DLSSv3 v3.7.0 D3D11'?? Thanks

I heard that, too, Ironhand... but also someone (I think one of the ED Testers) say that he was pretty sure that was not the case? Either way, it would be nice to get some sort of response from ED!

Many thanks, raus!

Hi - this is a great app!... any chance of an option to report distances and altitude in metric for red side flights? The nav info from my Su-25 mission gets converted to feet and knots. Thanks

Thanks - so BigNewy reported it nine years ago, and nothing appears to have happened apart from his reminder in 2019?

Thanks Draconus, yes, I saw (and linked) to that, but it was not in the 'Flaming Cliffs Bugs & Problems' folder - hence, my re-post.

I can't see that this long-standing problem - where it looks like the external model is clipping throught the cockpit model - has been reported here? See post below for full details. Given the work that has already been done on the Su-25 cockpit, can this please be fixed - at least for FC4, if not FC3. Thanks

yes, same for me - only in the F-4 - weird...

Still no fix for this? It doesn't happen with other aircraft...

FPS great in VR training missions. Gorgoeus cockpit... although perhaps a little dark? (had to bump up my gamma quite a bit).

I spoke too soon.... the red exclamation mark returned and I lost all pitch control... After further testing, it seems that the F-14 is confusing the JOY_X and JOY_Y axes on my Warthog throttle and stick, only producing the error when they are mapped on both devices. I wanted to use the slew controller on the throttle as the DLC axis, but if I set this vertically as JOY_Y it interferes with the pich axis on the stick; and if horizontally as JOY_X, the roll axis. This doesn't happen on other aircraft - eg, the F/A 18, where I use the slew axis as the TDC. Any ideas please Heatblur?

I think I may have fixed it with a clean and repair. That did some strange things to other peripherals (eg, replicating the pitch on my rudders), and deleted a number of button assignments, but once I'd sorted those, it seems to be OK now .... fingers crossed....

Currently, I have exactly the same problem as Quyes noted in his original email, and only with the F-14. The pitch axis has the red exclamation mark, but the Joy_Y axis on the Warthog joystick is not assigned to any other axis which could conceivably relate to the F-14B. I have deleted all profiles and re-entered from scratch. After entry, everything looked OK, but after restarting DCS the problem was right there again. I updated to 2.9 today, but the problem was there on the previous build 2.8 build yesterday Unless someone can help me to fix this problem, it seems that I will never be able to fly the F-14 again - a huge shame, as it's probably my favourite aircraft. Thanks Paul