Forum Discussion

🚨 This forum is archived and read-only. To submit a forum post, please visit our new Developer Forum. 🚨
genetransfer's avatar
genetransfer
Explorer
11 years ago

direct mode forceing windowed mode dx11.

(dx11 custom engine)
I just ran into an issue where my compute shader particles where not performing as well in direct mode as they do in extended mode which led me to think i was in windowed mode. sure enough direct mode seems to force directx into windowed mode. when i alt+enter it seems to go into fullscreen mode but my mouse acts like app doesn't have focus and spinns the camera around. if using "ovrHmdCap_NoMirrorToWindow()" and going into fullscreen (alt+enter) performance drops to 1 frame a second spins like i explained earlier.

is direct mode really windowed mode? why do compute shader seem to perform badly? is it me and i have missed a setting I followed tiny room and everything else is working well.

will keep looking to make sure I havn't missed anything, but everything runs fine in extended mode to the rift.

1 Reply

  • turned out because i render the scene using 4 cameras, 2 for the scene and 2 for displaying the scene textures on quads (to allow for dsr like resolution changes) the compute shader particles where being drawn to all 4 cameras. I prevented them from doing so and only allowed them to be drawn to the scene cameras and performance went back to a stable 75. however this does raise the issue if extended mode isn't more performance savvy as the frame rate was stable 75 in extended (fullscreen) before finding this out, doesn't matter at least it's working well now.