When I was testing my air 3.2 for ios game with starling framework and flash cs6, I got the error #1014: Class flash.display::Stage3D could not be found. So then I opened up a normal actionscript 3.0 flash document, and made a quick test, adding two squares to the stage with starling, and when I tested it, and it worked normally. Then I tried making another test but this time with an air for ios document, and I made it exactly as my previous test on the actionscript 3.0 flash document. I then got the error "This application is not correctly embedded, wrong wmode value". I'm getting an array of errors and I'm not sure how to approach this. The main difference between my air for ios game and the air for ios test document I made, is that the game had flash touchevents, I'm not sure if this is affecting anything. I checked all of my classes in my game and I had all my classes extended from the Sprite class from starling, I'm not sure why I am getting an error saying flash.display::Stage3d. I did have flash.display.Bitmap imported on a couple classes, but it was just used in the process of making starling textures.
Error #1014: Class flash.display::Stage3D could not be found.(16 posts) (5 voices)
I have an update, I'm actually silly and didn't set the render mode in AIR 3.2 to direct, so I did that and it fixed the wmode error I was getting with the air for ios test document, but unfortunately I'm still getting the 1014 error for my game. Any ideas?
I am getting the same error as you: 1014 Stage3d could not be found. If anyone could help I'd appreciate it.
(I've been developing a game for weeks and it suddenly stopped working.)
What tools are you guys using?
Sounds like you are pointing to the wrong PlayerGlobal.swc (this is where all the native as3 references come from)
If this is a runtime error, rather than a compiler error, then it sounds like you're testing in an older version of Flash Player or AIR.
In Rayne's case, if you've been developing this game without issue for a while, and it suddenly stopped working, maybe your file association for SWF files switched to a different standalone Flash Player executable? Or maybe you downgraded some other piece of software that includes a runtime and the version you were using got replaced somehow? It's hard to suggest more without knowing more about what your development environment looks like.
Well I am using Flash CS6, and after the intial install it was working perfectly until earlier this week. I'm not sure how it could have switched, but I have removed everything and reinstalled quite a few times to try and return to default.
My playerglobal swc is 11_3, but somehow I feel that it has to do with the flex sdk. I am still trying to solve the problem. I'm pointing to flex 4.5
I'll continue trying.
Interesting. I suspect that the compiler isn't using the correct swf-version for some reason. Even if you have the correct, newest playerglobal.swc, a swf-version that is too low will restrict your access to newer APIs. However, I don't really know how to change that in Flash Pro, beyond ensuring that the UI says that you're targeting Flash Player 11.3 (or at least whatever the minimum version is for Stage 3D support).
Since it's not clear from your post, is this a compiler error or a runtime error?
The Flex SDK shouldn't be causing your issue because it doesn't handle the final SWF compilation. It's only involved with embedding assets. Either way, you might want to switch to Flex SDK 4.6, since it's newer.
Well, just be sure, I completely reinstalled Windows7 and then Flash CS6, and I get the same error. So I think it might be a recent adobe update, because previously this exact setup worked.
It's not a compile error, it's a runtime error. As soon as I try and compile my output will be "VerifyError: Error #1014: Class flash.display::Stage3D could not be found."
And my compiled app will just be blank white screen.
This is an important project so I'm willing to do anything to get this working again.
If you're getting a VerifyError runtime error for a built-in class like Stage3D, it means that you're running the SWF in a version of Flash Player that is too old.
When you get this error, is the SWF running in Flash Pro's Test Movie? A browser? The standalone player?
Flash Pro's Test Movie. But you may be on to something, because I can run the .swf it generates, I just can't test it inside of Flash Pro.
I can specifically target 11.1 or 11.2 in Flash Pro, but I still get the error
It is most likely some setting you have to change in publishing settings, but unless it is somehow essential that you use Flash pro, I would recommend trying to do the project in FlashBuilder or FlashDevelop (if you are on windows), or even FDT.
You will have an easier type making and debugging the project in a proper IDE, with (in my experience) clearer ways to set things like build targets.
Also, as this is not a starling specific problem, you could try to get help op the official Adobe forums, where the Flash Pro wizards reside.
I'll talk to them. I chose Flash Pro to avoid these problems -_-. Thanks
I have managed to find a solution to the problem! When testing inside Flash Pro, I cannot use the "Test Project" button, I have to use the keyboard shortcut to "Test Movie". I have no idea why, but this is a relatively simple solution.
For my solution to this problem, I made a new fla and copy and pasted all my assets into the new flash document. Then when I tested my game from the new fla, I had no 1014 error. I think this may be because I worked on the game for a couple of weeks before downloading starling, then downloaded starling and put everything into the framework.
I had this error with Flash BUilder 4.5.
- Downloaded the 4.6 SDK and changed the Flex SDK version of my projetct.
- Changed "use a specific version" to 11.1.0
- Downloaded the last version of flashplayer_11_sa_debug and replaced the \Flash Builder\Adobe Flash Builder 4.5\player\win\10.2\FlashPlayerDebugger.exe with the new one, renaming it.Posted 4 months ago #
You must log in to post.