Armagetron Forums

round5_delidc_para_vs_ac.aarec 12088kb 1176s
round5_delieu_red_vs_bm.aarec 17668kb 1839s

final_delidc_red_vs_rx.aarec 46368kb 4181s

round3_delidc_para_vs_bm.aarec 21856kb 1977s
round3_delieu_ac_vs_rx.aarec 16388kb 1559s

round4_delieu_rx_vs_red.aarec 11456kb 996s
round5_delidc_ac_vs_bm_part1.aarec 8256kb 772s
round5_delidc_ac_vs_bm_part2.aarec 5900kb 592s
I fell for the old 'kill_all means new match' trap there.

Recordings for 0.2.9.1.1: Internet went away a bit during round 1. Skip to the second recording as soon as the first disconnects, I try to reconnect a bunch, but it fails. round1_delidc_para_vs_rx_part1.aarec 4744kb 485s round1_delidc_para_vs_rx_part2.aarec 15636kb 1462s round1_delieu_red_vs_ac_part...

I'm still considering writing scripts You don't have to. While it tends to make the content better, it also significantly changes the feel of videos. The editing you were already doing, plus the text correction/addition overlays you did in the Stargate video, are a perfectly fine way to polish thin...

That is correct. The still relevant intention there is that in incam only servers, having partially see-through walls would be cheating. The older intention was that there was to be occlusion culling of walls for incam only gameplay for optimization purposes, and that only works with nontransparent ...

It's a good start! I can only second that. I like the scribbling of the title on the whiteboard, that is a nice touch. The second video is already some improvement, it is more to the point, more in focus. I am required by law to have one nit to pick, so here it is: You should be more deliberate abo...

About editor auto-detecting the desired formatting standards: That is what your Kate did, apparently, only that it did not conclude mixed line endings would be tolerated... Really, editors should just leave lines you don't edit alone, and only apply whatever settings they divined (via user settings,...

Heh, just don't crash. It's not that hard. It's not that hard on any given specific day. To never crash is a lot harder. All it takes to fail is a bad combination. All that is required for you is a momentary lack of attention at the wrong time. If that coincides with other people doing something wr...

Beta confirmed working. But what's with the super new 0.4 beta? It has been here for a while, those are the builds from the trunk of the source control data. That gives me an error message "random_device::random_device(const std::string%)" and refuses to start on Windows XP and 7. Oh, tha...

Scratch that waiting, I just did the process again, there are not too many conflicts:
https://gitlab.com/zmanuel/armagetronad ... type=heads

The problem: sty+ct+ap is currently partially formatted with DOS style line endings, CR+LF; our branches have UNIX style line endings, only LF. Any straight merge gives conflicts of the form "the whole file has changed". I have a plan, successfully tested. It requires cooperation to be per...

Well, it's about time to get the macOS builds into a stable version, so I'm starting the process for 0.2.9.2. Latest builds: Release: 0.2.9.2.3 0.2.9.2_rc_z2996 0.2.9.2_beta_z2996 Ready to release: 0.2.9.2.1 You can get it as a direct download or by subscribing to the beta branch on Steam, Itch.io, ...

round4_delidc_para_vs_ac.aarec 15520kb 2001s round4_desony_rx_vs_bm.aarec 28612kb 2469s round5_delidc_ac_vs_red.aarec 9208kb 1000s round5_delieu_para_vs_rx.aarec 27832kb 2579s final_delidc_red_vs_para.aarec 46268kb 4170s Oh, and round 5 and the finals in video form with commentary by Andrei: https:...

Took place on January 7th, 2023. Recordings for 0.2.9.1.1: round1_delieu_bm_vs_ac.aarec 18752kb 1858s round1_desony_para_vs_red_starts_at_130s.aarec 12164kb 1161s I missed a reconnect window there, so fast forward to 130 for the start. round2_delidc_rx_vs_ac.aarec 10320kb 1195s round2_delieu_bm_vs_r...

Managed to get it going again; the SD card was indeed partially borked, but for the syncing, only an easily reconstructible git repository was affected. The rest I moved back to the build server, where apparently it was running originally? I can't remember why I moved it away. The Python2 constraint...