j9murphy

Sooooo.. whats the takeaway here. Are there circumstances when force ipd should be used? is there a recommended value? should we match the IPD number in the headset?

I removed everything - WMR, open composite, all the mbucchia stuff, and all my oculus and meta stuff before installing pimax play - i did leave steam installed. I'm also on the latest version of windows 11 - did you stop updating to keep running WMR? There will be a steam alternative to WMR coming out soon that mbucchia is working on.

Last night I was using the caucus super carrier cold start mission and I couldn't have the chief remove the wheel chocks... got a message which said it comply because the air wasn't connected? wheel chocks showed on the aircraft in the external view. Am I missing something or is this a bug? was able to salute and taxi anyway...

Thank you for the reply, very helpful!

I didn't have any problems with the install, but I think you'll find about as many opinions as people you ask lol. 1. I started by removing EVERYTHING related to VR from my PC. Is this your first VR headset? if so, you can skip that step of course. 2. rebooted 3. Installed PiPlay (i installed the latest), rebooted, started piplay again 4. Connected the headset for the first time - I did not connect the headset to the computer before installing piplay 5. registered and updated firmware, rebooted again 6. Configured my initial settings in piplay, configured play space as sitting/large, high resolution, turned on eye tracking and calibrated, set IPD, turned on dfr, added a little sharpening, made sure I saw the space scape in the headset - rebooted again 7. ran DCS the first time. no problems for me. Since I was on the latest version i wanted to see if I could get DCS to work before adding the mbucchia stuff back. was able to play DCS at 90fps in instant action no problem. Challenges I had along the way... - studioform comfort stuff is mandatary in IMHO, the headset is unusable without it. - really takes some fooling around to learn how to put the headset on and get comfortable while looking through the sweet spot, have to really crank it down to get a decent fov - if the chaperone comes on while in DCS it will cut your fps in half, you need to make sure your playspace is taken care of so it wont come on while your playing. - I still plan to try with the mbucchia stuff instead. 13900k/64gb/5090

For those of you using WhisperAttack... do find it to be a significant upgrade? Does it enable more flexible speech input - like liberal use of callsigns and more flexible phrasing?

I havnt experimented with that yet, but from what I have seen from others that have - they seem to prefer doing the sharpening in piplay now.

In general, if a game supports DLSS you should use that.. it should be better than upscaling with FSR or NIS, but you can check it out and see which you prefer. You can still apply sharpening though. If a game does not support DLSS then FSR or NIS is the only option.

I am unable to get this to work for the corsair, does the app need an update to support new aircraft? it crashes when I try to create a new folder. Creating the folder manually also does not seem to work (doesnt show up in the UI)

what would cause me to not be able to log into my dcs server installation using the same username and password that logs me into dcs and the web site?

Any chance you could PM me your TelemFFB settings that you used to get a good setup?

My limited understanding of converting to Vulcan would suggest that it will (initially)... bring more consistency to framerates (not necessarily more fps, but smoother fps create the basis for making further performance optimizations (this is a long road and one that only STARTS with implementing vulcan.) allow ED to make other enhancements without negatively impacting frame rate as much They could also choose to take advantage of some of these things before they release it to us, meaning that they take a little longer but we get more tangible benefits when its released. - most of this was said above:)

If your motherboard does indeed support it, but you dont have a bios option to do it - it could be that you need to update your bios to a later version.

Your GPU supports it (gpu-z), your motherboard does not - so NVCP reports not enabled, because you cant enable it in the BIOS.

All resizable bar does is enable the cpu to access a larger portion of the GPU frame buffer at one time. Whether this has any impact on game performance is dependent on how that specific game accesses that frame buffer (how often, the size of the transfer, what it does with it etc..). Some games see a lot of benefit, some see little to none. In some cases (at least I've heard, no first hand knowledge of this) it can be detrimental. For it to be enabled by default, my guess is that the game publisher must ask NVidia to provide that in their game profile - NVidia wont do it by default for obvious reasons. ED probably hasnt seen sufficient gain (or believes there are scenarios where it is a problem), or just hasn't tested it - and so its not turned on by default. So now we have this work around where we can turn it on ourselves and test it and draw our own conclusions. It is most certainly the case that results will vary based on the factors I raised above (cpu, gpu, rebar options, cpu/gpu bound game scenario, etc..). I used the cold start on super carrier to do my test, but that could just be a scenario where it doesnt help. So.... all I'm saying is it's great that people post "try this!", but for this one it would be helpful if those who see a benefit provide more information:)