Closed jeromepl closed 6 years ago
I am making massive updates to the code, so I am not sure I have already addressed the issue. Sadly, I can’t tell you to run that branch, as it was partially gutted and doesn’t do any renders yet. If possible, could you provide a copy of the replay file?
Also, you may not want to run that version in Dropbox. It will create an image for every single one of those 9190 frames in that replay. Might take up a lot of space and bandwidth... Next version will remove that entirely.
Alright, guess I am better off waiting on the next version then! I will also move this out of my dropbox folder just in case.
Here is one of the replay files anyway: replay.zip
Sorry about that... I typed my message to quickly, and forgot to apologize for all of that. I posted the program to Reddit a bit too soon it seemed... People liked it, but it was very broken: documentation was very lacking, the code was very inefficient and abused resources, and didn't even work that well on Windows...
The next version will not use the file per frame SVG creation anymore, and instead will interface with FFmpeg for the entire video process. Also, it will now use pure python without dependencies to make creating binaries and distributing them a lot easier (hopefully...).
Can confirm the issue is present on my end. I see the fix, and will apply it now.
This fix is only in the new branch, as I do not feel it is worth moving to the current broken code in master as I am nearly ready to release an alpha version of 1.4.0 either tomorrow night or during the week.
I have just released v1.4.0-alpha1
at https://github.com/enzanki-ars/rocket-league-replay-analysis/releases/tag/v1.4.0-alpha1, though it is missing the minimap output. Mind testing to see if that fixes the issues?
Tried running the new version but ended up with a new error. See #44
No matter what parsed replay I feed into rocketleaguereplayanalysis (through
python -m ...
), I get back the following: