Ryzom

I find that when I make a new landmark on my map (at my position) I am able to enter the information yet as soon as I hit enter I get a runtime error...

It shuts down Ryzom and puts all my user settings back to default. This means I lose all my other landmarks, all the windows go back to the original place and also I have to set up guild tags etc.

Anyone else get this?

Unfortunately this is a known issue; it's being looked into, but until we find a solution many people report that logging out with their compass set on North prevents the problem.

Taking backups of your save folder will stop you having to redo everything by hand, but obviously it's not an ideal solution.

I can pretty much create run time error on demand by going from main screen to F3 ... F4 and then back to F1.

But this is getting much worse as time goes on. Last night's kick required machine reboot. And there's another kick out that occurs when running which throws a blue screen for a sec and auto reboots machine. Happened repeatedly on 3 boxes tho not in last 2 weeks.

Was anything fixed ? Haven't had a runtime error in a week, knock on wood, <knocking on skull>. Not on exiting, not when planting a flag.

Yes I am also getting this Error. Please someone make a patch.

serpnt wrote:Yes I am also getting this Error. Please someone make a patch.

Unfortunately it is a known issue that hits only some players, so it's not as easy as "someone make a patch".
I for one have never ever had an error like this in four+ years of Ryzom, so I wouldn't want "someone" to patch "something" when the issue might just as well be on the users' side. Something could be wrong with your hardware, OS, file system, some software running on your machine but not on mine, drivers, etc.
I understand this is not a very satisfactory answer, but obviously more analysis is needed.

I think better said "some players are not getting this error". By far, the majority are. Some relevant points:

1. The problem "suddenly appeared overnight" for everyone. It does not seem logical that it could be a hardware, OS, file system, software, drivers, etc issue if one day nobody had the problem and then the next, 90+% of the players were experiencing it. Just not logical that hundreds of machines got fudged overnight, coincidentally, immediately after a Ryzom patch.

2. This error was introduced by a patch. That patch needs to be analyzed and see what caused it. Don't know if you were playing then but this was acknowledged by GameForge as a game problem shortly after the patch was issued.

3. I have 3 different machines w/ Ryzom on it and all experience the error. We do not have a person in our Guild who has not experience this error.

4. The frequency and initiators of the problem have varied over time. In the weeks immediately after the game was restarted, the runtime error frequently occurred to many of our guildies even when just when running (usually only on long sessions but one night was happening every 30 minutes or so); this has completely disappeared. One could precipitate the error just by going back and forth between screens 1-4 using the F1-F4 keys; this has since disappeared.

5. Setting the compass to north before quitting game or planting flags seems to work for many people. Can't see how this action within game would have an effect on hardware, OS, file system, software, drivers, etc issues.

6. It's been about 3 - 4 weeks now since I have experienced an error and most of our guildies (the more frequent players) have noted a similar decrease in occurences.

7. I hadn't "planted a flag" in probably 2 years or more but recently started digging Lakes region and have begun doing so throughout Enchanted Isle. haven't had one crash since getting there. Of course I am still doing "the ritual"....make sure it hasn't been long since I TP'd or forced a sync of my log file (/sleep 5) and pointing compass north before doing so. Note that if ya research the topic, I was one of the peeps that always stated that the compass thing never worked for me. Dunno if it is or it isn't but if it means I gotta run around my mek 3 times, do the FBT dance and spank a monkey (Frahar) before planting a flag so as not to crash, I ain't gonna risk it

8. One can crash the server on demand by doing a certain thing which increases a particulat number over 256. Maybe the problem only ocurs if you have more than 64, 128, 256 flags.

Seems to me all evidence points to a game related issue here and, based on player experiences, it looks like the spidey guys are starting to get a handle on it.