Page 4 of 4
Posted: 24 Sep 2010, 16:55
by appels
They didn't get it fixed, webplayer still crashes.
will get a bump and become Unity 3 only moving forward
what do you mean with this ?
Posted: 24 Sep 2010, 17:19
by ThomasLund
What I mean is, that the CultureInfo stuff is in there to work around a bug present in the mono version that 2.6 (and before) uses.
Now I am forced to remove the CultureInfo - and thus the API can only be used with the mono that is in 3.0 (that has the bug fixed).
Maintaining multiple versions of the API + Silverlight + the new SFS2X (in various versions) - no thanks. Less versions = good.
/Thomas
Posted: 24 Sep 2010, 19:42
by appels
yes i understand.
Posted: 26 Sep 2010, 08:57
by stevets
Good News...Unity3d RC4 appears to work again with the webplayer and the original SmartFoxClient.dll.
Please verify.
Steve
Posted: 26 Sep 2010, 09:07
by ThomasLund
Not according to the release notes - but I will test. Got a small repro project that I'll run in 10 mins.
/Thomas
Posted: 26 Sep 2010, 09:24
by stevets
Sorry. You are right. I did not copy the old API back into the plugins folder as I had thought.
What is your take on this issue? Is the temporary fix going to be the one we use going forward?
Steve
Posted: 26 Sep 2010, 09:29
by ThomasLund
Yeah - bug still there.
So the temporary fix is going to be a permanent one for Unity 3, yes.
I will get that out into the open during the week for everyone.
Just beware, that you should _not_ use the temporary fix dll together with Unity 2.6 or earlier.
All this is only webplayer relevant BTW - just wanted to note that
/Thomas
Posted: 26 Sep 2010, 09:37
by stevets
Thanks Thomas for all your help on this issue to keep us going.
I really appreciate it.
Also, Is this webplayer issue appearing in the SFS2x server version? I know you mentioned that earlier Unity3D betas were working ok. Has this changed with the latest RC's?
Thanks,
Steve
Posted: 26 Sep 2010, 09:43
by ThomasLund
Hey,
No - this issue is a non-issue for SFS2X. It has a completely different serialization pipeline not having to go through strings being parsed.
So its only an issue for SFS 1
/Thomas