Runes of Magic US / AU

Quoted from "Goron69;597334"

In the past year we have gone through everything we can think of, to stop the crashing for all our RoM players in the area (In our circle of friends, there is about 20 players, with 3 of us needing our RoM fix daily and the rest at least a few hours a week) We all have this crashing problem and its getting to be to that point where, enough is enough already and something has to change to try fixing our problem.

Watch how much memory rom uses. It has a bad memory leak. Unless the threshold has changed in the last few months once rom gets to around 1.5G - 1.6G of ram in use it crashes. Close enough, mine just went boom in Dalanis with 1.5G ram in use.

1. Play with your graphics settings to see if you can find a combination of settings that keep the crashes to a minimum

2. Don't teleport around too much. More you teleport around the place the sooner you crashed.

3. Changing between characters using the return to character screen option usually makes the client more prone to crash for me.

4. If you have to teleport around plan where you go. I have always found Silverspring -> Obsidian -> Dalanis or the reverse more crash prone than Silverspring -> Rorazan -> Dalanis. Anything involving Silverspring travel to frontline camp and back again nearly always involves a crash.

No matter how much you upgrade your hardware you are still left with a game that leaks memory and sooner or later goes boom.

You are likely playing on a really high resolution.

Since you have a powerful rig, I wouldn't suggest you sacrifice eye-candy or video quality just to not crash.

The memory leak problem is pretty well known and a work-around taught by my guild leader is to get a free software online called:

Advanced SystemCare which has a tool inside called SmartRam (It clears the memory so RoM stays under that 1.4-1.6gb threshold)

I have since switched to a smaller program called:

FreeRam XP pro (Clears memory every minute - which accomplishes the same thing as advanced system care)

Good luck on finding a solution to crashing!

As already stated, get some kind of freeware memory program that will clean up your ram every so often. As far as the crashing goes, that won't change until Runewaker decided to recode then ENTIRE game from scratch and stop with the spaghetti coding they're known for. If they can't get the simple in game things working, ie questlines, spawns, ect, that should just tell you how well coded the entire client is. Crashing has been around since open beta (I played on and off since the 2nd day of open beta).

This is what I use:
http://www.pcwintech.com/cleanmem

Keep in mind that you have to set it up to clean memory often, to prevent RoM from creating memory leak. You are not cleaning memory just because you need more memory, but just to reorganize ROM in memory, something that programmers were not able to take care off.

switch to a modern and stable Windows that actually supports your modern hardware well.

use Windows7 x64. Seriously. WindowsXP x64 is unstable as hell compared to a Win7. (Hell, even Vista x64 is stable too, but meh ... Vista is the bad in the usual good-bad-good-bad line (XP-Vista-7-8...) in MS OS's.

Not saying it's the one end-all problem solver but i even noticed it on my old rig before i got the new one.

Ultimately there is a limit of how much RAM the client can use regardless of how much your rig has, RoM is not 64bit capable. So unless you have constant crashes after 10 minutes of playing, the most likely cause is simply "the client sucks".

I know pbinfo and a few addons causes pple to crash. I run 3 computers on my place and just 1 does not have any addon except for Xbar and this one never crashed. As for the other 2, well my main computer crashes on RoM at least once a day, but latelly, due siege war lag I've been crashing more often. Yesterday any skill / buff / food / pot I tried to use was taking average 10 seconds to happen on the half end of siege

Quoted from "Murkalael;597367"

Yesterday any skill / buff / food / pot I tried to use was taking average 10 seconds to happen on the half end of siege

I got in SW last half hour and I had exactly the same issue...

I have several observations/suggestions.

1.) The US RoM servers are no longer in the SanFran area. If you want to run ping (latency) tests, point them towards Miami, FL. Chances are that the pathing may be quite different locally/regionally for you.

