Ryzom

thexdane, i've been observing ryzom and it's problems for quite some time and i have found out one thing: crashes are in most cases caused by weak/instable systems. ryzom isn't particularly hard on the gfx card, but it puts the whole infrastructure of your system to the max and then it's either bend or break.
you said your cpu "went through the roof" and i highly suspect it's doing that, becuase it's getting lots of hardware interrupts, which basically means that your hardware tells it to stop, coz it isn't done yet. you can test that by downloading procexp from http://www.sysinternals.com and watching the cpu percentage of the hardware interrupts while running into a town(window mode).
other things i'd suggest is: incresing ram to at least 1 gb, bios update, activating compatibility options in the bios, removing any overclocks, clocking the ram down to T2.5 or T3 and/or lowering it's clock to 333 or 266 (those things helped me when i was still running an asrock, a motherboard as crappy as they come)

xenofur wrote:thexdane, i've been observing ryzom and it's problems for quite some time and i have found out one thing: crashes are in most cases caused by weak/instable systems. ryzom isn't particularly hard on the gfx card, but it puts the whole infrastructure of your system to the max and then it's either bend or break.
you said your cpu "went through the roof" and i highly suspect it's doing that, becuase it's getting lots of hardware interrupts, which basically means that your hardware tells it to stop, coz it isn't done yet. you can test that by downloading procexp from http://www.sysinternals.com and watching the cpu percentage of the hardware interrupts while running into a town(window mode).
other things i'd suggest is: incresing ram to at least 1 gb, bios update, activating compatibility options in the bios, removing any overclocks, clocking the ram down to T2.5 or T3 and/or lowering it's clock to 333 or 266 (those things helped me when i was still running an asrock, a motherboard as crappy as they come)

i'd be more than willing to think it's my system if this was more random but it's not, i can reproduce it over and over, which means it's a bug or at least a very easily identifiable one

my friend has an issue where he keeps crashing over and over, thing is he hasn't changed anything on his system and the game keeps becoming more unstable (he's even gone as far as formatting his drive), so right now closed beta is running more stable than him

i've asked for this for many months now and my biggest wish list item, tho floating mouse chat focus would be nice instead of clicking each time (linux ppl will know what i'm talking about) would be nice, is to have a bug fix for the stability issues in the game

also i do realise that the squeaky wheel gets the oil but i'm not the only one that has reported this or similar issue, other suggestion i've put forth is to have a way to turn off the welcome music

tho after running around yrk for a bit last night, it seems to be something around the front gates of the city itself, i could be wrong but just seems more lag in that part of the city than anything and when i did it there was only a couple real ppl there and the normal npc's that are there

to sum up, you choose to completely ignore my explanation and hints for trying to actually resolve your problem on your own and instead prefer to complain about it and claim that it has to be a bug in the game.
i'll repeat myself in a way that is a bit shorter: ryzom crashes on crap systems or unstable systems because it has too high demands on the infrastructure(mainboard, cpu, ram).
the only ways to fix this are:
a) stabilize the system of the user
b) completely rewrite the whole engine of the game client to accomodate for abovementioned systems

i'm pretty sure that a) was already proposed to you, since that is everything the csr team can effectively do to help you. the only other option would be to send it in as a bug, but i'm pretty sure that nevrax is already aware of the existence of crash zones, which leads to b)
b) will probably happen, once more rites are in, the outposts, r² and nevrax actually has the time and leisure to prioritize the fixing of a problem, that a small sub-group of users suffers from and which could easily be fixed by the users themselves, above the bigger group of users with well-maintained or powerful systems who can play the game without problems and demand more content.

btw, you can only call an error reproducable if you can reproduce it without fail on every possible hardware combination, and since it doesn't happen to me or my guild you have only found a hardware incompatibility that is unique to your system and a few others.

another bit of information i forgot: your friends problem could stem from the phenomenon that the strain that ryzom puts on the hardware sometimes breaks cheap or faulty components.

xenofur wrote:to sum up, you choose to completely ignore my explanation and hints for trying to actually resolve your problem on your own and instead prefer to complain about it and claim that it has to be a bug in the game.
i'll repeat myself in a way that is a bit shorter: ryzom crashes on crap systems or unstable systems because it has too high demands on the infrastructure(mainboard, cpu, ram).
the only ways to fix this are:
a) stabilize the system of the user
b) completely rewrite the whole engine of the game client to accomodate for abovementioned systems

