seven10
-
Posts
89 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by seven10
-
Thank you, I will have a look and do some testing. The missions I was getting generated so far would generally only work if I took 100% fuel and no armament.
-
Sorry if I missed this somewhere in all the posts. Is there a way to set the max possible mission distance? When trying Crisis in Persian Gulf with the Kiowa the missions generated had objectives too far away for flying with a standard load out and 50% fuel.
-
Dynamic Foveated Rendering - Everything in one page
seven10 replied to mbucchia's topic in Virtual Reality
100% this is extremely distracting in my opinion. The sharp cut off squares when looking indirectly at light sources was something I was hoping was going to be fixed with the implementation of quad view and eye tracking support. At least with the out of focus sparkle that happens that can be toned down by messing with the smoothing. -
Any chance we may see an update to this great mod? Seems like tracking as of the recent patch is broken and missiles just fly out straight ahead of the Tomcat.
-
This is all well and good, but it would be excellent if for the time being we could at least be able to turn these on and off. In the future it would also be great if mission makers and server owners could force these off like how labels are managed.
-
I could see how this would be helpful for some, especially depending on their resolution or pd settings. However, the setting to turn it on and off as others reported is broken. For my current resolution settings of 4480x2272 and pd set at 1.0 they are blocky and very noticeable under 10nm and seem to fade out around 5nm. I personally would rather have a working option to turn them off.
-
Same, the selector doesn't work and trying to manually force it off via autoexec doesn't work either.
-
I'm curious to see if this will work for other people, but try disabling Core 0 in Task Manager's affinity settings when using the multi-threaded DCS client. I tried that with the F-4 thanks to the suggestion Heatblur put out and it seems to make the stutter with the Harrier tpod stop as well.
-
Yep, it's unfortunate, but still happening just in the Harrier. Doesn't seem to matter how much computing power you have, as soon as the pod starts masking when looking behind the aircraft the frame rate tanks. Hopefully this can finally get fixed once ED and Razbam sort their issues out.
-
Unfortunately I'm still having this issue and I'm on my 3rd full pc build, each with increasing power, since my original report. I can add updated tracks if it would be helpful and I will say it seems to happen more in multi-player now than single player.
-
Ok, glad it's not just me. It would be good to see if that behavior could be changed to be like the earlier versions.
-
I believe in the past while working as a Commander or when Pilots can control vehicles was enabled it was possible to select a unit, click Add Target, select a target, and then click Add Target again and repeat. Now it seems like after specifying a target for a unit to be able to specify an additional target that the unit needs to be unselected, then reselected, and Add Target works again. Am I doing something wrong or is that functionality that got broken that we could potentially get back?
-
I ran across this issue where AIM-120s stop functioning despite showing up in PACS and being physically on the jet still a few times and thought it was a mistake on my end or random issues, but I've been able to reproduce this with all JDAMs now. I have also tried this with GBUs, CBUs, and dumb bombs which did not cause the same issue. To replicate: Program combat jettison for STORES Configure JDAMs on armament page for Direct, Step, and N/T Be in A/A master mode and fire 1 or 2 AIM-120s Switch to A/G master mode Designate a target with the TPOD Transfer target to JDAMs on smart weapons page Drop all JDAMs in range Switch back to A/A master mode Combat jettison AIM-120 circle then disappears on the HUD and are no longer fireable F-15E Aim-120 JDAM Issue.trk
-
South Atlantic Terrain Terrain Look and Feel
seven10 replied to Raz_Specter's topic in South Atlantic
I am not sure how DCS handles terrain textures, but does it not support layers of detail to swap texture sets based on altitude? If so then the sat textures are mostly great at the highest altitudes and then it would be good if synthetic textures influenced by the sat textures were used more and more as one was closer to the ground. If that's not possible, I think starting from the sat texture and then artistically modifying it in key areas or where people find anomalies in the photography to be the best compromise. Perhaps some of the current ai up-scaling tools could clean up where sat textures get blocky. -
Hmm now that you mention that, I never saw this issue with my G2 and WMR while using openxr and the openxr toolkit. It has only been since switching over to the Quest Pro that this issue has cropped up for me as well even though my GPU has 16GB of VRAM. Once I'm back I can test 2.9 on my old setup since my brother has it.
-
Seems like they're bigger in MT than ST, but both look bad in my opinion. It would be great if they could be turned off or have the size adjusted for those who want them. Trying to use “DotRendererExperiment = False” in autoexec.cfg doesn't work for turning them off either.
-
The cable in my extension and base unfortunately died just pre-2.9 release, so I haven't been able to retest and see how things are since the update. Once the replacement comes in and I'm back from Japan I'll be able to update as well.
-
No, I do not run with shadow play active.
-
Here's a link to the track from last night: https://drive.google.com/file/d/17Y152xiyhD-n0qmTYPXY31tpVZFNJuse/view?usp=sharing As well as two from the last time I used MT and encountered the issue: https://drive.google.com/file/d/1Qgl--xq1zZs34bveDIZJLCYWRrSDPHMN/view?usp=sharing https://drive.google.com/file/d/1Cy-PbsTbKVVFF_0f3mPlivTq8enyrBv2/view?usp=sharing
-
Well, unfortunately it happened using the standard executable as well. Though the difference is that it only showed up after an hour of flying on a server and multiple F10 to F1 switches. It also seemed to go away for a little bit then come back whereas in MT once it starts to desync or whatever it never stops without a restart of DCS. Track from tonight is too large to upload, so I can dump it somewhere if needed. dcs.log
-
Sure, here you go Yep, I've tried 32GB, 64GB, and system managed all with no change to this issue. Unfortunately the only thing that seems to work for making things run smooth between multiple F10 to F1 switches is to use the non-MT exe.
-
This is all running on a Quest Pro at 72Hz, 4480 x 2256, ASW Off, and Adaptive GPU Scaling off dcs.log VR F10 Test.trk
-
Recent DCS log and DxDiag output on SpecialK's recommendation. dcs.log DxDiag.txt
-
Upon recommendation of the DCS Discord I tried ST tonight in MP and did not have the issue, however I did bump up against CPU limits down low. I can post the server tracks if they'd be helpful, but where should I put them since they're over 100MB each?
-
This has been happening to me as well and at first I thought it was just issues brought on by running very close to the limits of my previous CPU and GPU in multiplayer servers. It would mostly show up in the 14 and 15E, especially after switching between the F10 map and cockpit or opening the jester menu. However, I upgraded my system to a 7800X3D with 64GB of ram this past week and I unfortunately am seeing the same issues, especially on the 14. I have turned off ASW in the Oculus Debug Tool and tried the Ctrl+Num 1 method that was posted here to no avail. When looking at the frame times in OpenXR Tool kit I'm consistently under 13ms combined CPU and GPU latency so I should be able to maintain a solid 72fps without tearing. I'd be glad to provide any other info needed to replicate. Operation_Scarlet_Dawn-20231002-015020.trk
