Still Crashing on Plaza

[neddread]

Well have updated fully, tried all the solutions (terminal and others) but still will not get to the plaza.

4 weeks trying now.

G4 400MGHZ.Could that be the problem?Not powerful enough?

Please post if similar problems you have.

And sorry about the Yoda like last sentence.

[buddha]

Similar problem have I.  Now no fix do I see.  Be patient, we must.  Next thread is what you are seeking...

[blackbow33]

I had the same problem, and I really wish I could tell you how I finally got it working. I must\'ve tried 30 different things including 2 complete installs, running both versions of the updater, etc. I think it finally had something to do with running the updater through the terminal, but I really don\'t know. Basically I just tried everything (and I mean everything) that people posted in the Mac OS Package thread. And considering I had no idea what I was doing, really (I didn\'t even know I had a terminal, for one thing), I can say there may still be hope. I do have a slightly faster comp (G4 iMac, 1ghz, 768 ram), but I don\'t think that\'s necessarily it. Keep trying.

[buddha]

Blackbow, in a show of solidarity, you should refuse to play

Maaaaaaannnnn,  I wanna get back on.  I wish I could be more helpful, but...

[Zerak Toman]

This requires heavy use of Terminal.

Quotes show EXACTLY (including spaces) what to type/look for
1) Open up \"psupdater.cfg\" in TextEdit.  Change \"readxml\" to \"tinyxml\" and save.

2) Run terminal type \"cd \"  Drag and the PlaneShift folder into the terminal screen and press RETURN

3) Type \"./updater.app/Contents/MacOS/updater\" and hit RETURN.  This will launch the official updater.  Run it and wait for it to update.  When it\'s done exit out of it.

4) Type \"./psclient.app/Contents/MacOS/psclient\" and hit RETURN.

5) Enjoy!

Zerak Toman

PS.  You will probably have to repeat steps 2 and 4 (not 3) in order to launch CB from here on out as double-clicking seems to stop working.  Good luck and wait a little because we MacMen are a version behind the server at the moment.

[blackbow33]

Originally posted by buddha
Blackbow, in a show of solidarity, you should refuse to play

That\'s hilarious... If it makes you feel any better, of the 5 or 6 times I\'ve gotten in, it ended up crashing all but one time. Once I ran around for about 45 minutes or so and picked up a couple of quests, etc., but all the other times the app \"unexpectedly quit\" after a few minutes. I know lots of people are having this problem though; I can wait for the bugs to get worked out.

[Zerak Toman]

Hey, Blackbow, do you launch the psclient through the terminal and if so when PS unexpectedly quits, do you get \"Bus Error\" as the last line printed in terminal.

I hope the new version fixes this.

[dfryer]

\"Bus Error\" is usually what it says on any hard crash, so that doesn\'t say much, and the probability of the next version being absolutely free of crashing is next to 0

[Cha0s]

That\'s the weird thing about Buddha\'s and my crash. It yields \"Segmentation fault\" instead of \"Bus error\" and PS provides no error message either.

I personally have never had a crash in-game when I was in game (not counting the alpha testing, of course ) excepting one time where I \"fell off the edge of the world.\"

Anyway, as far as the Plaza crash goes, I\'ve been trying a few things, messing around, etc. and sadly, I haven\'t gotten anywhere. If anyone else crashes with \"Segmentation fault\" please post here or in the other thread so that we can gather some info on this crash. Also post anything you think might have caused it, system specs, etc.

[Zerak Toman]

Originally posted by dfryer
...probability of the next version being absolutely free of crashing is next to 0

And by know means is that what I meant.  I would just like to explore for a little more than two minutes at a time  

Zerak Toman

(Although crash free would be nice.)

[sigma]

sounds to me like a buffer overflow problem... developers should probably look for any new variables they\'ve been working with and how they\'re stored. I\'m sure that they\'re using malloc() and free() and such, so I\'m willing to bet  they\'re storing values too big to fit into malloc\'d variables. If not... malloc is your friend.