-
-
Notifications
You must be signed in to change notification settings - Fork 878
Jet Velocity: Cannot start game #10639
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
Comments
Progressed by #10638, #11045, and #11084. With all of those merged in, the main menu background gradient and music load correctly, but that's about it. The new error is:
|
Amazingly enough this does seem like a legit use of namespaces: |
Allegedly fixed by #12540. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Link to SWF: https://uploads.ungrounded.net/553000/553350_jet_velocity_viral.swf
After the loading screen, Jet Velocity shows nothing but a black screen.
In the current version of Ruffle, the game is blocked by XML.hasComplexContent being unimplemented. With #10638, the error no longer occurs, but the game still doesn't load.
Expected behavior
The game should load.
Note: when testing in the Flash projector, you'll need to load the game via the provided SWF URL (File => Open, then paste the URL). Due to Flash's security restrictions, the game doesn't load locally.
Affected platform
Desktop app
Operating system
Windows 10
Browser
No response
Additional information
Here is a decrypted version of the game with some trace statements added: jetvelocity_trace.zip
I recommend loading the game via a local web server so you can compare the trace output with the debug Flash projector.
Notice that both Flash and Ruffle trace "loading image bytes" many times, but only Flash ever traces "onLoaderComplete start!"
The relevant function is
onZipComplete
incom.devm.util.misc.BitmapZipDispenser
.The COMPLETE event of the Loader is never dispatched. I think this may have the same cause as #10463.
The text was updated successfully, but these errors were encountered: