I get this message every now and again as of today. I already re-installed azzy But i wonder if that will solve the problem
Posted 11 October 2015 - 07:36 PM
I get this message every now and again as of today. I already re-installed azzy But i wonder if that will solve the problem
Posted 11 October 2015 - 09:33 PM
help please I'm still getting this error Even after I re installed Azzy it still gives he this error
Posted 11 October 2015 - 10:02 PM
PM'd you. Check your inbox.
Posted 12 October 2015 - 08:08 AM
PM'd you. Check your inbox.
Still not working, when ever my tries to cast certain skills i still get the error
Posted 12 October 2015 - 09:03 AM
Are you using the 1.551 version?? I use to get the same error before i upgrade to such version...
Posted 20 October 2015 - 10:39 AM
issue has been resolved Thanks for the help
Posted 25 October 2015 - 07:10 PM
Now i got the error again, looking at the code, seems to be related with myid..... How did you solved it Kei???
Posted 30 October 2015 - 12:07 PM
This should be fixed in 1.551 - I think that's the issue that led to me hastily releasing 1.551 shortly after 1.55.
Debugging these is absolutely hellish, because you can't get the stack trace. What happens is that somewhere else in the code, a nil value is getting passed around instead of the ID, and you only get told where it finally tries to do something with that value and chokes - but the problem that resulted in nil getting passed as an argument could be half a dozen function calls back. Normally you just look at the stack trace, but the RO client has that functionality disabled.
Edited by DrAzzy, 30 October 2015 - 12:09 PM.
Posted 30 October 2015 - 12:32 PM
I understand, i just changed 1 thing at time, and i found out where the issue was
Posted 30 October 2015 - 12:35 PM
I understand, i just changed 1 thing at time, and i found out where the issue was
Did the issue occur in 1.551?
If so, did you fix it?
If it happened in 1.551, and you fixed it, could you tell me where the problem was so I can make sure it's in the next release?
Posted 30 October 2015 - 01:19 PM
Did the issue occur in 1.551?
If so, did you fix it?
If it happened in 1.551, and you fixed it, could you tell me where the problem was so I can make sure it's in the next release?
Yes 1.551, i did not really fixed it, just changed such option to another parameter.....
1.- At React Tactics, if i select w/ any, i got such error
2.- With my current settings, if i select Circle Route, and enable CastleRoute, i get another kind fo error, this time it says expecting a number and got "?".....
Here you can download my settings using the Export tool with config tool:
Edited by Akilez, 30 October 2015 - 01:23 PM.
0 members, 0 guests, 0 anonymous users