You are not logged in.

Applications: [GameMaster: OPEN] | [Volunteer Testers: OPEN]


This forum will be permanently shut down on Friday 13.07.2018
Please copy or save all important information from old forum before they will be deactivated
We have moved to new board. https://forum.runesofmagic.gameforge.com/Come join us.

ruisen2000

not a wallet warrior

Posts: 4,052

Location: here

Mood: Blink

  • Send private message

21

Tuesday, December 3rd 2013, 8:12pm

Alright, I'm getting this almost every siege now, and the appearance of this error message always corresponds with the starting of FPS dropping to 0 for a few seconds every 10 seconds. This is starting to get very irritating.

Does IT have any info on this?
Noblewarrior
lv 98/98/89/60 M/W/P/K
Kikosi 98/50/60 Wl/Ch/M
the fail clothie tank~

Inactive

22

Tuesday, December 3rd 2013, 8:57pm

I had this happen 3 times during siege lastnight. Was running along, & would get a huge lag (30k+) that wouldnt go away so i would close the game & get this error & have to restart PC.
Mightymoe 85/85/70 m/wlk/ch
Immasmaku
77/60 r/s (retired)
Evil Empires guild, Osha

23

Tuesday, December 3rd 2013, 9:12pm

Most likely this is being caused by dropped packets to the servers. It would explain the random ping spikes players have been getting the past few months.
--note-- this is usually not caused by other players but the servers themselves (or somewhere along the network path)
A real sysadmin knows how to change the time.
If you make the same mistake while trying to make up for the previous one, you are doing something wrong.

As much as I'd love to say I offer consulting services, the scope of things broken is too large.

24

Wednesday, December 4th 2013, 12:59am

I almost always play a warlock in siege and haven't noticed any additional laggyiness from my skills that is specific to my skills. I haven't seen this error except that one time, also have not faced that guild since then either.

I'm going out on a limb and hope I'm wrong, but maybe since a few people have reported this when fighting shady guilds, could it be some new "trick" conflicting with something and creating the error?

Needundead

Intermediate

Posts: 255

Location: Miami, FL

Occupation: Student

  • Send private message

25

Saturday, December 7th 2013, 2:52am

I just got this same message for the first time ever and we sieged the same guild that Zidlef named here. Nothing wrong with them since they are from the same server as I am but lets just say there were some fishy things going on today during siege.

Similar threads