Tales of Tamar

hello i am new (yes) but i found a few crashes in tOT ;(

i finally got regged today and sent my first turn, i love the game allready but there is some bugs and they are annoying!!!.

1. If u go to storage (ftp) it wont update or check on server for latest upd.

2. if u exit this screen then, then the gaME crAsh and amiga reboots.

3.Online games , same as ABOVE . crash when u exit the screen (because cant find online activity)

4. CHAT roOM , same here. game collapse after u quit.

are theese supposed to work ? , or are they still very beta? ...and are the crashes normal?

i use latest upd , and my setup is an a1260/66/240ppc with mediator and vodoo3. , with sb128 soundcard.

my inet settings are correct as UPLOAD works fine etc.

let me know guys....

thanx

Dear Sire Tamarian,

there must be something wrong with your inet-configuration. Tell me please which TCP/IP-stack do you use. If it is Genesis then you
_MUST_ change the interface name in the genesis scripts in ToT:rexx/ to your name.

If not, try you use the needed scripts for your personal stack in ToT:rexx/ with a cli and tell me which one dont work.

Wolfen
Eternity

both me and haymigga have the same probs here , we use miamiDX .

and we are both on broadband ad always online.

another problem found today, i got the email ... loaded up saw the story picture and game crashed.

started it a second time....same happend again.

started it a third time....same happend again.

4th time it worked... weird...

haymigga reported this aswell ....

beyond the bugs i LOVE this game allready, but if someone kill me early...aAAAAAARAGH

slowly please...

i am pretty sure that BardsTale dont crash. I think you hit the 'exit'-Button and ToT quits. If not, please send me debug report and the whole map and data directory next time.

I use also MiamiDx and have no problems at all with the internet routines. Do you check the scripts ?

Wolfen
game master

Greetings Tamarian,

are you sure that the bards tale screen crashed?

Or did you press a button and ToT simply quits and you are back on your WB?

Because if you press the wrong button there (read the screeninfo which one is right) then ToT quits.

Bye,
Tim

ermm how do i send u the log then wofl? u must explain more closer, i am new here .)

anyway yes it did escape 4 times in a row to wb..., and haymigga 5 times , maybe we pressed exit i dunnno but i did exactly the same thing the last time also ,
btw its ok now when i start it .

but ok i also got a defiant error (PPC) due to one of theese weird bards tale quits .

i will let u know how it goes tomorrow, might be we was abit to agressive

but haymigga is in denmark and i in norway , how on earth can it be a coincidence that we got the same problem ? at the very same time? (we play together u see , try to learn each other now at the beginning , to keep us motivated enough against you guys who have played this for ages

explain in depth on how to verify my miamidx cinnection (and haymigga's) and how to call up debugger.

thanx.

cheers

Tamarian,

The FTP part of the game doesn't work so well in the Amiga version (not sure about the Windows version) but it's no bother because you can ge the updates from the forum anyway.

As for the chatroom, this also crashes and as above it's not a problem because you can use IRC to visit the room (use the details I gave you in "questions".

As for other crash problems, there is a solution. I assume that you've got ToT installed on some kind of Games partition?? What you need to do is up the buffers on that partition to around 600-700. This will vastly improve the stability of the ToT client - it worked for me! *

*Credit to Bifford for originally finding this stability fix.

Lord Matador

Oh, as for the MiamiDX connection - forget about it. You're much better off selecting "AlwaysOn" from the preferences and then making sure Miami is connected and online before you start ToT. This is the way I now run the game.

Even now I still get the occasional crash from ToT but since I upped the buffers on my Games partition these crashes are fairly infrequent and the game is certainly very playable now whereas it wasn't before. Regarding the Bards Tale I think Lucksi is correct - it IS easy to accidentally quit from there I've done it myself.

Lord Matador

Hmmmm. Dont bother with the HD Buffer increase. It *seemed* to work for me but since I've been experimenting with it I've got problems of my own - and increasing the partition buffers isn't solving it.

I don't THINK it's an ElboxP96 problem because I had this problem before I upgraded my Amiga from ZorroII - and back then I used CyberGraphx4.0

It would be interesting to see if ToT is more willing to start in AGA instead, so if I dont have any further luck I'll connect my MultiSync and try that a bit later. Other than that I'm wondering if something is having a stack problem. I increased the tot executable stack to no effect, so I've put that back down to normal now... but hmmmmm. I wonder if Im back to a ramlib problem.

I have also tried disabling ALL programs in my WBStartup, turning off the PPC, removing BPPC fix, and I've tried manually putting the WB into the screen mode ToT tries to use BEFORE starting ToT. I think I'll try the AGA option next actually - see if I can get it working that way. If not Im stuck. Wolfen - suggestions?

Whatever it is it seems to effect some of us and not others - Id love to know what it is.

Lord Matador.

<font size=-1>[ This Message was edited by: Matador on 2003-06-14 13:17 ]</font>

Ok, on the 2nd turn I get a smiliar problem. The problem is not that it crashes, the problem is that after the two pages you can read, the only buttons that APPEAR usable is the "previous page" and the "exit", all the rest are X's, so after reading the docks, the far right button next to "exit" was the right one. Then it worked smoothly

The X's that appear on the second page are also the right buttons to press to return to the game (residence) screen.

Yes, I know it's not obvious and I remember my own experience going through exactly what you are going through when I started.