yeah similar things happen to me. Unity keep changing my script in all lower case and the compiler complains it cant recognize some of types(=filename)
it seems to me that we need quick-fix on this because of the snow leopard.
I’m goingto just dump this here … warnings from the asset server itself. Lots of them all showing the PSD as being added with all lowercase, when in reality it is not.
This is really going to start messing with the asset server ;/
WARNING: Adding med_centerupperintakebump.psd (e5893d9f7665c4dffa2ddb9885fd5a40) into configuration
CONTEXT: SQL statement “update changeset set frozen = true, commit_time = current_timestamp where serial = $1 and frozen = false”
PL/pgSQL function “freeze_changeset” line 4 at SQL statement
SQL function “maint_commit_freeze_changeset” statement 1
Why, oh why have we not received a fix for this!? This is making me crazy, I’m ready to throw Unity out the window!
Anyone got a good workaround for this? A script or something would be wonderful. As it is now, I have to overwrite each file with it self in order to get Unity to understand the state of things.
Thanks (and sorry for the anger release), now I better call the glazier…
I use SourceGear’s Vault (fully compatible with mono), I realize this is not a fix to this bug they are probably working on a solution for 2.6 for this (hopefully) but that is for them to say or do. Unity itself is one tool, the asset server is just a plugin. You can use any source control you want with Unity. Nice thing about external ones is that you have a seperate client to use for check-in and check-out.
No way you can fix this problem yourself because unless you have source access, you can not change the file name layout from lower to camel. I have no clue what they are doing to change the string variable of the name since all databases accept camel toe in a char/varchar/text or otherwise defined field. shrugs
It sounds like a good solution, only one thing… it seems to be a Windows only server install and I’m running an all Mac environment. Or, do you mean both client and server can be used with Mono? (I’ve never used Mono other than with Unity so I have no idea what functionality is provided). Can you verify this?
Also, I’m working on Unity iPhone 1.5, but in this case the two latest releases share a common bug…
I have been able to work past the problem by some extra steps when saving the scripts in Unitron - Using ‘Save as…’ and overwriting the same file makes Unity come back to reality. I can do this for a script or two, but no way I do it for all the scripts in the standard assets.
Anyway, I tried to use TextMate instead and have not seen the problem since - I cross my fingers
Their command line utility is setup to work with Linux and will work with Mac but takes a little work to get it to show up in side of Unity as an extension. The server on the other hand installs to MSDE or Sql Server Express if you want, but again, this is Windows for those. I haven’t looked through their docs to see if they work with MySQL or any other database engine, I use their server with Sql Express and use the client through the command line interface on my Mac, for my Visual Studio projects that work with Unity, I simply use the Vault Client interface inside of VS.
If you are pure Mac, this might not be a solution for you and you might have to wait until they release a version of the asset server or write your own to work with what ever database you want.
As normally is the case, these problems come in the worst of times. Only a couple of days left to live user test, an evasive bug that even crashes Unity.app running the player with iPhone remote, backup failure and finally on top of that, this case sensitivity problem suddenly got enormous proportions stretching through all the scripts in the project.
guess the desktop won’t get a hotfix for that as 2.6 is meant to happen pretty soon (was planned late summer so last months basically).
For the iphone one, which is bound to OSX, I hope that a hotfix is just around the corner but I guess fixing OSX missbehavior is not a trivial thing especially if it should not be documented and clearly pointed out by apple anywhere.