PredictedRigidbody RecordState can early out even when not intended

PredictedRigbody -> RecordState function has an early out to not run except at a set interval. But OnRecievedState, which comes from the server, fires RecordState expecting it to always save the state so we can compare with the most up to date information. So I think there needs to be a function or parameter that lets the recording function always fire. This probably only causes minor out of sync issues unless you set the recordInterval high.

Mirror Version: 89.15.6

I personally moved the time check in the FixedUpdate loop itself before it calls RecordState.
`

    void FixedUpdate() {
        ...

        // instead of recording every fixedupdate, let's record in an interval.
        // we don't want to record every tiny move and correct too hard.
        if (NetworkTime.time < lastRecordTime + recordInterval) return;

        RecordState();
    }

`

Navigation Menu

Repository navigation

PredictedRigidbody RecordState can early out even when not intended #3926

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

PredictedRigidbody RecordState can early out even when not intended #3926

Description

Activity

Tshadow05 commented on Oct 18, 2024

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions