|
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?
(comments are locked)
|
What did you do to solve this?,I have the same issue, what did you do?
I am downloading textures from a remote location on the server and it randomly throws the same error on www.texture..
Jitesh, It's generally a good idea to add your questions as comments rather than answers.
We have not found a solution to this error, but don't see it as frequently as we used to (our code has since changed). I suggest filing a bug report with Unity.
Converted to comment Julien. Thanks for the response. Oh I'm pretty stuck on this right now, I'll file a bug report anyhow.
Thanks, Jitesh. The more people that file bug reports, the more likely they are to look into it.