Confusing behavior from corrupted streamed assets

In matrix i was told to put this down somewhere

Having a completely busted asset in stream will result in a not very helpful message of “invalid fixup, address is neither virtual nor physical”


and for YBNs the error is even worse, with a full crash popup and some variations

note that these two came from seemingly the same thing in the loading phase, i don’t believe i did anything different but it was on two seperate machines.


The data that the ydr and ybn have in these is based on something i did myself, which was unresolved LFS files.

oid sha256:9cb87c75f0e8c02178497f058c3d6e30a0cf1f52dd41615adcc41b07d1fd9c27
size 319475

put that in there for exactly what i’ve done