Since 5.4.2 I have a problem that doesn’t appear in previous versions:
I have reported it to Unity.
Help @jonas-echterhoff_1
Since 5.4.2 I have a problem that doesn’t appear in previous versions:
I have reported it to Unity.
Help @jonas-echterhoff_1
Have you submitted a bug report ? If so, what’s the bug number ?
#846086
I said in the report that it happens with an AVPro Video but it happens in many other ways also.
It would be really helpful if you could attach a repro project.
Thanks.
I’m logged on my personal account.
#849188
I didn’t attach it because it was a big project but I have remove some videos and lower it down.
thanks for the new bug report and repro project, we are investigating.
Thanks!
Can be fixed for the next patch release? So I can decide to update to the next patch release or downgrade to 5.4.1 (the last version that worked).
We believe this is a side-effect of the MEMFS_APPEND_TO_TYPED_ARRAYS=1 workaround described in my recent memory blog post.
We are going to fix it ASAP but I can’t promise the next patch release. I will update you here.
For now I would suggest to use 5.4.1 or 5.4.1 Patch 1. Apologies for the inconvenience.
Thanks, Marco!!
I have another problem.
If I downgrade it to 5.4.1 I have this error in WebGL build:
I already tried to delete “Library” and “Temp” folders and do a full reimport without any luck.
I have now a serious problem because I can’t build my project in any version.
Any workaround Marco?
Have you tried building to a new folder ?
Yes because when I made the downgrade I duplicated the project (that is versioned) so I only need to downgrade it for WebGL because it targets more platforms (Windows, OS X, Android, iOS and UWP).
So yes, it’s a new directory.
I don’t know that error from where it comes.
ok… have you re-installed Unity on top of the previous one or into a new folder ? Maybe something got mixed up.
No, I have multiple Unity versions on my machine (Windows), I never overwrite a version.
What if you create a new empty project, are you able to build that ?
No, same problem.
So seen this it looks that I’ve found another bug. If you have multiple Unity versions installed in a machine you can’t publish with a previous version for WebGL (5.4.1 vs 5.4.2).
Should I report it?
Let me see if I can reproduce the problem. You downgraded from 5.4.2f1 to 5.4.1f1, is that right ?
In the meantime, could you please try 5.4.1 Patch 1 ?
I have multiple Unity versions installed on my machine including 5.4.1f1 and 5.4.2f2 on Windows 10.
Scenario 1: Project downgrade from 5.4.2f2 to 5.4.1f1
Result when opening published index.html: "Invalid serialized file version. File: “globalgamemanagers”. Expected version: 5.4.2f2. Actual version: 5.4.1f1.
Scenario 2: New project created on 5.4.1f1 directly.
Same result as before.
So as you can see we have found two bugs:
I’m going to try now, 5.4.1p1.
In 5.4.1p1 the:
“Invalid serialized file version. File: “globalgamemanagers”. Expected version: 5.4.2f2. Actual version: 5.4.1f1.”
It’s fixed.
I still have the 5.4.2 error of this thread “Uncaught RangeError” that I want to be fixed so I don’t have to have two Unity versions 5.4.1p1 (WebGL) and 5.4.2 (for other platforms).
We are working on a fix.