AIR 28 Error #3613: The native shader compilation failed

airsdk / Adobe-Runtime-Support

Report, track and discuss issues in Adobe AIR. Monitored by Adobe - and HARMAN - and maintained by the AIR community.

202 stars 11 forks source link

AIR 28 Error #3613: The native shader compilation failed #35

Open blackjyn opened 6 years ago

blackjyn commented 6 years ago

I have put it here: air28_feather-starlingerr

https://tracker.adobe.com/#/view/AIR-4198544

PrimaryFeather commented 6 years ago

Please provide a little more information about this problem:

Does it also happen with a pure Starling app?
Please post code with a minimal sample (e.g. displaying just a quad or image).
Your screenshots indicate that you're using "Baseline Constrained" profile. Does this also happen with other profiles? (E.g. by using the default "auto" value of Starling's constructor.)
Which are the exact versions of Windows, AIR SDK, Flash Player?
Did you experience this using the Flash Player (Projector), or an AIR app?

Thanks in advance!

blackjyn commented 6 years ago

I'm on Windows 8.1 x64 AIR SDK v28 , FP 28

It happens also for pure Starling app targeting desktop. For SWF target running on the browser it runs just fine air28_starlingerr

Adolio commented 6 years ago

Shouldn't you target -swf-version 39 for Adobe AIR 28?

blackjyn commented 6 years ago

Sadly this problem still persists in AIR v29 😢

PrimaryFeather commented 6 years ago

It's strange that no one else reported this problem yet. Could it be that this issue is Windows 8 related? Have you tried on Windows 10?

blackjyn commented 6 years ago

Actually somebody else has reported it : https://forum.starling-framework.org/topic/error-3613-the-native-shader-compilation-failed https://forums.adobe.com/thread/2414783 and yes, their OS are typically Win8/Win8.1

I don't test it on Windows 10, .. I don't have any plan to move on Win10 any time soon

blackjyn commented 6 years ago

and actually people who are using Win10 are also facing the same problem https://forum.starling-framework.org/topic/error-3613-the-native-shader-compilation-failed#post-108624 nativeshadererr

Or , is this Problem related to Intel HD Garphics???

blackjyn commented 6 years ago

UPDATE: For SWF target, it runs normally when the content is loaded under http:// protocol. So using local server , the content is running just fine

For Mobile target, running and debugging DIRECTLY on real mobile devices are Okay

The desktop target remain the same, still getting errors

blackjyn commented 6 years ago

With the release of AIR SDK 29.0.0.103 the problem still persists! Oh Cmon Adobe!

PrimaryFeather commented 6 years ago

You need to make it easier for them to reproduce the issue, @blackjyn. My recommendation:

Create a minimal sample SWF and host it on a website.
Add a link to that sample to the bug report (here and at Adobe Tracker).
Include a download for the complete source.
Describe the exact operating system and hardware you experienced the problem with.

Then send me another note, and I'll try to get it to their attention. Right now, it's just a vague report for them which won't get prioritized.

blackjyn commented 6 years ago

Simply run the Official Sample from Starling using AIR v29.0.0.103 on Windows 8.1 x64 , GPU Intel HD https://github.com/Gamua/Starling-Framework/tree/master/samples/demo_mobile

freaking clear , and I'm not the only one who experience this

PrimaryFeather commented 6 years ago

Hey, I'm trying to help you here get the proper attention from Adobe! "Freaking clear" or not, they need to have simple step-by-step recipe to recreate the problem, or they won't look into it.

blackjyn commented 6 years ago

I'm not get mad on you ~ Since this problem is quite 'classic' and has been there for years but Adobe did NOT listen (or probably doesn't care), and NO other resources could give meaningful help https://forum.starling-framework.org/topic/fault-the-native-shader-compilation-failed#post-84815 err

PrimaryFeather commented 6 years ago

No worries, I can understand that you're frustrated! 😞

In any case, you got a reply from Adobe in the tracker forum, so be sure to post as much information as possible over at "tracker.adobe.com" while you have their attention! Good luck!!

blackjyn commented 6 years ago

Yep I'm frustrated. while bringing "GPU-accelerated" mantra on Flash Platform is a great achievement, I think it leaves fundamental untouched problem specifically on DirectX11 . But I understand that this is the cost when we use the bare metal of hardware: hard to develop but its worth it

dedosmedia commented 6 years ago

Sorry for coming late to the party, I missed this thread. I have updated AIR-4198544 with a sample project so they can try to reproduce the issue. here is the link to the project and some more information: https://www.dropbox.com/sh/sc378ssvsepgzjt/AADEdjuFOscuTYeclSRH_96da?dl=0

Actually the project is as simple as the one explained here: https://gamua.com/starling/first-steps/

Unfortunately this just happens on older PCs (W8+) with Intel HD Graphics, hopefully Adobe can get one where to reproduce it.