Page 3 of 4

Posted: 21 Sep 2010, 15:13
by ThomasLund
Either you missed a few - or there are more problems.

Havent had time to test the workaround yet myself, so your test suggests more issues. (Had to do real work today too)

Will hopefully test tonight so we can get everything fixed in rc2

/Thomas

Posted: 21 Sep 2010, 19:28
by ThomasLund
It was another error - similar, but not the same.

Also reported to Unity.

Will keep you posted

If you really are in need of a "here and now workaround", remove the CultureInfo stuff. What it does it work around an old mono bug of not being able to parse floats between people who use . and people who use , as delimiters.

Maybe its solved in the updated mono that Unity 3 uses - maybe not. If you dont send floats, then this will not hit you.

Will remove them here for testing, to see if there are any other bugs after this one

/Thomas

Posted: 21 Sep 2010, 19:36
by ThomasLund
Fast update.

I removed all the CultureInfo stuff and it ran nicely in the browser. So seems to be no follow up errors once these suckers are fixed.

Thanks for reporting

/Thomas

Posted: 21 Sep 2010, 19:41
by appels
quick question... you removed the CultureInfo stuff from the API ?
is there a way we can use that API ?
i have no idea how to do this ?
( just asking in case it's not fixed in RC2)

Posted: 21 Sep 2010, 19:42
by ThomasLund
Hit me with an email. thomas - and then to shake off the spammers - fullcontrol.dk

I can send you a dll to use while developing

/T

Posted: 21 Sep 2010, 19:57
by stevets
Thomas,
I sent you a request for the modified API.

Thanks for all your work on getting this fixed.

Steve

Posted: 21 Sep 2010, 20:33
by appels
Thanks Thomas, just tested it and all works now.

Posted: 21 Sep 2010, 20:36
by ThomasLund
Perfect. At least we then have the option of doing that if Unity doesnt fix the bugger

/T

Posted: 21 Sep 2010, 23:25
by stevets
Tested the modified API and it works here as well.

Many thanks Thomas!

Steve

Posted: 22 Sep 2010, 02:59
by stevets
I've tried Unity3 f2 and still have the same problems with the webplayer crashing :(

Steve

Posted: 22 Sep 2010, 06:03
by ThomasLund
Downloading - we most likely missed the deadline to get the fixes in. At least they write in their release email, that there is time to fix webplayer security issues. So rc3 it is

/Thomas

Posted: 22 Sep 2010, 12:28
by appels
Thomas,

i just noticed that when i spawn my player the remote doesn't see it.
as soon as i move the player thats not seen by the other it pops up on the screen.
could this be something with the temp fixed plugin or just my code ?
i am using a custom login extension.

Posted: 22 Sep 2010, 12:35
by ThomasLund
Sounds like your code :-)

Send out a "remote player spawned" message, so that existing players can show the player.

It might also be that the remote avatar is spawned at 0,0,0 in your world and not moved to the correct coordinates until you move around?

/Thomas

Posted: 24 Sep 2010, 16:11
by appels
downloading f3 now, will do a test and see if it's fixed now :)

Posted: 24 Sep 2010, 16:49
by ThomasLund
I doubt it to be honest.

Had some discussions with Unity, and I dont think the fixes made it into rc3 either.

Which means that - if true - then the API will get a bump and become Unity 3 only moving forward. But lets see

/Thomas