# \[OptiX 8.0\] OPTIX\_DEVICE\_PROPERTY\_SHADER\_EXECUTION\_REORDERING returns 0

**URL:** https://forums.developer.nvidia.com/t/optix-8-0-optix-device-property-shader-execution-reordering-returns-0/263025
**Category:** OptiX
**Created:** [August 13, 2023, 11:48pm UTC](https://forums.developer.nvidia.com/t/optix-8-0-optix-device-property-shader-execution-reordering-returns-0/263025 "2023-08-13T23:48:10Z")
**Posts on this page:** 1
**Showing post:** 6

<div class="post-metadata">

### Author: ![droettger](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/droettger/32/14043_2.png) [@droettger](https://forums.developer.nvidia.com/u/droettger)
#### Post date: [August 15, 2023, 5:59am UTC](https://forums.developer.nvidia.com/t/optix-8-0-optix-device-property-shader-execution-reordering-returns-0/263025/6 "2023-08-15T05:59:50Z")

</div>

The printf issue is fixed in R535 drivers.

I haven’t tried with current drivers but I think debugging and profiling still needs it unfortunately.  
As the programming guide says, only set it when you don’t hit breakpoints.  
It’s definitely going away in the future when all involved components have added the necessary support.

---

_[View the full topic](https://forums.developer.nvidia.com/t/optix-8-0-optix-device-property-shader-execution-reordering-returns-0/263025)._