You are not logged in. Please login or register.
Opening the map with Linux reproducible crashes the game with latest wine and nvidia drivers.
Is anyone playing on ATI and having the same problem? How about crossover users?
Is this problem known and worked on?
It is listed as a defect in the comments on winehq.
http://appdb.winehq.org/objectManager.p … ;iId=22164
The game works perfectly otherwise.
(only thing additionally installed was "d3dx9" via winetricks.
Ente, this is not a bug, Perpetuum is only supported for MS windows OS, so you are on your own I guess.
I tried it too on ubuntu 10.10 had the same problems, I have a Nvidia card and also tried it in crossover and same problems arises... well couldn't be bothered I gave up due to multiple accounts running ( and their was an issue with that too) would be a nightmare to fix tbh, might be plausible though.
There is no problem with running several clients at once on linux. I just made two users and made two perpertuum directories.
It runs completely without problems and also there is a linux and mac link on the download page. So it is supported by the devs.
It is only a minor problem as you can work your way around it using the rest of the UI and by clicking only "upload" on scan results and not "upload & show".
So it would be nice if this was fixed or analyzed with some support by the perpetuum devs. It could however be just a problem of wine.
how does it work ? I can open the map no problem. actualy the game has no issues on my Gentoo box.
how can I reproduce it ?
wine 1.3.24
kernel 2.6.38
fglrx 11.6 (Radeon 5830)
What version of Wine and nVidia drivers? The releases are frequent, OP please edit you post with that information.
Updated all involved software. Opening the map still crashes wine.
My specs are as follows:
Opensuse 11.3 64bit / Kernel 2.6.34.10 (Opensuse 11.4 makes no difference...same thing on another machine)
Nvidia GTS 250 / 64bit driver 280.13
wine 1.3.26
The error currently is:
X Error of failed request: GLXBadContextTag
Major opcode of failed request: 135 (GLX)
Minor opcode of failed request: 5 (X_GLXMakeCurrent)
Serial number of failed request: 8179
Current serial of failed request: 8180
The error displayed with wine 1.3.17 before they changed lots of d3d stuff was:
XIO: fatal IO error 11 (Resource temporarily unavailable) on X
server ":0.0"
after 7823 requests (7823 known processed) with 0 events
remaining.
Sometimes the map opens and works. If i open and close it three times it is most likely that wine crashes.
Therefore i'm not sure if it is a problem of wine or can be resolved by the perpetuum team.
It must be a problem with wine, linux or drivers in general but as it works in windows I guess they don't have the time or resources to look into. This I am sure it's wine's fault and you should report the bug to wine.
It must be a problem with wine, linux or drivers in general but as it works in windows I guess they don't have the time or resources to look into. This I am sure it's wine's fault and you should report the bug to wine.
Unfortunately this is only one side of the medal...
It is unclear how severe the bug in wine is and if it is fixable in a timely manner. It could also be that a lot of the framework is missing at what contributes to the bug and that it will take a long time to fix. Also fixing this one bug does not prevent new bugs to appear when new patches and features come out for perpetuum.
A similar story happened at that other game and developer (C*P/E*E) about 5-6 years ago. There also opening the map would crash the game on wine. (funny coincidence...)
What C*P did back then was to take the quirks of wine into account and programmed around them, which led to a stable experience for the user.
A developer of perpetuum could most certainly tell very fast why it crashes and if it is possible to do a workaround in perpetuum or supply the wine people with a detailed problem report on what is happening...
Celebro wrote:It must be a problem with wine, linux or drivers in general but as it works in windows I guess they don't have the time or resources to look into. This I am sure it's wine's fault and you should report the bug to wine.
Unfortunately this is only one side of the medal...
It is unclear how severe the bug in wine is and if it is fixable in a timely manner. It could also be that a lot of the framework is missing at what contributes to the bug and that it will take a long time to fix. Also fixing this one bug does not prevent new bugs to appear when new patches and features come out for perpetuum.
A similar story happened at that other game and developer (C*P/E*E) about 5-6 years ago. There also opening the map would crash the game on wine. (funny coincidence...)
What C*P did back then was to take the quirks of wine into account and programmed around them, which led to a stable experience for the user.
A developer of perpetuum could most certainly tell very fast why it crashes and if it is possible to do a workaround in perpetuum or supply the wine people with a detailed problem report on what is happening...
judging by the error message, it's an nvidia driver problem. ati/amd just deliver the driver, nvidia replaces parts of the X stack with their own. maybe some X related libraries and nvidia drivers don't work well together.
I had 2 ATI cards (firepro, radeon) with different drivers and no map problems.
judging by the error message, it's an nvidia driver problem. ati/amd just deliver the driver, nvidia replaces parts of the X stack with their own. maybe some X related libraries and nvidia drivers don't work well together.
I had 2 ATI cards (firepro, radeon) with different drivers and no map problems.
Thinking the same. And it seems to be related to pixmap but i havnt played around with it yet. If someone wants to go ahead:
Attribute 'PixmapCache' : 1.
'PixmapCache' is a boolean attribute; valid values are: 1 (on/true) and 0 (off/false).
'PixmapCache' can use the following target types: X Screen.
Attribute 'PixmapCacheRoundSizeKB' : 1024.
The valid values for 'PixmapCacheRoundSizeKB' are in the range 4 - 1048576 (inclusive).
'PixmapCacheRoundSizeKB' can use the following target types: X Screen.
Maybe that disabling the cache works.
Hugh Ruka wrote:judging by the error message, it's an nvidia driver problem. ati/amd just deliver the driver, nvidia replaces parts of the X stack with their own. maybe some X related libraries and nvidia drivers don't work well together.
I had 2 ATI cards (firepro, radeon) with different drivers and no map problems.
Thinking the same. And it seems to be related to pixmap but i havnt played around with it yet. If someone wants to go ahead:
Attribute 'PixmapCache' : 1.
'PixmapCache' is a boolean attribute; valid values are: 1 (on/true) and 0 (off/false).
'PixmapCache' can use the following target types: X Screen.Attribute 'PixmapCacheRoundSizeKB' : 1024.
The valid values for 'PixmapCacheRoundSizeKB' are in the range 4 - 1048576 (inclusive).
'PixmapCacheRoundSizeKB' can use the following target types: X Screen.Maybe that disabling the cache works.
Disabling PixmapCache seems to do the trick...have to test it a bit longer but for now it seems to work.
Thank you!
AgY wrote:Hugh Ruka wrote:judging by the error message, it's an nvidia driver problem. ati/amd just deliver the driver, nvidia replaces parts of the X stack with their own. maybe some X related libraries and nvidia drivers don't work well together.
I had 2 ATI cards (firepro, radeon) with different drivers and no map problems.
Thinking the same. And it seems to be related to pixmap but i havnt played around with it yet. If someone wants to go ahead:
Attribute 'PixmapCache' : 1.
'PixmapCache' is a boolean attribute; valid values are: 1 (on/true) and 0 (off/false).
'PixmapCache' can use the following target types: X Screen.Attribute 'PixmapCacheRoundSizeKB' : 1024.
The valid values for 'PixmapCacheRoundSizeKB' are in the range 4 - 1048576 (inclusive).
'PixmapCacheRoundSizeKB' can use the following target types: X Screen.Maybe that disabling the cache works.
Disabling PixmapCache seems to do the trick...have to test it a bit longer but for now it seems to work.
Thank you!
maybe you could post that at wine appdb so that PO has a bit better rating ? 
It seems to be not so easy...works for me on one machine but not the other...have to check further for options and stuff...
I got it to work somehow when i scanned and the used "upload&show result" to get to the map...directly opening the map would crash the client. Then i deactivated all options besides base and result. Restarted the client and the map opens now directly without crash. However, i'm not sure this is reliable.
hi. i am new to perpetuum - but long time, avid *nix user, and admin.
i find the same issue running on older core2duo/geforce 8600gt-m based laptop running ubuntu 10.04, and wine1.3 - canonical nvidia dist, current.
i think ente is onto it... im going to play around with this pixmap cache thing, and see how it goes.(had problems with other games too)
i dont see why this game can't keep it's gold rating - it runs flawlessly under wine... (except for the map thing) in fact i have found it faster and more stable than under windows.
oh and btw celebro... 11.10 and 10.10 sucks my b**** - unreliable, buggy, not to mention too many changes... u r way better off waiting for the next LTS - and oh umm perp wants their game to run under linux so i think they WILL fix it either that or there will be a patch developed by one of us to fix the problem so 
windows fanboy
p.s. to the devs of Perp - THIS GAME IS GORGEOUS thankyou for blessing me with such a well developed, constantly expanding game.
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
Generated in 0.084 seconds (90% PHP - 10% DB) with 20 queries
Copyright © Avatar Creations
