pixie

Has ED, at some point or another, mentioned the will to fix the map regarding this slow performance issue ? Was this poor performance even acknowledged ? I know it's a free addition to DCS world, and we shouldn't complain, but since it's not playable for most VR users, it feels like a waste of hard and dedicated work. All in all the Marinanas is a lovingly crafted map.

Hi guys, and thank you muelch for this amazing work. Like mentioned in a different thread I ( and a few others) have had good results caping the RAM with memory cleaner https://www.koshyjohn.com/software/memclean/ All I need to do is running this app in the backgroupnf and check in the options "staying under 80% of RAM", not too sure how it can help, but definitely worth trying

You VR experience will need some compromise, for sure, but like everyone else you'll have some compromises to decide on.. A 1080 TI should run DCS smoothly as long as you are not to greedy when it comes to eye candy. I had a good first VR experience running DCS on a 1070. If you have DCS on Steam, I recommend launching the game with oculusVR rather than SteamVR. Leave your Quest 2 parameters on default or recommended resolutions and frequency in oculus software, start from a Low DCS graphic configuration and slowly increase the quality one paramater at the time. Check the framerate impact for each parameter, and always choose smoothness and FPS over eyecandy. Otherwise you'll get sick and you don't want the VR experience looking like a powerpoint slideshow.

I had issues with my Quest 2 and the lower tier of the display. Got rid of it by reducing the bitrate of the encoded video running through the USB cable. Go to oculus debug tool (ODT) which is installed somewhere by default, and modify variable bitrate to a capped value , 500 if I recall correctly.

FWIW I run memory cleaner right before launching DCS... and forget it. I haven't checked the actual memory usage of my 32gb with and without memorycleaner. Right now, the VR stutters that were plaguing my game after a while seems to be gone. I can play as much as I want without restarting / alt-tabing DCS. One possible explanation could be related to some kind of memory leak that fills the RAM forcing the system to swap data on the hard drive.Since the RAM is prevented from being maxed out, there is no swap file on the HD and no VR stutters. I know it seems simplistic as an explanation, but it's plausible enough to me.

So far so good ! @Gruble Thank you very much for the tip, in my case this memory cleaner tool is a blessing

Like Digitalvole I have recently succeded with air-refueling for the first time. Everything has been said, but in all honesty I was considering this task impossible for me. I believe my issue was being too nervous and I overcompensate with unvolontary strong stick inputs when closing to the basket. The trick that worked for me to avoid those large uncontroled stick movements was to make tons of micro stick back and forth inputs. In order to dampen my inputs I'm shaking the stick with small movements around the desired position. Quit unorthodox but efficient in my case, it looks like I have tremors or shakiness. So far it makes sense since you are supposed to "walk the throttle" all the time and pushing it back and forth for a good precision on a carrier landing. Same goes for stick input ! After a while, and some more practice, it seems I can almost fly normaly to the basket without so much trembling.

I have tried memclean with very good results for VR related problems on my system. There is another thread in the VR sub-section that suggests using memcleaner with auto-trim set to 80% (tick the first two options). After a while many VR users, including me , are suffering from "display stuttering". This often happens after respawingn or jumping from F10 map or external views. This makes the VR experience unplayable, and generally forces me to restart DCS. A common trick to get rid of this stuttering is to alt-tab out from DCS and go back after 30sec or so. It doesn't work all the time, but so far it's the best work around the VR community came up with. VR dedicated PCs are quite difficult to stabilize for DCS and it's all about achieving a compromise between eye candy vs FPS performance. I'm far from being an expert but the "memory leak" hypothesis has been around for a while, at least it makes sense to me and could explain a lot of issues. Using this memory cleaner tool has recently proven efficient in my case, but it could also adress a larger problem most DCS users are suffering from.

I have tried memcleaner for a few sessions and it seems all my stutters are gone ! This might be a little bit soon to claim victory, and I should make some further investigations. So far the results are very promising. can anyone concur ?

Thank you, I will give this a try. It might proves helpful since a well known trick in VR, is to alt-tab out of DCS and go back after a while (a minute or so) I will let you know if this helps

