How to report a technical game issue:

Heres the console messages...

Dump thread list ...
Group main,ac=23,agc=2,pri=10
main,5,alive
Timer-0,5,alive
traceMsgQueueThread,5,alive,daemon
Java Plug-In Pipe Worker Thread (Client-Side),5,alive
AWT-Shutdown,5,alive
AWT-Windows,6,alive,daemon
AWT-EventQueue-0,6,alive
Java Plug-In Heartbeat Thread,5,alive
CacheMemoryCleanUpThread,5,alive,daemon
Windows Tray Icon Thread,5,alive
Browser Side Object Cleanup Thread,5,alive
Group Plugin Thread Group,ac=4,agc=0,pri=10
AWT-EventQueue-1,6,alive
Image Fetcher 0,8,alive,daemon
ConsoleWriterThread,6,alive,daemon
TimerQueue,5,alive,daemon
Group http://www.nodiatis.com/-threadGroup,ac=8,agc=0,pri=4
Applet 1 LiveConnect Worker Thread,4,alive
AWT-EventQueue-2,4,alive
thread applet-Dark.class-1,4,alive
Thread-10,4,alive
Thread-12,4,alive
Thread-11,4,alive
Image Fetcher 0,4,alive,daemon
Image Fetcher 1,3,alive,daemon
Done.
Memory: 47,968K Free: 5,025K (10%) ... completed.

So, I've upgraded to service pack 3 and java update 11 obtained direct from the sun website, and the game is still unplayably laggy with Java 11. With all the new updates, update 7 has also become slightly laggy with 2 versions of the client running.

[Glitchless]

Trippy, do you get the following message(s) prior to timing out: "Attempting to re-establish connectivity to server... Timeout in XX seconds." ?

Hoblit, it sounds like you may not have enough RAM to play multiple clients. Your computer begins to use hard drive space for RAM when you run out and it makes things go extremely slow. We recommend at least 1 gig for running 2 or more clients. 2 gigs is preferable.

I've got 2 gigs of RAM. The issue is that I was able to happily run 2 instances of the client last week, but as of yesterday, while two instances are playable, they are now notably laggy compared to previously.

With one instance of the client my framerate is between 80 and 100. as soon as I load 2, it drops to less than 20, which I suspect is why it appears laggy.

I'll try running them in different instances of firefox, rather than in different tabs to see if that makes a difference.

[Glitchless]

Let me know if using 2 instances fixes your problem. The client has always had trouble determining if it has focus when run in tabbed mode and the two clients compete with each other for processor resources rather than properly throttling.

No, still having the same issues when running two instances of firefox. It looks like it's a display issue rather than a lag issue. I suspect the animations are a little jerky below 30 fps which is what I have seen on other games, however, there is no onticeable lag between the interface and the commands.

When I try to run with update 11 however it gives substantial lag issues.

Hi Jeff, yes I do have those messages.

But sometimes i have the "timeout in 49 seconds message" after i lag for a while, then the message reboots to "timeout in 49 seconds" rather than counting down to 39, 29, seconds, etc.

Its very very bad. I cant even move my gems during combat, the error message about the item speed, (i cant recall the exact phrase) and then sometimes I even have problems loggin on. I get the attempt timed out error message.

I used to be able to play two characters no issue. but now, even with everything shut down, ie. no downground downloading, no other open windows, it keeps lagging. pls let me know how to fix this. thanks!

[Glitchless]

Trippy, If you are seeing those messages then your problems are due to net connection as opposed to issues with the client. Assuming your computer is free of malware your only choice is to get a better ISP.

Hoblit, does the exact same thing happen if you use Internet Explorer? I would also scan your computer using housecall since you've been without SP3 for so long.

When I run 2 instances of Nodiatis, 1 in Explorer and 1 in Firefox, they both run fine.

Thanks for the tipp about Housecall.

[Hopilus]

OS - Windows Vista Home Premium
Browser - 7.0.6000.16764
Client - v1.117
Java Suns Microsystem Inc. 1.6.0_11
RAM - 959 MB
1 client

timed out for no reason

