seedlingattempt/godot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge pull request #108109 from lawnjelly/fti_fix_multimesh_init

Browse Source 
`FTI` - Fix `MultiMesh` init and stable behaviour
This commit is contained in:
Thaddeus Crews
2025-07-01 17:57:53 -05:00
parent 639c41d086 02b444a988
commit fa401ebf03
1 changed files with 16 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
servers/rendering/storage/mesh_storage.cpp
View File

@ -258,7 +258,20 @@ void RendererMeshStorage::multimesh_set_buffer_interpolated(RID p_multimesh, con
void RendererMeshStorage::multimesh_set_physics_interpolated(RID p_multimesh, bool p_interpolated) {
MultiMeshInterpolator *mmi = _multimesh_get_interpolator(p_multimesh);
if (mmi) {
if (p_interpolated == mmi->interpolated) {
return;
}
mmi->interpolated = p_interpolated;
// If we are turning on physics interpolation, as a convenience,
// we want to get the current buffer data from the backend,
// and reset all the instances.
if (p_interpolated) {
mmi->_data_curr = _multimesh_get_buffer(p_multimesh);
mmi->_data_prev = mmi->_data_curr;
mmi->_data_interpolated = mmi->_data_curr;
}
}
}
@ -337,6 +350,9 @@ void RendererMeshStorage::update_interpolation_tick(bool p_process) {
// ... and that both prev and current are the same, just in case of any interpolations.
mmi->_data_prev = mmi->_data_curr;
// Update the actual stable buffer to the backend.
_multimesh_set_buffer(rid, mmi->_data_interpolated);
}
if (!mmi) {