WebGL huge performance lost when deffault 3d object added (Only on Safari)

[Biebras]

When I build a webGL project with a default 3d quad object (I only tested quad and plane) the fps drop from 60 to 15 (only for Safari). When I build the project without a quad, the game runs 60 fps on every browser.

Some info about my project:

• I’m using URP with default settings.
• The scene has 111 cards. Each card has 2 quads that use a custom shader (These cards appear not to cause any performance issues, there are no other 3D objects).
• The target fps is set to 60 FPS

I am attaching a profiler screenshot.

[Biebras]

I tested more, if I leave the quad scale to 1 the performance does not go down. But if I set the scale to 20, the fps drops to 15.

[Biebras]

I assigned custom material with a custom shader and the issue is solved. The material is unlit. I don’t understand what’s happening…

[CodeSmile]

WebGL, particularly on iOS, can exhibit strange behaviour.
Would have been interesting to see if the same issue occurs with a Cube, scaled the same way.

In any case, since you’re just starting out with the project be sure to use URP as it will be faster on WebGL. It does add ~2 MB to the app size though.

[Biebras]

Hello,
I already mentioned that I use URP.

I tried adding a cube with the same scale values, the results are the same.

[GediminasR]

Hello,

Would you kindly please report this issue via the Bug Reporter tool?

Unity QA: Building quality with passion

Please make sure to write the exact steps needed to be taken so that the reproduction would be visually seen. Also make sure to attach a reproduction project and any visual material so that when testing our CQA team can verify that they got the same results. If you can, please use this template:

How to reproduce:

1. Open the attached project
2. Do this
3. Do that
4. Select this
5. Observe that

Expected result: Something is visible, something is printed or something happens
Actual result: The opposite of what I expect happens

Reproducible with: Editor version I am using (e.g: 2021.3.xf1)

Reproduced on: The OS I am on (e.g: Windows 11, macOS Ventura 13.1 (Intel/Silicon))

[Biebras]

Reported!

[duartejuca]

Hi I have an issue like this, the game runs first scene, when goes to another scene unity getback to first one, I still trying to solve if someone has a solution please share

[Kurt-Dekker]

@duartejuca

Hi I have an issue like this

Please don’t necro-post. If you have a new question, make a new post. It’s FREE!!

How to report your problem productively in the Unity3D forums:

http://plbm.com/?p=220

This is the bare minimum of information to report:

• what you want
• what you tried
• what you expected to happen
• what actually happened, log output, variable values, and especially any errors you see
• links to actual Unity3D documentation you used to cross-check your work (CRITICAL!!!)

The purpose of YOU providing links is to make our job easier, while simultaneously showing us that you actually put effort into the process. If you haven’t put effort into finding the documentation, why should we bother putting effort into replying?

If you post a code snippet, ALWAYS USE CODE TAGS:

How to use code tags: https://discussions.unity.com/t/481379

• Do not TALK about code without posting it.
• Do NOT post unformatted code.
• Do NOT retype code. Use copy/paste properly using code tags.
• Do NOT post screenshots of code.
• Do NOT post photographs of code.
• Do NOT attach entire scripts to your post.
• ONLY post the relevant code, and then refer to it in your discussion.

If you have no idea what your code is doing, FIX THAT FIRST. Here’s how:

Time to start debugging!

By debugging you can find out exactly what your program is doing so you can fix it.

Here is how you can begin your exciting new debugging adventures:

You must find a way to get the information you need in order to reason about what the problem is.

Once you understand what the problem is, you may begin to reason about a solution to the problem.

What is often happening in these cases is one of the following:

• the code you think is executing is not actually executing at all
• the code is executing far EARLIER or LATER than you think
• the code is executing far LESS OFTEN than you think
• the code is executing far MORE OFTEN than you think
• the code is executing on another GameObject than you think it is
• you’re getting an error or warning and you haven’t noticed it in the console window

To help gain more insight into your problem, I recommend liberally sprinkling Debug.Log() statements through your code to display information in realtime.

Doing this should help you answer these types of questions:

• is this code even running? which parts are running? how often does it run? what order does it run in?
• what are the names of the GameObjects or Components involved?
• what are the values of the variables involved? Are they initialized? Are the values reasonable?
• are you meeting ALL the requirements to receive callbacks such as triggers / colliders (review the documentation)

Knowing this information will help you reason about the behavior you are seeing.

You can also supply a second argument to Debug.Log() and when you click the message, it will highlight the object in scene, such as Debug.Log("Problem!",this);

If your problem would benefit from in-scene or in-game visualization, Debug.DrawRay() or Debug.DrawLine() can help you visualize things like rays (used in raycasting) or distances.

You can also call Debug.Break() to pause the Editor when certain interesting pieces of code run, and then study the scene manually, looking for all the parts, where they are, what scripts are on them, etc.

You can also call GameObject.CreatePrimitive() to emplace debug-marker-ish objects in the scene at runtime.

You could also just display various important quantities in UI Text elements to watch them change as you play the game.

Visit Google for how to see console output from builds. If you are running a mobile device you can also view the console output. Google for how on your particular mobile target, such as this answer for iOS: https://discussions.unity.com/t/700551 or this answer for Android: https://discussions.unity.com/t/699654

If you are working in VR, it might be useful to make your on onscreen log output, or integrate one from the asset store, so you can see what is happening as you operate your software.

Another useful approach is to temporarily strip out everything besides what is necessary to prove your issue. This can simplify and isolate compounding effects of other items in your scene or prefab.

If your problem is with OnCollision-type functions, print the name of what is passed in!

Here’s an example of putting in a laser-focused Debug.Log() and how that can save you a TON of time wallowing around speculating what might be going wrong:

https://discussions.unity.com/t/839300/3

If you are looking for how to attach an actual debugger to Unity: https://docs.unity3d.com/2021.1/Documentation/Manual/ManagedCodeDebugging.html

“When in doubt, print it out!™” - Kurt Dekker (and many others)

Note: the print() function is an alias for Debug.Log() provided by the MonoBehaviour class.