Assertion failed: Invalid worldAABB. Object is too large or too far away from the origin.
Something has simply blown.
I was s working in an scene it blew .
I loaded other working scene and boom.
I get that message, the vehicles that shows that message are like 5 meters from 0,0,0 on start.
But what happens is that those AI vehicles simply go boom and do skyrocket that far that the error triggers. I’ve been only touching art not a line of code.
OK. I’ve found what causes yet I’ve not yet get to guess why.
The AI vehicles load config from a file. The data 1) Has corrumpted on an unity hick up 2)something else.
But the loaded values are pretty crazy.
I’ve touched nothing related to this, I’ve been doing only art.
Would be useful if UT can improve the error message and add the name of the object that is causing this error to it.
Example:
It was extremelly late I wanted to do a quick report. I’ll be tracking source of this following days. But something happened that make the things break very seriously on the vehicle physics. But may be I didnt make clear enough.
The error seems legit, like the vehicle gets projected in teh sky at blazing speeds so gets out of usable range.
That happens because the loaded values have become all of a sudden corrupted.
I was doing art all the time, so there is no reason for that to happen.
The important now is get to know what is causing external files or code not to work all of a sudden because the only thing that has been modified meanwhile are shaders and textures.
Ok update.
Is not the file data, I’ vejust overwritten the theese with a backup data and AI cars still go boom after they get values loaded
Are you using version control? Can you check the difference between the last working backup and the version that broke it? Then you can go through the individual changes and see at which point it breaks. Figuring out what broke it will make solving it easier.
Sorry I’m not using. I did tho overwrite the scripts involved in the specs loading data aswell as the data itself and to my surprise it keeps not working. 
I’m doing extra art work will later tonight check step by step debuging to console read values and assigned values and see where it breaks.
BOOM found. I was checking the builds, trying to see any difference and found that "bleeding edge"folder and exe thing… that was new … googled…—> and as soon as saw the latest .net thing… I realized surfing the new options and had switched to latest scripting runtime. All was working fine so I forgot about that change… all but… the load features form file thing. Will check what is incompatible raises no exception so that kind of silent double agent issue… I can submit script to unity if you think is of any value. for me this is case closed
A bug report with the attached script in a minimal reproduction project and the expected results would be appreciated.