NXT is better for some things (takes up fewer resources than Java, if you put it on minimum, turn ground blending off, and limit it to 5fps - but somehow
still
manages to cause overheat shutdowns after a few hours, while only using 23-25% of CPU, when programmes that use >85% of CPU can go for day, without
any
overheating problems), like AFK-skilling, and Questing, provided you have a stable connection.
Java is still better, for me, for Minigaming, intensive Skilling, and PvM, there's just no competition between the two, for these things, as the issues with NXT compound eachother:
• Handles disconnects and delays differently, and can show you as logged in for 10-15 minutes past when you actually dc'd, meaning you have to restart the client to get back to doing things.
• It has different timing for whether it registers clicks as on an object, or off it.
• The graphics settings make some things very obscured for some things, when on low settings, that are completely clear on low-setting Java.
• There is an even bigger delay whenever interacting with banks, and before clicks after any teleport will register - and no, this isn't just to do with the loading looking different.. this is when you have a tik counter taking accurate readings.
• It fails to show your accurate position, even without a delay.
• When you have connection problems, it has a far greater tendency to 'make things up' at the client-end (you can perform actions, that you can see having an effect, and can move about, but when you get a connection again, it rapidly rewinds them so you see them in reverse, and then plays about 1/4 of your actions forward again, but just random actions from any point during your dc', so that you end up in an entirely different place, and if PvMing, likely dead).
Some of these things can be familiarised, and coped with, but not when they are all together.. thus Java remains useful for me (despite it somehow using almost 2x as much as 18 Months ago).
19-Feb-2018 19:41:29
