Willie Nelson

I was fairly confident that in fact I had not overclocked this CPU! I see what you’re looking at, is that not the native setting potentially being displayed? I am informed by somebody that know more that me that there’s not a lot to be gained from OC ing a 14series Intel. With regards to the Memtest 86 do you have any guesses what I might be missing there with my attempts to run the USB image? I’m a bit concerned about setting anything to 115 degrees Celsius. :- 0

Ok, thanks. I’ll keep that figure in mind, I can do some geometry and work out my likely capture range from a given SAM safe altitude with that. Now if only I had some time to confirm your claim and not have to go to work!

Do we have any ideas on how close I need to be before I can reasonably expect that a lased target will be picked up in the event that the TGP is looking within the vicinity of whatever is being lased? I can make it all happen but it sometimes seems that I need to be able to see the whites of their eyes before a lased target will be picked up, perhaps I’m missing something.

Thanks again for the response. I have a 4090 and a 14900KF with a high quality air cooler although I am told that these will often go up to 100 degrees which makes it hard to determine whether that's the issue becuase as you can see, I get there on several cores at least for a time (I am not if there's a more detailed log as there was nothing in the folder depsite me switching on the Core Temp log). This sceenshot shows a MP seesion on an empty 4YA server that I played for perhaps half an hour without fault. I have followed the instructions for the Freeware Memtest86 and cannot for the life of me get it to boot from the Freeware file saved to a USB stick, I have checked that I am using UEFI BIOS mode and that secure boot if off. When I attempt to run it from my F12 boot menu list it keeps coming back to the same F12 boot menu list within a few seconds. Any ideas? I did run a Windows 11 inbuilt memory test but apparently that's checking several different things than Memtest86. The PSU is a definitive possibility, it is also new and I sometimes have to switch it on by recycling the mains power point switch! I know that's not normal in itself but once it's on it does stay on and my time limit constraints mean that if I take it back to the store I am likely going to run in to the problem where they cannot get it to crash while bench testing it because theyre not using DCS in VR with a Pimax Crystal. The stress tests that I have previouly run don't seem to cause it any promblems either. Not sure how useful a PSU tester would be in this case but I'm open to any of your suggestions.

Both have in fact happened but it almost always just a garden variety CTD.

So I have now done both of those suggestions and while I have had some seesions, perhaps four maybe, without a crash, I have also had two to three that have continued to crash. Here's the latest log. dcs.log

That's the one, thanks for your help.

I seem to remember some months back ED introduced a native in game scratchpad particularly for us VR users whereby we could collect a Lat and Long from F10 and present it on screen back in seat to then enter it into the aircraft. I cannot for the life of me find that mapping option, can someone help me remember?

Thanks for that, just disabling OpenXR Toolkit for the time being to see one change at a time, So far, three successful flights without crash, I'll see if that causal and report back, thanks again.

Thanks for getting back to me so quickly I have tried delting the fxo and metashaders2 previoulsy as I am aware that sometimes that helps, I did it again this morning as you reqested. I dont have a DXCache in that location just a GL Cache which I tried deleting but one of the folders was in use at the time (DCS was closed but the Pimax client was open, so I am guessing it was that...?) I have attached a screenshot of what else other apps that are in use for some context and some of my NVIDIA settings, if it makes any difference. I am also using Joytokey for Apache Xbox controller mapping. Still crashing after clearing all of your suggested folders were cleared (that could be cleared) here's this moring's crash logs. I appreciate you looking in to it. dcs.log dcs.log.old

This CTD is back again (or didn't go away for long enough for a family man who doesn't get anywhere near enough time on DCS these days) @Flappie can you help? These files represent the two most recent crashes only. I have already deleted all mods as far as I can tell and completed a repair and clean-up. I appreciate whatever you can do. dcs.log dcs.log.old debrief.log

I’ll keep watching this space.

Out of interest p, which other sims use native voice recognition?

“Although we have a solid design to provide an exceptional ATC experience, much of the work in 2024 will involve how we generate the voice dialog and create a much-improved interface.” Be interesting to see what sort interface they’re looking at……sounds hopeful.

Yes it was, thanks and sorry for not doing as instructed in the crash instructions. I appreciate you getting back to me.

Thank you.

@Flappie Bump

Hello, I have done a clean up and repair. I am playing in VR with a new Pimax Crystal, GPU and CPU and PSU on the AH64 instant action mission and are consistently, though not always, getting a CTD with no 'proper crash' in the log as you discuss in option C (i.e. not specifically noted in the crash log). It seems to be consistently occurring when I takeoff in the AH-64 firing range mission (a good amount of ground units) and get some low level translational lift, which makes me suspect that this is correlating to when performance demanded is too high......? Not sure if it might be a temperature thing on my system but it's hard to asses that while I'm playing. I appreciate it may be outside of the scope of DCS but if you could point me to where I might look next then that would be much appreciated. I have attached two crash logs from the same crash type to assist. I would appreciate any assistance you might be able to provide. Kind regards, Willie dcs.log dcs.log

Matt states on the now defunct Discord page that the source code is available should either a hardware or software platform wish to develop it. Made any money from this venture and I amof the understanding that he is allowing others to tinker where they wish to. For now at least, it still works and there is no problem. It is up to others however to take on his legacy, which is probably a better way for the industry to deal with this as there is mork work than one man alone can do.

It is genuinely in ED’s interest to keep working on VR as their gear is used by commercial clients in VR so although it may not be easy to adopt for all hardware platforms, it will help their business model to keep up the good work and continue to pursue whatever performance pathways they can wether they be Vulkan or a QVFR, etc.

Maybe it is perceived as a niche group for the time being, that is perhaps a circular argument. If VR integrates well with platforms like DCS and has a reputation for not needing a wildly expensive pc to run it with 12 apps to integrate it then maybe it will no longer be perceived that way. It is possible.

I see @mbucchia has pulled the pin on continued support for OpenXR Toolkit, Quad Views Foveated, Varjo Foveated and other associated VR apps due to work life balance concerns. Completely understandable, but thanks for all the work you've done Matt. Having eye tracking is a significant quality of life improvement for this little community.

Legends!

Just had this problem too, I cheated on the steps though, not sure if I really want to uninstall all mods, I simply deleted the in game default warthog thrust lever profiles on the Hornet (my problem was on the speed brake extension) and then repaired DCS. So far so good.