You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some, seemingly valid, configurations produce the following warning: UNSUPPORTED (log once): POSSIBLE ISSUE: unit 4 GLD_TEXTURE_INDEX_1D is unloadable and bound to sampler type (Float) - using zero texture because texture unloadable
So far I've seen units 0, 4 and 5 and indices 1D, 2D and 3D. The easiest way to reproduce this is to set the number of regions in the example "InOut" case to 0. Resetting the number of regions to the original value does not always clear the warning. Sometimes the warning appears with other values as well, however it is not a 100% reproducible. Changing the number of FOV-s may also produce this warning.
The text was updated successfully, but these errors were encountered:
I see this one myself reliably when I run "42 Demo". I haven't isolated it. The error message gets generated somewhere between the call to glutMainLoop and the first entry into Idle. I reckon that means that I'll have to check each texture until I find the offender. So it's on the to-do list, but low priority.
Some, seemingly valid, configurations produce the following warning:
UNSUPPORTED (log once): POSSIBLE ISSUE: unit 4 GLD_TEXTURE_INDEX_1D is unloadable and bound to sampler type (Float) - using zero texture because texture unloadable
So far I've seen units 0, 4 and 5 and indices 1D, 2D and 3D. The easiest way to reproduce this is to set the number of regions in the example "InOut" case to 0. Resetting the number of regions to the original value does not always clear the warning. Sometimes the warning appears with other values as well, however it is not a 100% reproducible. Changing the number of FOV-s may also produce this warning.
The text was updated successfully, but these errors were encountered: