Hello,
We are uploading a new version, this one should fix the cursor bug in game, scrolling using borders in windowed mode, and the windows deck compatibility problem. Please note that decks created under Linux may become incorrect after this update.
Thanks for testing, I believe thanks to you we managed to raise significantly the quality of our Linux port.
Linux beta bug reports
Re: Linux beta bug reports
Also, If you buy the game, it will not remove your beta access, so do not worry.
Re: Linux beta bug reports
I can confirm that muy Athlon x2 1045t (Six cores) works flawlessly.
Re: Linux beta bug reports
I can confirm, that the white box next to the mouse cursor is fixed, but I got a new issue.
I'm able to start the first single player mission, but the when I try to start the second one, game
chrashes at the moment I click on the 'next' button.
console:
dmesg:
system:
I'm able to start the first single player mission, but the when I try to start the second one, game
chrashes at the moment I click on the 'next' button.
console:
Code: Select all
Failed to load installscript /home/sip/.local/share/Steam/SteamApps/common/Wargame European Escalation/installscript.vdf
Game update: AppID 58610 "Wargame: European Escalation", ProcID 3701, IP 0.0.0.0:0
Setting breakpad minidump AppID = 58610
Steam_SetMinidumpSteamID: Caching Steam ID: 76561197982625080 [API loaded no]
saving roaming config store to 'sharedconfig.vdf'
roaming config store 2 saved successfully
Segmentation fault (core dumped)
Game removed: AppID 58610 "Wargame: European Escalation", ProcID 3702
saving roaming config store to 'sharedconfig.vdf'
roaming config store 2 saved successfully
dmesg:
Code: Select all
[ 139.743994] Wargame[2684]: segfault at 4 ip 0904bf8e sp bfc42f50 error 4 in Wargame[8048000+2594000]
[ 192.414563] Wargame[3002]: segfault at 4 ip 0904bf8e sp bff782d0 error 4 in Wargame[8048000+2594000]
[ 233.228639] Wargame[3025]: segfault at 4 ip 0904bf8e sp bfd4b320 error 4 in Wargame[8048000+2594000]
[ 539.988241] Wargame[3266]: segfault at 4 ip 0904bf8e sp bf903310 error 4 in Wargame[8048000+2594000]
[ 744.321060] Wargame[3299]: segfault at 4 ip 0904bf8e sp bfe24930 error 4 in Wargame[8048000+2594000]
system:
Spoiler : :
-
- Private First-Class
- Posts: 8
- Joined: Fri 1 Feb 2013 01:12
- Contact:
Re: Linux beta bug reports
After one of the recent updates the game is now crashing for me as soon as I load the second mission Crossroads. I have played the mission once, but abandoned it towards the end.
Multiplayer loads ok, as does the first mission, but the second causes this segfault as soon as I press Launch:
I would provide more info but I get this message in gdb:
Multiplayer loads ok, as does the first mission, but the second causes this segfault as soon as I press Launch:
Code: Select all
Program received signal SIGSEGV, Segmentation fault.
0x0904bf8e in ?? ()
(gdb) bt
#0 0x0904bf8e in ?? ()
#1 0x0886f93f in ?? ()
#2 0x10605564 in ?? ()
#3 0x0a854200 in ?? ()
I would provide more info but I get this message in gdb:
Code: Select all
warning: the debug information found in "/media/editing/Steam/SteamApps/common/Wargame European Escalation/Wargame.dbg" does not match "/media/editing/Steam/SteamApps/common/Wargame European Escalation/Wargame" (CRC mismatch).
Re: Linux beta bug reports
Could you upload the core file ? I did not manage to reproduce your crashes here.
Re: Linux beta bug reports
Ok, I got an explanation for your crashes.
As you have some persistence for units between mission, we use some hidden decks to store this information. The crashs are due to decks generated by the previous linux version which used bugged deck loading/saving code. This means you have some corrupted decks in your PROFILE_LOCAL_PART.wargame file. However if you delete this file, you will end up deleting all your decks, so a better solution would be to replay (and win) the campaign mission from the first (for each operation independantly).
Could you confirm that wining the first mission fixes the second mission launch ?
Thanks.
As you have some persistence for units between mission, we use some hidden decks to store this information. The crashs are due to decks generated by the previous linux version which used bugged deck loading/saving code. This means you have some corrupted decks in your PROFILE_LOCAL_PART.wargame file. However if you delete this file, you will end up deleting all your decks, so a better solution would be to replay (and win) the campaign mission from the first (for each operation independantly).
Could you confirm that wining the first mission fixes the second mission launch ?
Thanks.
Re: Linux beta bug reports
Mawww wrote:Ok, I got an explanation for your crashes.
As you have some persistence for units between mission, we use some hidden decks to store this information. The crashs are due to decks generated by the previous linux version which used bugged deck loading/saving code. This means you have some corrupted decks in your PROFILE_LOCAL_PART.wargame file. However if you delete this file, you will end up deleting all your decks, so a better solution would be to replay (and win) the campaign mission from the first (for each operation independantly).
Could you confirm that wining the first mission fixes the second mission launch ?
Thanks.
I can confirm, that this works for me. I completed mission one and now I can start the second one. THX
Re: Linux beta bug reports
I'm also affected by the problem with loading savegames. I can play from the begining.
Today I catched a weird state. After the crossroads mission I couldn't proceed to the next mission, yet the current one was over (all units visible outro brief already said). After quiting current mission I could manually start third mission from the SOLO menu though.
Today I catched a weird state. After the crossroads mission I couldn't proceed to the next mission, yet the current one was over (all units visible outro brief already said). After quiting current mission I could manually start third mission from the SOLO menu though.
Re: Linux beta bug reports
Hello,
Today new version bring some work on the OpenGL backend. Wargame should work better (i.e. not crash) with open source drivers. Intel HD4000 for example should be supported.
Thanks for testing.
Today new version bring some work on the OpenGL backend. Wargame should work better (i.e. not crash) with open source drivers. Intel HD4000 for example should be supported.
Thanks for testing.
Who is online
Users browsing this forum: No registered users and 3 guests