Andrew Frost

Hi Interesting: yes there was a change to this but we had checked that it only impacted the use of 'ignored' for that value .. but let me double-check! thanks

FYI we've been able to reproduce this too now, but cannot see how the failure was introduced -> working back and debugging, we may look to do a minor patch...

Thanks @itlancer - yes we've just been looking at this. There's some error handling that had kicked in as part of the earlier change, in some conditions, but the handler...

FYI we have a fix for this one now in the updated release: https://airsdk.harman.com/download

Thanks (fixed in 33.1.1.929)

Hi So while we'll continue to try to work out what part of Direct3D 11 is causing the problem, a workaround here would be to limit your app to Direct3D...

@LeeTomahawk the tag should go into your application descriptor file e.g. ``` ... 1.0 ... 9 ... ``` It would need to have that namespace value ending in `33.1` to...

Hi all Can I get some more details on the graphics drivers here please: can you try: 1) Hit Windows-X key and select “Device Manager” 2) Expand “Display Adapters” .....

Thanks - a little bit higher than that would be good too, so we know the name used for the adapter! and given the driver version there is 31.0, vs...

Okay thanks... so it's possible we could add a condition to check the driver details and version and then automatically limit things. Although this may be a bit of effort...