-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Starling/Away3D interoperability is broken #55
Comments
Just to follow up on this, we were able to get it working on our project essentially by fiddling around with events/ordering of things. Here is a commit that fixes it on our project: TerryCavanagh/radio-silence-hx@72f9f2f#diff-63879aafd34c9dbb5251d9c8266fc04c72c1259d876eae0cba9d84dfa8872684 So: there is a bug here, but it's one that can be worked around, so perhaps it's not that serious. Happy to close this? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I think Starling and Away3D interoperability is currently broken. When I try making a simple demo project with a starling layer and an Away3D layer, it just renders a black screen. Here's an example:
radiosilence_hx.zip
(or on github here: TerryCavanagh/radio-silence-hx@d398652)
This example is basically just following this old Away3D tutorial written with AS3 - http://away3d.com/tutorials/Away3D_and_Starling_Interoperation
In addition, this unrelated issue #39 contains an example Away3D + Starling project, and it just renders a black screen for me too.
(Tested on Haxe 4.3.1, OpenFL 9.2.2, Lime 8.0.2, and Away3D and Starling up to date from github. Apologies if I'm just doing something dumb, as usual)
The text was updated successfully, but these errors were encountered: