diamond26
-
Posts
399 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by diamond26
-
Change default kneeboard position to right side
diamond26 replied to Tshark's topic in Bugs and Problems
+1 -
Thanks @Sydy. As always a must have kneeboard set.
-
With Qpro on latest v76 and Link app also on v76 and a repair of QuadViews software, eye tracking is working again in DCS
-
It's definitely an issue with META PC software as everything is enabled as before, Layers are correct but eye tracking is not working anymore with META Link in DCS. With exact same configuration in terms of layers in DCS, eye tracking works as always in VD.
-
Similarly my quest link crashed out of the blue and then after reinstalling I got v76 and eye tracking stopped working Luckily I have VD installed. Headset is still on v69 (switched off updates)
-
Clear, thanks for the support. @BIGNEWY wouldn't be possible for those already having the maps to use dedicated server (same pc) with the core maps and save this important volume of GBs?
-
I thought the whole exercise was to use terrains from the core installation to save space as @Darkdiz suggested and used before.
-
Bitdefender Antivirus Plus. So far no issues with DCS
-
I wish you can solve it as it will save me (and many others) the hassle (and cost) of buying additional drive just because maps are becoming huge these days and I'll like to have different maps in DCS
-
Here it is Thanks autoupdate_log.txt
-
Here is my log from the server with symlink enabled. It clearly shows that the maps are not authorised although no other instance of DCS is running anywhere. Thanks @BIGNEWY for trying to resolve this one dcs.log
-
If they make it work again it will be a good save (300gb in my case) which we leave space for the upcoming Germany map
-
I tried too the symbolic links. The server starts but stays offline and have no possibility to choose a mission although visible.
-
Did you have any success in making the Symlink work for the Server terrains folder again?
-
Constant stuttering in VR. I gave up.
diamond26 replied to Alexified's topic in Game Performance Bugs
@speed-of-heat, @MoleUK I can confirm that NVCP FPS limit works in DCS VR using Link. Tested with QuestPro and Nividia drivers 566.36. Requested 90hz from Qpro and the result was 71 FPS which was the limit in NVCP -
I guess you mean through Dlsstweak not in DCS setting.
-
If I'm not totally mistaken, preset K overwrites any DCS DLSS option and forces Ultra Performance. At least this is what I get when I check the Quad Views log file. (I guess something similar happens with J)
-
Why you say it’s redundant? OTT is just an overlay of ODT (with some helpful functions) which you use by default when you connect through Link Also you mentioned 14gb+ of VRAM use. Which tool you use to get this report ? I haven’t seen more than 12gb in my 16gb 4090 mobile one (in CapframeX or build in metrics of DCS). Is that for all modules or specific cases ?
-
If it's any help I have attached my dcs.log from my Laptop with Intel Core Ultra 9 185H. Its performance is definitely below par for a gaming laptop (definitely below my desktop i7 12700K). dcs_laptop.log
-
are you using VDXR option in VD stream app?
-
Using Quest Pro (max resolution), Quad Views with focus resolution 1.8/ peripheral 0.2, DLSS/Performance and preset J, I can concur to the following: There is still some smearing around the edges of planes like "leaking oil". Loss of contrast of planes against clouds or ground (not at all times though) On the other side performance has been exceptional and clarity is comparable now to 2D
-
I wondered if DCS actually never changed the DLSS option from quality to none as the performance is almost identical which shouldn't be the case. I have the feeling, as I mentioned elsewhere, that Global override keeps the DLSS Quality level at a certain point (in DLSSTweaks it was 0.6666 which is the quality one)
-
As it's always the case, everyone has a different view especially when it comes to VR. I'm really happy with what I get from the new DLSS in terms of clarity and performance. It will definitely not solve VRAM issues but it provides a better clarity and the option to run the system at DLLS/performance without loosing clarity. Also I don't get any noticeable artifacts.
-
Yes I mean all the way to the right in meta app. Focus resolution is mentioned above at 1.8 with 0.4 x 0.4 size. Eye tracking doesn’t let me see any low resolution parts. The only place I see the low resolution is at video recordings or casting. In QV log I see 7.5 million pixels
-
Very strange as I'm moving between Link and VD all the time (especially now with testing for new DLSS) for 2 different computers and haven't seen this problem!
