Can't move

[loftar]

That's quite interesting, as it looks to be the exact same failure mode as in this thread, which I ascribed to hardware failure. I guess this makes that explanation less likely, but I'm still having a very hard time imagining what could cause a failure mode like this. Could you please post what GPU you are using, for comparison?

[loftar]

In fact, I noticed that you're running 32-bit Java. 64-bit Java is better in all ways anyway, so if you would please try upgrading to that just to see if that perturbs the bug out of existence.

[Zodiac215]

Amber and Ender were fixed instaling the 64-bit java.
The standart still seems to be broken, or its still running on java 32-bits, how do i know which am i using?

[loftar]

how do i know which am i using?

Not sure how to check that on Windows to be honest, but if you simply uninstall 32-bit Java you will be sure that it's not being used. :)

Seeing as how it was fixed on the custom clients, I think that in fact is a pretty safe guess, though. Quite interesting to know that it helps.

[MagicManICT]

Open task manager. Find the running Java process in the list. You can then open the containing folder and see what executable is being used. I believe if you download Process Explorer* from Microsoft, I believe it will just show the command line in a pop-up tool tip. You can see which version of Java is being used from the folder tree. 32-bit versions are labeled "x86" and 64-bit "x64."

Process Explorer is like Task Manager on steroids. You can do everything in it you can in Task Manager and a lot more. Some of it can disrupt operation of your computer, and is probably why they haven't changed over. (They like to keep it simple for the simple user.)

[Granger]

Open task manager. Find the running Java process in the list. You can then open the containing folder and see what executable is being used. I believe if you download Process Explorer* from Microsoft, I believe it will just show the command line in a pop-up tool tip. You can see which version of Java is being used from the folder tree. 32-bit versions are labeled "x86" and 64-bit "x64."

You can add the column with the path to the executeable in normal task manager - can't provide the exact entry since I don't have an english windows, loosely translated View -> Select Columns -> one of Image path name or command line (or something similar) should do the trick.

[loftar]

Now that you speak of it, though, doesn't the 64-bit Task Manager display something like "*32" in the end of the name column for 32-bit processes?

[MagicManICT]

Actually, you need to click on the column listings and you get a check list of items to display... at least on Win 10. (I think you are correct with Win7 and earlier.)

Not in the name, no, and at least no in Task Manager Processes (again, using Win 10; would have to check on earlier versions). I'm not seeing anywhere in Task Manager that shows this. It is another one of the things you get with Process Explorer you can't get directly in Task Manager.