I'm not sure if there's corruption in the demo recording, the demotool or somewhere else. Either way when I run the demotool, all the stats it reports are way off. If I had to guess it looks like an endian issue, but I'm not 100% sure. I just figured I'd check here before posting a bug report.
If there's another way to get the game statistics that'd be helpful too.
My output looks like this:
-- Team statistics for player 0, game second 128 --
MetalUsed: 7.88861e-030
EnergyUsed: 0
MetalProduced: 0
EnergyProduced: 0
MetalExcess: 1.07003e+038
EnergyExcess: 2.6364e-041
MetalReceived: -1.44504e+024
EnergyReceived: 2.63542e-041
MetalSent: 0
EnergySent: 0
DamageDealt: 0
DamageReceived: 0
UnitsProduced: 0
UnitsDied: 5767168
UnitsReceived: 65536
UnitsSent: 0
UnitsCaptured: 0
UnitsOutCaptured: 0
UnitsKilled: 0
demos/demotool output error
Moderator: Moderators
Re: demos/demotool output error
if that happend, the replay would not play correctly at all. you would notice pretty soon that the replay plays different then the real game.corruption in the demo recording
what demotool do you mean?
Re: demos/demotool output error
I'm using the demotool provided in the source code. I'm mostly looking to get the stats that are presented at the end of a match (damage over time, units lost etc). It seems like that data is saved in the demo files, but I have no way to read it outside of the demotool (as far as I know).knorke wrote:if that happend, the replay would not play correctly at all. you would notice pretty soon that the replay plays different then the real game.corruption in the demo recording
what demotool do you mean?
Re: demos/demotool output error
hm, at least UnitsReceived: 65536 seems like a bug because 65536 is also 2^16?
so i guess you could make a real bugreport...
so i guess you could make a real bugreport...
if you do not mind running the whole replay (on fast forward) you can use Lua scripting.If there's another way to get the game statistics that'd be helpful too.
Re: demos/demotool output error
i'm unsure if this bug is fixed in current spring master... can you check that?
if the bug still persits, it should be located here:
https://github.com/spring/spring/blob/m ... r.cpp#L107
https://github.com/spring/spring/blob/m ... r.cpp#L235
which version of the demotool did you use?
did you compile the demotool from the 0.82.7.1 source-code? your link on github goes to the development version, this demotool should be incompatible to demos recoreded in 0.82.7.1... correct link would be: https://github.com/spring/spring/tree/0 ... s/DemoTool
if the bug still persits, it should be located here:
https://github.com/spring/spring/blob/m ... r.cpp#L107
https://github.com/spring/spring/blob/m ... r.cpp#L235
which version of the demotool did you use?
did you compile the demotool from the 0.82.7.1 source-code? your link on github goes to the development version, this demotool should be incompatible to demos recoreded in 0.82.7.1... correct link would be: https://github.com/spring/spring/tree/0 ... s/DemoTool