this broke recently with the reverse-z, the froxel calculation relies on the depth, which is now inverted. we actually fix our getNormalizedViewportCorrd() public API, which the froxel code uses.
this broke recently with the reverse-z, the froxel calculation relies on the depth, which is now inverted. we actually fix our getNormalizedViewportCorrd() public API, which the froxel code uses.