geert

Have you tried adding the 2 registry keys descriped in this blog post? https://varjo.com/vr-lab/make-the-best-out-of-your-varjo-experience-update-on-varjo-quad-view-eye-tracked-foveation-and-varjo-base-settings/ I have to do this every time after an upgrade of vario base. It should work for V 4.3 and above. You don't have to use any additional software. Check "use quad view" under VR settings in DCS and do NOT enable "use eye tracking" in DCS. But make sure that "allow eye tracking" is set to ON in varjo base under "support" --> Privacy.

I did try a bunch of things yesterday, like setting visible range to high and even decreasing lots of other stuff, like shadows on flatt, clouds high (or even standard), ppd in Varjo to 35 and it doesn't really matter much. Even in Caucasus I get 45FPS lots of the time, like flying low over a forest and dogfighting. Only exception seems to be the straight of Hormuz (PG) map which works a bit better. So it kinda seems I'm CPU bottlenecked but is there any other way to check this? Also, I have a 12600K with hyperthreading enabled. Does it actually help to have more cores with DCS HT right now? Any help is certainly appreciated, thanks!

CPU is a 12600K @ 5.1 GHz. I'm not sure if that means its the bottleneck. I haven't seen much CPU benchmarks for DCS lately. My DCS settings are pretty high. DFR is on (using varjo-foveated v0.2.0). I tried quad views foveated briefly, but seemed to work much worse. Maybe I am missing somethings here? Would be nice to be able to run @90FPS but I can only reach that in low density scenes. Caucasus sometimes works at 90FPS. My benchmark is flying over Beirut in the hornet which is obviously quite demanding. Also seeing some eye tracking artifacts sometimes. I found that SSS (something something shadows) does not seem to be compatible with eye tracking (yet?? I hope). Here's my settings: I'm experimenting with ppd in Varjo base, but does not seem to matter that much. Usually down to 35ppd. Regardless whether I can improve things, a 20% (free) performance increase (72 vs 90 FPS) would not be bad thing, also future proofing wise.

Hi all, So I got myself an Aero about 1 week ago coming from the HP reverb G1. On the reverb I used to play at 90Hz with motion smoothing which used to work fine at 45 or sometimes even 30FPS (had a 2070 super back then) but only in single threaded DCS. The 2.9 update caused a nice performance boost to my system but HT and motion smoothing in my G1 didn't get along very well, so I switched to 60Hz which I really liked after the getting used to the flickering part. In the meantime, I had already switched to a 4090. The good news is that motion smoothing on the aero seems to work pretty well with DCS HT but it's definitely not perfect and still, I really liked 60 FPS on 60 Hz so no motion smoothing at all. The bad news is that 90FPS on the aero with my (or virtually any) system is almost unobtainable. So, why is there no option to change the refresh rate on the Aero? Apparently (I never tried) 72Hz seems to be a good compromise between the very stable 90Hz and quite flickery 60Hz refresh rates. Obviously, 72FPS is MUCH more in reach than 90FPS for most of us. Technically, I would THINK that it would/should be feasible? So I asked Varjo that question yesterday and the guy that answered seemed sympathetic and asked the team about it. Unfortunately, there are no plans to implement the refresh rate to be adjusted, but at least it was now on their radar (his words). It almost seemed like it was the first time they got that request so I am wondering if it might be a good idea for others do the same. Dunno if something like that works, but maybe they're just not aware of the huge benefits, in contrast to the competition. You can make a ticket at: https://support.varjo.com/hc/en-us/kb-tickets/new Cheers

Hi, I have no idea when these crashes started, but it´s been a while. Sometimes I can play for 1-2 h without crash sometimes after 5 min. it crashes. I can´t see any connection with modules although training missions in the F-18 SEEM to crash more consistently. Always play in VR, just today did something in non-VR and still got a crash. After that I decided to check some logs and always found this line: ERROR DX11BACKEND: failed to create vertex buffer. Reason: DXGI_ERROR_DEVICE_REMOVED This message always seems come at the start of the crash. I attached 4 of these logs since these are small and seem to contain the relevant info. Do I need to post some more stuff? Any help is appreciated. Thanks. dcs crash log files.rar

Did you fix it already with the latest update? In trying to reproduce the problem to get a track I wasn´t even able to reproduce it after only short testing, then came the latest update and all seems fine. In case you already fixed it: many thanks donated :) (since I can´t find any donate button) And hoping you can make a fix for the stationary, very quiet Spitfire, like you mentioned.

Bug in the SA342 Gazelle Thanks for the fix! Tested it briefly and seems to work now. Have you tried talking to ED about exporting more features (like engine RPM and firing of canon) to be exported? Just wondering about their response if any. And I have another bug for you to squash: In the Gazelle I sometimes get huge vibrations which don´t seem to go away. Yesterday I was able to reproduce the error in the same missions and after restarting DCS and simshaker. It had to do with the "failure and damage" effect, when deselected all is fine. Tested in the new Caucasus map. Thanks again. Cheers. Geert

+1

Thanks for that!

Sure, definitely some problems with DS, especially MSAA not working properly which is a real issue in VR, but despite those problems it does look really good. What makes the issue in the Mi8 different, is that other modules don´t seem to have this problem, and even in the Mi8, if you open a window the problem is gone, which gives the impression that it might be easy to fix. Of course I might be wrong...

Hi, I believe this problem has been around for a long time and not sure it has been mentioned at all. Since the introduction of the new lighting system, and so now also with DCS 2.5, looking through the cockpit windows of the Mi8 is much different that all the planes and Gazelle (not sure about the Uh1-h) in that the colors look much different, depending on the angle of light, they look very washed out, more white, less contrast. You can test this by opening the blisters left and right, looks much different. Or could this be intentionally simulating some effect of strong sunlight through windows? Sorry if I missed anything on this.thanks. cheers, Geert

Even when I deselect all the available effect options, nothing changes and the effect continues. Only checking / unchecking the last effect (touchdown) gives an additional effect for like 1 sec. Strange thing is that in 2.2 (Normandy always and I believe NTTR too) this effect is always there, but in 2.5 there was one time in my brief testing that this effect was not active, it was the first time the spit was not shaking on cold start, however, my bass shakers are not working atm so I might be missing some stuff. I remember checking/unchecking all the effects at least once some time ago, and it didn´t change anything back then either. Hope this helps a bit... thanks

Problem with the new sound module Hi, The new sound module does not seem to support my particular sound output device (steinberg UR22 = USB device). It´s there as an option to select, but when I select it I get the following error message (after restart of the software): "Thank you for using SimShaker software! Visit me at https://andres.shop to find more interesting offers! Happy flying :) 21:27:0.89 beta SimShaker Sound Module | Version 2.0 21:27:0.237 NaudioPlaybackEngine: could not initialize playback device.Can't find a supported format to use" Other sound output options do not give this error message. It used to work just fine in all previous versions. Is there a fix for this? Also, on a more SSA related topic, I noticed that with the spitfire there is shaking going on even when the aircraft is off. Haven´t read this thread in a while, don´t know if it´s a known issue. As always thanks for your efforts. cheers, Geert

I renamed the file and everything worked well after that without the need to re enter the serial number. Thanks.

problem... Hi Olaf, I´m getting a bunch of error messages when I start SSA. It seems to only affect sound module part which has reverted to the non-activated test mode without any options to even select audio output device. See attachments for first 2 error messages. More error messages come after that but maybe the first one is all you need. Thanks, Geert