You can subscribe to this list here.
| 2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(29) |
Dec
(64) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2008 |
Jan
(121) |
Feb
(273) |
Mar
(69) |
Apr
(41) |
May
(91) |
Jun
(121) |
Jul
(65) |
Aug
(52) |
Sep
(34) |
Oct
(95) |
Nov
(51) |
Dec
(147) |
| 2009 |
Jan
(93) |
Feb
(207) |
Mar
(229) |
Apr
(239) |
May
(410) |
Jun
(324) |
Jul
(332) |
Aug
(88) |
Sep
(195) |
Oct
(637) |
Nov
(434) |
Dec
(275) |
| 2010 |
Jan
(471) |
Feb
(95) |
Mar
(80) |
Apr
(157) |
May
(60) |
Jun
(38) |
Jul
(28) |
Aug
(21) |
Sep
(15) |
Oct
(18) |
Nov
(6) |
Dec
(6) |
| 2011 |
Jan
(12) |
Feb
(13) |
Mar
(9) |
Apr
(2) |
May
(67) |
Jun
(4) |
Jul
(4) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(17) |
| 2012 |
Jan
|
Feb
(2) |
Mar
(1) |
Apr
(6) |
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
(3) |
Nov
|
Dec
|
| 2013 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(3) |
Oct
|
Nov
|
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(5) |
| 2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(3) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2019 |
Jan
(4) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2020 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Matthias M. <mat...@ma...> - 2022-05-27 20:56:36
|
Hi, I created a Flatpak package at https://github.com/flathub/flathub/pull/3220 Had to update the AppStream metadata file with more mandatory data. I tried to send a merge request, but apparently this file is only in the tarball but not in git. See the file attached. Regards, Matt |
|
From: Albert Z. <al...@go...> - 2020-04-25 21:36:45
|
Just in case you have not seen this yet: https://www.webliero.com/ https://news.ycombinator.com/item?id=22980676 (I am discussing there on HN.) Best, Albert |
|
From: Albert Z. <alb...@rw...> - 2019-01-30 08:24:17
|
Just a normal C cast. typedef void (*sigfunc)(int, siginfo*, void*); sa.sa_sigaction_ = (sigfunc) SignalHandler; On Tue, Jan 29, 2019 at 11:29 PM Jozef Riha <jos...@gm...> wrote: > Sorry, I do not know what you mean by that. Can you please explain? > Thanks, jose > > On Mon, Jan 28, 2019 at 9:25 AM Albert Zeyer <alb...@rw...> > wrote: > >> Hi, >> >> I guess some cast should be fine. >> >> Best, >> Albert >> >> >> On Sat, Jan 26, 2019 at 11:42 PM Jozef Riha <jos...@gm...> wrote: >> >>> >>> compiling now, this could take some time ... >>> libs/coredumper/src/linuxthreads.c: In function ‘void >>> ListerThread(ListerParams*)’: >>> libs/coredumper/src/linuxthreads.c:316:24: error: invalid conversion >>> from ‘void (*)(int, siginfo_t*, void*)’ to ‘void (*)(int, siginfo*, void*)’ >>> [-fpermissive] >>> sa.sa_sigaction_ = SignalHandler; >>> ^~~~~~~~~~~~~ >>> >>> error(s) reported, check the output above >>> gcc version 8.2.1 20181127 (GCC) >>> >>> any idea? thank you, jose >>> _______________________________________________ >>> Openlierox-devel mailing list >>> Ope...@li... >>> https://lists.sourceforge.net/lists/listinfo/openlierox-devel >>> >> _______________________________________________ >> Openlierox-devel mailing list >> Ope...@li... >> https://lists.sourceforge.net/lists/listinfo/openlierox-devel >> > > > _______________________________________________ > Openlierox-devel mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openlierox-devel > |
|
From: Jozef R. <jos...@gm...> - 2019-01-29 22:29:39
|
Sorry, I do not know what you mean by that. Can you please explain? Thanks, jose On Mon, Jan 28, 2019 at 9:25 AM Albert Zeyer <alb...@rw...> wrote: > Hi, > > I guess some cast should be fine. > > Best, > Albert > > > On Sat, Jan 26, 2019 at 11:42 PM Jozef Riha <jos...@gm...> wrote: > >> >>> compiling now, this could take some time ... >> libs/coredumper/src/linuxthreads.c: In function ‘void >> ListerThread(ListerParams*)’: >> libs/coredumper/src/linuxthreads.c:316:24: error: invalid conversion from >> ‘void (*)(int, siginfo_t*, void*)’ to ‘void (*)(int, siginfo*, void*)’ >> [-fpermissive] >> sa.sa_sigaction_ = SignalHandler; >> ^~~~~~~~~~~~~ >> >>> error(s) reported, check the output above >> gcc version 8.2.1 20181127 (GCC) >> >> any idea? thank you, jose >> _______________________________________________ >> Openlierox-devel mailing list >> Ope...@li... >> https://lists.sourceforge.net/lists/listinfo/openlierox-devel >> > _______________________________________________ > Openlierox-devel mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openlierox-devel > |
|
From: Albert Z. <alb...@rw...> - 2019-01-28 08:25:45
|
Hi, I guess some cast should be fine. Best, Albert On Sat, Jan 26, 2019 at 11:42 PM Jozef Riha <jos...@gm...> wrote: > >>> compiling now, this could take some time ... > libs/coredumper/src/linuxthreads.c: In function ‘void > ListerThread(ListerParams*)’: > libs/coredumper/src/linuxthreads.c:316:24: error: invalid conversion from > ‘void (*)(int, siginfo_t*, void*)’ to ‘void (*)(int, siginfo*, void*)’ > [-fpermissive] > sa.sa_sigaction_ = SignalHandler; > ^~~~~~~~~~~~~ > >>> error(s) reported, check the output above > gcc version 8.2.1 20181127 (GCC) > > any idea? thank you, jose > _______________________________________________ > Openlierox-devel mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openlierox-devel > |
|
From: Jozef R. <jos...@gm...> - 2019-01-26 22:42:34
|
>>> compiling now, this could take some time ...
libs/coredumper/src/linuxthreads.c: In function ‘void
ListerThread(ListerParams*)’:
libs/coredumper/src/linuxthreads.c:316:24: error: invalid conversion from
‘void (*)(int, siginfo_t*, void*)’ to ‘void (*)(int, siginfo*, void*)’
[-fpermissive]
sa.sa_sigaction_ = SignalHandler;
^~~~~~~~~~~~~
>>> error(s) reported, check the output above
gcc version 8.2.1 20181127 (GCC)
any idea? thank you, jose
|
|
From: Karel P. <kar...@gm...> - 2018-07-30 23:06:16
|
Hi guys, apologies for the lag, I was on holiday and then your mail kind of fell through, sorry! I've updated the download links and changelog on the website, the HTTPS will take a bit longer to sort out but working on that, too. Thank you for the release and all the care you're still putting in the project :) Cheers! Karel On 30.07.2018 at 20:22 Sergii Pylypenko wrote: > Bump. > > Karel, any chance of updating download links at openlierox.net > <http://openlierox.net> ? Did you forget the site SSH password? > BTW the site HTTPS certificate has long been incorrect. Do you have > any control over server settings? It's now easy to get HTTPS > certificate using https://certbot.eff.org/ > > On Tue, Jul 24, 2018 at 12:20 AM, Albert Zeyer > <alb...@rw... <mailto:alb...@rw...>> wrote: > > Btw, I'm finally going to CCC congress again this year. Maybe > someone wants to join? > > > On Mon, Jul 23, 2018 at 11:19 PM Albert Zeyer > <alb...@rw... <mailto:alb...@rw...>> > wrote: > > Very cool! :) > > > On Mon, Jul 23, 2018 at 10:11 PM Sergii Pylypenko > <x.p...@gm... <mailto:x.p...@gm...>> wrote: > > Hi everyone. > > I've published OpenLieroX 0.58 rc5 release (that's our > stable branch, I don't care about 0.59 at the moment, > since people are playing only 0.58). > Karel, could you please update the download links at > http://www.openlierox.net/ ? > There also was rc4, but it did not have MacOs package, and > Windows package was broken. > I did some basic testing on Windows laptop and iMac, so at > least it should run. > Windows version is 32-bit as usual, MacOs version is > 64-bit only, compiled on MacOs 10.11, I hope everyone has > new MacBooks at this point. > Android version is also there, just in case - ignore 'a24' > suffix, it's Android-specific revision. > I've uploaded it to both SourceForge and Github, because > SourceForge tends to go offline quite often. > > https://sourceforge.net/projects/openlierox/files/openlierox/OpenLieroX%200.58%20rc5/ > <https://sourceforge.net/projects/openlierox/files/openlierox/OpenLieroX%200.58%20rc5/> > > https://github.com/albertz/openlierox/releases/tag/0.58_rc5 > <https://github.com/albertz/openlierox/releases/tag/0.58_rc5> > > Changelog (includes both rc4 and rc5 changes): > > * IPv6 support. > * Show death count in games with infinite lives. > * Navigate all menus with arrow keys, for better gamepad > support. > * Fixed rope warping and explosions not drawn on > infinite map. > * Fixed desynced shots in network games. This will not > eliminate network lag entirely, but it should improve > the situation when your shots hit the other player > without doing any damage. > * Fixed invisible laser in network games. > * New game options: mirror the map, indestructible bonuses. > * Added all player skins from Quality Skins Pack. > * Show weapon name when picking up a bonus, for GunGame > gamemode. > > |
|
From: Albert Z. <alb...@rw...> - 2018-07-23 21:21:13
|
Btw, I'm finally going to CCC congress again this year. Maybe someone wants to join? On Mon, Jul 23, 2018 at 11:19 PM Albert Zeyer <alb...@rw...> wrote: > Very cool! :) > > > On Mon, Jul 23, 2018 at 10:11 PM Sergii Pylypenko <x.p...@gm...> > wrote: > >> Hi everyone. >> >> I've published OpenLieroX 0.58 rc5 release (that's our stable branch, I >> don't care about 0.59 at the moment, since people are playing only 0.58). >> Karel, could you please update the download links at >> http://www.openlierox.net/ ? >> There also was rc4, but it did not have MacOs package, and Windows >> package was broken. >> I did some basic testing on Windows laptop and iMac, so at least it >> should run. >> Windows version is 32-bit as usual, MacOs version is 64-bit only, >> compiled on MacOs 10.11, I hope everyone has new MacBooks at this point. >> Android version is also there, just in case - ignore 'a24' suffix, it's >> Android-specific revision. >> I've uploaded it to both SourceForge and Github, because SourceForge >> tends to go offline quite often. >> >> >> https://sourceforge.net/projects/openlierox/files/openlierox/OpenLieroX%200.58%20rc5/ >> >> https://github.com/albertz/openlierox/releases/tag/0.58_rc5 >> >> Changelog (includes both rc4 and rc5 changes): >> >> - IPv6 support. >> - Show death count in games with infinite lives. >> - Navigate all menus with arrow keys, for better gamepad support. >> - Fixed rope warping and explosions not drawn on infinite map. >> - Fixed desynced shots in network games. This will not eliminate >> network lag entirely, but it should improve the situation when your shots >> hit the other player without doing any damage. >> - Fixed invisible laser in network games. >> - New game options: mirror the map, indestructible bonuses. >> - Added all player skins from Quality Skins Pack. >> - Show weapon name when picking up a bonus, for GunGame gamemode. >> >> |
|
From: Albert Z. <alb...@rw...> - 2018-07-23 21:20:22
|
Very cool! :) On Mon, Jul 23, 2018 at 10:11 PM Sergii Pylypenko <x.p...@gm...> wrote: > Hi everyone. > > I've published OpenLieroX 0.58 rc5 release (that's our stable branch, I > don't care about 0.59 at the moment, since people are playing only 0.58). > Karel, could you please update the download links at > http://www.openlierox.net/ ? > There also was rc4, but it did not have MacOs package, and Windows package > was broken. > I did some basic testing on Windows laptop and iMac, so at least it should > run. > Windows version is 32-bit as usual, MacOs version is 64-bit only, compiled > on MacOs 10.11, I hope everyone has new MacBooks at this point. > Android version is also there, just in case - ignore 'a24' suffix, it's > Android-specific revision. > I've uploaded it to both SourceForge and Github, because SourceForge tends > to go offline quite often. > > > https://sourceforge.net/projects/openlierox/files/openlierox/OpenLieroX%200.58%20rc5/ > > https://github.com/albertz/openlierox/releases/tag/0.58_rc5 > > Changelog (includes both rc4 and rc5 changes): > > - IPv6 support. > - Show death count in games with infinite lives. > - Navigate all menus with arrow keys, for better gamepad support. > - Fixed rope warping and explosions not drawn on infinite map. > - Fixed desynced shots in network games. This will not eliminate > network lag entirely, but it should improve the situation when your shots > hit the other player without doing any damage. > - Fixed invisible laser in network games. > - New game options: mirror the map, indestructible bonuses. > - Added all player skins from Quality Skins Pack. > - Show weapon name when picking up a bonus, for GunGame gamemode. > > |
|
From: Albert Z. <al...@go...> - 2016-12-07 08:55:18
|
Hey everyone, @Sergii: Sad to hear that but I you already said something similar earlier. I still wouldn't give up on your interest though. :) I think I can revive it. About playing on smartphone, that is definitely also something I'm interested in. You are probably right with the controls. I will think a bit about that. However, performance is also a problem. That is one of the reasons I wanted to push more OpenGL acceleration but you are right that it is not easy because we do a lot of pixel pushing. But maybe that is not so much a problem. In any case, this would need a lot of time and work and that is probably the deal-breaker. About jetpack or other elements, I think some mods already have that. I think we can do a lot of experiments in the form of new mods and can also make gameplay changes in new mods. @Karel: The Gusanos code merge is far advanced since last time. There is not much duplication anymore and it has become more clean. So I don't really see a problem in that, although it can maybe still be better abstracted. E.g. the old LX physics could also be implemented as Lua code and then we can get rid of the old LX physics C++ code and we would have one single very generic and powerful engine based on generalized Gusanos with Lua. I think that is a much better and more flexible engine than what we had before. But there is still a lot which could be done for further simplification in the code. Regarding networking and the Lua engine, I think this could need some work. I don't think changing low level socket handling to libuv should break anything. Why should it? Also if we read files with libuv, the file content should not be different. @Kareem: Great to hear that you want to help! Are you familiar with the code? If not, maybe read this: http://www.openlierox.net/wiki/index.php/Contribute_to_the_source_code And then maybe let's talk via chat. I have to say that my time is also limited, so don't expect too much changes in the near future. Best, Albert On Wed, Dec 7, 2016 at 9:37 AM, Kareem Moussa <its...@gm...> wrote: > Hey Albert, > > I'd be glad to help you. I have 4 weeks off from university and this > sounds like a great project. How can I help you out? > > - Kareem > > On Mon, Dec 5, 2016 at 3:12 PM, Karel Petránek <kar...@gm...> > wrote: > > Hi, > > > > I'm currently very busy and I know I will have no time for OLX at least > in > > the next 6 months. Your plans look impressive, I'm however not able to > help > > with them :( I think OLX needs a lot of simlification and fat reduction > - I > > feel the added Gusanos code for example does not carry its own weight. > Also, > > as you mention, the networking and physics simulation code are more > > complicated than they should be. I agree that using something like libuv > is > > better than rolling our own, it might, however, break the compatibility > with > > 0.58. > > > > I like your take on using Deep RL to play OLX. Perhaps we can get it to > the > > OpenAI Universe? :) > > > > > > Karel > > > > 2016-12-04 11:13 GMT-06:00 Sergii Pylypenko <x.p...@gm...>: > >> > >> Hello Albert, I'm glad to hear from you, and I'm surprised that OLX is > >> still not dead. > >> > >> With a great sadness, I have to announce that I have to leave OLX > >> development team. Mostly because I do not care about this game anymore. > >> > >> I am only interested in games which I can play on my phone, and there's > >> absolutely no way I can adapt OLX controls to the touchscreen. > >> > >> On top of this, my job takes all my time lately, I won't have any free > >> time until February at least. > >> > >> Talking about the controls, there are too many actions that the player > has > >> to perform at the same time in OLX, two fingers are not enough for this. > >> > >> I would like you to prove me wrong, but I don't see that happening - > I've > >> tried my hand at porting TeeWorlds some time ago, and after three > complete > >> rewrites of touchscreen controls, it's still not playable. Well, the > >> 'racing' touchscreen scheme works decently enough, as long as you don't > >> intend to use your weapon. > >> > >> I might be interested, if the game would use a jetpack or some > combination > >> of wall clinging and double jump to navigate the level, or any other > >> gameplay which can be handled with only two fingers, but at this point > that > >> won't be OLX anymore. I was recently working on a game called Ninslash, > >> which uses this kind of gameplay, I think the touchscreen controls > there are > >> basically done. It's on Google Play in beta stage. > >> > >> I don't care about technical details that much, I can handle mostly > >> anything. Lately I've been learning GLES2, and I technically can move > OLX > >> rendering to OpenGL, however the game itself is ill-suited to OpenGL, it > >> uses a lot of operations on individual pixels, so it's still faster to > draw > >> everything into the software buffer than trying to render each > individual > >> pixel-size particle using OpenGL. Hovever, it would be nice to try out > some > >> C++11 for a change, I cannot use it on my job. > >> > >> And before you ask, I did not play any game on a PC for, like, 4 years, > >> and I don't own a console either. > >> > >> But I still would like to play some good multiplayer jump-n-shoot > >> skirmish, with no ads or premium currency, and there's still no game > like > >> this on Android, not counting Ninslash, hehe, but even in Ninslash the > >> weapons are kinda dull and both the maps and the gameplay need > rebalancing. > >> > >> The only few good skirmish games are all 3D shooters trying to copy > >> Counter Strike or Battlefield, and I'm tired of 3D shooter controls, > swiping > >> all the time is no fun. > >> > >> > >> On Dec 4, 2016 6:33 AM, "Albert Zeyer" <al...@go...> wrote: > >> > >> Hey, > >> > >> How are you? We haven't talked in a while about OLX. Just yesterday I > was > >> browsing through the code and if I find some rare free time, I want to > work > >> a bit on the OLX 0.59 branch again. > >> > >> I'm not sure if you still have interest and/or time in working on OLX. > But > >> maybe you can give me some input on some things I want to work on. > >> > >> I think nowadays, a more modern approach for multithreading and handling > >> of all the events (network sockets, file handling, etc) is to use some > of > >> the async IO techniques. Actually, I think we can just use some library > for > >> that. Any recommendations? A quick search gave me this: > >> * libuv, http://libuv.org. used by Nodejs and many others > >> (https://github.com/libuv/libuv/wiki/Projects-that-use-libuv). > >> * libev, http://software.schmorp.de/pkg/libev.html > >> * libevent, http://libevent.org > >> * C++ asio, now Boost.Asio, http://think-async.com, > >> http://www.boost.org/doc/libs/1_62_0/doc/html/boost_asio.html, might > also be > >> in standard C++ at some point, > >> https://en.wikipedia.org/wiki/Asio_C%2B%2B_library > >> > >> I think libuv is really the best supported and developed library, and I > >> have used it already a bit, so I tend to use that. I would replace the > >> networking code, the file IO code, the thread pool and our internal > task job > >> system. Some other OLX code uses some more conventional multithreading > (e.g. > >> AI path search) which I would just leave as-is. > >> I think there are also some problems with HawkNL which would hopefully > be > >> resolved by that. > >> > >> Maybe you have seen it already, I have switched to SDL2, and did a lot > of > >> refactoring a few month ago (I don't remember all details anymore, > check the > >> git logs). That mostly works. Current 0.59 seems stable, much more > stable > >> than the latest 0.59 beta release (which was also already mostly > stable). > >> Some parts are also faster, but gameplay itself is slightly slower I > think. > >> I'm not sure how much I can do about that. > >> > >> I think one thing to make it faster would be to really switch to full > >> OpenGL drawing. But this would require quite some work and I'm not sure > if I > >> find that time. Otherwise, maybe some further careful optimization, > >> simplification of the gameloop, etc, might also be already enough, > although > >> that's also not so simple with OLX in its current state. > >> > >> We use OpenAL some sounds, and FreeALUT some some sound utilities. I > >> haven't fully debugged it but I was not sure if it properly can load > all our > >> formats (which are mp3, ogg, wav), at least I sometimes get errors (but > >> maybe just missing files). > >> > >> The biggest problem with the latest 0.59 release was that the networking > >> was somewhat broken. I think you could play on 0.58 servers, and also > host > >> servers for 0.58 players, and also a single 0.59 client could connect, > but > >> multiple 0.59 clients on a 0.59 server was broken or so (don't exactly > >> remember anymore). This was maybe related to the Gusanos/Lua > networking. I > >> have simplified it a bit but I think this is still not really fixed yet. > >> This really has to be fixed for any future 0.59 release. > >> > >> Maybe a big refactoring for the networking is the best thing. I.e. > having > >> it similar like Quake3 or anything more modern, i.e. a pure server and > the > >> client predicts and emulates everything. But also this might be too much > >> work, so probably I wont start it. > >> > >> I want to encapsulate some parts of the code for better automatic > testing. > >> I also want to have a dedicated client, which might help to debug the > >> networking issues. > >> > >> I want to work a bit on the settings GUI. Maybe when switching the > slider > >> from basic settings to advanced settings, it should not add more config > >> options to the list but just show the items which were not shown in the > >> previous setting selection, so it really shows only advanced settings > and > >> not the basic settings. This might be easier to find settings. > >> > >> I want to make the console GUI nicer. > >> > >> And I want to play around with some alternative bot AI implementations. > As > >> you know, my research topic is Deep Learning. And I want to play around > with > >> some reinforcement learning for bot control. > >> > >> Best, > >> Albert > >> > >> > >> > > > > > > ------------------------------------------------------------ > ------------------ > > Developer Access Program for Intel Xeon Phi Processors > > Access to Intel Xeon Phi processor-based developer platforms. > > With one year of Intel Parallel Studio XE. > > Training and support from Colfax. > > Order your platform today.http://sdm.link/xeonphi > > _______________________________________________ > > Openlierox-devel mailing list > > Ope...@li... > > https://lists.sourceforge.net/lists/listinfo/openlierox-devel > > > |
|
From: Kareem M. <its...@gm...> - 2016-12-07 08:37:09
|
Hey Albert, I'd be glad to help you. I have 4 weeks off from university and this sounds like a great project. How can I help you out? - Kareem On Mon, Dec 5, 2016 at 3:12 PM, Karel Petránek <kar...@gm...> wrote: > Hi, > > I'm currently very busy and I know I will have no time for OLX at least in > the next 6 months. Your plans look impressive, I'm however not able to help > with them :( I think OLX needs a lot of simlification and fat reduction - I > feel the added Gusanos code for example does not carry its own weight. Also, > as you mention, the networking and physics simulation code are more > complicated than they should be. I agree that using something like libuv is > better than rolling our own, it might, however, break the compatibility with > 0.58. > > I like your take on using Deep RL to play OLX. Perhaps we can get it to the > OpenAI Universe? :) > > > Karel > > 2016-12-04 11:13 GMT-06:00 Sergii Pylypenko <x.p...@gm...>: >> >> Hello Albert, I'm glad to hear from you, and I'm surprised that OLX is >> still not dead. >> >> With a great sadness, I have to announce that I have to leave OLX >> development team. Mostly because I do not care about this game anymore. >> >> I am only interested in games which I can play on my phone, and there's >> absolutely no way I can adapt OLX controls to the touchscreen. >> >> On top of this, my job takes all my time lately, I won't have any free >> time until February at least. >> >> Talking about the controls, there are too many actions that the player has >> to perform at the same time in OLX, two fingers are not enough for this. >> >> I would like you to prove me wrong, but I don't see that happening - I've >> tried my hand at porting TeeWorlds some time ago, and after three complete >> rewrites of touchscreen controls, it's still not playable. Well, the >> 'racing' touchscreen scheme works decently enough, as long as you don't >> intend to use your weapon. >> >> I might be interested, if the game would use a jetpack or some combination >> of wall clinging and double jump to navigate the level, or any other >> gameplay which can be handled with only two fingers, but at this point that >> won't be OLX anymore. I was recently working on a game called Ninslash, >> which uses this kind of gameplay, I think the touchscreen controls there are >> basically done. It's on Google Play in beta stage. >> >> I don't care about technical details that much, I can handle mostly >> anything. Lately I've been learning GLES2, and I technically can move OLX >> rendering to OpenGL, however the game itself is ill-suited to OpenGL, it >> uses a lot of operations on individual pixels, so it's still faster to draw >> everything into the software buffer than trying to render each individual >> pixel-size particle using OpenGL. Hovever, it would be nice to try out some >> C++11 for a change, I cannot use it on my job. >> >> And before you ask, I did not play any game on a PC for, like, 4 years, >> and I don't own a console either. >> >> But I still would like to play some good multiplayer jump-n-shoot >> skirmish, with no ads or premium currency, and there's still no game like >> this on Android, not counting Ninslash, hehe, but even in Ninslash the >> weapons are kinda dull and both the maps and the gameplay need rebalancing. >> >> The only few good skirmish games are all 3D shooters trying to copy >> Counter Strike or Battlefield, and I'm tired of 3D shooter controls, swiping >> all the time is no fun. >> >> >> On Dec 4, 2016 6:33 AM, "Albert Zeyer" <al...@go...> wrote: >> >> Hey, >> >> How are you? We haven't talked in a while about OLX. Just yesterday I was >> browsing through the code and if I find some rare free time, I want to work >> a bit on the OLX 0.59 branch again. >> >> I'm not sure if you still have interest and/or time in working on OLX. But >> maybe you can give me some input on some things I want to work on. >> >> I think nowadays, a more modern approach for multithreading and handling >> of all the events (network sockets, file handling, etc) is to use some of >> the async IO techniques. Actually, I think we can just use some library for >> that. Any recommendations? A quick search gave me this: >> * libuv, http://libuv.org. used by Nodejs and many others >> (https://github.com/libuv/libuv/wiki/Projects-that-use-libuv). >> * libev, http://software.schmorp.de/pkg/libev.html >> * libevent, http://libevent.org >> * C++ asio, now Boost.Asio, http://think-async.com, >> http://www.boost.org/doc/libs/1_62_0/doc/html/boost_asio.html, might also be >> in standard C++ at some point, >> https://en.wikipedia.org/wiki/Asio_C%2B%2B_library >> >> I think libuv is really the best supported and developed library, and I >> have used it already a bit, so I tend to use that. I would replace the >> networking code, the file IO code, the thread pool and our internal task job >> system. Some other OLX code uses some more conventional multithreading (e.g. >> AI path search) which I would just leave as-is. >> I think there are also some problems with HawkNL which would hopefully be >> resolved by that. >> >> Maybe you have seen it already, I have switched to SDL2, and did a lot of >> refactoring a few month ago (I don't remember all details anymore, check the >> git logs). That mostly works. Current 0.59 seems stable, much more stable >> than the latest 0.59 beta release (which was also already mostly stable). >> Some parts are also faster, but gameplay itself is slightly slower I think. >> I'm not sure how much I can do about that. >> >> I think one thing to make it faster would be to really switch to full >> OpenGL drawing. But this would require quite some work and I'm not sure if I >> find that time. Otherwise, maybe some further careful optimization, >> simplification of the gameloop, etc, might also be already enough, although >> that's also not so simple with OLX in its current state. >> >> We use OpenAL some sounds, and FreeALUT some some sound utilities. I >> haven't fully debugged it but I was not sure if it properly can load all our >> formats (which are mp3, ogg, wav), at least I sometimes get errors (but >> maybe just missing files). >> >> The biggest problem with the latest 0.59 release was that the networking >> was somewhat broken. I think you could play on 0.58 servers, and also host >> servers for 0.58 players, and also a single 0.59 client could connect, but >> multiple 0.59 clients on a 0.59 server was broken or so (don't exactly >> remember anymore). This was maybe related to the Gusanos/Lua networking. I >> have simplified it a bit but I think this is still not really fixed yet. >> This really has to be fixed for any future 0.59 release. >> >> Maybe a big refactoring for the networking is the best thing. I.e. having >> it similar like Quake3 or anything more modern, i.e. a pure server and the >> client predicts and emulates everything. But also this might be too much >> work, so probably I wont start it. >> >> I want to encapsulate some parts of the code for better automatic testing. >> I also want to have a dedicated client, which might help to debug the >> networking issues. >> >> I want to work a bit on the settings GUI. Maybe when switching the slider >> from basic settings to advanced settings, it should not add more config >> options to the list but just show the items which were not shown in the >> previous setting selection, so it really shows only advanced settings and >> not the basic settings. This might be easier to find settings. >> >> I want to make the console GUI nicer. >> >> And I want to play around with some alternative bot AI implementations. As >> you know, my research topic is Deep Learning. And I want to play around with >> some reinforcement learning for bot control. >> >> Best, >> Albert >> >> >> > > > ------------------------------------------------------------------------------ > Developer Access Program for Intel Xeon Phi Processors > Access to Intel Xeon Phi processor-based developer platforms. > With one year of Intel Parallel Studio XE. > Training and support from Colfax. > Order your platform today.http://sdm.link/xeonphi > _______________________________________________ > Openlierox-devel mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openlierox-devel > |
|
From: Karel P. <kar...@gm...> - 2016-12-05 23:13:07
|
Hi, I'm currently very busy and I know I will have no time for OLX at least in the next 6 months. Your plans look impressive, I'm however not able to help with them :( I think OLX needs a lot of simlification and fat reduction - I feel the added Gusanos code for example does not carry its own weight. Also, as you mention, the networking and physics simulation code are more complicated than they should be. I agree that using something like libuv is better than rolling our own, it might, however, break the compatibility with 0.58. I like your take on using Deep RL to play OLX. Perhaps we can get it to the OpenAI Universe? :) Karel 2016-12-04 11:13 GMT-06:00 Sergii Pylypenko <x.p...@gm...>: > Hello Albert, I'm glad to hear from you, and I'm surprised that OLX is > still not dead. > > With a great sadness, I have to announce that I have to leave OLX > development team. Mostly because I do not care about this game anymore. > > I am only interested in games which I can play on my phone, and there's > absolutely no way I can adapt OLX controls to the touchscreen. > > On top of this, my job takes all my time lately, I won't have any free > time until February at least. > > Talking about the controls, there are too many actions that the player has > to perform at the same time in OLX, two fingers are not enough for this. > > I would like you to prove me wrong, but I don't see that happening - I've > tried my hand at porting TeeWorlds some time ago, and after three complete > rewrites of touchscreen controls, it's still not playable. Well, the > 'racing' touchscreen scheme works decently enough, as long as you don't > intend to use your weapon. > > I might be interested, if the game would use a jetpack or some combination > of wall clinging and double jump to navigate the level, or any other > gameplay which can be handled with only two fingers, but at this point that > won't be OLX anymore. I was recently working on a game called Ninslash, > which uses this kind of gameplay, I think the touchscreen controls there > are basically done. It's on Google Play in beta stage. > > I don't care about technical details that much, I can handle mostly > anything. Lately I've been learning GLES2, and I technically can move OLX > rendering to OpenGL, however the game itself is ill-suited to OpenGL, it > uses a lot of operations on individual pixels, so it's still faster to draw > everything into the software buffer than trying to render each individual > pixel-size particle using OpenGL. Hovever, it would be nice to try out some > C++11 for a change, I cannot use it on my job. > > And before you ask, I did not play any game on a PC for, like, 4 years, > and I don't own a console either. > > But I still would like to play some good multiplayer jump-n-shoot > skirmish, with no ads or premium currency, and there's still no game like > this on Android, not counting Ninslash, hehe, but even in Ninslash the > weapons are kinda dull and both the maps and the gameplay need rebalancing. > > The only few good skirmish games are all 3D shooters trying to copy > Counter Strike or Battlefield, and I'm tired of 3D shooter controls, > swiping all the time is no fun. > > > On Dec 4, 2016 6:33 AM, "Albert Zeyer" <al...@go...> wrote: > > Hey, > > How are you? We haven't talked in a while about OLX. Just yesterday I was > browsing through the code and if I find some rare free time, I want to work > a bit on the OLX 0.59 branch again. > > I'm not sure if you still have interest and/or time in working on OLX. But > maybe you can give me some input on some things I want to work on. > > I think nowadays, a more modern approach for multithreading and handling > of all the events (network sockets, file handling, etc) is to use some of > the async IO techniques. Actually, I think we can just use some library for > that. Any recommendations? A quick search gave me this: > * libuv, http://libuv.org. used by Nodejs and many others ( > https://github.com/libuv/libuv/wiki/Projects-that-use-libuv). > * libev, http://software.schmorp.de/pkg/libev.html > * libevent, http://libevent.org > * C++ asio, now Boost.Asio, http://think-async.com, > http://www.boost.org/doc/libs/1_62_0/doc/html/boost_asio.html, might also > be in standard C++ at some point, https://en.wikipedia.or > g/wiki/Asio_C%2B%2B_library > > I think libuv is really the best supported and developed library, and I > have used it already a bit, so I tend to use that. I would replace the > networking code, the file IO code, the thread pool and our internal task > job system. Some other OLX code uses some more conventional multithreading > (e.g. AI path search) which I would just leave as-is. > I think there are also some problems with HawkNL which would hopefully be > resolved by that. > > Maybe you have seen it already, I have switched to SDL2, and did a lot of > refactoring a few month ago (I don't remember all details anymore, check > the git logs). That mostly works. Current 0.59 seems stable, much more > stable than the latest 0.59 beta release (which was also already mostly > stable). Some parts are also faster, but gameplay itself is slightly slower > I think. I'm not sure how much I can do about that. > > I think one thing to make it faster would be to really switch to full > OpenGL drawing. But this would require quite some work and I'm not sure if > I find that time. Otherwise, maybe some further careful optimization, > simplification of the gameloop, etc, might also be already enough, although > that's also not so simple with OLX in its current state. > > We use OpenAL some sounds, and FreeALUT some some sound utilities. I > haven't fully debugged it but I was not sure if it properly can load all > our formats (which are mp3, ogg, wav), at least I sometimes get errors (but > maybe just missing files). > > The biggest problem with the latest 0.59 release was that the networking > was somewhat broken. I think you could play on 0.58 servers, and also host > servers for 0.58 players, and also a single 0.59 client could connect, but > multiple 0.59 clients on a 0.59 server was broken or so (don't exactly > remember anymore). This was maybe related to the Gusanos/Lua networking. I > have simplified it a bit but I think this is still not really fixed yet. > This really has to be fixed for any future 0.59 release. > > Maybe a big refactoring for the networking is the best thing. I.e. having > it similar like Quake3 or anything more modern, i.e. a pure server and the > client predicts and emulates everything. But also this might be too much > work, so probably I wont start it. > > I want to encapsulate some parts of the code for better automatic testing. > I also want to have a dedicated client, which might help to debug the > networking issues. > > I want to work a bit on the settings GUI. Maybe when switching the slider > from basic settings to advanced settings, it should not add more config > options to the list but just show the items which were not shown in the > previous setting selection, so it really shows only advanced settings and > not the basic settings. This might be easier to find settings. > > I want to make the console GUI nicer. > > And I want to play around with some alternative bot AI implementations. As > you know, my research topic is Deep Learning. And I want to play around > with some reinforcement learning for bot control. > > Best, > Albert > > > > |
|
From: Sergii P. <x.p...@gm...> - 2016-12-04 17:13:53
|
Hello Albert, I'm glad to hear from you, and I'm surprised that OLX is still not dead. With a great sadness, I have to announce that I have to leave OLX development team. Mostly because I do not care about this game anymore. I am only interested in games which I can play on my phone, and there's absolutely no way I can adapt OLX controls to the touchscreen. On top of this, my job takes all my time lately, I won't have any free time until February at least. Talking about the controls, there are too many actions that the player has to perform at the same time in OLX, two fingers are not enough for this. I would like you to prove me wrong, but I don't see that happening - I've tried my hand at porting TeeWorlds some time ago, and after three complete rewrites of touchscreen controls, it's still not playable. Well, the 'racing' touchscreen scheme works decently enough, as long as you don't intend to use your weapon. I might be interested, if the game would use a jetpack or some combination of wall clinging and double jump to navigate the level, or any other gameplay which can be handled with only two fingers, but at this point that won't be OLX anymore. I was recently working on a game called Ninslash, which uses this kind of gameplay, I think the touchscreen controls there are basically done. It's on Google Play in beta stage. I don't care about technical details that much, I can handle mostly anything. Lately I've been learning GLES2, and I technically can move OLX rendering to OpenGL, however the game itself is ill-suited to OpenGL, it uses a lot of operations on individual pixels, so it's still faster to draw everything into the software buffer than trying to render each individual pixel-size particle using OpenGL. Hovever, it would be nice to try out some C++11 for a change, I cannot use it on my job. And before you ask, I did not play any game on a PC for, like, 4 years, and I don't own a console either. But I still would like to play some good multiplayer jump-n-shoot skirmish, with no ads or premium currency, and there's still no game like this on Android, not counting Ninslash, hehe, but even in Ninslash the weapons are kinda dull and both the maps and the gameplay need rebalancing. The only few good skirmish games are all 3D shooters trying to copy Counter Strike or Battlefield, and I'm tired of 3D shooter controls, swiping all the time is no fun. On Dec 4, 2016 6:33 AM, "Albert Zeyer" <al...@go...> wrote: Hey, How are you? We haven't talked in a while about OLX. Just yesterday I was browsing through the code and if I find some rare free time, I want to work a bit on the OLX 0.59 branch again. I'm not sure if you still have interest and/or time in working on OLX. But maybe you can give me some input on some things I want to work on. I think nowadays, a more modern approach for multithreading and handling of all the events (network sockets, file handling, etc) is to use some of the async IO techniques. Actually, I think we can just use some library for that. Any recommendations? A quick search gave me this: * libuv, http://libuv.org. used by Nodejs and many others ( https://github.com/libuv/libuv/wiki/Projects-that-use-libuv). * libev, http://software.schmorp.de/pkg/libev.html * libevent, http://libevent.org * C++ asio, now Boost.Asio, http://think-async.com, http://www.boost.org/doc/libs/1_62_0/doc/html/boost_asio.html, might also be in standard C++ at some point, https://en.wikipedia. org/wiki/Asio_C%2B%2B_library I think libuv is really the best supported and developed library, and I have used it already a bit, so I tend to use that. I would replace the networking code, the file IO code, the thread pool and our internal task job system. Some other OLX code uses some more conventional multithreading (e.g. AI path search) which I would just leave as-is. I think there are also some problems with HawkNL which would hopefully be resolved by that. Maybe you have seen it already, I have switched to SDL2, and did a lot of refactoring a few month ago (I don't remember all details anymore, check the git logs). That mostly works. Current 0.59 seems stable, much more stable than the latest 0.59 beta release (which was also already mostly stable). Some parts are also faster, but gameplay itself is slightly slower I think. I'm not sure how much I can do about that. I think one thing to make it faster would be to really switch to full OpenGL drawing. But this would require quite some work and I'm not sure if I find that time. Otherwise, maybe some further careful optimization, simplification of the gameloop, etc, might also be already enough, although that's also not so simple with OLX in its current state. We use OpenAL some sounds, and FreeALUT some some sound utilities. I haven't fully debugged it but I was not sure if it properly can load all our formats (which are mp3, ogg, wav), at least I sometimes get errors (but maybe just missing files). The biggest problem with the latest 0.59 release was that the networking was somewhat broken. I think you could play on 0.58 servers, and also host servers for 0.58 players, and also a single 0.59 client could connect, but multiple 0.59 clients on a 0.59 server was broken or so (don't exactly remember anymore). This was maybe related to the Gusanos/Lua networking. I have simplified it a bit but I think this is still not really fixed yet. This really has to be fixed for any future 0.59 release. Maybe a big refactoring for the networking is the best thing. I.e. having it similar like Quake3 or anything more modern, i.e. a pure server and the client predicts and emulates everything. But also this might be too much work, so probably I wont start it. I want to encapsulate some parts of the code for better automatic testing. I also want to have a dedicated client, which might help to debug the networking issues. I want to work a bit on the settings GUI. Maybe when switching the slider from basic settings to advanced settings, it should not add more config options to the list but just show the items which were not shown in the previous setting selection, so it really shows only advanced settings and not the basic settings. This might be easier to find settings. I want to make the console GUI nicer. And I want to play around with some alternative bot AI implementations. As you know, my research topic is Deep Learning. And I want to play around with some reinforcement learning for bot control. Best, Albert |
|
From: Albert Z. <al...@go...> - 2016-12-04 13:33:24
|
Hey, How are you? We haven't talked in a while about OLX. Just yesterday I was browsing through the code and if I find some rare free time, I want to work a bit on the OLX 0.59 branch again. I'm not sure if you still have interest and/or time in working on OLX. But maybe you can give me some input on some things I want to work on. I think nowadays, a more modern approach for multithreading and handling of all the events (network sockets, file handling, etc) is to use some of the async IO techniques. Actually, I think we can just use some library for that. Any recommendations? A quick search gave me this: * libuv, http://libuv.org. used by Nodejs and many others ( https://github.com/libuv/libuv/wiki/Projects-that-use-libuv). * libev, http://software.schmorp.de/pkg/libev.html * libevent, http://libevent.org * C++ asio, now Boost.Asio, http://think-async.com, http://www.boost.org/doc/libs/1_62_0/doc/html/boost_asio.html, might also be in standard C++ at some point, https://en.wikipedia.org/wiki/Asio_C%2B%2B_library I think libuv is really the best supported and developed library, and I have used it already a bit, so I tend to use that. I would replace the networking code, the file IO code, the thread pool and our internal task job system. Some other OLX code uses some more conventional multithreading (e.g. AI path search) which I would just leave as-is. I think there are also some problems with HawkNL which would hopefully be resolved by that. Maybe you have seen it already, I have switched to SDL2, and did a lot of refactoring a few month ago (I don't remember all details anymore, check the git logs). That mostly works. Current 0.59 seems stable, much more stable than the latest 0.59 beta release (which was also already mostly stable). Some parts are also faster, but gameplay itself is slightly slower I think. I'm not sure how much I can do about that. I think one thing to make it faster would be to really switch to full OpenGL drawing. But this would require quite some work and I'm not sure if I find that time. Otherwise, maybe some further careful optimization, simplification of the gameloop, etc, might also be already enough, although that's also not so simple with OLX in its current state. We use OpenAL some sounds, and FreeALUT some some sound utilities. I haven't fully debugged it but I was not sure if it properly can load all our formats (which are mp3, ogg, wav), at least I sometimes get errors (but maybe just missing files). The biggest problem with the latest 0.59 release was that the networking was somewhat broken. I think you could play on 0.58 servers, and also host servers for 0.58 players, and also a single 0.59 client could connect, but multiple 0.59 clients on a 0.59 server was broken or so (don't exactly remember anymore). This was maybe related to the Gusanos/Lua networking. I have simplified it a bit but I think this is still not really fixed yet. This really has to be fixed for any future 0.59 release. Maybe a big refactoring for the networking is the best thing. I.e. having it similar like Quake3 or anything more modern, i.e. a pure server and the client predicts and emulates everything. But also this might be too much work, so probably I wont start it. I want to encapsulate some parts of the code for better automatic testing. I also want to have a dedicated client, which might help to debug the networking issues. I want to work a bit on the settings GUI. Maybe when switching the slider from basic settings to advanced settings, it should not add more config options to the list but just show the items which were not shown in the previous setting selection, so it really shows only advanced settings and not the basic settings. This might be easier to find settings. I want to make the console GUI nicer. And I want to play around with some alternative bot AI implementations. As you know, my research topic is Deep Learning. And I want to play around with some reinforcement learning for bot control. Best, Albert |
|
From: Dan B <dan...@gm...> - 2015-09-24 07:53:46
|
Hi Albert, Not my server - but I'm glad OLX is not dead, I still check back every now and again :) Dan On 23 September 2015 at 13:52, Albert Zeyer <alb...@rw...> wrote: > Hi Daniel, > > How is it going? It has been a while. > > There is a discussion about your UDP master server. > https://github.com/albertz/openlierox/pull/793 > > All of us have been quite inactive our OLX in the last time. Quite > busy with work / studies / PhD / life. However, OLX is not dead! > > Kind Regards, > Albert > > > > On Sun, Dec 18, 2011 at 2:00 AM, Daniel Sjöholm <ste...@gm...> > wrote: > > Ah, good. > > The IP-address for my server is 217.76.87.68 and should stay that way > > for the foreseeable future. > > Yeah I know. Probably going to have to make a note about it also, for > > those who don't update to latest release. > > I agree, I see no reason for the addresses to be given under different > > domains when openlierox.net exists for the game itself. > > > > Daniel > > > > On 12/13/2011 11:24 PM, Karel Petránek wrote: > >> Hey, > >> I own the openlierox.net domain and it's not a problem to redirect the > DNS > >> of the master server to point to the IP address you specify. A little > >> pelicularity is that we'll need to update the masterservers data file > but I > >> guess there's no way around that. I also think we should move all the > >> masterservers under openlierox.net domain to make things simpler in the > >> future. > >> > >> There are also certain bugs in the current rc3 release that should be > >> fixed - how about having a little hackathon at CCC/during Xmas fixing > those > >> and creating a final 0.58 version with the masterservers updated? > >> > >> Karel > >> > >> -----Původní zpráva----- > >> From: Daniel Sjöholm > >> Sent: Tuesday, December 13, 2011 10:56 PM > >> To: ope...@li... > >> Subject: [Openlierox-devel] udpmasterserver and Openlierox.net > >> domainownership? > >> > >> Hi, > >> as you know I'm running one of the UDP masterservers, currently in the > >> udpmsaterservers.txt as ms.olx.dailyupload.net:23450. > >> I'm probably going to retire dailyupload.net from active use in a few > >> months, and that would mean that the file needs to be updated with a new > >> address.. > >> > >> I can still run the udp-masterserver on my server, but need something > >> new pointing to it. > >> Preferably this should be done under the openlierox.net domain imo. Who > >> owns openlierox.net? > >> Could this person point some subdomain to my host? Easiest way to have > >> everything in one place, and should I ever need to bring my server down, > >> you can easily point it to a new one. > >> > >> Daniel > >> > >> > >> > ------------------------------------------------------------------------------ > >> Systems Optimization Self Assessment > >> Improve efficiency and utilization of IT resources. Drive out cost and > >> improve service delivery. Take 5 minutes to use this Systems > Optimization > >> Self Assessment. http://www.accelacomm.com/jaw/sdnl/114/51450054/ > >> _______________________________________________ > >> Openlierox-devel mailing list > >> Ope...@li... > >> https://lists.sourceforge.net/lists/listinfo/openlierox-devel > >> > >> > >> > ------------------------------------------------------------------------------ > >> Systems Optimization Self Assessment > >> Improve efficiency and utilization of IT resources. Drive out cost and > >> improve service delivery. Take 5 minutes to use this Systems > Optimization > >> Self Assessment. http://www.accelacomm.com/jaw/sdnl/114/51450054/ > >> _______________________________________________ > >> Openlierox-devel mailing list > >> Ope...@li... > >> https://lists.sourceforge.net/lists/listinfo/openlierox-devel > > > > > > > ------------------------------------------------------------------------------ > > Learn Windows Azure Live! Tuesday, Dec 13, 2011 > > Microsoft is holding a special Learn Windows Azure training event for > > developers. It will provide a great way to learn Windows Azure and what > it > > provides. You can attend the event by watching it streamed LIVE online. > > Learn more at http://p.sf.net/sfu/ms-windowsazure > > _______________________________________________ > > Openlierox-devel mailing list > > Ope...@li... > > https://lists.sourceforge.net/lists/listinfo/openlierox-devel > > > ------------------------------------------------------------------------------ > Monitor Your Dynamic Infrastructure at Any Scale With Datadog! > Get real-time metrics from all of your servers, apps and tools > in one place. > SourceForge users - Click here to start your Free Trial of Datadog now! > http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140 > _______________________________________________ > Openlierox-devel mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openlierox-devel > |
|
From: Sergii P. <x.p...@gm...> - 2015-09-23 13:04:16
|
Hi Albert. Yes, the forums are not dead, I don't know about the game. On Sep 23, 2015 3:52 PM, "Albert Zeyer" <alb...@rw...> wrote: > Hi Daniel, > > How is it going? It has been a while. > > There is a discussion about your UDP master server. > https://github.com/albertz/openlierox/pull/793 > > All of us have been quite inactive our OLX in the last time. Quite > busy with work / studies / PhD / life. However, OLX is not dead! > > Kind Regards, > Albert > > > > On Sun, Dec 18, 2011 at 2:00 AM, Daniel Sjöholm <ste...@gm...> > wrote: > > Ah, good. > > The IP-address for my server is 217.76.87.68 and should stay that way > > for the foreseeable future. > > Yeah I know. Probably going to have to make a note about it also, for > > those who don't update to latest release. > > I agree, I see no reason for the addresses to be given under different > > domains when openlierox.net exists for the game itself. > > > > Daniel > > > > On 12/13/2011 11:24 PM, Karel Petránek wrote: > >> Hey, > >> I own the openlierox.net domain and it's not a problem to redirect the > DNS > >> of the master server to point to the IP address you specify. A little > >> pelicularity is that we'll need to update the masterservers data file > but I > >> guess there's no way around that. I also think we should move all the > >> masterservers under openlierox.net domain to make things simpler in the > >> future. > >> > >> There are also certain bugs in the current rc3 release that should be > >> fixed - how about having a little hackathon at CCC/during Xmas fixing > those > >> and creating a final 0.58 version with the masterservers updated? > >> > >> Karel > >> > >> -----Původní zpráva----- > >> From: Daniel Sjöholm > >> Sent: Tuesday, December 13, 2011 10:56 PM > >> To: ope...@li... > >> Subject: [Openlierox-devel] udpmasterserver and Openlierox.net > >> domainownership? > >> > >> Hi, > >> as you know I'm running one of the UDP masterservers, currently in the > >> udpmsaterservers.txt as ms.olx.dailyupload.net:23450. > >> I'm probably going to retire dailyupload.net from active use in a few > >> months, and that would mean that the file needs to be updated with a new > >> address.. > >> > >> I can still run the udp-masterserver on my server, but need something > >> new pointing to it. > >> Preferably this should be done under the openlierox.net domain imo. Who > >> owns openlierox.net? > >> Could this person point some subdomain to my host? Easiest way to have > >> everything in one place, and should I ever need to bring my server down, > >> you can easily point it to a new one. > >> > >> Daniel > >> > >> > >> > ------------------------------------------------------------------------------ > >> Systems Optimization Self Assessment > >> Improve efficiency and utilization of IT resources. Drive out cost and > >> improve service delivery. Take 5 minutes to use this Systems > Optimization > >> Self Assessment. http://www.accelacomm.com/jaw/sdnl/114/51450054/ > >> _______________________________________________ > >> Openlierox-devel mailing list > >> Ope...@li... > >> https://lists.sourceforge.net/lists/listinfo/openlierox-devel > >> > >> > >> > ------------------------------------------------------------------------------ > >> Systems Optimization Self Assessment > >> Improve efficiency and utilization of IT resources. Drive out cost and > >> improve service delivery. Take 5 minutes to use this Systems > Optimization > >> Self Assessment. http://www.accelacomm.com/jaw/sdnl/114/51450054/ > >> _______________________________________________ > >> Openlierox-devel mailing list > >> Ope...@li... > >> https://lists.sourceforge.net/lists/listinfo/openlierox-devel > > > > > > > ------------------------------------------------------------------------------ > > Learn Windows Azure Live! Tuesday, Dec 13, 2011 > > Microsoft is holding a special Learn Windows Azure training event for > > developers. It will provide a great way to learn Windows Azure and what > it > > provides. You can attend the event by watching it streamed LIVE online. > > Learn more at http://p.sf.net/sfu/ms-windowsazure > > _______________________________________________ > > Openlierox-devel mailing list > > Ope...@li... > > https://lists.sourceforge.net/lists/listinfo/openlierox-devel > |
|
From: Albert Z. <alb...@rw...> - 2015-09-23 12:52:59
|
Hi Daniel, How is it going? It has been a while. There is a discussion about your UDP master server. https://github.com/albertz/openlierox/pull/793 All of us have been quite inactive our OLX in the last time. Quite busy with work / studies / PhD / life. However, OLX is not dead! Kind Regards, Albert On Sun, Dec 18, 2011 at 2:00 AM, Daniel Sjöholm <ste...@gm...> wrote: > Ah, good. > The IP-address for my server is 217.76.87.68 and should stay that way > for the foreseeable future. > Yeah I know. Probably going to have to make a note about it also, for > those who don't update to latest release. > I agree, I see no reason for the addresses to be given under different > domains when openlierox.net exists for the game itself. > > Daniel > > On 12/13/2011 11:24 PM, Karel Petránek wrote: >> Hey, >> I own the openlierox.net domain and it's not a problem to redirect the DNS >> of the master server to point to the IP address you specify. A little >> pelicularity is that we'll need to update the masterservers data file but I >> guess there's no way around that. I also think we should move all the >> masterservers under openlierox.net domain to make things simpler in the >> future. >> >> There are also certain bugs in the current rc3 release that should be >> fixed - how about having a little hackathon at CCC/during Xmas fixing those >> and creating a final 0.58 version with the masterservers updated? >> >> Karel >> >> -----Původní zpráva----- >> From: Daniel Sjöholm >> Sent: Tuesday, December 13, 2011 10:56 PM >> To: ope...@li... >> Subject: [Openlierox-devel] udpmasterserver and Openlierox.net >> domainownership? >> >> Hi, >> as you know I'm running one of the UDP masterservers, currently in the >> udpmsaterservers.txt as ms.olx.dailyupload.net:23450. >> I'm probably going to retire dailyupload.net from active use in a few >> months, and that would mean that the file needs to be updated with a new >> address.. >> >> I can still run the udp-masterserver on my server, but need something >> new pointing to it. >> Preferably this should be done under the openlierox.net domain imo. Who >> owns openlierox.net? >> Could this person point some subdomain to my host? Easiest way to have >> everything in one place, and should I ever need to bring my server down, >> you can easily point it to a new one. >> >> Daniel >> >> >> ------------------------------------------------------------------------------ >> Systems Optimization Self Assessment >> Improve efficiency and utilization of IT resources. Drive out cost and >> improve service delivery. Take 5 minutes to use this Systems Optimization >> Self Assessment. http://www.accelacomm.com/jaw/sdnl/114/51450054/ >> _______________________________________________ >> Openlierox-devel mailing list >> Ope...@li... >> https://lists.sourceforge.net/lists/listinfo/openlierox-devel >> >> >> ------------------------------------------------------------------------------ >> Systems Optimization Self Assessment >> Improve efficiency and utilization of IT resources. Drive out cost and >> improve service delivery. Take 5 minutes to use this Systems Optimization >> Self Assessment. http://www.accelacomm.com/jaw/sdnl/114/51450054/ >> _______________________________________________ >> Openlierox-devel mailing list >> Ope...@li... >> https://lists.sourceforge.net/lists/listinfo/openlierox-devel > > > ------------------------------------------------------------------------------ > Learn Windows Azure Live! Tuesday, Dec 13, 2011 > Microsoft is holding a special Learn Windows Azure training event for > developers. It will provide a great way to learn Windows Azure and what it > provides. You can attend the event by watching it streamed LIVE online. > Learn more at http://p.sf.net/sfu/ms-windowsazure > _______________________________________________ > Openlierox-devel mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openlierox-devel |
|
From: Karel P. <kar...@gm...> - 2013-01-07 17:32:17
|
Sorry, your messages are ending in spam :( I set up the DNS udpmaster.openlierox.net to point to your IP, should be effective in few hours. Karel Dne 5. 1. 2013 21:42, Daniel Sjöholm napsal(a): > Bumping this, my domain runs out in february. > > On 22/10/12 18:14, Daniel Sjöholm wrote: >> Hi, great to see releases still coming out! >> >> Bit late now I realise, but I'd still like if you added an entry for >> the udp-masterserver running on my host (217.76.87.68) as something >> under openlierox.net, as I can continue to keep it up, but am planning >> on releasing the domain it's currently located on (dailyupload.net, >> way too long and bulky). >> I could provide an alternative domainname to replace my current entry, >> but I still think it would be nicer if all the masterservers are >> subdomains of openlierox.net :) >> >> Daniel >> >> On 03/04/12 20:00, Karel Petránek wrote: >>> Hey, >>> >>> I'm not sure whether OLX is suited for touchscreens at all. If you >>> plan to >>> change it that much, please do it in a separate branch :) >>> >>> One more thing I remembered - I set up a masterserver at the >>> openlierox.net >>> domain. The address is http://server.openlierox.net/ and we should >>> add it to >>> the config files before a new release. We can also remove GU server >>> as it >>> will probably never be up again (thegaminguniverse.com domain is for >>> sale). >>> >>> - Karel >>> >>> -----Původní zpráva----- >>> From: Albert Zeyer >>> Sent: Sunday, April 01, 2012 7:57 PM >>> To: ope...@li... >>> Subject: Re: [Openlierox-devel] OLX 0.59 b10 >>> >>> On Sun, Apr 1, 2012 at 10:37 AM, Sergii Pylypenko<x.p...@gm...> >>> wrote: >>>> Hi. It's good to know thal OLX is still alive (and both of you too). >>> Yea! :) >>> >>>> Did you already gained your academic degree Albert? >>> Not yet. But I'm mostly there. I also have some deadlines now. >>> >>>> I'm going to port OLX to Android, 'cause there's no >>>> other way for me to run it. >>> Hehe. :) >>> >>> I was planning the same for iPhone. But we probably need some more >>> work on the gfx to make it running at a good performance. >>> >>> >>>> Also I grew myself a belly, and abandoned sports, and became >>>> undisciplined >>>> and easily irritated. >>> Hey, don't do that. :) I recently started to do much sports (haven't >>> done any earlier) and it feels great and is fun. Besides programming, >>> it's almost my main activity now. >>> >>>> I've already ported TeeWorlds, and it was an >>>> utter failure, and OLX has more complicated controls and gameplay than >>>> TeeWorlds. >>> Yea, I guess we have just to try things out. Not sure yet about the >>> optimal controls. >>> >>>> Naturally, this will cause an outrage in our lovely oldskoolers >>>> community, >>> I guess we will probably target a different audience anyway on smart >>> phones. >>> >>> >>>> Implementing >>>> the perfect sync on all the clients, as I wanted to do previously, is >>>> almost >>>> impossible with our huge codebase. >>> I haven't lost the hope on this. :) >>> >>>> The game state should be easily >>>> serializable for that task, it's easy for LX mods, but I don't know how >>>> hard >>>> for Lua, although you're claiming you've done that. >>> For Lua, it's not really done yet, although most code is there and it >>> isn't too hard. >>> >>> Some other plans for the net engine: I want to send all game updates >>> over an unreliable channel. And the receiver acknowledges all >>> well-received updates. The sender always sends a diff based on the >>> time of the last acknowledges package. This would greatly improve the >>> performance on unreliable networks and also the Internet. >>> >>> Also, we can do it and even do an automatic bandwidth calculation >>> based on that. We can do something similar as the TCP retransmission >>> algorithm, TCP adaptive window scaling algorithm, ec. >>> >>> Some more similar things are not too complicated to implement now. >>> >>> But if the current net code already is performant enough, maybe all >>> that is not so much important. >>> >>> ------------------------------------------------------------------------------ >>> >>> This SF email is sponsosred by: >>> Try Windows Azure free for 90 days Click Here >>> http://p.sf.net/sfu/sfd2d-msazure >>> _______________________________________________ >>> Openlierox-devel mailing list >>> Ope...@li... >>> https://lists.sourceforge.net/lists/listinfo/openlierox-devel >>> >>> >>> ------------------------------------------------------------------------------ >>> >>> Better than sec? Nothing is better than sec when it comes to >>> monitoring Big Data applications. Try Boundary one-second >>> resolution app monitoring today. Free. >>> http://p.sf.net/sfu/Boundary-dev2dev >>> _______________________________________________ >>> Openlierox-devel mailing list >>> Ope...@li... >>> https://lists.sourceforge.net/lists/listinfo/openlierox-devel > > ------------------------------------------------------------------------------ > Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, > MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current > with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft > MVPs and experts. SALE $99.99 this month only -- learn more at: > http://p.sf.net/sfu/learnmore_122912 > _______________________________________________ > Openlierox-devel mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openlierox-devel |
|
From: Daniel S. <ste...@us...> - 2013-01-05 20:43:08
|
Bumping this, my domain runs out in february. On 22/10/12 18:14, Daniel Sjöholm wrote: > Hi, great to see releases still coming out! > > Bit late now I realise, but I'd still like if you added an entry for > the udp-masterserver running on my host (217.76.87.68) as something > under openlierox.net, as I can continue to keep it up, but am planning > on releasing the domain it's currently located on (dailyupload.net, > way too long and bulky). > I could provide an alternative domainname to replace my current entry, > but I still think it would be nicer if all the masterservers are > subdomains of openlierox.net :) > > Daniel > > On 03/04/12 20:00, Karel Petránek wrote: >> Hey, >> >> I'm not sure whether OLX is suited for touchscreens at all. If you >> plan to >> change it that much, please do it in a separate branch :) >> >> One more thing I remembered - I set up a masterserver at the >> openlierox.net >> domain. The address is http://server.openlierox.net/ and we should >> add it to >> the config files before a new release. We can also remove GU server >> as it >> will probably never be up again (thegaminguniverse.com domain is for >> sale). >> >> - Karel >> >> -----Původní zpráva----- >> From: Albert Zeyer >> Sent: Sunday, April 01, 2012 7:57 PM >> To: ope...@li... >> Subject: Re: [Openlierox-devel] OLX 0.59 b10 >> >> On Sun, Apr 1, 2012 at 10:37 AM, Sergii Pylypenko<x.p...@gm...> >> wrote: >>> Hi. It's good to know thal OLX is still alive (and both of you too). >> Yea! :) >> >>> Did you already gained your academic degree Albert? >> Not yet. But I'm mostly there. I also have some deadlines now. >> >>> I'm going to port OLX to Android, 'cause there's no >>> other way for me to run it. >> Hehe. :) >> >> I was planning the same for iPhone. But we probably need some more >> work on the gfx to make it running at a good performance. >> >> >>> Also I grew myself a belly, and abandoned sports, and became >>> undisciplined >>> and easily irritated. >> Hey, don't do that. :) I recently started to do much sports (haven't >> done any earlier) and it feels great and is fun. Besides programming, >> it's almost my main activity now. >> >>> I've already ported TeeWorlds, and it was an >>> utter failure, and OLX has more complicated controls and gameplay than >>> TeeWorlds. >> Yea, I guess we have just to try things out. Not sure yet about the >> optimal controls. >> >>> Naturally, this will cause an outrage in our lovely oldskoolers >>> community, >> I guess we will probably target a different audience anyway on smart >> phones. >> >> >>> Implementing >>> the perfect sync on all the clients, as I wanted to do previously, is >>> almost >>> impossible with our huge codebase. >> I haven't lost the hope on this. :) >> >>> The game state should be easily >>> serializable for that task, it's easy for LX mods, but I don't know how >>> hard >>> for Lua, although you're claiming you've done that. >> For Lua, it's not really done yet, although most code is there and it >> isn't too hard. >> >> Some other plans for the net engine: I want to send all game updates >> over an unreliable channel. And the receiver acknowledges all >> well-received updates. The sender always sends a diff based on the >> time of the last acknowledges package. This would greatly improve the >> performance on unreliable networks and also the Internet. >> >> Also, we can do it and even do an automatic bandwidth calculation >> based on that. We can do something similar as the TCP retransmission >> algorithm, TCP adaptive window scaling algorithm, ec. >> >> Some more similar things are not too complicated to implement now. >> >> But if the current net code already is performant enough, maybe all >> that is not so much important. >> >> ------------------------------------------------------------------------------ >> >> This SF email is sponsosred by: >> Try Windows Azure free for 90 days Click Here >> http://p.sf.net/sfu/sfd2d-msazure >> _______________________________________________ >> Openlierox-devel mailing list >> Ope...@li... >> https://lists.sourceforge.net/lists/listinfo/openlierox-devel >> >> >> ------------------------------------------------------------------------------ >> >> Better than sec? Nothing is better than sec when it comes to >> monitoring Big Data applications. Try Boundary one-second >> resolution app monitoring today. Free. >> http://p.sf.net/sfu/Boundary-dev2dev >> _______________________________________________ >> Openlierox-devel mailing list >> Ope...@li... >> https://lists.sourceforge.net/lists/listinfo/openlierox-devel > |
|
From: Daniel S. <ste...@us...> - 2012-10-22 16:15:06
|
Hi, great to see releases still coming out! Bit late now I realise, but I'd still like if you added an entry for the udp-masterserver running on my host (217.76.87.68) as something under openlierox.net, as I can continue to keep it up, but am planning on releasing the domain it's currently located on (dailyupload.net, way too long and bulky). I could provide an alternative domainname to replace my current entry, but I still think it would be nicer if all the masterservers are subdomains of openlierox.net :) Daniel On 03/04/12 20:00, Karel Petránek wrote: > Hey, > > I'm not sure whether OLX is suited for touchscreens at all. If you plan to > change it that much, please do it in a separate branch :) > > One more thing I remembered - I set up a masterserver at the openlierox.net > domain. The address is http://server.openlierox.net/ and we should add it to > the config files before a new release. We can also remove GU server as it > will probably never be up again (thegaminguniverse.com domain is for sale). > > - Karel > > -----Původní zpráva----- > From: Albert Zeyer > Sent: Sunday, April 01, 2012 7:57 PM > To: ope...@li... > Subject: Re: [Openlierox-devel] OLX 0.59 b10 > > On Sun, Apr 1, 2012 at 10:37 AM, Sergii Pylypenko<x.p...@gm...> > wrote: >> Hi. It's good to know thal OLX is still alive (and both of you too). > Yea! :) > >> Did you already gained your academic degree Albert? > Not yet. But I'm mostly there. I also have some deadlines now. > >> I'm going to port OLX to Android, 'cause there's no >> other way for me to run it. > Hehe. :) > > I was planning the same for iPhone. But we probably need some more > work on the gfx to make it running at a good performance. > > >> Also I grew myself a belly, and abandoned sports, and became undisciplined >> and easily irritated. > Hey, don't do that. :) I recently started to do much sports (haven't > done any earlier) and it feels great and is fun. Besides programming, > it's almost my main activity now. > >> I've already ported TeeWorlds, and it was an >> utter failure, and OLX has more complicated controls and gameplay than >> TeeWorlds. > Yea, I guess we have just to try things out. Not sure yet about the > optimal controls. > >> Naturally, this will cause an outrage in our lovely oldskoolers community, > I guess we will probably target a different audience anyway on smart phones. > > >> Implementing >> the perfect sync on all the clients, as I wanted to do previously, is >> almost >> impossible with our huge codebase. > I haven't lost the hope on this. :) > >> The game state should be easily >> serializable for that task, it's easy for LX mods, but I don't know how >> hard >> for Lua, although you're claiming you've done that. > For Lua, it's not really done yet, although most code is there and it > isn't too hard. > > Some other plans for the net engine: I want to send all game updates > over an unreliable channel. And the receiver acknowledges all > well-received updates. The sender always sends a diff based on the > time of the last acknowledges package. This would greatly improve the > performance on unreliable networks and also the Internet. > > Also, we can do it and even do an automatic bandwidth calculation > based on that. We can do something similar as the TCP retransmission > algorithm, TCP adaptive window scaling algorithm, ec. > > Some more similar things are not too complicated to implement now. > > But if the current net code already is performant enough, maybe all > that is not so much important. > > ------------------------------------------------------------------------------ > This SF email is sponsosred by: > Try Windows Azure free for 90 days Click Here > http://p.sf.net/sfu/sfd2d-msazure > _______________________________________________ > Openlierox-devel mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openlierox-devel > > > ------------------------------------------------------------------------------ > Better than sec? Nothing is better than sec when it comes to > monitoring Big Data applications. Try Boundary one-second > resolution app monitoring today. Free. > http://p.sf.net/sfu/Boundary-dev2dev > _______________________________________________ > Openlierox-devel mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openlierox-devel |
|
From: Karel P. <kar...@ti...> - 2012-10-09 22:42:03
|
I think it's perfectly fine to do the upgrade. K. -----Původní zpráva----- From: Albert Zeyer Sent: Tuesday, October 09, 2012 2:38 AM To: ope...@li... Subject: Re: [Openlierox-devel] OpenLieroX and the New SourceForge I think we can safely just upgrade, don't we? We anyway moved basically most important stuff (Git, issue tracker) over to GitHub. Afaik, the remaining parts on SF are: - File releases - Mailinglist On the update information page, it just says it can update these (and many other things). I guess it should/would just work as expected and not really change anything for us. So, if you are ok, I'll just let OLX be scheduled for upgrading by SF. Cheers, Albert On Mon, Oct 8, 2012 at 9:42 PM, Rich Bowen <rb...@so...> wrote: > > > Dear OpenLieroX project admin, > > As one of our top projects, we want to be sure that you are aware of > what's coming in the near future. As you are no doubt aware by now, > SourceForge is upgrading our core development product from the "Classic" > forge to a new product, code-named "Allura". Allura is itself Open > Source, and is developed on SourceForge, at http://sf.net/p/allura/ > Allura is also incubating at the Apache Software Foundation, to become > an ASF project. (http://incubator.apache.org/projects/allura.html) > > Early next year, we hope to be 100% migrated off of the classic > platform. As a developer yourself, you understand that we want to > retire the legacy code base, so that we can spend less time in > maintenance, and more time moving forward. > > We'd like for you to have the opportunity to upgrade on your own > schedule, rather than ours. You can read about the upgrade process at > https://sourceforge.net/p/upgrade/ and then press the 'Upgrade' button > next to your project name. > > In our surveys of projects that have upgraded, 97% of respondants tell > us that the upgrade improved, or at least didn't change (12% said that), > their developer experience. > > Please don't hesitate to email me with any questions or comments you > might have about the upgrade process. > > -- > Rich Bowen, for the SourceForge Community Team > com...@so... ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ Openlierox-devel mailing list Ope...@li... https://lists.sourceforge.net/lists/listinfo/openlierox-devel |
|
From: Albert Z. <al...@go...> - 2012-10-09 00:38:54
|
I think we can safely just upgrade, don't we? We anyway moved basically most important stuff (Git, issue tracker) over to GitHub. Afaik, the remaining parts on SF are: - File releases - Mailinglist On the update information page, it just says it can update these (and many other things). I guess it should/would just work as expected and not really change anything for us. So, if you are ok, I'll just let OLX be scheduled for upgrading by SF. Cheers, Albert On Mon, Oct 8, 2012 at 9:42 PM, Rich Bowen <rb...@so...> wrote: > > > Dear OpenLieroX project admin, > > As one of our top projects, we want to be sure that you are aware of > what's coming in the near future. As you are no doubt aware by now, > SourceForge is upgrading our core development product from the "Classic" > forge to a new product, code-named "Allura". Allura is itself Open > Source, and is developed on SourceForge, at http://sf.net/p/allura/ > Allura is also incubating at the Apache Software Foundation, to become > an ASF project. (http://incubator.apache.org/projects/allura.html) > > Early next year, we hope to be 100% migrated off of the classic > platform. As a developer yourself, you understand that we want to > retire the legacy code base, so that we can spend less time in > maintenance, and more time moving forward. > > We'd like for you to have the opportunity to upgrade on your own > schedule, rather than ours. You can read about the upgrade process at > https://sourceforge.net/p/upgrade/ and then press the 'Upgrade' button > next to your project name. > > In our surveys of projects that have upgraded, 97% of respondants tell > us that the upgrade improved, or at least didn't change (12% said that), > their developer experience. > > Please don't hesitate to email me with any questions or comments you > might have about the upgrade process. > > -- > Rich Bowen, for the SourceForge Community Team > com...@so... |
|
From: Albert Z. <al...@go...> - 2012-08-06 01:01:25
|
Hey Jayce, What version have you tried? Many of your suggestions are already possible in OpenLieroX 0.59. If you don't play network games, try the latest OLX 0.59 beta10 version which should be really stable for non-network games (unfortunately, for network games, this 0.59 beta10 is somewhat broken; you should use 0.58 rc3). In 0.59, esp. try some of the Gusanos mods and Gusanos maps. On lxalliance.net as well as in the OLX wiki, you will find some posts about the development of OLX 0.59 with all its new features. Many of your suggested weapons are possible to implement in mods (and there might already be some mods who have some of them). But that is not what we (the OLX developers) do. That is up to the mod developers. If some weapon is not possible to implement, that is where we have to do some work. I guess you haven't tried OLX 0.59 yet. So try it out and re-contact us with further suggestions. :) You are correct, we are always interested in and open to them. If you would like to make it a bit easier for us, register on github.com, visit https://github.com/albertz/openlierox and for each separate suggestion, make a new issue report (click on "Issues" -> "New Issue"). Cya, Albert On Sat, Aug 4, 2012 at 7:10 PM, Judy Thomson <tho...@gm...> wrote: > I tried the email from the Liero text, but the email no longer works, so I > am sending ideas here....... > > This game is totally awesome! It's soooo fun! I read that you're open to > suggestions, so here's a few: > > Sprites: > Maybe being able to change the worms to human sprites > > Maps: > Having more materials like wood and metal > Background, i.e. having above ground fights > Environments: Trees, water that would slow weapons' projectiles and > movement, snow, lava, etc. > > Weapons: > Water gun: shoots water that slows movement, weapon projectiles, possilbly > drowning > Acid gun: like water gun, but hurts > Lava gun: like acid gun, but BURNS >:D > BFG 9000: shoots a big plasma ball that digs through dirt and then explodes > :D > Taser: shoots like the ninja rope, but doesn't drag you in and zaps your > opponent > Skitter gun: shoots a little spider-like droid that you can move around and > then explode near your opponent (climbs walls?) > Ice gun: shoots ice. much like dirtball, but eventually the ice will > disappear. to compensate, can freeze enemy worms > Melee weapons like lightsabers, swords, axes, spears, etc. > Drill: shoots a drill that goes really fast throughout the dirt, and does > massive damage to enemy worms > Thunder cannon: shoots a bunch of lightning bolts that splay around > moltov cocktails (set ground on fire?) > glue gun: glues your opponent in place or make traps > auto-turrets: place them down and let them shoot anything that moves in a > straight line! > buzzsaw cannon: shoots buzzsaws that will stick to ground and move along it, > even going vertically (eventually disappear) > Assualt rifle: an accurate uze pretty much > B.L.A.C.K.H.O.L.E. Rifle: shoots mini black holes that tear up terrain and > worms (eventually disappear) > Stinger: shoots tons of little darts that semi-home > Vorpal handgun: each shot drains the enemies life and gives you back some > Nailgun: hehehe, just imagine nailing a worm to the ground!!!! > Sonic phaser: collapses tunnels! > etc. > > Tools: > Jetpack (would act like a weapon, i.e. use until all bar is gone, then needs > to recharge) > Shovel (faster digging) > Cloner (makes illusions of your worm, so your enemy doesn't know which is > the real worm) > etc. > > Powerups: > regular health pickups > regular box pickups > shield: temporarily gives you a blue shield around you > speed: temporarily boosts your movement and digging speed > etc. > > > > > Yup, just some ideas!! > Jayce Thomson > |
|
From: Judy T. <tho...@gm...> - 2012-08-04 17:10:59
|
I tried the email from the Liero text, but the email no longer works, so I am sending ideas here....... This game is totally awesome! It's soooo fun! I read that you're open to suggestions, so here's a few: Sprites: Maybe being able to change the worms to human sprites Maps: Having more materials like wood and metal Background, i.e. having above ground fights Environments: Trees, water that would slow weapons' projectiles and movement, snow, lava, etc. Weapons: Water gun: shoots water that slows movement, weapon projectiles, possilbly drowning Acid gun: like water gun, but hurts Lava gun: like acid gun, but BURNS >:D BFG 9000: shoots a big plasma ball that digs through dirt and then explodes :D Taser: shoots like the ninja rope, but doesn't drag you in and zaps your opponent Skitter gun: shoots a little spider-like droid that you can move around and then explode near your opponent (climbs walls?) Ice gun: shoots ice. much like dirtball, but eventually the ice will disappear. to compensate, can freeze enemy worms Melee weapons like lightsabers, swords, axes, spears, etc. Drill: shoots a drill that goes really fast throughout the dirt, and does massive damage to enemy worms Thunder cannon: shoots a bunch of lightning bolts that splay around moltov cocktails (set ground on fire?) glue gun: glues your opponent in place or make traps auto-turrets: place them down and let them shoot anything that moves in a straight line! buzzsaw cannon: shoots buzzsaws that will stick to ground and move along it, even going vertically (eventually disappear) Assualt rifle: an accurate uze pretty much B.L.A.C.K.H.O.L.E. Rifle: shoots mini black holes that tear up terrain and worms (eventually disappear) Stinger: shoots tons of little darts that semi-home Vorpal handgun: each shot drains the enemies life and gives you back some Nailgun: hehehe, just imagine nailing a worm to the ground!!!! Sonic phaser: collapses tunnels! etc. Tools: Jetpack (would act like a weapon, i.e. use until all bar is gone, then needs to recharge) Shovel (faster digging) Cloner (makes illusions of your worm, so your enemy doesn't know which is the real worm) etc. Powerups: regular health pickups regular box pickups shield: temporarily gives you a blue shield around you speed: temporarily boosts your movement and digging speed etc. Yup, just some ideas!! Jayce Thomson |
|
From: Albert Z. <al...@go...> - 2012-04-17 17:05:15
|
Hey, I released 0.59 beta10 now. See here for the LXA thread: http://www.openlierox.net/forum/index.php/topic,13681 It seems that there are quite a few bugs. And esp. the network seems quite broken. The problem is, this is a bit hard to debug only locally. I tested it with two OLX instances on the same system. Some reports suggest that once there are more than one client, things get messed up (the client only sees the host). I wont be able to do much on OLX for the next three months, though. But I'll be available for questions. And we can quite easily make another release now; I updated most of the distrib scripts (with some restrictions) and have all the environment setup again. I think once these bugs are fixed, 0.59 will be quite a big thing for the OLX community. -Albert |