Web Player behaving differently in different browsers

Unity Engine
1

Hi everyone, new to the forums, and fairly new to Unity. Made the wise switch from Virtools a bit ago (and in my lurking I think I have found some people from the swap-meet are here too!)

Anyway, I am on the indie license of Unity 2.5. I develop on XP but the project I’m on has to work universally through the web player. Some of my colleagues are on OSX, which is great for testing. I have found that on an Intel MacBook that the web player behaves strangely on Safari and on Firefox (OSX). I fear this has a lot to do with the PhysX calculations. Controls would be completely erratic or moving our player in the wrong direction in these browsers. The forces applied to the RigidBodies seems to be accelerated as well.

However, this is where it gets interesting. In the same version, it will work fine in Netscape and in the standalone Mac build.

Booting into Windows on the same laptop and it works as expected in the Web Player. Are there any big obvious differences in the plug-ins for the web players that would make this happen? This is pretty perplexing.

Oh and all my calculations are FPS defendant and all physics are handled in FixedUpdate…

2

I’m going to bump this, mainly because I work with Ken and this is a HUGE problem for us at the moment.

Any ideas? I’m sure Unity must be structured to force/allow the Web Player to behave the same on PC/Mac. Or…is there a list of published limitations we should be aware of? Any suggestions on a remedy?

Thanks in advance.

3

Never had problems in Firefox OSX other than that it does not release the focus even if the window / tab is not active, so ensure that you never have 2 players active if one is firefox.

4

Unity should give the same results on any platform. If this is not what you are seeing, please make an example project, and file a bug on it.

5

Will do. I have been tracking what Input.mousePosition is returning and it is definitely not accurate.

Where the lower left corner should be 0, 0 instead it is 297, -50.

However, switching to fullscreen mode seems to fix this.

6

I would like to confirm this (my post is a few down from here)

My experience is that it does not register clickCount correctly and again fullscreen fixes this.

7

Ken has logged a bug on this and I’ll get that into engineering’s hands to take a look at this problem. Given that a few of you are reporting it I sense a real issue here that we need to investigate.

8

Any update on this? We are having similar problems with clicking on items in Netscape vs Internet Explorer.