Error #3613: The native shader compilation failed.

mikale

Using the latest version of Starling. My AIR SDK is working and updated, but I am getting this error trying to initiate Starling: Error #3613: The native shader compilation failed. Any ideas?

Daniel

Do you have any additional shaders / extensions in your project besides vanilla Starling?
On which device / platform are you seeing this?

mikale

No I do not, I am on an Acer Aspire 7741Z running Windows 10. Intel HD graphics. Tried in both Flash Builder 4.7 and FlashDevelop and am getting the same error. I can run the Starling demo on the website so I think that my graphics card is capable. Just not debugging/running code I make.

dfdiaza

I have also seen this error in one of my PC running W8 x64 (it does not happen on a Mac mini running W8.1 x64) when working with AIR SDK 27, running the Starling Flappy example I get the Error #3613

This was a screenshot I took showing the error and Adobe Scout Session info:

On the same machine, using AIR SDK 27 but with --swf-version=37, I don't get the error, here a screenshot showing Adobe Scout Session info:

It seems like the AIR SDK 27, is trying to use DirectX 11 but it does not work for any reason on some Windows 8+ machines, instead of falling back to DirectX 9 it just fails.

Hope this can help you to understand the issue.

mikale

Thank you for the insight. Set swf-version to 37 and it's debugging just fine. It was set to 38 before. I guess newer isn't always better. Now I can get back to coding 😃

donricardo

I am also having the Error #3613: The native shader compilation failed
Setting swf-version=37 works but I think it's not a solution. What if I need "Asynchronous texture upload for AIR Desktop" which is only available on AIR SDK 27?

Is there a way (other than setting swf-version=37) to keep AIR using DirectX9 instead of DirectX11 and at the same time allowing me to use new AIR SDK 27 features?

Hope someone else have fix for this issue. Thanks

Daniel

I suppose that the problem is related to AIR 27 switching to DirectX 11 for rendering (as described in the release notes).

You're right, donricardo, sticking to the old swf-version is not a permanent solution. We need to make Adobe aware of this, so that they can fix it.

Could one of you please create an issue (as described here)? It's important that Adobe has a working sample and all the information it needs to reproduce the issue. Then I'm sure we'll see a fix on this one.

As soon as it's there, I'll ping them so that they're not overlooking it!
Thanks a lot in advance!