This project is read-only.

OMSetRenderTargets Access violation reading location


If you maximize your window at all the Oculus Rift sample will stop rendering everything but the Warning text.

If you maximize with windows key + up arrow immediately when starting it throws an error
Unhandled exception at 0x547E55B0 (d3d11_2sdklayers.dll) in OculusRiftSample_Desktop.exe: 0xC0000005: Access violation reading location 0x0000008C.

Not sure if this error happens outside of the oculus sample program.


jacobsgriffith wrote Nov 15, 2014 at 6:18 AM

The error throws on line 490 of CAPI_D3D1X_DistortionRenderer.cpp

RParams.pContext->OMSetRenderTargets(1, &RParams.pBackBufferRT, 0);

jzink wrote Nov 15, 2014 at 1:17 PM

Thanks for reporting this - I never tried to maximize the window in the Rift samples. I am in the process of upgrading to the DK2 and Oculus SDK 0.4.3, so I can take a look to see what is the problem.

jacobsgriffith wrote Nov 15, 2014 at 5:28 PM

Awesome! I'm also getting unresolved external symbol errors with the DirectXTK with the Oculus project as well.. I upgraded DXTK to the latest version and it gave me those errors. Which version are you using?

jacobsgriffith wrote Nov 15, 2014 at 6:06 PM

So I tried getting the latest DirectXTK nuget package 2014.07.15.1 and it was still showing unresolved external symbols so I ended up downloading the library from and then commented out lines

1286 of RendererDX11.cpp which handled loading of dds texturesand8027 of PipelineManagerDX11.cpp which handled saving a screenshot

and now my solution is compiling!

jzink wrote Nov 18, 2014 at 2:40 AM

I am using an older nuget package, and will be upgrading soon to the VS2013 packages found here: I'm not sure if that would resolve your issue or not, but the key is to have the proper PDB's in the nuget package that is being used. It will take a little while to use that package though, because I need to upgrade all the project and solution files accordingly :(