2.) I agree with YomanROM. Windows XP is so early 2000s. An upgrade to Windows 7 64-bit would help immensely. Not only is it far newer than XP, it's more stable and handles memory partitioning far better than XP could ever dream of doing. You may have problems finding a commercial retail Windows 7 package (full package), now that Windows 8 is out. And, if I remember correctly, there's no normal upgrade path to Windows 7 directly from Windows XP. It is possible to use a Windows 7 upgrade package to perform a full retail installation. Google is your friend here, if you have to go that direction. RoM will work on Windows 8, but many people cannot stand the "Modern" UI that it uses as its default UI.

3.) Even though you have a very high-level system, keep in mind that the RoM client doesn't effectively use multi-core CPUs very well. If you're lucky, it might utilize two of the eight cores in your CPU, and that's due more to the CPU than the game client itself. (I have an earlier Core i7 processor in my toaster and it seems to utilize no more than two cores for the game client.)

In addition, you'll have difficulties in trying to balance stability with maxed video settings. This has been the case for years now. Your video card is far more capable than the client's rendering engine needs, so you can afford to reduce your View Distance and the Texture settings somewhat. Doing so won't affect the video quality very much but it will improve the stability of the client. Also, deselect (uncheck) all of the boxes for Special Effects, other than the one for Hide effects of other players. None of the others are needed, do little to "improve" the video quality, and do contribute to client instability.

The other suggestions regarding improving stability--reducing the number of times you 'port around in the game, installing some sort of RAM "cleaner" applet, things like that--will be helpful. And if you do need to do several 'ports, consider relogging after doing the last one--after you've reached the zone/area you need to be in, or before entering Siege. This includes entering and exiting your house and the Guild Castle. Each time you enter/leave, or where you have a loading screen, a certain amount of RAM is used and, for some reason, the client declines or fails to release some of that memory space back to the memory pool (the so-called "memory leak" issue.) The RAM cleaner applets do help with this, but many times it's better to be safe than sorry. When in doubt, relog to mitigate a crash.

I rarely crash these days. Using Windows 7 64 bit, most settings on low. All that bloom/shadow stuff off. If I ever have to go to the character screen, I'll do so by closing the client, waiting a few seconds, loading it back up, and going from there. Before any instance runs or siege war, I'll do the same. Close client, wait a few seconds, start it back up again.

Its nothing on your end, rather, the client. The more you zone, the more prone you are to crashing. This is because of all the memory the client gathers and does not dump. Each time you zone, you accumulate more unneeded mem. Even if I port a lot, takes quite awhile before I get crashing symptoms. I can port to dalanis, silverspring, AKoR, Obsidian, Heffner, all with no problem. But you gotta be constantly restarting that client.

Another practice I've gotten into is ending all the unneccesary processes in the task manager. Not sure if it helps with rom specifically, but perhaps it helps to have more RAM available for it to use. Who knows.

All I know is restarting the whole client = less crashes

There are other...stuff you can do that also create problems for the client. Errors and such. Removing the possibility of those errors happening in the first place would greatly improve your client's performance. Just gotta know what to do.

1- ditch XP 64bit ASAP. That will cause more problems than anything. Windows 7 64bit is more than suitable

2- Cleanmem, have it run every 2-15 minutes while rom is running. Adjust up or down considering how often you encounter loading screens/go to laggy areas.

3- Lowest settings + medium to high view distance at a decent resolution are ok even without cleanmem

I've never encountered having something else running as being an issue for rom. The cause for problems in rom are either rom or addons. Plus with most modern machines it is extremely unlikely that there is a hardware bottleneck causing a crash for rom.

Quoted from "Ravesden;597389"

All I know is restarting the whole client = less crashes

Because that isn't pretty much what crashing does anyway....besides actually saving your UI settings your not changing much ^.^

Quoted from "CammoXD;597417"

Because that isn't pretty much what crashing does anyway....besides actually saving your UI settings your not changing much ^.^

I'd rather restart client on my own than have rom restart it for me right before i reach the crystal room in siege to get herald, or mid-boss fight

Both have happened to me before x.x