21 replies to this topic

[XRay]

HOW HARD is it to fix your stupid game???!!! NO IT'S NOT MY PC

everyone is getting dc's on relog after every stupid TBF and SVS thanks to some bull-_- called Runtime Error. Why can't I relog normally? why do I have to crash every mother-_-ing time after every battlefield that isn't foc for months now?

can some1 please answer this?? what causes the runtime error? why is there a runtime error everytime? and most important of all - why isn't anyone doing anything about this bull-_-??

actually don't bother to answer, I know the answer already.....

Edited by XRay, 21 September 2010 - 10:52 AM.

[MakoXD]

hmm weired , game crashed 3 times at RH at me , no error window , just back to desktop. didnt had that at other raids or while GW

[RealiBrad]

a run time error to me would mean that your local client has a problem. Could be a driver, could be corrupt file, could be hardware. a Run Time Error is a very general error that that alone means nothing to devs.

I dont get that issue, so my guess is that it is not inherent to the coding. Could be a possible conflict between your hardware and how the code is run maybe?

I would try and update your graphics drivers first to see if anything changes...

[Fimbul]

+1

its since they up the svs, where regio was buggy, HS was buggy, parties have been buggy etc.
they fixed most of the issues in svs, but the runtime error is still alive...

and yeah, it happens so almost everyone i know...

[Mortuus]

Yep.

[Nadesh]

a run time error to me would mean that your local client has a problem. Could be a driver, could be corrupt file, could be hardware. a Run Time Error is a very general error that that alone means nothing to devs.

I dont get that issue, so my guess is that it is not inherent to the coding. Could be a possible conflict between your hardware and how the code is run maybe?

I would try and update your graphics drivers first to see if anything changes...

A bad patch would be my best guess. I use to get that error some times (when i went to the character screen and try to log another character) and one day it banish. Now it start happening again, after a specific patch: to me, it mostly happens when o go to the character screen: after svs i can be logged all i want with no problems, but as far as i go to the character screen, it crash giving that error.

[Calista]

Is it true that leaving any battleground (FOC, ION) with 'Public Chat' activated and then rejoining the same battleground makes people DC?? Happened to me once that the whole party crashed,, but didnt test it again.

interesting. really cool. if so, lets do it a lot so Gravity fixes it. the only thing they seem to pay attention to is server (i.e. Cash Shop downtime). Sadly Stealth bug and all the other many many bugs we suffer in game only affect us, not them.

Oh ye,,, discovered another bug today... If you crit 2 or more mobs at once and you check your battle log it will only appear that you've hit 1 mob.

hmmmm. not consistently. ground targetted AoEs typically show correct combat log damage, but many other spells, particularly ones with splash dmg like fire arrow or whatever don't reliably show true damage. honestly the combat log is so unreliable, for this and like 3 other good reasons, it's not worth looking at.

[Calista]

Is it true that leaving any battleground (FOC, ION) with 'Public Chat' activated and then rejoining the same battleground makes people DC?? Happened to me once that the whole party crashed,, but didnt test it again.

interesting. really cool. if so, lets do it a lot so Gravity fixes it. the only thing they seem to pay attention to is server (i.e. Cash Shop downtime). Sadly Stealth bug and all the other many many bugs we suffer in game only affect us, not them.

Oh ye,,, discovered another bug today... If you crit 2 or more mobs at once and you check your battle log it will only appear that you've hit 1 mob.

hmmmm. not consistently. ground targetted AoEs typically show correct combat log damage, but many other spells, particularly ones with splash dmg like fire arrow or whatever don't reliably show true damage. honestly the combat log is so unreliable, for this and like 3 other good reasons, it's not worth looking at.

[EDIT:stupid forum formatting.]

[Loyalty1]

HOW HARD is it to fix your stupid game???!!! NO IT'S NOT MY PC

everyone is getting dc's on relog after every stupid TBF and SVS thanks to some bull-_- called Runtime Error. Why can't I relog normally? why do I have to crash every mother-_-ing time after every battlefield that isn't foc for months now?

can some1 please answer this?? what causes the runtime error? why is there a runtime error everytime? and most important of all - why isn't anyone doing anything about this bull-_-??

actually don't bother to answer, I know the answer already.....

Thank you for taking the time to submit this, but unfortunatly we are unable to reproduce this error.

