Visualiser

Okay, I can confirm I can replicate the issue where it stops on round 98 in Chrome. Busy looking at it.

Bad news folks, from my investigation it seems like Chrome only resolves the first 100 entries in the dropped folder, starting with the files and then the folders. So what happens is that the two files with the bot’s moves gets resolved, and then the first 98 folders.

You may see a demo here and test with a replay folder: https://mdn.mozillademos.org/en-US/docs/Web/API/DataTransferItem/webkitGetAsEntry%24samples/Example?revision=1493829

Firefox seems to be the only browser that supports this API fully: https://developer.mozilla.org/en-US/docs/Web/API/FileSystemDirectoryReader/readEntries#Browser_compatibility

So support for the visualiser is only on Firefox.

if you’re using the HTML5 filesystem API you need to call the readEntries() method repeatedly until it returns 0 entries. Each time it’s called it returns folders in batches of 100.

1 Like

Chrome round 98 bug fixed! Thanks for the info @marcin_k !

This visualizer is great! Well done mate!

1 Like

Version 0.1.8 released, containing visual changes to indicate the moves made and health on the map itself
The Worm that moved is highlighted: image
Shooting: image
Invalid moves: image
Nothings: image
Digging: image

Health now indicated through opacity:image

After I drag the replay folder the screen just goes blank and just displays the background.

Using Chrome

When I do that the round gets replayed using chrome:sweat_smile: Do you have any errors in your browser console?

I’m getting the same behaviour as @KageNinja - can provide some more info when I’m back at my desk

I await your feedback :sweat_smile:

I think it is from the new entelect code release?

Ya I have some console errors, not sure if they are relevant:

On chrome:

TypeError: Cannot read property ‘startsWith’ of null
at t.n.mapOccupier (Square.js:24)
at t.value (Square.js:83)
at Oi (react-dom.production.min.js:3785)
at Ri (react-dom.production.min.js:3776)
at Mi (react-dom.production.min.js:3960)
at qa (react-dom.production.min.js:5514)
at $a (react-dom.production.min.js:5536)
at Ol (react-dom.production.min.js:5958)
at Pl (react-dom.production.min.js:5925)
at Tl (react-dom.production.min.js:5860)
da @ react-dom.production.min.js:4408


TypeError: Cannot read property ‘startsWith’ of null
at t.n.mapOccupier (Square.js:33)
at t.value (Square.js:83)
at Oi (react-dom.production.min.js:3785)
at Ri (react-dom.production.min.js:3776)
at Mi (react-dom.production.min.js:3960)
at qa (react-dom.production.min.js:5514)
at $a (react-dom.production.min.js:5536)
at Ol (react-dom.production.min.js:5958)
at Pl (react-dom.production.min.js:5925)
at Tl (react-dom.production.min.js:5860)
da @ react-dom.production.min.js:4408


Uncaught TypeError: Cannot read property ‘startsWith’ of null
at t.n.mapOccupier (Square.js:24)
at t.value (Square.js:83)
at Oi (react-dom.production.min.js:3785)
at Ri (react-dom.production.min.js:3776)
at Mi (react-dom.production.min.js:3960)
at qa (react-dom.production.min.js:5514)
at $a (react-dom.production.min.js:5536)
at Ol (react-dom.production.min.js:5958)
at Pl (react-dom.production.min.js:5925)
at Tl (react-dom.production.min.js:5860)

On firefox I’m getting something that looks more relevant:

Then the error is caused by the lack of the two CSV files that contain the moves. They should be in the root of the replay folder.

Im also getting the same console error as @japes on chrome.

Running the latest Game engine, using Chrome, both CSV files are in the replay root folder.

Edit: My earlier replays before the game engine update still run.

hmm :thinking: Will have a look then over the weekend.

Okay so it seems like there is an issue in the latest release where two columns in the csv file is populated with “null”.
I created a new topic here: Bug in output files of Release 2019.1.0 runner

3 Likes

This has been resolved. We have not released a new starter pack yet, but if this issue is affecting you, please use the game engine version on the develop branch of our repo.

1 Like

Good news, I made some changes, and the visualiser will work with any release version of the game engine. You will not just not have access to the move info on the left hand panel, or the visual indicators on the worms in the release where move info is unavailable.

Good luck everyone!

Thank you for the Visualiser! I have used it now for the first time and it works beautifully. A great help to look at the tournament match logs.

1 Like

You can now see if a worm uses a banana in v0.1.10 image
I will next try to indicate the target of the banana bomb.

3 Likes