EOL v. 1.0.11 released

[Kopaka]

We have just released a new EOL game update! This is a massive client+server update that provides dozens of new features and fixes dozens of bugs. Everyone needs to update their EOL client as instructed in the "How to update" section at https://elma.online/help/updates (TL;DR: Steam users should receive the update automatically. For the standalone version, you need to download https://up.elma.online/u/is1yr0b07j/EOL ... -09-05.zip and extract it in your EOL folder, replacing the old files.)

Highlights of this release include new 64-bit versions of startballe and eolconf, real-time result updating for first finish and one-life battles, best times lists always showing your own position, legacy times imported from Moposite/Kopasite/skintatious, automatic shirt downloading, more customizable replay controls (up to 1024x fast motion), ingame FPS changing, taken apples staying hidden in apple battles, team chat, chat timestamps, longer chat lines, enabling cripple modes outside battle, the last run being automatically saved in a temporary rec file, being able to watch replays of all your PRs and other finished runs on the website (all your PRs/finishes driven after this release), large font layout option for the ingame texts, customizable table alignment, ingame help showing the default key bindings and chat commands, better support for high resolutions, and much more!

See https://elma.online/help/updates for the full list of new features and bug fixes. Enjoy!


Linux/macOS notes:
Startballe and eolconf may stop working since they're now 64 bit.
Wineskin won't work anymore
Install if you don't have homebrew and wine
https://brew.sh/
brew install --cask wine-stable
Update wine and install visual studio 2019 files
sudo winetricks --self-update
winetricks vcrun2019
Run startballe like:
wine startballe.exe

[Bludek]

Wow. This is so big. Can't wait to try it.

[roope]

It's been awesome to follow the development of this and I've been so eager for it to go public. Great job everyone, especially Markku and Kopa

Also, everyone, please do say if you notice anything weird! Despite some testing there can still be something that wasn't thought of.

[zebra]

Nice to see that EOL is still being developed! I thought that it was obsoleted and okeol or Steam Elma or Elasto Mania 2 would take its place. But it's good this way. I hope that this will prevent elma community from breaking up into fragments.

[Igge]

Wow!! Sick effort guys!
Haven't played in a while but this alone makes me want to get back to elma)

[ROKKEBOL]

It's been awesome to follow the development of this and I've been so eager for it to go public. Great job everyone, especially Markku and Kopa

Also, everyone, please do say if you notice anything weird! Despite some testing there can still be something that wasn't thought of.

Yes, now i have empty f5 list and when i press f12 i immediately get the permanent "reconnect" message. Only helps if i close the eol and start again. Happens not always, usually when apple or ff battle is on going.

[culinko]

Hi. I changed my eol password today so had to set the new one in eolconf. Ever since the patching with eolconf, it now takes 5-10 seconds to open elma (before it was instant) and other programs in Windows are really choppy (elma itself is still smooth and elma fps is oke). I am using D3DWindower to start elma in windowed mode.

It seems like patching with the new version of eolconf caused some issues with my setup. If there is anything you need from me let me know and I will help you troubleshoot this issue.

Edit: If I check "play offline" in eolconf and re-patch it, everything is fine. So this has to be something related to the connection or idk.

Edit 2: I changed resolution, map dimensions and zoom levels to different values (still same issue), then changed them back and suddenly it works normally Idk if you did something on your side or what exactly happened but it's fixed now

[Xiphias]

I just wanted to say congratulations on this major update! Must have been a lot of work.

[Cfilorvy]

Started Elma today.
Could not play because I needed update.
Installed update, but can't open eol.exe.
Can't find MSVCP140.dll and VCRUNTIME140.dll.

[ArZeNiK]

Started Elma today.
Could not play because I needed update.
Installed update, but can't open eol.exe.
Can't find MSVCP140.dll and VCRUNTIME140.dll.

those are related to some microsoft visual c++ shit but you can just grab them individually from e.g. www.dll-files.com

[Labs]

Started Elma today.
Could not play because I needed update.
Installed update, but can't open eol.exe.
Can't find MSVCP140.dll and VCRUNTIME140.dll.

https://aka.ms/vs/16/release/vc_redist.x64.exe
https://www.microsoft.com/en-us/downloa ... x?id=49981
https://www.microsoft.com/en-us/downloa ... x?id=40784

Install all these shit and it should work. Both 32 and 64 bit versions where its possible.

[Cfilorvy]

Wow! Thanks a lot!

[culinko]

Hi. I changed my eol password today so had to set the new one in eolconf. Ever since the patching with eolconf, it now takes 5-10 seconds to open elma (before it was instant) and other programs in Windows are really choppy (elma itself is still smooth and elma fps is oke). I am using D3DWindower to start elma in windowed mode.

It seems like patching with the new version of eolconf caused some issues with my setup. If there is anything you need from me let me know and I will help you troubleshoot this issue.

Edit: If I check "play offline" in eolconf and re-patch it, everything is fine. So this has to be something related to the connection or idk.

Edit 2: I changed resolution, map dimensions and zoom levels to different values (still same issue), then changed them back and suddenly it works normally Idk if you did something on your side or what exactly happened but it's fixed now

So had this happen again after patching it with the newest update (1.0.14). I couldn't make it work yesterday but today it worked first try. I then tried eol.exe that wasn't working properly yesterday (that I had backed up) and even that was working now. Compared the binary files and they were identical so it has to be some Windows issue. The only thing I did different is that yesterday I opened old version of eol.exe before patching and today I patched first and only then opened eol. I checked regedit and there are many entries with eol.exe so probably some Direct3D fak or some file hash is being cached somewhere or whatever the fuck.

Afterwards I tried fiddling around with it a bit. I opened eolconf and changed some minor thing (like unchecking the option for "still food"), patched the game, opened it via D3DWindower and the issue was happening again. I then opened eolconf and reverted the change and re-patched the game and it was working properly again. So it's like it remembers that specific eol.exe hash and doesn't work with anything else unless you change it back. It doesn't even work if I restart my pc, then patch with eolconf first before opening eol, so it's either being cached for some specific time somewhere (Windows registry?) or I got extremely lucky that today it worked when I patched it.

Anyways, I won't be investigating more, I'm just happy I got it working with the new eol patch I am posting this mainly for other ppl, in case someone encounters this issue.

(Btw. I also managed to get eol work without D3DWindower with the 12kb ddraw.dll, however it felt very different to play so I will be keeping my current setup with D3DWindower for now.)

[Labs]

Hi. I changed my eol password today so had to set the new one in eolconf. Ever since the patching with eolconf, it now takes 5-10 seconds to open elma (before it was instant) and other programs in Windows are really choppy (elma itself is still smooth and elma fps is oke). I am using D3DWindower to start elma in windowed mode.

It seems like patching with the new version of eolconf caused some issues with my setup. If there is anything you need from me let me know and I will help you troubleshoot this issue.

Edit: If I check "play offline" in eolconf and re-patch it, everything is fine. So this has to be something related to the connection or idk.

Edit 2: I changed resolution, map dimensions and zoom levels to different values (still same issue), then changed them back and suddenly it works normally Idk if you did something on your side or what exactly happened but it's fixed now

So had this happen again after patching it with the newest update (1.0.14). I couldn't make it work yesterday but today it worked first try. I then tried eol.exe that wasn't working properly yesterday (that I had backed up) and even that was working now. Compared the binary files and they were identical so it has to be some Windows issue. The only thing I did different is that yesterday I opened old version of eol.exe before patching and today I patched first and only then opened eol. I checked regedit and there are many entries with eol.exe so probably some Direct3D fak or some file hash is being cached somewhere or whatever the fuck.

Afterwards I tried fiddling around with it a bit. I opened eolconf and changed some minor thing (like unchecking the option for "still food"), patched the game, opened it via D3DWindower and the issue was happening again. I then opened eolconf and reverted the change and re-patched the game and it was working properly again. So it's like it remembers that specific eol.exe hash and doesn't work with anything else unless you change it back. It doesn't even work if I restart my pc, then patch with eolconf first before opening eol, so it's either being cached for some specific time somewhere (Windows registry?) or I got extremely lucky that today it worked when I patched it.

Anyways, I won't be investigating more, I'm just happy I got it working with the new eol patch I am posting this mainly for other ppl, in case someone encounters this issue.

(Btw. I also managed to get eol work without D3DWindower with the 12kb ddraw.dll, however it felt very different to play so I will be keeping my current setup with D3DWindower for now.)

Why would anyone use d3dwindower nowadays? Just use steam ddraw and dxgl.ini to get windowed elma.

[culinko]

I mean, it would be great to ditch the D3DWindower as it is an ancient soft and may very well stop working in the future, however Elma would need to feel the same way and I haven't managed to replicate that with any of the ddraws yet (but that could be just fps issue or resolution/scaling).

Thanks for your dxgl.ini, I managed to get it working with the Steam ddraw.dll I will pm u on Discord and hopefully will be able to adjust it to feel similar to my old setup.

[Labs]

I mean, it would be great to ditch the D3DWindower as it is an ancient soft and may very well stop working in the future, however Elma would need to feel the same way and I haven't managed to replicate that with any of the ddraws yet (but that could be just fps issue or resolution/scaling).

Thanks for your dxgl.ini, I managed to get it working with the Steam ddraw.dll I will pm u on Discord and hopefully will be able to adjust it to feel similar to my old setup.

Prolly u just have more fps than before, try limit it to 300 or smth.