176
Closed bug reports / Re: 4772.542242d / CEGUI: Options > Misc > Camera Move Speed
« on: 15 March 2014, 21:26:51 »
Confirmed, thanks.
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
177
MegaGlest / Re: A first cup to begin this idea ^^ (enrrollment)
« on: 15 March 2014, 21:22:13 »
Count me in, too.
Maybe consider changing the subject line to something more catchy such as "MegaGlest Cup"? (This topic is now sticky.)
Maybe consider changing the subject line to something more catchy such as "MegaGlest Cup"? (This topic is now sticky.)
178
MegaGlest / WIP: dabascht's QT4/5 based map editor
« on: 15 March 2014, 18:33:07 »
dabascht AKA basxto is currently working on a QT4/5 based clone of the (cureently wxgtk based) map editor:
https://github.com/dabascht/megaglest-source/tree/qt4
It's work in progress, most functionality isn't there, yet, but it's possible to build it already.
So here's how to build it on Ubuntu:
Ubuntu 12.04 LTS (QT4):
Ubuntu 13.10 (QT5):
Ubuntu 14.04 LTS will likely work the same as 13.10.
SCM stands for source code management, it's just where I like to keep any source code repositories - you can name this differently and place it elsewhere, of course. The same goes for the megaglest-source_dabascht directory.
https://github.com/dabascht/megaglest-source/tree/qt4
It's work in progress, most functionality isn't there, yet, but it's possible to build it already.
So here's how to build it on Ubuntu:
Ubuntu 12.04 LTS (QT4):
Code: [Select]
cd
mkdir SCM
cd SCM
git clone https://github.com/dabascht/megaglest-source.git megaglest-source_dabascht
cd megaglest-source_dabascht
# If you also want the default MegaGlest assets:
#git submodule update --init --recursive
git checkout qt4
cd mk/linux
sudo ./setupBuildDeps.sh
sudo apt-get install libqt4-dev
sed -i 's/^EXTRA_CMAKE_OPTIONS=$/EXTRA_CMAKE_OPTIONS="-DBUILD_MEGAGLEST=Off -DBUILD_MEGAGLEST_MAP_EDITOR=On -DBUILD_MEGAGLEST_MODEL_IMPORT_EXPORT_TOOLS=Off -DBUILD_MEGAGLEST_MODEL_VIEWER=Off -DUSE_QT5=Off"/' build-mg.sh
./build-mg.sh
Ubuntu 13.10 (QT5):
Code: [Select]
cd
mkdir SCM
cd SCM
git clone https://github.com/dabascht/megaglest-source.git megaglest-source_dabascht
cd megaglest-source_dabascht
# If you also want the default MegaGlest assets:
#git submodule update --init --recursive
git checkout qt4
cd mk/linux
sudo ./setupBuildDeps.sh
sudo apt-get install qt5-default
sed -i 's/^EXTRA_CMAKE_OPTIONS=$/EXTRA_CMAKE_OPTIONS="-DBUILD_MEGAGLEST=Off -DBUILD_MEGAGLEST_MAP_EDITOR=On -DBUILD_MEGAGLEST_MODEL_IMPORT_EXPORT_TOOLS=Off -DBUILD_MEGAGLEST_MODEL_VIEWER=Off -DUSE_QT5=On"/' build-mg.sh
./build-mg.sh
Ubuntu 14.04 LTS will likely work the same as 13.10.
SCM stands for source code management, it's just where I like to keep any source code repositories - you can name this differently and place it elsewhere, of course. The same goes for the megaglest-source_dabascht directory.
179
Closed bug reports / Re: 4772.542242d / CEGUI: Options > Misc > Camera Move Speed
« on: 15 March 2014, 13:36:47 »
In 4776.6643ef4, camera move speed is now configured using a slider (no values are printed). However, the values you configure using the slider may not be stored properly.
Try this: draw the camera move speed slider to the rightmost position. Then click on "Save", notice how the slider position changes, and repeat.
Try this: draw the camera move speed slider to the rightmost position. Then click on "Save", notice how the slider position changes, and repeat.
180
Closed bug reports / Re: 4772.542242d / CEGUI: Options > Video > Rain Effect
« on: 15 March 2014, 13:33:18 »
Confirmed, thanks.
181
Closed bug reports / Re: git+4773.4f216e7 / CEGUI: Tutorial fails to start
« on: 15 March 2014, 13:20:57 »
Both of these (tutorials, scenarios) are [fixed] in 4776.6643ef4. Thanks.
182
Closed bug reports / Re: git+4773.4f216e7 / CEGUI: Tutorial fails to start
« on: 14 March 2014, 21:09:32 »
The same issue also occurs on the scenario menu. There, in addition to the crash when starting the game, the scenario information is not loaded when you select a different scenario from the drop down menu.
183
Closed bug reports / [fixed] git+4773.4f216e7 / CEGUI: Tutorial fails to start
« on: 14 March 2014, 21:00:23 »
When you try to start the advanced tutorial from the CEGUI-fied tutorial menu, you run into a SegF with this:
GDB:
Code: [Select]
*ERROR* [2014-03-14 21:53:57] In [/home/tomreyn/SCM/megaglest-source/source/glest_game/main/main.cpp::handleRuntimeError Line: 633] [listBoxScenario.getSelectedItemIndex() >= scenarioFiles.size(), = [4][3]
Stack Trace:
./megaglest:Shared::Platform::megaglest_runtime_error::megaglest_runtime_error(std::string const&, bool)address [0xc54ad8] line: 305
./megaglest:Glest::Game::MenuStateScenario::loadGameSettings(Glest::Game::ScenarioInfo const*, Glest::Game::GameSettings*)address [0x8b6871] line: 532
./megaglest:Glest::Game::MenuStateScenario::launchGame()address [0x8b9cbc] line: 441
./megaglest:Glest::Game::MenuStateScenario::callDelayedCallbacks()address [0x8b5e58] line: 207
./megaglest:Glest::Game::MenuStateScenario::update()address [0x8c0528] line: 432
./megaglest:Glest::Game::Program::loopWorker()address [0x8396ac] line: 467
./megaglest:Glest::Game::glestMain(int, char**)address [0x819e07] line: 5509
./megaglest:Glest::Game::glestMainSEHWrapper(int, char**)address [0x81c631] line: 5757
./megaglest:Glest::Game::glestMainWrapper(int, char**)address [0x81c834] line: 5831
/lib/x86_64-linux-gnu/libc.so.6:__libc_start_main()address [0x7faf87219de5] line: 0
./megaglest() [0x617f09]address [0x617f09]
] gameInitialized = 1, program = 0x3216630
listBoxScenario.getSelectedItemIndex() >= scenarioFiles.size(), = [4][3]
Stack Trace:
./megaglest:Shared::Platform::megaglest_runtime_error::megaglest_runtime_error(std::string const&, bool)address [0xc54ad8] line: 305
./megaglest:Glest::Game::MenuStateScenario::loadGameSettings(Glest::Game::ScenarioInfo const*, Glest::Game::GameSettings*)address [0x8b6871] line: 532
./megaglest:Glest::Game::MenuStateScenario::launchGame()address [0x8b9cbc] line: 441
./megaglest:Glest::Game::MenuStateScenario::callDelayedCallbacks()address [0x8b5e58] line: 207
./megaglest:Glest::Game::MenuStateScenario::update()address [0x8c0528] line: 432
./megaglest:Glest::Game::Program::loopWorker()address [0x8396ac] line: 467
./megaglest:Glest::Game::glestMain(int, char**)address [0x819e07] line: 5509
./megaglest:Glest::Game::glestMainSEHWrapper(int, char**)address [0x81c631] line: 5757
./megaglest:Glest::Game::glestMainWrapper(int, char**)address [0x81c834] line: 5831
/lib/x86_64-linux-gnu/libc.so.6:__libc_start_main()address [0x7faf87219de5] line: 0
./megaglest() [0x617f09]address [0x617f09]GDB:
Code: [Select]
Core was generated by `./megaglest'.
Program terminated with signal 6, Aborted.
#0 0x00007faf8722ef77 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#0 0x00007faf8722ef77 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1 0x00007faf872325e8 in __GI_abort () at abort.c:90
#2 0x000000000080976e in Glest::Game::ExceptionHandler::handleRuntimeError (msg=<optimized out>, getStackTraceString=getStackTraceString@entry=false) at /home/tomreyn/SCM/megaglest-source/source/glest_game/main/main.cpp:760
#3 0x0000000000809c84 in Glest::Game::ExceptionHandler::handleRuntimeError (ex=...) at /home/tomreyn/SCM/megaglest-source/source/glest_game/main/main.cpp:614
#4 0x0000000000810b2e in Glest::Game::glestMain (argc=argc@entry=1, argv=argv@entry=0x7fff17237f38) at /home/tomreyn/SCM/megaglest-source/source/glest_game/main/main.cpp:5569
#5 0x000000000081c631 in Glest::Game::glestMainSEHWrapper (argc=argc@entry=1, argv=argv@entry=0x7fff17237f38) at /home/tomreyn/SCM/megaglest-source/source/glest_game/main/main.cpp:5755
#6 0x000000000081c834 in Glest::Game::glestMainWrapper (argc=1, argv=0x7fff17237f38) at /home/tomreyn/SCM/megaglest-source/source/glest_game/main/main.cpp:5830
#7 0x00007faf87219de5 in __libc_start_main (main=0x5fe590 <main(int, char**)>, argc=1, ubp_av=0x7fff17237f38, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff17237f28) at libc-start.c:260
#8 0x0000000000617f09 in _start ()
184
Closed bug reports / [fixed] 4772.542242d / CEGUI: Options > Video > Rain Effect
« on: 14 March 2014, 04:35:48 »
On the CEGUI branch, the video options menu offers two Rain Effect options at Options > Video > Rain Effect. However, in the CEGUI variant, there i only one such option (or one of the tick boxes is completely covering the other). There should be two such options, one for enabling/disabling the rain effect on the menus, the other for enabling / disabling it in-game.
185
Closed bug reports / Re: 4772.542242d / CEGUI: Options > Misc > Camera Move Speed
« on: 14 March 2014, 04:28:51 »
The same issue also affects Options > Network > Server Port. And I think there, too, the best solution is to allow to freely edit this field and to set a custom value within a given range.
186
Closed bug reports / [fixed] 4772.542242d / CEGUI: Options > Misc > Camera Move Speed
« on: 14 March 2014, 04:24:37 »
The camera move speed option at Options > Misc > Camera Move Speed provides a text input box. However, any attempts to replace an existing value there by a value of 20 by means of editing the text failed for me. Since these are fixed values, this should probably not be editable text in the first place, but just a drop down menu. Alternatively, and maybe better, allow a specific range of values without intervals (I assume there is any need for the steps of 5 in the first place).
187
Closed bug reports / Re: CEGUI improvements (tracking bug)
« on: 14 March 2014, 02:24:57 »
Both issues are now solved - thanks Softcoder!
188
Closed bug reports / [fixed] 4769.e03536f / CEGUI: Keyboard setup + notices
« on: 13 March 2014, 18:39:57 »
Two minor issues in this version:
Horizontal table width is too large by default (specifically the first table row is too wide).
These messages display on download / removal of translation updates from Transifex:
There should not be a YES / NO prompt there, since these messages are purely informational.
Code: [Select]
Compiled using: GNUC: 40801 [64bit] on: Mar 13 2014 19:03:45 platform: Linux-X64 endianness: little
GIT: [Rev: 4769.e03536f] - using STREFLOP [SSE] - [no-denormals]Horizontal table width is too large by default (specifically the first table row is too wide).
These messages display on download / removal of translation updates from Transifex:
189
Closed bug reports / [fixed] git+4768.5660876 / CEGUI: Crash on exit game prompt
« on: 13 March 2014, 17:05:13 »
I'm not sure this is actually a bug or just lack of implementation. Currently, when I just run the CEGUI branch on atibox and press Escape while the intro is still running, I run into this:
gdb:
Code: [Select]
megaglest v3.10.0-dev
Compiled using: GNUC: 40801 [64bit] on: Mar 13 2014 17:43:41 platform: Linux-X64 endianness: little
GIT: [Rev: 4768.5660876] - using STREFLOP [SSE] - [no-denormals]
In [/home/tomreyn/SCM/megaglest-source/source/glest_game/main/main.cpp::handleSIGSEGV Line: 5660] Error detected: signal 11:
Error saved to logfile [/home/tomreyn/.megaglest/error.log]
*ERROR* [2014-03-13 18:01:04] In [/home/tomreyn/SCM/megaglest-source/source/glest_game/main/main.cpp::handleRuntimeError Line: 633] [In [/home/tomreyn/SCM/megaglest-source/source/glest_game/main/main.cpp::handleSIGSEGV Line: 5660] Error detected: signal 11:
] gameInitialized = 1, program = 0x1eea630
*ERROR* [2014-03-13 18:01:06] In [/home/tomreyn/SCM/megaglest-source/source/glest_game/main/main.cpp::handleRuntimeError Line: 652] [In [/home/tomreyn/SCM/megaglest-source/source/glest_game/main/main.cpp::handleSIGSEGV Line: 5660] Error detected: signal 11:
Stack Trace:
./megaglest:Glest::Game::ExceptionHandler::handleRuntimeError(char const*, bool)address [0x809102] line: 643
./megaglest() [0x80941f]address [0x80941f]
/lib/x86_64-linux-gnu/libc.so.6:()address [0x7f075f615ff0] line: 0
./megaglest:CEGUI::NamedElement::isChild(CEGUI::String const&) constaddress [0xd52754] line: 0
./megaglest:Glest::Game::MegaGlest_CEGUIManager::getMessageBoxRoot(std::string)address [0x7c3214] line: 506
./megaglest:Glest::Game::MegaGlest_CEGUIManager::isMessageBoxShowing(std::string)address [0x7c416f] line: 542
./megaglest:Glest::Game::Program::keyDown(SDL_KeyboardEvent)address [0x836552] line: 327
./megaglest:Glest::Game::MainWindow::eventKeyDown(SDL_KeyboardEvent)address [0x7e942e] line: 1105
./megaglest:Shared::Platform::Window::handleEvent()address [0xc4e3d7] line: 420
./megaglest:Glest::Game::glestMain(int, char**)address [0x8194e5] line: 5422
./megaglest:Glest::Game::glestMainSEHWrapper(int, char**)address [0x81bd31] line: 5757
./megaglest:Glest::Game::glestMainWrapper(int, char**)address [0x81bf34] line: 5831
/lib/x86_64-linux-gnu/libc.so.6:__libc_start_main()address [0x7f075f600de5] line: 0
./megaglest() [0x6175f9]address [0x6175f9]
]
In [/home/tomreyn/SCM/megaglest-source/source/glest_game/main/main.cpp::handleSIGSEGV Line: 5660] Error detected: signal 11:
Stack Trace:
./megaglest:Glest::Game::ExceptionHandler::handleRuntimeError(char const*, bool)address [0x809102] line: 643
./megaglest() [0x80941f]address [0x80941f]
/lib/x86_64-linux-gnu/libc.so.6:()address [0x7f075f615ff0] line: 0
./megaglest:CEGUI::NamedElement::isChild(CEGUI::String const&) constaddress [0xd52754] line: 0
./megaglest:Glest::Game::MegaGlest_CEGUIManager::getMessageBoxRoot(std::string)address [0x7c3214] line: 506
./megaglest:Glest::Game::MegaGlest_CEGUIManager::isMessageBoxShowing(std::string)address [0x7c416f] line: 542
./megaglest:Glest::Game::Program::keyDown(SDL_KeyboardEvent)address [0x836552] line: 327
./megaglest:Glest::Game::MainWindow::eventKeyDown(SDL_KeyboardEvent)address [0x7e942e] line: 1105
./megaglest:Shared::Platform::Window::handleEvent()address [0xc4e3d7] line: 420
./megaglest:Glest::Game::glestMain(int, char**)address [0x8194e5] line: 5422
./megaglest:Glest::Game::glestMainSEHWrapper(int, char**)address [0x81bd31] line: 5757
./megaglest:Glest::Game::glestMainWrapper(int, char**)address [0x81bf34] line: 5831
/lib/x86_64-linux-gnu/libc.so.6:__libc_start_main()address [0x7f075f600de5] line: 0
./megaglest() [0x6175f9]address [0x6175f9]
gdb:
Code: [Select]
Program terminated with signal 6, Aborted.
#0 0x00007fce7ada2f77 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#0 0x00007fce7ada2f77 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1 0x00007fce7ada65e8 in __GI_abort () at abort.c:90
#2 0x0000000000808e6e in Glest::Game::ExceptionHandler::handleRuntimeError (msg=msg@entry=0x7fff22cc5b00 "In [/home/tomreyn/SCM/megaglest-source/source/glest_game/main/main.cpp::handleSIGSEGV Line: 5660] Error detected: signal 11:\n", getStackTraceString=getStackTraceString@entry=true) at /home/tomreyn/SCM/megaglest-source/source/glest_game/main/main.cpp:760
#3 0x000000000080941f in Glest::Game::handleSIGSEGV (sig=<optimized out>) at /home/tomreyn/SCM/megaglest-source/source/glest_game/main/main.cpp:5664
#4 <signal handler called>
#5 0x0000000000d52754 in CEGUI::NamedElement::isChild(CEGUI::String const&) const ()
#6 0x00000000007c3214 in Glest::Game::MegaGlest_CEGUIManager::getMessageBoxRoot (this=this@entry=0x144ec20 <Glest::Game::MegaGlest_CEGUIManager::getInstance()::manager>, rootMessageBoxFullName=...) at /home/tomreyn/SCM/megaglest-source/source/glest_game/gui/megaglest_cegui_manager.cpp:506
#7 0x00000000007c416f in Glest::Game::MegaGlest_CEGUIManager::isMessageBoxShowing (this=this@entry=0x144ec20 <Glest::Game::MegaGlest_CEGUIManager::getInstance()::manager>, rootMessageBoxFullName=...) at /home/tomreyn/SCM/megaglest-source/source/glest_game/gui/megaglest_cegui_manager.cpp:542
#8 0x0000000000836552 in Glest::Game::Program::keyDown (this=0x30a8630, key=...) at /home/tomreyn/SCM/megaglest-source/source/glest_game/main/program.cpp:327
#9 0x00000000007e942e in Glest::Game::MainWindow::eventKeyDown (this=0x30d7c60, key=...) at /home/tomreyn/SCM/megaglest-source/source/glest_game/main/main.cpp:1103
#10 0x0000000000c4e3d7 in Shared::Platform::Window::handleEvent () at /home/tomreyn/SCM/megaglest-source/source/shared_lib/sources/platform/sdl/window.cpp:419
#11 0x00000000008194e5 in Glest::Game::glestMain (argc=argc@entry=1, argv=argv@entry=0x7fff22ccdff8) at /home/tomreyn/SCM/megaglest-source/source/glest_game/main/main.cpp:5422
#12 0x000000000081bd31 in Glest::Game::glestMainSEHWrapper (argc=argc@entry=1, argv=argv@entry=0x7fff22ccdff8) at /home/tomreyn/SCM/megaglest-source/source/glest_game/main/main.cpp:5755
#13 0x000000000081bf34 in Glest::Game::glestMainWrapper (argc=1, argv=0x7fff22ccdff8) at /home/tomreyn/SCM/megaglest-source/source/glest_game/main/main.cpp:5830
#14 0x00007fce7ad8dde5 in __libc_start_main (main=0x5fdc80 <main(int, char**)>, argc=1, ubp_av=0x7fff22ccdff8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff22ccdfe8) at libc-start.c:260
#15 0x00000000006175f9 in _start ()
190
MegaGlest / Re: [still problems] how to make headless server much less cpu/memory demanding
« on: 10 March 2014, 14:57:28 »
This would be my suggestion, too, but chances are this will slow the headless server down so much that there will be network timeouts rather quickly. It may still be worth a try, though.
Another option would be for someone else to review the code. Softcoder has the best understanding of the networking code, but doesn't have any spare time available these days. We may just need to wait until this changes - which is fine, since this is not time critical at all, and thanks to feature branches we can just start to work on something else in the meantime.
Another option would be for someone else to review the code. Softcoder has the best understanding of the networking code, but doesn't have any spare time available these days. We may just need to wait until this changes - which is fine, since this is not time critical at all, and thanks to feature branches we can just start to work on something else in the meantime.
191
MegaGlest / Re: Just an idea : A megaglest cup
« on: 8 March 2014, 18:49:27 »
I'd love it. Now it just takes someone to take the lead and organize it. Both in terms of setting date(s) and time(s) for an international community, as well as in coming up with a good set of rules.
192
Forum discussion / Re: Notifications for edited posts
« on: 8 March 2014, 18:36:49 »
You are probably referring to this:
Those do not rule each other out, but complement one another.
Quote from: tomreyn
When you add more information to a forum topic within minutes and there's no reply, yet, please just edit/update your previous forum post (don't make a fresh post). Thanks.
you can just make another post if you're adding new information which is sufficiently relevant to trigger notifications, that's OK in this case.
Those do not rule each other out, but complement one another.
193
Bug reports / Re: trouble with path names
« on: 8 March 2014, 16:55:14 »Speaking of which, I'd like to see semantic versioning enforced in our releases.
Since this is off-topic here, I've started a separate thread about development news which also discusses semantic versioning.
194
MegaGlest / Development update
« on: 8 March 2014, 16:47:29 »
Since Omega brought this up:
For two releases now, we use a semantic method of versioning, if not "semantic versioning".
We use MAJOR.MINOR.PATCH but their meaning is slightly different (and actually makes more sense to me). We increment the:
As you know we migrated to Git and GitHub not too long ago, and have since started using the Git Flow branching model, and (optionally) the Git Flow AVH Edition for managing the branches. Currently there are two feature branches, one (managed by Softcoder) introduces a new GUI (thanks to CEGUI), the other holds Titi's light-weight headless server variant.
For the past months we used Travis-CI for Continuous Integration. And just since yesterday our own Continuous Integration (Jenkins) installation is back (but it needs yet to be configured), so we shall have snapshot builds for Linux and Windows again soon, too.
When I say we then I mean it inclusively, namely whoever regularly contributes to MegaGlest's development and the project as a whole, or will do so in the future.
For two releases now, we use a semantic method of versioning, if not "semantic versioning".
We use MAJOR.MINOR.PATCH but their meaning is slightly different (and actually makes more sense to me). We increment the:
- MAJOR version when we make major changes, which may include incompatible API changes, or a major change in functionality or usability
- MINOR version when we make "normal" changes, which may include new or improved functionality and other changes, as well as non backward compatible bug fixes
- PATCH version when we make backwards-compatible bug fixes.
As you know we migrated to Git and GitHub not too long ago, and have since started using the Git Flow branching model, and (optionally) the Git Flow AVH Edition for managing the branches. Currently there are two feature branches, one (managed by Softcoder) introduces a new GUI (thanks to CEGUI), the other holds Titi's light-weight headless server variant.
For the past months we used Travis-CI for Continuous Integration. And just since yesterday our own Continuous Integration (Jenkins) installation is back (but it needs yet to be configured), so we shall have snapshot builds for Linux and Windows again soon, too.
When I say we then I mean it inclusively, namely whoever regularly contributes to MegaGlest's development and the project as a whole, or will do so in the future.
195
MegaGlest / Re: Hello Topic
« on: 8 March 2014, 16:16:59 »
Welcome to the MegaGlest forums, Mytos7ita, kratos (yes I'm late!) and dadadu66! Thanks for registering and saying "hi", I hope you'll enjoy the ride.
196
Bug reports / 3.9.1: Game initialization timeout on one player can cause entire game to fail
« on: 6 March 2014, 00:28:12 »
When you start a game and any one (does not need to be host or controlling player) player runs into an initialization timeout (180s), this can cause the entire game to fail for all connected players, meaning that every player gets disconnected just because one timed out.
This should not happen. If one player is unable to initialize the game, it should be dropped and replaced by AI, allowing the other players to start the game fine.
This should not happen. If one player is unable to initialize the game, it should be dropped and replaced by AI, allowing the other players to start the game fine.
197
Bug reports / 3.9.1: Timeout message is displayed in language of user who timed out
« on: 6 March 2014, 00:17:09 »
When a user timed out at the start of a game (i.e. the 180s timeout), all players get to see the timeout notice in the language of the player who timed out, instead of their own.
Example:
This message is also displayed in this locale on the GUI in a message window.
Example:
Code: [Select]
*ERROR* [2014-03-06 00:24:27] In [network_interface.cpp::DisplayErrorMessage Line: 198] sErr [Tiempo de espera para el servidor.]This message is also displayed in this locale on the GUI in a message window.
198
Forum discussion / Re: Notifications for edited posts
« on: 5 March 2014, 14:48:07 »
We will most likely not find the time to modify the source code of this forum software, SimpleMachines Forum (SMF), as well as to maintain these patches, to achieve what you're suggesting. However, you can just make another post if you're adding new information which is sufficiently relevant to trigger notifications, that's OK in this case.
199
MegaGlest / New headless servers "MG-Team"
« on: 3 March 2014, 15:11:06 »
Last night, Titi set up three new headless servers ("MG-Team") which run on a new very well equipped VM (3 GB RAM and a strong CPU) and are listed with dutch IP addresses (the actual server is hosted in France, though). This VM is currently managed by Titi and me (Filux was also invited).
For locations in at least Europe and North America (surely eastern locations), the "Near East" and for parts of Africa and these new gameservers should be quite well connected and stable (that is if your local Internet connection is fine - a common problem we cannot solve). This online service checks how well this new server is reachable from several locations around the world - look for a location close to you to get an estimate of how well you will be able to play there.
To test, each of these sites send a couple ping (ICMP echo) requests, which the server responds to. The site measures the period from when it sent the packet until it receives the servers' reply, called the round trip time (RTT). min. rtt is how long the shortest round trip took, max. rtt is how long the longest round trip took, and avg. rtt is the average across all packets sent.
You can get individual statistics on your own network connection to the server by using the "ping" command line utility (available on Linux, Windows and - I assume - OS X). For more details and an optional graphical interface, there is the "mtr" utility which is available for Linux and Windows ("winmtr" then). By default, Windows also has the "pathping" command line utility which does something quite similar.
For locations in at least Europe and North America (surely eastern locations), the "Near East" and for parts of Africa and these new gameservers should be quite well connected and stable (that is if your local Internet connection is fine - a common problem we cannot solve). This online service checks how well this new server is reachable from several locations around the world - look for a location close to you to get an estimate of how well you will be able to play there.
To test, each of these sites send a couple ping (ICMP echo) requests, which the server responds to. The site measures the period from when it sent the packet until it receives the servers' reply, called the round trip time (RTT). min. rtt is how long the shortest round trip took, max. rtt is how long the longest round trip took, and avg. rtt is the average across all packets sent.
You can get individual statistics on your own network connection to the server by using the "ping" command line utility (available on Linux, Windows and - I assume - OS X). For more details and an optional graphical interface, there is the "mtr" utility which is available for Linux and Windows ("winmtr" then). By default, Windows also has the "pathping" command line utility which does something quite similar.
200
Mods / Re: Anyone needs these files?
« on: 1 March 2014, 13:25:16 »
Thanks. Those are now mirrored on download.megaglest.org/scenarios, too.