Hey,

i have a task for you programmers out there :-) As you might have seen i am working on the tool mprEdit. Currently i am preparing the next release which has a major change: Instead of collecting all "important" replay events and playing them back in the beginning of the replay i am creating a completely new replay header, resulting (theoretically) in a replay that looks and feels exactly the same like it had been recorded with lfs.

Now i have still one big challenge left: Coping with car body damage. The replay header has a section containing the damage for each car at replay start. To create this header i simply have to collect all "damage packets" that occur in the replay and put the in the header.

BUT

My analysis so far shows a discrepancy between the damage packets that are contained in the replay and in the damage data that is contained in the replay header. And i have no clue how the damage packets are combined/converted/whatever into the header!

Here is an example. XF GTi, crashing several times into walls.

Damage data from the header that contains all damage (The replay was started after all crashes had already happened):

Damage data from the running replay (replay starting with an undamaged car):

I would have expected that all information from the running replay is included in the header. But only the green parts are contained, the red parts are not.

I spent already a few hours trying to understand what is removed and why, but so far i found no clue.

So here is your task: Find out the correlation between the in-replay damage data and the header damage data! How can i recreate the header data from the existing in-replay data?

Notes:
The data comes from the exact same situation. One lfs instance was recording from the beginning, another instance joined the server at a later stage.

From my understanding each line (4 Bytes) represents force on the body, containing point where force is applied and direction and/or strength.

PS: Scawen, if you happen to read this - It would be awesome if you could explain this :-) But i am not expecting or demanding any help from you. I understand well if you don't want to support undocumented formats and unofficial add-ons.

Thanks very much for your effort

Quote from MikeB :

PS: Scawen, if you happen to read this - It would be awesome if you could explain this :-) But i am not expecting or demanding any help from you. I understand well if you don't want to support undocumented formats and unofficial add-ons.

Thanks very much for your effort

I don't think he will, but it would be nice to be pointed into the correct direction every now and then.

The second byte in a damage node is the severity of the damage. Only the 16 most severe damage nodes are retained.

When a new damage node arrives, if it is greater in severity than any existing damage node, the least severe node is removed and the others are shunted down so the new node can be added to the end of the list.

Is it just me or does that green text on a light blue background make your eyes go funny?

Quote from Scawen :

Is it just me or does that green text on a light blue background make your eyes go funny?

Yeah it had the same effect on me.

PS: did you post just cause Dygear said u wouldn't?

No I just came across this and realised the answer was easy, I could get it in a minute. I have not tried to think through anything else about creating MPR headers so I have no idea what the issues are and if I'd be able to help in future.

Well, that is awesome never the less! Thanks Scawen!

Quote from Scawen :

The second byte in a damage node is the severity of the damage. Only the 16 most severe damage nodes are retained.

When a new damage node arrives, if it is greater in severity than any existing damage node, the least severe node is removed and the others are shunted down so the new node can be added to the end of the list.

Is it just me or does that green text on a light blue background make your eyes go funny?

Great Scawen, big thanks for the answer! You just made me another happy customer

PS: And yeah, the colors are a bit disturbing