Possible bug in texture lock code

[kduske]

Produces nan in one of the face attributes.

[kduske]

@totalnewbie here is the bug report for the nan issue in case you find out how to reproduce it.

[totalnewbie]

Ok, thanks. I'll keep trying.

Here's the map file you asked for: https://gist.github.com/totalnewbie/f466c40804db72529570 It's just something I played around with for a couple of hours to try out a few things (i.e. it sucks, but I know it sucks).

As I wrote on Func_msgboard, manually replacing all instances of "nan" with "0" seems to fix things; otherwise TB refuses to open the file and just says

(line 441, column 107)Expected integer or decimal, but got 'nan'

[ericwa]

I see the 'nan' is only happening in the Valve 220 "texture rotation" field.

This is the value whose purpose is to record the rotation knob position in the Hammer texture alignment UI, and is ignored by qbsp.

[kduske]

I think I was trying to be smart about that field by recomputing it somewhere. Guess I messed up.

[kduske]

I'm going to push this to 2.1.0 or until someone comes up with a reproducible test case.