Example: stock Yav1.lvl on Xbox will give "Unknown VBUF type encountered", and the beta version gives "Chunk magic number mismatch"
We determined before that BF1 doesn't really care too much about strictly following its guidelines on the magic number of 81 (and will still load ingame), so maybe something a little more flexible for VBUF_type::geometry could be used for BF1. I have very little knowledge of how the TER file handles this, so suppressing the errors just gives a seemingly blank terrain.
Example: stock Yav1.lvl on Xbox will give "Unknown VBUF type encountered", and the beta version gives "Chunk magic number mismatch" We determined before that BF1 doesn't really care too much about strictly following its guidelines on the magic number of 81 (and will still load ingame), so maybe something a little more flexible for VBUF_type::geometry could be used for BF1. I have very little knowledge of how the TER file handles this, so suppressing the errors just gives a seemingly blank terrain.