Successful post.
Processing: &a04XPb=26OI&a01XPk=14R6&pAdT=14JH1V&pHP=2D3&pPSb= A03E8&_t=CP0BJ&_p=1LM&
RECEIVED a04XPb:26OI
RECEIVED a01XPk:14R6
RECEIVED pAdT:14JH1V
RECEIVED pHP:2D3
RECEIVED pPSb:A03E8
RECEIVED _t:CP0BJ
RECEIVED _p:1LM
Instant Send: ID=37&UID=1705638985&Action=i&Modifier=m&Amount=1& OriginArrayType=18&OriginArrayIndex=0&ItemType=18& ItemIndex=182&DestArrayType=1&DestArrayIndex=38&La stPacket=13402483
Successful post.
Processing: &s00Hnd=|Gnarled Club|A|0|1A|0|2TO|6|4|1|4|462|0|0|z|0|0|0|0|z&s16I nv=|Thistleberries|4|0|0|0|C5|1405N|0|0|0|0|0|0|z| 1|I|0|5M|z&pAdT=14JGEU&pHP=2D6&pGsD=CP0HU&PEnc=2SD E&_t=CP0HU&_p=1LN&
RECEIVED s00Hnd:|Gnarled Club|A|0|1A|0|2TO|6|4|1|4|462|0|0|z|0|0|0|0|z
RECEIVED s16Inv:|Thistleberries|4|0|0|0|C5|1405N|0|0|0|0|0| 0|z|1|I|0|5M|z
RECEIVED pAdT:14JGEU
RECEIVED pHP:2D6
RECEIVED pGsD:CP0HU
RECEIVED PEnc:2SDE
RECEIVED _t:CP0HU
RECEIVED _p:1LN
Instant Send: ID=37&UID=1705638985&Action=u&LastPacket=13402686
Successful post.
Processing: &a04XPb=26P7&a01XPk=14RD&pAdT=14JBI6&pHP=2E1&pPSb= A03E6&_t=CP266&_p=1LO&
RECEIVED a04XPb:26P7
RECEIVED a01XPk:14RD
RECEIVED pAdT:14JBI6
RECEIVED pHP:2E1
RECEIVED pPSb:A03E6
RECEIVED _t:CP266
RECEIVED _p:1LO
Instant Send: ID=37&UID=1705638985&Action=u&LastPacket=13404358
Successful post.
Processing: &a04XPb=26PS&a01XPk=14RK&pAdT=14J6LE&pHP=2ER&pPSb= A03E4&_t=CP3QE&_p=1LP&
RECEIVED a04XPb:26PS
RECEIVED a01XPk:14RK
RECEIVED pAdT:14J6LE
RECEIVED pHP:2ER
RECEIVED pPSb:A03E4
RECEIVED _t:CP3QE
RECEIVED _p:1LP
Instant Send: ID=37&UID=1705638985&Action=u&LastPacket=13406030
Successful post.
Processing: &a04XPb=26Q6&a01XPk=14RN&pAdT=14J1T3&pHP=2FK&pPSb= A03E3&_t=CP5D7&_p=1LQ&
RECEIVED a04XPb:26Q6
RECEIVED a01XPk:14RN
RECEIVED pAdT:14J1T3
RECEIVED pHP:2FK
RECEIVED pPSb:A03E3
RECEIVED _t:CP5D7
RECEIVED _p:1LQ
Instant Send: ID=37&UID=1705638985&Action=u&LastPacket=13407655
Successful post.
Processing: &a04XPb=26QR&a01XPk=14RU&pAdT=14IT38&pHP=2GE&pPSb= A03E1&_t=CP70G&_p=1LR&
RECEIVED a04XPb:26QR
RECEIVED a01XPk:14RU
RECEIVED pAdT:14IT38
RECEIVED pHP:2GE
RECEIVED pPSb:A03E1
RECEIVED _t:CP70G
RECEIVED _p:1LR
Instant Send: ID=37&UID=1705638985&Action=u&LastPacket=13409296
Successful post.
Processing: &a04XPb=26RG&a01XPk=14S5&pAdT=14IOCD&pHP=2H7&pPSb= A03DV&_t=CP8IP&_p=1LS&
RECEIVED a04XPb:26RG
RECEIVED a01XPk:14S5
RECEIVED pAdT:14IOCD
RECEIVED pHP:2H7
RECEIVED pPSb:A03DV
RECEIVED _t:CP8IP
RECEIVED _p:1LS
Instant Send: ID=37&UID=1705638985&Action=u&LastPacket=13410905
Successful post.
Processing: &a04XPb=26RR&a01XPk=14S8&pAdT=14IJH5&pHP=2I1&pPSb= A03DU&_t=CPA6H&_p=1LT&
RECEIVED a04XPb:26RR
RECEIVED a01XPk:14S8
RECEIVED pAdT:14IJH5
RECEIVED pHP:2I1
RECEIVED pPSb:A03DU
RECEIVED _t:CPA6H
RECEIVED _p:1LT
Instant Send: ID=37&UID=1705638985&Action=u&LastPacket=13412561
Successful post.
Processing: &a04XPb=26SG&a01XPk=14SF&pAdT=14IELQ&pHP=2IR&pPSb= A03DS&_t=CPBQA&_p=1LU&
RECEIVED a04XPb:26SG
RECEIVED a01XPk:14SF
RECEIVED pAdT:14IELQ
RECEIVED pHP:2IR
RECEIVED pPSb:A03DS
RECEIVED _t:CPBQA
RECEIVED _p:1LU
Instant Send: ID=37&UID=1705638985&Action=u&LastPacket=13414218
Successful post.
Processing: &a04XPb=26T5&a01XPk=14SM&pAdT=14I9UV&pHP=2JK&pPSb= A03DQ&_t=CPDCJ&_p=1LV&
RECEIVED a04XPb:26T5
RECEIVED a01XPk:14SM
RECEIVED pAdT:14I9UV
RECEIVED pHP:2JK
RECEIVED pPSb:A03DQ
RECEIVED _t:CPDCJ
RECEIVED _p:1LV
Instant Send: ID=37&UID=1705638985&Action=u&LastPacket=13415827
Successful post.
Processing: &a04XPb=26TF&a01XPk=14SP&pAdT=14I56K&pHP=2KD&pPSb= A03DP&_t=CPEVC&_p=1M0&
RECEIVED a04XPb:26TF
RECEIVED a01XPk:14SP
RECEIVED pAdT:14I56K
RECEIVED pHP:2KD
RECEIVED pPSb:A03DP
RECEIVED _t:CPEVC
RECEIVED _p:1M0
Instant Send: ID=37&UID=1705638985&Action=u&LastPacket=13417452
Successful post.
Processing: &a04XPb=26U4&a01XPk=14T0&pHP=2KU&pPSb=A03DN&_t=CPG IL&_p=1M1&
RECEIVED a04XPb:26U4
RECEIVED a01XPk:14T0
RECEIVED pHP:2KU
RECEIVED pPSb:A03DN
RECEIVED _t:CPGIL
RECEIVED _p:1M1
Instant Send: ID=37&UID=1705638985&Action=u&LastPacket=13419093
Successful post.
Processing: &a04XPb=26UF&a01XPk=14T3&pPSb=A03DM&_t=CPI5T&_p=1M 2&
RECEIVED a04XPb:26UF
RECEIVED a01XPk:14T3
RECEIVED pPSb:A03DM
RECEIVED _t:CPI5T
RECEIVED _p:1M2
Instant Send: ID=37&UID=1705638985&Action=u&LastPacket=13420733
Successful post.
Processing: &H0=ok|DG008|FUM5H|FUEVV|Madonna|2E090&a04XPb=26V4 &a01XPk=14TA&pPSb=A03DK&_t=CPJO7&_p=1M3&
RECEIVED H0k|DG008|FUM5H|FUEVV|Madonna|2E090
RECEIVED a04XPb:26V4
RECEIVED a01XPk:14TA
RECEIVED pPSb:A03DK
RECEIVED _t:CPJO7
RECEIVED _p:1M3
Loaded image: http://www.nodiatis.com/ex/P.png
Instant Send: ID=37&UID=1705638985&Action=u&LastPacket=13422343
Successful post.
Processing: &_c=3&_e=You have timed out.&_p=1M4&
CLEARVARS()!!!!!!!!!!!!!!!!!
RECEIVED _c:3
RECEIVED _e:You have timed out.
RECEIVED _p:1M4
NonSendAction Send: Action=a
Successful post.
Processing: &_v=12T&_a=02/06/09 Further Crafting Improvements|Several changes have been made to crafting to make it easier. For instances you can get all your Resourcefulness skills maxed now via the Collection skill. For more details on the changes view the forums.|01/31/09 220,000 Accounts!|Despite the short amount of time Nodiatis has been live it has managed to acquire over 220,000 sign-ups. Thank you to everyone who has helped spread the word that Nodiatis is not your average browser MMO.&_p=1&
Dump thread list ...
Group main,ac=22,agc=2,pri=10
main,5,alive
Timer-0,5,alive
traceMsgQueueThread,5,alive,daemon
Java Plug-In Pipe Worker Thread (Client-Side),5,alive
AWT-Shutdown,5,alive
AWT-Windows,6,alive,daemon
AWT-EventQueue-0,6,alive
Java Plug-In Heartbeat Thread,5,alive
CacheMemoryCleanUpThread,5,alive,daemon
CacheCleanUpThread,5,alive,daemon
Windows Tray Icon Thread,5,alive
Browser Side Object Cleanup Thread,5,alive
Group Plugin Thread Group,ac=4,agc=0,pri=10
AWT-EventQueue-1,6,alive
Image Fetcher 0,8,alive,daemon
ConsoleWriterThread,6,alive,daemon
TimerQueue,5,alive,daemon
Group http://www.nodiatis.com/-threadGroup,ac=6,agc=0,pri=4
Applet 1 LiveConnect Worker Thread,4,alive
AWT-EventQueue-2,4,alive
thread applet-Dark.class-1,4,alive
Thread-10,4,alive
Thread-12,4,alive
Thread-11,4,alive
Done.
Memory: 112,640K Free: 15,564K (13%) ... completed.

