Wednesday, September 14, 2016

finished callback pattern, and...unity problems?

First part of the day (the productive part): figured out what was wrong with my unit tests after moving to the new MossDelegate pattern (of course, it was the single-shot change; I hadn't written the unit tests with that in mind and it caused problems that should have been predictable).

Second part of the day: returned to trying to hook up my UI to code in Unity. Only, weird things were happening. I was getting an UnassignedReferenceError on a field in a prefab that totally was filled out (with a GameObject inside the prefab's own dependency tree). I could also see that the GameObject existed in the instantiated prefab, and it showed up in the script's parameters as properly filled out.

Something wasn't adding up, so I started deleting stuff. Eventually I got down to a completely empty scene--not even a camera--and the error was still being thrown. That is to say, a script on a prefab was running and erroring, when--not only wasn't that prefab instantiated, nothing was instantiated.

That seems pretty wrong.

I'm running 5.3.5 on Ubuntu 15 and this is the first time I'm seriously worried I shot myself in the foot by running on an unsupported platform. Things were working so well I got a little complacent. But maybe fun time's over--if this proves to be a linux-specific issue then I think it's back to Windows for me. I will try reproducing with 5.4, and if it still repro's I will try reproducing with the same project on Windows.

I haven't had to fight any real Unity battles yet, so I guess I'm due.


No comments:

Post a Comment

Note: Only a member of this blog may post a comment.