1. Cecil-based code analyzer that looks for and complains about common sources of intermittent failure, such as (in other words, a Unity-specific "lint" tool):
   1. Keeping a reference to a Component on the same GameObject (or even a direct reference to the GameObject itself) and accessing it from OnDelete.  
   2. Calling MonoBehaviour's component access helpers (.gameObject, .renderer, etc), or general accessors (GetComponent, GetComponentInChildren, etc), things lik... more >
      Category: Indie On the Loose | Posted by: Sciandu on 2010-04-15 @ 21:57

Punny title notwithstanding, I have decided that "prefab overrides" in Unity are more trouble than they are worth.  The idea of course is to allow parametric variation of instances within a scene, but in practice I just seem to wind up with accidental breakage where overrides get lost because of a change to the prefab itself.

The Reflective/Diffuse shader shipping with Unity 2.6.0 (haven't checked 2.6.1 just yet) does not work properly when the object is lit exclusively with vertex lighting.  Here's how you fix it -- it's just one line.

more >
Category: Indie On the Loose | Posted by: Sciandu on 2010-01-27 @ 22:24

The Problem

Almost every headache I've had with Unity has ultimately come down to two simple but fairly amorphous problems. My goal is to make the nature and implications of those problems clear, and present a possible solution that Unity Technologies could implement to (hopefully) solve them.

more >
Category: Indie On the Loose | Posted by: Sciandu on 2010-01-22 @ 14:04

When it comes to pathfinding in Unity, you can roll your own, or use one of two publicly available resources.  The most drool-worthy is AngryAnt's Path.  Having gotten way too familiar with the problem of pathfinding myself, and wanting a better workflow and richer capabilities than my home-grown solution affords me, I decided to poke around with AngryAnt's code last night. more >
Category: Indie On the Loose | Posted by: Sciandu on 2009-12-18 @ 11:26