i'm pretty sure that a) was already proposed to you, since that is everything the csr team can effectively do to help you. the only other option would be to send it in as a bug, but i'm pretty sure that nevrax is already aware of the existence of crash zones, which leads to b)
b) will probably happen, once more rites are in, the outposts, r² and nevrax actually has the time and leisure to prioritize the fixing of a problem, that a small sub-group of users suffers from and which could easily be fixed by the users themselves, above the bigger group of users with well-maintained or powerful systems who can play the game without problems and demand more content.

btw, you can only call an error reproducable if you can reproduce it without fail on every possible hardware combination, and since it doesn't happen to me or my guild you have only found a hardware incompatibility that is unique to your system and a few others.

another bit of information i forgot: your friends problem could stem from the phenomenon that the strain that ryzom puts on the hardware sometimes breaks cheap or faulty components.

no i didn't ignore what you said, you and everyone else have ignored what i said

as for my friend, explaing how open and closed betas ran better on his system then then do now? last time i checked betas were the unstable branches of development and not the gold release

as for "my" problem i've tracked it down even further, it's something in or around the gates of yrk causing this. walked by there i started to lag, walked away and "my" problem was gone

so yeah that means it's my system

as for slower systems the game box says 1gig min, if they say it's any different, i'd call that a great case of false advertisement

thexdane wrote: so yeah that means it's my system

It may be incompability between some certain hardware/driver configuration(s) and Ryzom. If you do not want to send your system specs to Nevrax, they can't do anything to pinpoint the problem and to fix it (fix might be updating drivers or circumventing the problematic part in game code if this is very common problem)

Right it seems this is an end to "the problem"!!! can we leave it there?

Im now going to restart and hopefully it will finish the way it was originally intended!

thexdane wrote:as for slower systems the game box says 1gig min, if they say it's any different, i'd call that a great case of false advertisement

Hmmm box also said outposts (sorry sorry hehe)

thexdane wrote:last time i checked betas were the unstable branches of development and not the gold release

Minor nitpicking...

Actually beta and unstable are two completely different aspects of software.
Alpha/beta/RC/gold/etc.: Describes where in the "time frame" a release of the code/software is.
Stable/Testing/Unstable (to pick Debians Linux releases). Is exactly that, how crashprone the code is or isn't (no garanties given), and how well tested it is for bugs etc.

You can have unstable alpha software that is rock solid and will run for years, and stable gold software that crashes every second.

as the original poster has given up the thread(sorry alibasil :/ ):

>> no i didn't ignore what you said, you and everyone else have ignored what i said
actually, if you read back, i didn't, i explained why what you think is a bug is in fact not a bug but a phenomenon that is caused by this simple fact:
more performance means less stability and more stability means less performance

>> as for my friend, explaing how open and closed betas ran better on his
>> system then then do now? last time i checked betas were the unstable
>> branches of development and not the gold release
like i already said: "your friends problem could stem from the phenomenon that the strain that ryzom puts on the hardware sometimes breaks cheap or faulty components."
added to that the betas didn't have such high performance requirements, due to a lot of stuff not yet being in the program

>> as for "my" problem i've tracked it down even further, it's something in or
>> around the gates of yrk causing this. walked by there i started to lag,
>> walked away and "my" problem was gone
>> so yeah that means it's my system
means that something in that place is causing some piece of your hardware to do so many errors in it's calculations that it has to stop the whole system very often in order to be able to complete it's task(hardware interrupts i talked about above)

>> as for slower systems the game box says 1gig min, if they say it's any
>> different, i'd call that a great case of false advertisement
1 gig is perfectly fine, if you really have 1 gig of ram then either some other pieces of your system are sub-specs or your hardware settings are not properly done, making your system unstable

i'll give you a real example:
my box was: amd athlon 2000+ xp, 1 gig ram(2x512 3rd infineon), asrock k7s8x
i was running rzm with sound off, so soudn card doesn't matter
the ram was running at 400 mhz, T2.5 and i was able to play doom3 or anything else i wanted to play, but in rzm i crashed when running around in fyros noobland
lowered the ram to 266 mhz, lost 3 frames in doom3 and suddenly was able to play rzm without ever crashing
recently bought a new mainboard, msi k7n2 delta-l rev. 3 and lo and behold, i was able to play ryzom with the ram set at 400 mhz and T2

what i'm saying now is that you can do three things:
a) actually try and follow some of my hints and resolve the problem on your end
b) keep on complaining and give us proof of the fact that you aren't bringing this issue up to have it resolved, but to have something you can complain about
c) try these things, fail and prove that i was talking out of my ***