Fognum sometimes goes way out of range

[ensiform]

I am having sporadic cases where fognum becomes 31 after sort is processed so it seems likely that there is an issue with the shifting into the sort value but I cannot figure out what that is.

Help on finding the cause would be greatly appreciated.

[ensiform]

Very difficult to reproduce right now and can't even track down a specific map.

[tsiren]

fognum variable defined where and which sort function?

[ensiform]

I Believe it was detected out of range at the time in RB_CalcFogTexCoords.

See RB_RenderDrawSurfList R_DecomposeSort R_SortDrawSurfs R_AddDrawSurf for possible areas that deal with the sort packed data (including fognum)

[tsiren]

Is there a specific error that occurred when this happened? By glance I cannot spot any range checking.

[ensiform]

Trying remember but I think the shader pointer becomes access violation later down.

There should not need to be any range checking in backend rendering functions.

[tsiren]

I don't think I have seen this one. You can decrease the priority then.

[ensiform]

Don't think I've seen this issue come up at all in years either tbh