FWIW, I have dedicated a small desktop workstation (dell optiplex 7040) to the sole purpose of running Through The Inferno server. It works quite well and spare some computing power to my gaming PC which is running VR. I haven't done any benchmarks, but it certainly helps. Especially on complex missions. My friends can join the server as well using my public IP. Even If my gaming PC crashes or needs rebooting, the server is still running the mission in background and we can reconnect whenever we want. Having my own private DCS server is cool and a refurbished dell optiplex 7040 is quite cheap.

Better yet, try to match the pilot body to your real counterparts limbs. It makes the pit snug and fit like a tailored suit. If find this method more natural than trying to guess the stick, seat and gauges proper size.

Hi, could you be more specific about "resetting the computer" ? Thank you

FWIW , I avoid SteamVR, so far I have better performance using OculusVR. I also think the settings are more straightforward. Everything is on default on OculusVR parameters, then I tweak DSC settings to my likings

Stable release seems to have improved things, Having a proper VR experience is quite a challenge. One false move and you're done ^^

well... no luck after defaulting ODT, I even tried to reinstall Oculus desktop app. I'm not sure what went wrong in the last few weeks, maybe the last quest2 firmware update ?

Hello, I have exactly the same issue after the deltasim slew upgrade. All my right throttle buttons are not functionning properly. The only difference is the problem seems to be random and I generally fix it for a while when jiggling the right throttle. I wasn't suspecting a ribbon cable issue since all the buttons stop working at the same time, but your brown wire issue lets me believe it could be a ground problem. Is your brown wire a part of the ribbon cable or is it somthing else ? Could you pinpoint it for me ? Thank you for your help

You are right, maybe it's time for default settings experience !

I have a Quest chopiness isue as well ! I have it since the last Quest firmware/driver update, are we talking about the same update ? I also have noticed a new option in ODT : Mobile ASW. I have no idea what's the difference with regular ASW Since we are among Quest users, are you using steamVR or oculusVR option when launching DCS ? I have chosen OculusVR since it seems more straightforward to set up but I could be convinced otherwise. Are there some benefits you might know of using SteamVR ?

Hi, not sure we are talking about the same issue here, but I used to have the kind of problem you are describing with my Quest2. I think it's related to the way the video is encoded and streamed to your headset. For me, It's been resolved for good by lowering the bandwith of the oculus link in Oculus Debug Tool, I think the setting is on "auto" by default. You can try a lower value like 300 and see if it happens again. I suppose somehow the video stream can get clogged with too much bandwith. Hope this helps

I have never suceeded using LST with F18's ATFLIR too. I'm flying mainly Through the Inferno, where all the JTAC 9 lines stuff are automated. Laser code is defaulted to 1688 both LST and LTDR. I can't get my ATLIR locking the target using LST, even when flying straight at it. Maybe I'm doing something wrong though. Can anyone report some success buddy lasing and locking ATFLIR using LST ?

The VR pilot body, or lack thereof, is a very subjective issue and an interesting one. It all depends on how your particular brain work and how VR tricks your brain to make you actually feel in the pit. I belong to the group which definitely needs a VR body to project oneself into. But I perfectly understand someone who couldn't care less. There is no need to argue with the "other group". That's how your brain is rigged. End of story. Somehow, there is one useful aspect I have discovered using F18 virtual body under VR : It helps you immensely to set the correct IPD, and therefore the sense of scale in the cockpit. I simply tweak the IPD setting and look down at my legs. If I feel childish or like a giant, the IPD value is obviously wrong. I change the IPD value until I sense my body has the "right" proportions and feeling. Once IPD is set, you can hide the pilot body for good if you're not confortable with it. BTW, the IPD setting is not really an Inter Pupillary Distance, but rather a scale slider for close proximity objects. It really defines how you feel in your VR pit.

I have switched terrain texture to low, and so far so good, no more stuttering with the Quest 2 VR. It really seems to ease up on the GPU memory. Thx for the tip. And btw, if I don't compare side by side high and low terrain texture, I very much doubt i can tell the difference

I have difficulties convincing myself to switch to low terrain texture. I guess I should try.

February bump ! ED could at least give us a straight answer on this subject, a simple yes-no would be a start.