Targeting reticle doesn't always draw properly #61

New Issue

2018-02-11T17:04:50Z

daerogami commented

2018-02-11 17:04:50 +00:00

(Migrated from github.com)

Win10, commit cb9f0ed

Sometimes it works, sometimes i get this

I suspect this has to do with the hidden-from-view behavior or bad masking with certain tiles. Need to confirm.

Did further testing. This is a bug with the new UI scaling feature. The targeting mask/boundary looks like its dimensions are not being resized as well.

Win10, commit cb9f0ed Sometimes it works, sometimes i get this ![badreticle](https://user-images.githubusercontent.com/2267600/36075949-8926a264-0f23-11e8-92ab-cc12b1fac632.png) I suspect this has to do with the hidden-from-view behavior or bad masking with certain tiles. Need to confirm. Did further testing. This is a bug with the new UI scaling feature. The targeting mask/boundary looks like its dimensions are not being resized as well.

clort81 commented

2020-01-04 07:47:56 +00:00

(Migrated from github.com)

I confirm this behavior - same on linux build, with scaling = 2.00000

x-qq commented

2020-02-10 03:43:05 +00:00

(Migrated from github.com)

I think this is mostly fixed now, but there is still a small (and possibly unrelated glitch) where the top part of the reticle is clipped away when targeting topmost row of the world view:

I think this is mostly fixed now, but there is still a small (and possibly unrelated glitch) where the top part of the reticle is clipped away when targeting topmost row of the world view: ![topclip](https://user-images.githubusercontent.com/55463047/74119468-343a4d80-4bc8-11ea-8dfe-0232e1e84a2a.png)

retropipes commented

2020-02-10 10:49:49 +00:00

(Migrated from github.com)

I bet that glitch is related to the automatic scaling causing the very top of the reticle to be out of bounds, combined with draw call combining resulting in that piece not appearing... something to investigate.

NQNStudios commented

2025-02-23 13:42:13 +00:00

(Migrated from github.com)

Yesterday I changed my window mode preference while playing, and after I went from Small Window to Bottom Right Corner Fullscreen, the targeting line and reticle were clipped around where I think the terrain window would have been in Small Window mode. Maybe a clip_rect gets set and not updated when adjust_window_mode() happens. Not that this would explain everything mentioned in this issue -- just one reproducible instance of it (I need to try it again).

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: openboe/oboe#61