[Glitchless]

This is due to corrupt packets. Nonetheless our communication should be robust enough to handle bad packets without a disconnect, it will be enhanced.

Enhanced robustness ftw

i still get kicked from server wel in fights in bat caves in middle of fights i'm getting trueley agrivated at this i loss alot of time when this happens!

EDIT: I CANT READ

[Abeltronics]

i had these time outs recently even after maxing out the java and everything so i dont know what is going on and i dont know what other things i should do so that this doesnt happen again

p.s. this did not happen before the "Glitchless is making minor repairs but not going to re-load-

[Hopilus]

*GL edit*

[Hopilus]

going to try and close my browsers, and then see if I can relog her. took three tries till it let me log in. kept saying that hopilus was already logged by someone with full priveledge. -.-

[Glitchless]

Hopilus, the corrupted packet issue was identified and fixed.

Abeltronics, whenever you get a timeout countdown message it is due to internet connectivity issues. In rare cases it is due to the server but in those cases everyone will experience it at the same time.

[Astor]

1. OS. Example: Vista 32bit
2. Browser. Firefox, latest version
3. Nodiatis Client Version. 1.124
4. Java Vendor and Version. Sun Microsystems Inc. 1.6.0._09
5. Your amount of RAM. 4gb
6. How many clients are you running at once? 1
7. If you are disconnecting is it due to a lock up or do you get the "Attempting to re-establish connectivity to server... Timeout in 49 seconds..." messages?

