Ticket #3450: t3450_do_not_serialize_m_PassabilityMapChangedRecently_v1.patch

File t3450_do_not_serialize_m_PassabilityMapChangedRecently_v1.patch, 894 bytes (added by elexis, 9 years ago)

Resolves the discrepancy by just not serializing that value. Works all commands.txt files linked but needs further testing. Could there be a case where serializing that state is required?

  • source/simulation2/components/CCmpUnitMotion.cpp

    public:  
    369369        serialize.Bool("moving", m_Moving);
    370370        serialize.Bool("facePointAfterMove", m_FacePointAfterMove);
    371371
    372372        SerializeVector<SerializeWaypoint>()(serialize, "long path", m_LongPath.m_Waypoints);
    373373        SerializeVector<SerializeWaypoint>()(serialize, "short path", m_ShortPath.m_Waypoints);
    374         serialize.Bool("passability map changed recently", m_PassabilityMapChangedRecently);
     374
     375        // Do not serialize m_PassabilityMapChangedRecently. It is only valid for the local simulation.
    375376
    376377        SerializeUnitMotionPlanning()(serialize, "planning", m_Planning);
    377378
    378379        SerializeGoal()(serialize, "goal", m_FinalGoal);
    379380    }