X Tutup
Skip to content

Fix wrong indices used for transform & UBO matrix for double precision build#111403

Merged
Repiteo merged 1 commit intogodotengine:masterfrom
AeioMuch:fix_double_precision_wrong_indexes
Oct 10, 2025
Merged

Fix wrong indices used for transform & UBO matrix for double precision build#111403
Repiteo merged 1 commit intogodotengine:masterfrom
AeioMuch:fix_double_precision_wrong_indexes

Conversation

@AeioMuch
Copy link
Contributor

@AeioMuch AeioMuch commented Oct 8, 2025

Fix #111308

@AeioMuch AeioMuch requested a review from a team as a code owner October 8, 2025 09:28
@AeioMuch AeioMuch force-pushed the fix_double_precision_wrong_indexes branch from 033114f to 1c92c30 Compare October 8, 2025 09:31
@AThousandShips AThousandShips changed the title Fix wrong indexes used for transform & UBO matrix for double precision build Fix wrong indices used for transform & UBO matrix for double precision build Oct 8, 2025
@AThousandShips AThousandShips added this to the 4.6 milestone Oct 8, 2025
Copy link
Member

@clayjohn clayjohn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The changes to the indices look great! Nice work.

I left comments on the other changes that were added. In general we prefer if bug fix PRs are restricted to fixing the particular bug and don't include unrelated stylistic changes. So please go ahead and remove the changes that aren't related to the fix

@AeioMuch AeioMuch force-pushed the fix_double_precision_wrong_indexes branch from c1255f3 to 6889825 Compare October 9, 2025 20:00
@AeioMuch AeioMuch force-pushed the fix_double_precision_wrong_indexes branch from 6889825 to dae2122 Compare October 9, 2025 20:01
@AeioMuch
Copy link
Contributor Author

AeioMuch commented Oct 9, 2025

Yes sorry, I saw only one or two warning(s) by clangd per each of those files; so I figured, let me sneak those changes in at the same time since it's so little, I though why not, no idea if it's useful apart from the removal of the warning 😅 But I 100% understand it's not ideal to include those unrelated changes here, lol. Anyway, removed !

@clayjohn
Copy link
Member

clayjohn commented Oct 9, 2025

Yes sorry, I saw only one or two warning(s) by clangd per each of those files; so I figured, let me sneak those changes in at the same time since it's so little, I though why not, no idea if it's useful apart from the removal of the warning 😅 But I 100% understand it's not ideal to include those unrelated changes here, lol. Anyway, removed !

Thanks! I appreciate your quick response. To be clear, its not like we don't want to fix things that are creating warnings. But I don't want to block merging this clear fix while we discuss the performance tradeoffs of zeroing a struct right before filling that struct in order to fix a warning that isn't actually harming anything. Unfortunately in hot paths we need to be super careful as even the cost of writing 0 to a bunch of properties can add up.

@AeioMuch
Copy link
Contributor Author

AeioMuch commented Oct 9, 2025

Yes sorry, I saw only one or two warning(s) by clangd per each of those files; so I figured, let me sneak those changes in at the same time since it's so little, I though why not, no idea if it's useful apart from the removal of the warning 😅 But I 100% understand it's not ideal to include those unrelated changes here, lol. Anyway, removed !

Thanks! I appreciate your quick response. To be clear, its not like we don't want to fix things that are creating warnings. But I don't want to block merging this clear fix while we discuss the performance tradeoffs of zeroing a struct right before filling that struct in order to fix a warning that isn't actually harming anything. Unfortunately in hot paths we need to be super careful as even the cost of writing 0 to a bunch of properties can add up.

Oh yes make sense, thanks for the explanation and for pointing it out!

Copy link
Member

@clayjohn clayjohn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great! Thank you

@Repiteo Repiteo merged commit 8150cb9 into godotengine:master Oct 10, 2025
20 checks passed
@Repiteo
Copy link
Contributor

Repiteo commented Oct 10, 2025

Thanks!

@AeioMuch AeioMuch deleted the fix_double_precision_wrong_indexes branch October 10, 2025 15:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3D rendering broken in double precision build

4 participants

X Tutup