Here are my specs (and, yeah, I'm kinda irked that I've put this much money into a rig and am getting kinda hosed on the VR experience):Ģ x M.2 SSDs (DCS is on a separate drive than Windows) It seems (although I could be completely off base) to be more than just an in-game settings issue if that were the case, it seems like I would be experiencing 'lag' but the headset crashes are beyond that.? In VR, the WMR and SteamVR lobby seem to be running smoothly as well - no glaring issues or crashes that I've seen, and no error codes from WMR.Īt this point, I'm not sure where the issue lies - either in DCS' VR settings, the G2 trying to process the game/images, or a combination of the two. I've run DCS in non-VR mode, and it launches like a champ - smooth as butter and relatively quick loading, etc. And when that occurs, DCS seems to be still running - I can see the game in the 'duplicated' window on the desktop. I think that is one of the things that make the issue particularly frustrating: it's not the same thing each time. I'll either get blue screens in my headset, or black screens, or black screen with 4 rotating white balls (perhaps that is a SteamVR thing?).
When I can get DCS to launch, the initial screens are laggy to the point that I can barely even use the mouse to navigate, and when I do attempt to launch a mission (via Mission Editor, as I have a few short test-ish missions to double check my controls, etc.) my headset crashes out. With my new PC (which seems like it should be pretty much able to handle DCS and more) my G2 has been nothing but problematic, in many ways. I have had an HP Reverb G2 for a while (purchased one not long after they were initially released) and with my previous PC had some issues, but I was able to get around them after many hours of trial and error. I recently built a new rig for gaming, almost exclusively intended for DCS. I'll start by saying, please let me know if any of this is duplicative of another post, or if I should be posting in another location.
0 kommentar(er)
