WebGL - Raycasting and physics positions are completely off

Hi,
I'm trying to get a first person controller to work in a webGL build. I'm using Unity 2019.4.8LTS.

Here's my script :

Code (CSharp):

1.         isPaused = pauseManager.isPaused;
2.         var ray = Camera.main.ScreenPointToRay(Input.mousePosition);
3.         //var ray = Camera.main.ScreenPointToRay(new Vector3(width / 2f, height / 2f, 0f));
4.         RaycastHit hit;
5.         if (isPaused == false)
6.         {
7.             if (Physics.Raycast(ray, out hit, 15.0f))
8.             {
9.                 var selection = hit.transform;
10.                 if (selection.CompareTag(serialTag))
11.                 {
12.                     reticle.SetActive(true);
13.                     _selection = selection;
14.                     Debug.Log(Input.mousePosition);
15.                 }

I try it in the Gameview, no issues whatsoever, it does what it's supposed to do.

However, in the WebGL build, it doesn't work but I investigated a bit more. It will find a raycast at some point but really out of the raycast's lenght, at random places.

I gave a try and checked the mouse position when I got one. X 805, Y 65.

Only problem :
This element was, not only outside the screen, but also behind 3-4 different colliders.

This is nuts!
(Also, same behaviour on FullScreen)

What could be the issue at this point? This doesn't seem like an error on my end at all now.

 

Hi,
So after checking out the console, I think I found the issue :
It displaces my raycast origin point by either 15 units of Z forward or backwards, and 2 units up on Y axis. The only axis that is fine is the X one.

I removed all the colliders except the ones that are selectable and I'm still getting the same result.

Testing on PC + Mac Build, everything is ok. It's clearly a WebGL issue.

Anybody else getting this issue?

 

Yes, Raycasting hasn't been working here either in WebGL - everything else works well.

This has apparently been an issue for awhile and hasn't been fixed in previous builds. I believe the issue is exactly as AHFontaine described above. When dealing with desktop web resolutions in WebGL, it isn't casting the ray correctly.

I attempted to download the latest 2020 version, and it's an issue there as well - Version 2020.1.2f1.

Picking something up initially works well, but then if it gets put down, somehow that throws off the ray checking. In this case, it's basic box colliders - not mesh colliders. In the meantime, I've worked out an alternative method to pick up valid items, although raycasting would make it more accurate.

 

I suppose this will never be addressed?
That's just a shame and asking to not use Unity for webGL anymore.

 

https://quakeulf.itch.io/parametric

 

I suggest it will be more helpful if you sent it as a bug report with full sources.

 

I need monetary compensation for this as I pay for the software.

 

I don't understand... you want Unity to pay you to help report a bug?

 

I am a Pro-user. I pay to use their product. They are not delivering what I am paying for. Why should I spend my own time on something they should be able to address by looking here?

 

That's a big assumption. How do you know they can find the root issue just by looking at a compiled build? How long you think this is going to take them vs getting a repro project? Time not spent fixing other bugs.

Also, no. You're wrong. You paid for a software, and software is not perfect. Do you ask a game developer to pay you for bugs in their games? Heck, will YOU be paying your own customers to report bugs in what you're developing? Of course not.

I get you're frustrated by a bug (we all are, we are Devs) but all I was doing is helping you direct your energy where it will be the most efficient to resolve this quickly.

 

By replying to me you aren't helping either.

 

So you just post a compiled version in an issue I raised, without any explanations of what exactly is the problem in your build, and is currently arguing that you should get a refund?
Thanks for not helping to the general cause, I guess?

 

Hi Jukka,
Just wanted to say that I didn't send a minimal repro and a bug report yet because the project I worked on decided to remove it altogether. This being said, I remember that my issues was not reproducible in a situation where you had one cube, no player, and just clicked on the cube itself.
The big difference that comes to mind is that the issue happens when I'm using a First-Person Controller, starting on a non 0,0,0 world position.
Wondering if this helps. If not, I'll try to find a moment to have a minimal repro. Note that I'm currently using 2019 LTS.

 

This was a really critical situation with a potential customer involving a few big tech companies. I was desperate and disappointed that things I took for granted in previous versions of Unity as well as UWP did not work in WebGL.

I have since managed to resolve the situation, but some of these things should really be unit tested internally at Unity3D. There are lots of good automated testing tools out there and these things can be avoided.

 

Nyanpas, can you share anything about the resolution? I'm encountering what I think is the same issue with Raycasting anomalies in a WebGL build from Unity 2019.4