iOS 15 + WebGL 2 issue

This is exactly the same behavior I experience here: The suggested workaround by @brendanduncan_u3d lets my game start again without crashing. But after playing for some seconds the elements on the screen start to flicker heavily.

I tried to enforce WebGL1 again, but the behavior remains the same (flickering).

Is there a page where we can follow the "P1 Major issue" along? Or is this all Apple-Internal?

 

Thanks so much @brendanduncan_u3d for narrowing this one down, the workaround seems good for my test case too.

One little note for anyone using Unity 2020, the Library folder to delete to ensure the il2cpp code with the workaround is rebuilt seems to be Library/Il2cppBuildCache - might be worth editing your post / posting a new topic so all the info is in one place.

 

Thanks Brendan...But this solution doesn't work for webGL+URP....

Ios15.4+unity3d 2020.3.31f1 + webGL + Universal RP 10.8.1 + windows10.1 64 ...

 

It works! Thanks for your hardwork @brendanduncan_u3d!

 

It seems very weird that disabling optimizations for one function would cause this, but I see the same thing here - thanks for the note.

 

My game also has a canvas UI bug that keeps flickering and I have tried to build in both WebGL1 and WebGL2 and tried to turn off and on WebGL2 in ios but the issue is still there.

 

@brendanduncan_u3d I am using WebGL2.
In my project, when the RenderMode of the Canvas is Screen Space - Camera, the image flashes.
This does not happen when Screen Space - Overlay is selected.
I am not sure if this is a problem specific to my project or not.

 

Good Point!
For me the flickering is also happening on the UI Canvas Layer

 

Thanks this actually fix my issue for the UI but my 2D character in the game is still flickering

Edit: After a bit of testing I found out that my 2D character require multiple different materials on it and I suspect it might be the issue.

 

hello brendanduncan.I'm not very familiar with C#, I want to ask how to add #pragma clang optimize off and #pragma clang optimize on

 

I did everything as brendanduncan_u3d
said, but I still don't have the game running on iOS 15.4. What to do?(

 

@brendanduncan_u3d Thank you very much for your work.

The issue that is not running in iOS 15.4 has been resolved,
but SortingGroup has a issue that does not work normally. (Looks like z-axis fighting)

I know Apple will solve this problem someday, but I just wanted to let you know this issue.

 

Where does it come from? -->The issue that is not running in iOS 15.4 has been resolved, would love to know how you solved it please.
I still couldn't run webgl on my IOS 15.4?

 

I've done a bit more digging into relevant WebKit bugs on the webgl regressions to see if they give any hints for potential workarounds. There are a couple of interesting recent fixes that have potential workarounds:

https://chromium-review.googlesource.com/c/angle/angle/+/3450033
This one fixes a bug around not resolving multisample buffers at the right time, and looks like it can be worked around by disabling antialiasing; I've confirmed this fixes this three js example with Safari 15.4 on M1 Mac (in both webgl1 and webgl2).

https://chromium-review.googlesource.com/c/angle/angle/+/3426828
It looks like invalidateFramebuffer is broken in 15.4, and Unity uses this (correctly) internally according to kbr. As this is intended to just be a performance optimization, some of the issues might be improved by just avoiding these calls on 15.4. One way might be to monkey-patch the function in the webgl context to a no-op to avoid the need to change Unity code at all.

I hope this helps someone!

 

I have reproduced the Flickering Issue in a minimal clean project.

Here you can find a small Unity Project with the sources:
https://github.com/chilledbits/unityWebkitIssue

