Jump to content
  • Advertisement
Sign in to follow this  
kretash

IASetIndexBuffer Error

This topic is 1067 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Hello,

 

I started getting the following error in my project:

 

D3D12 ERROR: ID3D12CommandList::IASetIndexBuffer: pDesc->BufferLocation + SizeInBytes - 1 (0x000000020514a4cb) exceeds end of the virtual address range of Resource (0x0000000000000000, Debug Name: '(nullptr)', GPU VA Range: 0x0000000204e5d000 - 0x0000000204e6cfff). This is OK as out of bounds access is guarded by the GPU (writes are discarded and reads return 0). However the developer probably did not intend to make use of this behavior.  [ STATE_CREATION ERROR #725: SET_INDEX_BUFFER_INVALID]

 

The error came out of nowhere as I wasn't touching that part of the project. I decided to execute one of the sample projects ( D3D12Multithreading ) and it was getting the same error. Both projects work well. I'm guessing this was part of the driver update? What does it mean?

 

Thanks.

Edited by kretash

Share this post


Link to post
Share on other sites
Advertisement

Do you mean the D3D12 samples throw this error unmodified? Maybe toss an issue at their github if that's the case. It's usually because the parameters in D3D12_INDEX_BUFFER_VIEW are incorrect. The buffer is too small or the range is too large.

Share this post


Link to post
Share on other sites


What does it mean?
 

It's basically like an array out of bounds error.  You say it started happening out of nowhere?  And whats this about drivers?

Share this post


Link to post
Share on other sites
So it's saying the virtual address supplied by your index buffer view is outside the range of the resource to which that address belongs to. However it lists the address of the resource as 'nullptr', which is peculiar. Is there any chance that perhaps you're already destroyed the resource containing your index buffer?

Share this post


Link to post
Share on other sites


Do you mean the D3D12 samples throw this error unmodified? Maybe toss an issue at their github if that's the case. It's usually because the parameters in D3D12_INDEX_BUFFER_VIEW are incorrect. The buffer is too small or the range is too large.

 

Yes, the error appeared in my code and it was also present in a sample that was working well and had no error messages. I'm gonna open a ticket.

 


And whats this about drivers?

 

It just came out of no where in both my code and the unmodified samples code, so I guessed that it must have come with the new drivers. Not sure, just a guess.

 


Is there any chance that perhaps you're already destroyed the resource containing your index buffer?

 

The index buffer is live. I'm updating it in between frames, don't know if that could be part of the issue.

Share this post


Link to post
Share on other sites

I add myself to the list: similar errors (IASetVertexBuffers and IASetIndexBuffer) after visual studio and drivers updates. It's a relief that I'm not the only one, though.

Share this post


Link to post
Share on other sites

Microsoft engineer here. I've reported this to where it'll get investigated and I/they will let you know the outcome.

Share this post


Link to post
Share on other sites

Microsoft engineer here. I've reported this to where it'll get investigated and I/they will let you know the outcome.


Thank you very much!

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

GameDev.net is your game development community. Create an account for your GameDev Portfolio and participate in the largest developer community in the games industry.

Sign me up!