Aedif
commented
11 months ago It's not a bug per se. You see shapes and text are rendered at twice the resolution to keep them looking sharp. Didn't matter in the contexts I was using these types of overlays but I guess it was relevant here.
I might add an option to let you specify the resolution when rendering shapes but that would merely be kicking the can down the road. Eventually you'd still run texture size limits.
That said... I think there might be a way to to get around this texture size limit entirely... by not rendering a texture for these primitive shapes to begin with... I'll think about this.
Dumbhuman
This could likely be just user error on my part, so apologies if this bug report is a waste of time. It's also pretty rare I'll ever actually need shapes this large and I'd guess I'm stretching things far beyond the intended scope, but the specific numbers made me curious as to whether there was a bug involved.
I had the idea of setting up some ranges for weapons with a green line for the normal range and yellow for the max. Worked well on a 100 grid scene for a thrown dagger (20'/60'):
When I got up to bow ranges, I ran into a rendering problem:
After some testing it seems the maximum shape radius I can render is 4095 pixels (the token below is 100 pixels so 4045 + 50):
When the radius is 4096 (which fails to render for me), that's a 8,192 diameter which also happens to be exactly half of my browser's supposed max texture size of 16,384:
I imagine the width of the border could be pushing the actual image just above 8,192 pixels, but I'm not sure why that wouldn't render for me unless the overall dimensions are being doubled somewhere under the hood. Here you can see the shape render error happening on top of a single tile that's a 12000 x 12000 pixel image:
It's been a long time since I ran a battle where the maximum distance of a Shortbow or Longbow mattered, so I'd guess this is literally an edge case (and probably not the most efficient way to do range-finding regardless).