Here you can check the testcase:
https://romanwache.de/uploads/webkitbug
(UPDATE: or the simplified one: https://romanwache.de/uploads/webkitbug_notween/)

We can only see the Flickering behavior since iOS 15.4, beforehand everything was fine.
Actually it doesn't happen on my MacOS Safari.

How to reproduce:

• visit the live-test: https://romanwache.de/uploads/webkitbug with an iOS device ( >= 15.4)
  
• Let the cards fly for around 40 seconds
  
• Tap anywhere on the screen (NOT the button "remove canvas") this toggles the Animations on the screen
  
• When the animations are stopped the Flickering starts
• Once you click the button "remove canvas" the flickering stops

So this seems to happen in the combination of Animators and more than one Canvas-Elements in the scene.

@brendanduncan_u3d >> I would be super happy if you could find the time to have a look here.
Your help is highly appreciated.

UPDATE
I simplified the version more: removed all DOTweens and went down to one single card with an Animator attached.
The same happens, but now it could be easier to find the reason.
https://romanwache.de/uploads/webkitbug_notween/

 

IOS 15.4.1 still cannot load webgl...???
Runtime error: Out-of-bounds memory access (evaluating 'Module["asm"]

 

@RickLeung - Indeed, the underlying wasm issue in webkit hasn't been fixed yet, so 15.4.1 still requires the workaround. https://bugs.webkit.org/show_bug.cgi?id=238302 is the webkit bug to watch - there's a patch there now but not yet committed.

@chilledbits - From Safari's WebGL canvas recording function, it looks like the draws end up in the wrong order when the flickering happens. In the frame below the "wooden" background is actually the last draw call made. The first 3 are also mis-ordered (text, dot, background for the top overlay). No idea why this behaviour would be iOS only, but might give someone a hint about where to look.

 

Updated ios 15.4.1, the problem is not resolved....

 

Apply the cpp code fix below and build. It does not work perfectly, but run is possible.

 

@
brendanduncan_u3d

I have been getting the same issue after upgrading to latest safari version 15.4 in Unity version 2020.3.22f, Unity version 2020.3.20f1,2019.4.31f1,2021.2.8f1

Runtime Error
: Out of bounds memory access(evaluating'dynCall_ii(index,a1)')<?>.wasm-function[23135]@[wasm code]<?>.wasm-function[24968]@@[wasm code]<?>.wasm-function[26322]@[wasmcode]wasm-stub@[native code]nvoke_ii@blob:https://..............

but the weird part is the Webgl builds from 2020.3.11f , 2019.4.28 loads without the above error but the screen is zoomed in.. resolution is messed up.


but now I have noticed in the versions that work when we try using the notification bar or bring the app into background the error pops up

 

Hello,
We've been struggling with this too. Tried the CPP fix suggested by brendanduncan_u3d, but did not work.
We followed the exact same steps suggested but ended up getting the same Runtime Error
: Out of bounds memory access(evaluating'dynCall_ii(index,a1)')<?>.wasm-function[23135]@[wasm code]<?
@brendanduncan_u3d, Can you kindly provide any other directions?

 

VideoPlayer Component does not work properly in IOS even if I modify the CPP code and run the build.
How can i fix it?

 

i fix it like this

Code (CSharp):

1.         vp.audioOutputMode = VideoAudioOutputMode.None;
2.         vp.EnableAudioTrack(0, false);
3.         vp.SetDirectAudioMute(0, true);
4.         vp.Play();    

 

Hello everyone;

just wanted to jump in with some info if it helps anyone:

We're developing WebGL games for mobile phones for a client, and as you may imagine - we hit a hard rock with this 15.4+ iOS thing - people are not happy either

However after some tests (lot of builds to be honest lol) - we found a FULLY working solution:

Unity 2021.1.22 (can't say if this works on other unity editor versions but it might):
1. Do this https://forum.unity.com/threads/ios-15-webgl-2-issue.1176116/#post-7982496
2. Build settings:
- development build OR non-dev (both work)
3. Publishing settings:
- enable exceptions: explicitly thrown
- data caching - works with on or off

And - yes, games work back on iOS 15.4.1 here and normal as usual on Android phones.

Good luck everyone!

 

This is working, thank you very much, but then when it would be fixed officially?

 

How about the decompression option? None? Gzip?

 

Hi,
We're sadly battling the same issue. However the fixes proposed in the thread (setting the #pragma directives in GenericMetadata.cpp to turn clang optimizations off and on suggested by @brendanduncan_u3d ) do not seem to make any noticeable change in the build result, we're seeing the same artifacts as before.

This is quickly becoming a major problem for us... Getting lot's of complaints from our customers that our application does not work...

We're using Brotli compression but disabling it doesn't seem to achieve any result either.

Our Unity Version is 2020.1.11f1. Could it be that this version won't work even with the fix? We're currently trying to upgrade to 2021.3.0f1 (LTS) to see if the fix works there. Will post an update when we know.

Depending on the computer we're seeing different artifacts. My teammate who's on an Intel Mac is seeing all lights cast an enormous glare (screenshot 1) whereas I'm on an M1 Pro MacBook and I just see ghosting of gameobjects whenever I move plus a weird corrupted part of the screen looking like an EGA monitor.

Intel Mac




M1 Pro Mac



I understand this is ultimately on Apple to fix but our customers simply do not care (nor should they, to be honest) so any help in getting to an interim fix would be greatly appreciated.

 

@brendanduncan_u3d thank you so much for replying. I do understand that you and the Unity team are doing everything you can to push apple for a Fix and providing support and transparency about the situation here in the forums!!

Evidently I misunderstood the fix for a graphics issue fix so I'm sorry for that confusion. I'm left wondering whether all the others just fixed the WASM crash and just have tons of graphic glitches on their applications or if there's something we're doing particularly wrong to experience all of these issues and glitches or if this is just plain bad luck.

The fact that the build behaves perfectly fine in Chrome suggests this is entirely on WebKit but I'm a bit surprised that some people in the thread seem to have had their issues fixed while our project is clearly unusable in this state. (we never saw WASM crashes, with or without the clang fix)

Again, I cannot overstate how thankful I am for the support provided, even if it ultimately doesn't solve our issue at the moment.

 

Hi,
we've studied and tried all suggested solutions on this forum thread. Unfortunately nothing worked for us.
Maybe this workaround will be helpful for someone. We've downgraded our project to Unity 2019 LTS version and it solved all issues with WASP and JS loading errors. The WebGL build works on iOS 15.4 with no issues. We had to create new project in Unity 2019 and manually export/import packages from 2020 LTS to 2019. Unity 2019 has different HTML template so this had to be changed as well but finally this solved all issues on iOS 15.4. Maybe this will help someone. Good luck.

 

For us the clang-optimizations made the game not crash anymore on startup. But we still have strong graphical issues (flickering due to different draw-call-orders from frame to frame). We are a bit fortunate as our game is not released yet - so I can cross my fingers and hope for iOS 15.5
I know this doesn't help you, just wanted to show that you aren't alone.

 

I'm using Unity 2020.3.25f1. The same issue happens.

Same issue happens. Is there any workaround?

 

15.5 Beta 2 is out and still doesn't resolve the UI-Flickering for us

 

Apple is a joke

 

But does it at least load now, or do you need to do the workarounds from earlier in this thread?

 

I always say this as well. Toy company )

Anyway - wanted to also add - despite our great success with fixing 15 2D games with approach described in earlier post and while games seem to work just fine - we lost all sound on builds :/ Currently don't know much about that (I had some vacation in between things) - and we're unable to test on 15.2 right now.

Will keep posted here if anything becomes clear.

Also - re 15.5 - if anyone checked - do they load without this .cpp workaround? Thank you.

 

Hello Brendan, we tried everything in this thread and we still having some issues in both Safari Mac M1 and Safari iOS 15+. The game loads correctly in every other browser (ff, chrome) in both platforms.

Unity Version: 2021.2.19f1
The error we have is different from what's reported here but probably related.
The game starts and loads fine (before it wasn't loading at all) but when we trigger some particle explosions, the game crashes with the following error:

Code (CSharp):

1. An error occurred running the Unity content on this page. See your browser JavaScript console for more info. The error was:
2. RuntimeError: Out of bounds memory access (evaluating 'asm[name].apply(null, arguments)')
3. <?>.wasm-function[AnimationCurveTpl<float>::Evaluate(float, AnimationCurveTpl<float>::Cache*) const]@[wasm code]
4. <?>.wasm-function[EvaluateSlow(MinMaxCurve const&, math::_float4 const&, math::_float4 const&)]@[wasm code]
5. <?>.wasm-function[Evaluate(MinMaxCurve const&, math::_float4 const&, math::_float4 const&)]@[wasm code]
6. <?>.wasm-function[ParticleSystem::UpdateModulesPreSimulationIncremental(ParticleSystemUpdateData const&, ParticleSystemParticles&, unsigned long, unsigned long, math::_float4 const&, bool)]@[wasm code]
7. <?>.wasm-function[ParticleSystem::Update1b(ParticleSystemUpdateData&, int)]@[wasm code]
8. <?>.wasm-function[ParticleSystem::UpdateFunction(ParticleSystemUpdateData*)]@[wasm code]
9. <?>.wasm-function[ParticleSystem::BeginUpdateAll()]@[wasm code]
10. <?>.wasm-function[ParticleSystem::InitializeClass()::PreLateUpdateParticleSystemBeginUpdateAllRegistrator::Forward()]@[wasm code]
11. <?>.wasm-function[ExecutePlayerLoop(NativePlayerLoopSystem*)]@[wasm code]
12. <?>.wasm-function[ExecutePlayerLoop(NativePlayerLoopSystem*)]@[wasm code]
13. <?>.wasm-function[MainLoop()]@[wasm code]
14. <?>.wasm-function[dynCall_v]@[wasm code]
15. wasm-stub@[wasm code]

We also found this link with somebody else having the same issue:
https://stackoverflow.com/questions/71367372/unity-webgl-build-particle-system-error-on-safari

Is it possible that we need to do the proposed fix here but for a different function?

Thanks!!!

 

Cannot expect the company that delay webpush and webxr for many years to just fix webgl for us

Really hope this company should just bankrupt