MacOS: How to move? (workaround available)

[MagicManICT]

He's serious.

Apple seriously hates Java. Don't expect to do much with Java on Apple products. This isn't the only Java game I've ran across that has issues with MacOS. If you don't like rebooting a system to play, booting a second OS with MacOS still running (so you don't have to reboot and manage multiple boot partitions) is possible. Just one of several articles I found: http://osxdaily.com/2012/03/27/install- ... irtualbox/

edit: fixed a couple typos

[Hervarth]

For what its worth, this bug started for me with salem when I got a retina display. It is not to do with 16-bit vs 32-bit displays for me - in yosemite there is no way to change this (its always 32bit).

I think its sadly apples fault, as magicmanict says - the version of java installed is very odd and customised, and its hard to disentangle it from the version all other operating systems use (and which you can update to on the java website..)

I can use the default client, but not custom clients... so I have to listen for hearthlings approaching from offscreen instead of seeing a dot :p. I messed around with my java installation to get salem to work a while back - if loftar felt like taking a look at my system to see why the default works for me I'd be up for that, but really its apple and not his fault so I don't blame him for not fixing this.

[Granger]

Yes I'm serious.

Please try bootcamp or parallels for Windows and/or virtual box for Linux.

Sorry for you Mac guys that the Java support is a bad apple, but i can't come up with something better because i don't buy from Cupertino so i have nothing to test on...

[Hervarth]

Yes I'm serious.

Please try bootcamp or parallels for Windows and/or virtual box for Linux.

Sorry for you Mac guys that the Java support is a bad apple

[Zirael]

Debugging shows that problem is not in client - problem in JOGL native bindings or some like that (or client bad uses JOGL).

I try to fix.

[Granger]

Debugging shows that problem is not in client - problem in JOGL native bindings or some like that (or client bad uses JOGL).

I try to fix.

Thanks for your interest in attacking this problem.
Hopefully you'll find a solution, if so please forward it to Loftar.

[loftar]

I had brief access to a Mac yesterday and dumped some debug data. Interestingly enough, it seems that the color values that OpenGL reads back to the client for the click-testing comes from the final, finished frame (or perhaps the previous frame; who knows) rather than the pseudo-color click-test images, for some reason. I do find it very strange that it would be so and can't immediately see why that would happen, but at least it's some kind of entry into the problem.

For the record, the Mac I tried on was using Intel graphics. Is that a common factor for the people having this problem, or does it happen with discrete GPUs as well?

[CSharpRU]

I had brief access to a Mac yesterday and dumped some debug data. Interestingly enough, it seems that the color values that OpenGL reads back to the client for the click-testing comes from the final, finished frame (or perhaps the previous frame; who knows) rather than the pseudo-color click-test images, for some reason. I do find it very strange that it would be so and can't immediately see why that would happen, but at least it's some kind of entry into the problem.

For the record, the Mac I tried on was using Intel graphics. Is that a common factor for the people having this problem, or does it happen with discrete GPUs as well?

I've got same result yesterday (viewtopic.php?f=47&t=39840&start=60#p557950 - my wife account ).

It seems that getpixel function returns wrong data from last layer (or frame as you say), so MapView never comes to execute hit function. If you need more debug data, I'm ready to provide it.

[CSharpRU]

Seems loftar won't work with me to do this problem. So, last news about problem:

• Game runs normally in virtual machine (Linux/Windows).
• Quartz uses own implementation of OpenGL specification that called CGL (GLX in X11 and WGL in Windows accordingly).
• It seems that CGL has problems with OpenGL FBO (or some like that).

[loftar]

It seems that CGL has problems with OpenGL FBO (or some like that).

Do you have any more information about this?