We thank you very much for the money you spent on the game and if you have more questions, please submit a ticket and we'll do our best to help.

[Calista]

Thank you for taking the time to submit this, but unfortunatly we are unable to reproduce this error.

We thank you very much for the money you spent on the game and if you have more questions, please submit a ticket and we'll do our best to help.

[XtremeStyle]

get that error after every svs

[sonemere]

get that error after every svs

its the damn client/networkin api and its inability to cope with what the game has now. it was never designed to handle all this gay .
swimsuits
robolizard
motorcycles
possession beast
lvl 10 dna calculation.... counting to 10 for the client is what causes it.
hackers that get off when they pay premium.....

[RealiBrad]

Xray, have you tried to manually patch the client to see if maybe it fixes it?

if not, try and make sure you have all your drivers updated. When is the last time you updated your gpu drivers, cpu drivers, bios and all that crap?

I know that for me, i get very few crashes now that i play in windowed mode, and not full screen. Im running Vista 64 Ultimate so i remember when everything was wrong in terms of crashing ever few seconds.

But, if they were to do a ground up rebuild of the code, it would probably solve 80% of the problems that we know of. Maybe some day they will decide that investment to improve quality is a good idea.....

[XRay]

Reinstalled the system 2 weeks ago with newest drives and shizzle, play only in window mode since day 1 of requiem. reinstalled requiem 2 days ago.

it's not my pc. I srsly doubt that my pc causes crashes on relog for 85% of the ppl I know on valdes.

[Loyalty1]

Reinstalled the system 2 weeks ago with newest drives and shizzle, play only in window mode since day 1 of requiem. reinstalled requiem 2 days ago.

it's not my pc. I srsly doubt that my pc causes crashes on relog for 85% of the ppl I know on valdes.

Ever since I came back to the game, I always crash if I try to switch of character after SvS.

[Colly]

Lots of people get it including myself, I have recently done a fresh install of windows with only requiem installed and had that runtime error still. It's been reported to the Devs, Crappy coding and like everything else in this game nothing ever gets fixed which is why i don't play anymore.

Edited by Colly, 21 September 2010 - 01:58 PM.

[Confused]

Dear Customer,

We are deeply sorry for our mistakes and we apologize for your frustration. However, our IT team is not able to reproduce the frustration you are having currently. To help improving our service, you may submit a ticket with a picture of yourself being frustrated so we will understand you.

[XRay]

GUESS what just happened after svs on relog w0985789589439078%&/()&$%&/()/ Å ()ZTFGWQUENVCJ) FGHJ )C(D/GF&/$R%) &/(%R&T/(=)

[Nadesh]

Lol, i got it too, lucky me, it was when the screen was loading to go back to the open map, and still got the points.


The wasnt a file we can save after the crash to send it to the suport in a ticket?

Edited by Nadesh, 24 September 2010 - 09:29 AM.

[Calista]

it is unfortunate that the game doesn't generate a crash dump every time. there certainly would be a lot of learning opportunities for improving the game if it did.

[Lanka]

Doesn't happen after every SvS/TB for me - used to though.. Without being in SvS/TB happens after playing for like 4~6 hours and try relog.

So my un-educated guess would be something to do with memory leak&how game loads animations&other crap for skills (and keep loading them up until something breaks.)


http://forums.playre...posts=8#M215367
its been around forever.. That's oldest thread I could find from old forums, but I remember reporting it myself even before that (probably the link in second post, which is broken unfortunately). So if the issue has been around for over a year doubt they'll be in any hurry to fix it now, or ever.

ed: ah.. little manual link fixing did the trick;
http://forums.playre...w.asp?tid=15149

Hey.. couple more months and the issue has been around for 2 YEARS! Dev incompetance ftw!

Edited by Lanka, 03 October 2010 - 09:16 AM.

[Colly]

I have found a link where the runtime error is guranteed to happen, If i relog to another toon i only get the runtime error crash 50/60% of the time however if i go afk for a long period of time i experience a seperate bug/issue where my toon is glued to the spot i went afk in and if i move around it looks like i am moving but i get rubber-banded back to my original spot. After this issue if i try to relog the Runtime Error happens 100% guaranteed.

Edited by Colly, 10 October 2010 - 01:39 PM.