DX11 Compute buffers broken?

@vrdaweb: We're only using direct-mode at the moment, as all of our attempts to get extended mode working for a unity build have failed. Crashes/weird behavior/etc. There were also critical fixes in 4.5.3 (originally in patch build 3) that our project needed, so we're stuck with that version. For the next SDK update, would it be helpful for you if we put together a more complete Unity 4.5.3 project for you guys to test with, to make sure the compute buffer stuff works? I can assemble and pass you one if you'd like.

Hey there,

Thanks for the reply vrdaveb. Do note that this was tested on 4.5.2 patch build 3 as well, which I believe came before the ovr 0.4.1. Still might be worth to try vanilla 4.5.2 though, as they did change some things for DX11 in the patch. Also as Anton noted, we're only using Direct to Rift, other modes crash and burn completely.

About the stripes: These are the rings that are otherwise rendered fine, but because the compute buffer only has it's first element set, the ring becomes a stripe. It was a bright orange stripe, like the rings you saw. It was not a distortion artifact.

Also note that editor intergration is completely broken for me, the game view only very occasionally shows something. All these issues are talking about issues in the build.

It would be great if you try to make a build of the project in 4.5.3, and see if that is broken for you. Even if it works in 4.5.2, 4.5.3 contains fixes quite specifically for DX11 + the rift, so it would be great to have that.

Also, I will send you the TC Particles package as well to try out. Thank you!

"Anton" wrote:
For the next SDK update, would it be helpful for you if we put together a more complete Unity 4.5.3 project for you guys to test with, to make sure the compute buffer stuff works?

Thanks. We will use the two sample projects you've already sent as test cases moving forward. That should be enough unless you are having other issues that aren't present in these projects.

"Anton" wrote:
We're only using direct-mode at the moment, as all of our attempts to get extended mode working for a unity build have failed. Crashes/weird behavior/etc.

What kinds of problems are you having there? I would expect extended mode to be at least as stable as direct mode right now. Note that with 4.5.3 (and the recent 4.5.2 patch releases), the "-adapter" flag is broken, so you have to hold ALT and choose the Rift manually the first time you run the app.

"ArthurBrussee" wrote:
Also note that editor intergration is completely broken for me, the game view only very occasionally shows something.

The editor integration doesn't support direct mode yet.

"ArthurBrussee" wrote:
It would be great if you try to make a build of the project in 4.5.3, and see if that is broken for you... These are the rings that are otherwise rendered fine, but because the compute buffer only has it's first element set, the ring becomes a stripe.

Yep, with 4.5.3 and direct mode, I was finally able to reproduce the problem. There were two separate horizontal stripes, one in each eye. I'll let our driver guys know about the problem. For now I'd like to help you resolve any issue you're still having with extended mode.

Hello,
Has this been fixed for an upcoming version? I really need to get my DX11 FX working again for upcoming demos...
Let me know if there is anything I can do to help.
Thanks!

@vrdaweb: Any word on whether this has been fixed yet? We're totally stalled out on vr development of our game until this is fixed (our entire vfx stack relies on compute buffers).

There is a release in QA right now that includes some significant driver improvements. I'll make sure we test this case.

Is there a rough release day for this new SDK yet? My project was largely dependent on DX11 and it's very difficult to make progress. I have made a new project using SteamVR, which has working DX11 and head tracking, etc. I can't have both the Oculus SDK and SteamVR in the same Unity project though, so I need to decide very soon which one to commit to.

There's a new SDK coming relatively soon, but I'm not sure your issue will be solved. Sorry for the delay.

0.4.3 should have fixed this. Is it working now?

This is fixed for me (Unity 4.5.5f1)...TCparticles as an example. Thanks!!