Closed n0samu closed 1 year ago
The same error is displayed when trying to start the game in Koutack and when trying to start a level in Track the Ball. Both games use tweening when transitioning between screens. Is it the same problem?
same problem with Road_of_the_Dead.swf
screen goes white link to swf
Update: I found that the issue with Koutack is indeed the same problem. On the other hand, the issue with Track the Ball occurs because the levels are stored as XML data, and the required XML functions are not yet implemented.
same problem with Road_of_the_Dead.swf
screen goes white link to swf
This does indeed seem to be the same problem - it's also fixed by #9007!
Describe the bug
Link to SWF: http://i.notdoppler.com/files/accurateslapshot.swf Note: Requires a stub of
SharedObject.size
.In Accurate Slapshot, there are 2 related issues:
Both buttons are supposed to go to the level select screen. And in both cases the following error is shown in the terminal:
[ERROR ruffle_core::avm2::events] Error dispatching event EventObject(EventObject { type: "enterFrame", class: flash.events::Event, ptr: 0x29adda9bf20 }) to handler FunctionObject(FunctionObject(GcCell(Gc { ptr: 0x29ac48bac88 }))) : RustError("Cannot access property ::length of null or undefined")
Expected behavior
Both buttons should take you to the level select screen.
Affected platform
Desktop app
Operating system
Windows 10
Browser
No response
Additional information
Both problems are caused by code in the game's
TweenMax
package. Here is an SWF with many trace statements added to demonstrate: accurateslapshot_trace.zipAfter clicking the Continue button, the
showLevelManager()
function runs:Notice that in Ruffle, the first trace is shown right before the error, and the second trace never shows.
The
killChildTweensOf
function callsgetAllTweens()
:Notice that in Ruffle, the first trace is shown right before the error, and the second trace never shows.
And finally in
getAllTweens
, we have the offending use oflength
:This code is very difficult to read, and I can't figure out why
_loc4_.length
causes the error, but it does.