Yes I am getting the time out 59 seconds... 49...39...29.

Only posting because this is really the only time I can EVER remember timing out not due to an update or something along those lines...


ANy reason specifically why? I mean my computer isn't a piece of crap, fairly decent .


Was just killing mobs in ancient oak.

LAst few lines of java.

Loaded image: http://www.nodiatis.com/ex/East.png
Loaded image: http://www.nodiatis.com/ex/West.png
Loaded image: http://www.nodiatis.com/ex/faces/Face_261.png
Loaded image: http://www.nodiatis.com/ex/facebgs/facebg_1.jpg
Loaded image: http://www.nodiatis.com/ex/faces/Face_296.png
Loaded image: http://www.nodiatis.com/ex/facebgs/facebg_111.jpg
Loaded image: http://www.nodiatis.com/ex/faces/Face_254.png
Loaded image: http://www.nodiatis.com/ex/ChatDown.jpg
Loaded image: http://www.nodiatis.com/ex/faces/Face_230.png
Loaded image: http://www.nodiatis.com/ex/facebgs/facebg_63.jpg
Loaded image: http://www.nodiatis.com/ex/faces/Face_264.png
Loaded image: http://www.nodiatis.com/ex/facebgs/facebg_22.jpg
Loaded image: http://www.nodiatis.com/ex/faces/Face_51.png
Loaded image: http://www.nodiatis.com/ex/facebgs/facebg_68.jpg
Loaded image: http://www.nodiatis.com/ex/facebgs/facebg_10.jpg
Loaded image: http://www.nodiatis.com/ex/faces/Face_180.png
Loaded image: http://www.nodiatis.com/ex/facebgs/facebg_102.jpg
Loaded image: http://www.nodiatis.com/ex/faces/Face_997.png
Loaded image: http://www.nodiatis.com/ex/faces/Face_6.png
Loaded image: http://www.nodiatis.com/ex/facebgs/facebg_78.jpg

[Glitchless]

Whenever you get any of the 49,39,29, etc time out messages it is an indication that the nature of the problem is strictly connectivity. Unless everyone on the server spams chat after it resolves saying they all lagged at the same time then this means that your ISP is having difficulty communicating with our ISP. 90% of the time it is merely an issue with your individual internet connection, however, sometimes it has to do with an overloaded router or offline router in between your computer and our server - often times not even owned by either of our ISP's. Short of changing ISP's to change your internet's route to our server there is nothing that can be done to prevent these messages from occasionally occuring.

[Astor]

Ok , thanks .