You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi guys, I'm using 2.0.0-rc11 assetConversion.js script to migrate my assets. I've successfully migrated all asset I have, but there's one, large one. which fails and throws maximum call stack size exceeded error on libSetup method. The file is 10372K, 386061 lines of code. I know, it's very big resource file, but is there any to chance to get this fixed, to have higher limit of source assets file size? I'll try to split it manually, or reexport from Animate, but I'd expect the script should convert assets of any size? Maybe there's something that can be optimized to allow this large conversion, what do you think about this, have you got any reports, or is there someone, who had the same problem? Thanks a lot, good luck in upcoming releases!:)
The text was updated successfully, but these errors were encountered:
I've successfully exported the mentioned assets of a big project from the source fla from Animate. But anyway, I'll leave this issue here just to let you know that this can happen, on a large assets file.
Hmm, it's been a while since I was in that script, but I didn't think there was any recursion going on that would hit a max call stack. I will take a look when I get a chance.
Hi guys, I'm using 2.0.0-rc11 assetConversion.js script to migrate my assets. I've successfully migrated all asset I have, but there's one, large one. which fails and throws maximum call stack size exceeded error on libSetup method. The file is 10372K, 386061 lines of code. I know, it's very big resource file, but is there any to chance to get this fixed, to have higher limit of source assets file size? I'll try to split it manually, or reexport from Animate, but I'd expect the script should convert assets of any size? Maybe there's something that can be optimized to allow this large conversion, what do you think about this, have you got any reports, or is there someone, who had the same problem? Thanks a lot, good luck in upcoming releases!:)
The text was updated successfully, but these errors were encountered: