Spring RTS Engine

They are on https://springrts.com/dl/buildbot/default/maintenance/ and available through pr-dl/upq. This is what makes them appear on api.springfiles.com, but they won't appear on the webpages of www.springfiles.com There is a (short) delay between appearance on the main server and appearance via t...

Can we get recent spring maintenance builds on springfiles? See http://zero-k.info/Forum/Post/204703#204703

I don't see how that ticket is relevant or what needs handling there which is related to engines. I guess you only want to use non-breaking changes because the zk selected 104 was bad in some way, i say this because https://github.com/spring/spring/commit/6971132e was excluded from maintenance. Per...

sprunk, that is only if game(zk) devs do not have the time or will to test develop. I suspect hokomoko and perhaps even kloot are willing to contribute to that zk branch if zk devs do not have time/will for it. Imo, it is clear all develop changes should be tested by game devs and testers like me si...

I suggested to let games(zk) handle this: https://github.com/ZeroK-RTS/Zero-K/issues/2535
I think this is better since the GL changes will be tested and you do not have to worry about commits with both GL and other changes.

Just curious why you use a self built spring and unitsync ?
Downloaded 104.0 spring and unitsync works good for me in flobby.
As a workaround you can config your 104.0 flobby spring profile to use your spring exe and the downloaded 104.0 unitsync.

Using dlmopen fixed the C++ ABI problem for me, see https://github.com/cleanrock/flobby/commit/4196506 for details.

Arch switched to the new ABI recently:
https://www.archlinux.org/news/c-abi-change/

Oddly I only first ran into problems with downloaded 100.0 unitsync when I started using boost 1.60.
I don't know why I did not see this problem earlier when I was using boost 1.59 which was rebuilt using the new ABI.

Probably archlinux specific atm but may be of interest to users: I rebuilt flobby with boost 1.60 today and it seems the C++ ABI change caused a crash in the downloaded 100.0 libunitsync.so. Not sure why I have not seen this issue before but I fixed it by using my locally built 100.0, edit your flob...

Test if "LoadingMT = 0" removes the hang at exit.

Perhaps this is the same issue I see, latest engines are not found on api.springfiles.com.
Latest I see on springfiles is "100.0.1-235-g0cd8d66 develop".

The ImageMagick build problems I have heard about should now be fixed:
https://github.com/cleanrock/flobby/com ... 45a7473e28

Split from https://springrts.com/phpbb/viewtopic.php?f=1&t=33366. I think wiki search have regressed, try to search for SpawnProjectile -> no hits ... you have to search for Spring.SpawnProjectile to find it. Previously i think wiki search used a custom google search which worked fine when sear...

Update flobby to be able to start spring engine in paths with spaces.
This fix is needed since pr-downloader now extracts develop engines to folder with space, e.g.
".spring/engine/98.0.1-529-g86a5f10 develop", see https://github.com/springfiles/upq/commit/11c82e0 .

smoth wrote: it is IMPORTANT for me to read the poster's name first ...

smoth, the poster name is in text above the message.

I think having the sidebar with info about the poster to the right is a big improvement.

These are my biggest complaints about new forum:
- "View the latest post" is a 5 pixel icon that is hard to hit
- "New posts" hidden in "Quick links"

Let us make spring forum easy to use and not look like an experiment.

jK wrote:seems you use FLTK in src/main.cpp, but only include_dir it in src/gui/*

This should be fixed now: https://github.com/cleanrock/flobby/commit/7b83aea

Added Zero-K lobby server support, use -z or --zerok argument.
New dependency is jsoncpp.
Bug reports are welcome.

Turns out overriding XDG env vars is not that good when opening web links, update flobby and use new -d|--dir argument instead, e.g. :
$ flobby -title zk -d ~/flobby_zk

Update flobby to be able to login to lobby.zero-k.info.
To run two flobby clients simultaneously i recommend setting XDG env vars for the extra flobby instance, e.g: