DirectX 11: slow reading from DEFAULT textures (C++)

[YuriyYuriy]

Hi

I've asked this question in Intel ARC Graphics forum, but I've been redirected here (https://community.intel.com/t5/Intel-ARC-Graphics/Direct-X-11-slow-reading-from-DEFAULT-textures-c/td-p/1539759)

In short: reading from DirectX 11 DEFAULT texture with "MiscFlags" set to 0 is too slow (depends on size of the texture, reading from 1920x1080 can take up to 60ms). If "MiscFlags" is not 0 (e.g. D3D11_RESOURCE_MISC_SHARED), then reading is much faster (1920x1080, less than 16ms)

No such issue on Intel UHD 770 and GeForce RTX3050

I've updated to the latest version of GPU drivers. Sample app project and environment files are attached

[karen_intel]

Hi @YuriyYuriy indeed this is the right forum for your report
Allow us to make a quick verification on our end, we'll be back soon!

Karen

[karen_intel]

Hello again @YuriyYuriy 

I was able to reproduce the behavior you're reporting in this thread. I am creating an internal report for our development team.

Will get back soon with the tracking number FYI

Karen

[karen_intel]

Hello again @YuriyYuriy 

We have reported your findings. Our internal tracking number for reference is 14020829805
Can you share what type of application you're trying to build? Just to add this info to the report.

We will update this thread as soon as we have news

Keep you posted

Karen

[YuriyYuriy]

Hello @karen_intel

Thank you for the reply.

The project I'm working on is related to video surveillance.

[karen_intel]

Hey @YuriyYuriy can you help us with the video surveillance application name you're working on?

It is a request from our development team. Thank you

Karen

[YuriyYuriy]

Hello @karen_intel 

It is named "Luxriot EVO"

[karen_intel]

Thank you @YuriyYuriy 

I have informed our team. If I need anything else, I'll let you know

Karen

[YuriyYuriy]

Hi @karen_intel 

Are there any updates from the development teams?

Thank you

[karen_intel]

Hi @YuriyYuriy 

Our average response for fixes after internal submission is ~3 to 6 months, fyi.

In some cases we have a faster response so I will let you know once we have a fix in a public driver for you to test (we have to test it first) 

Karen

[YuriyYuriy]

Hi @karen_intel 

Are there any news related to the problem?

Thank you

[karen_intel]

Hey @YuriyYuriy we're still waiting on feedback from the driver team
FYI fixes may take from 3 up to 6 months to be released. If we have any news sooner I'll let you know
Karen

[YuriyYuriy]

Hi @karen_intel 

Are there any news?

[karen_intel]

Hey @YuriyYuriy the issue is still WIP on our end and we've detected it has been spotted in newer products too.
Tomorrow I will be sharing the second report number
Thanks again for your patience.

Karen

[Esteban_Intel]

Hi @YuriyYuriy,

A possible fix for this issue is included with our latest driver version 32.0.101.6130 or newer. Can you please test using this driver version and let us know?