We've created a progressive disclosure tool that goes out to various services (our own tile server and the google static maps api) to request images, and then creates tiles (procedural mesh generation) and applies the images to the materials of the tiles. It works great for a while, but then we start getting weird errors during the step where we load images into a Texture2D (e.g. with LoadImage, or direct assignment like texture = www.texture). The error is:
Once we get the error once, we get it over and over from that point on until stopping and restarting. I've been looking into the issue, but it's rare and seemingly random, and acts in ways that are surprising. For instance, yesterday I started getting the error within 30 seconds on some new code, while a coworker didn't get it at all; when I restarted my computer, it disappeared for me as well.
Has anyone else seen this error, and do you know more than I do about what conditions cause it?
asked Feb 21 '12 at 05:11 PM