cool, thats good to know.
btw just curious which browser do you use?
and does the lwjgl gears applet work for you? http://www.lwjgl.org/applet
cool, thats good to know.
btw just curious which browser do you use?
and does the lwjgl gears applet work for you? http://www.lwjgl.org/applet
Yes, it works. Firefox.
ah thats why it probably works, the issue seems to be with Safari (and maybe Chrome too).
Both minecraft and the gears applet work for me in safari too.
odd, well at least its a big relief for the lwjgl devs :).
maybe the problems on shawnkendall side? broken update?
any other mac users here that can confirm if applets work or are broke?
Not offending me in the slightest. Just letting you know who might have an answer for you. As I understand it, John came from Apple and knows the people over there. As he is responsible for FX, perhaps he knows what they are thinking…
Verified:
LWJGL Gears Applet works in both Firefox and Safari… it loads in Chrome, but does not display (sounds like a Chrome issue then).
Minecraft does the same.
Also… when I run them on Chrome, I can hear them running (both game sound and video-card whine). I just can’t see them.
That is great news (for LWJGL). We are about to run pretty extensive tests (3 diff Mac arch, 3 diff browsers, 2 security settings) with your applets and we’ll post the results.
And can you give me two good applet links you think are working now?
[MOD]
Here is a variation that may be affecting our success. In the Mac Java Preferences, we have
“Run Applets: [X] In their own process” set. This is because on Leopard (not Snow), it is the only way to run Java 6.0. What do you guys that are having success have it set to? “Within the browser process” I bet?
Yep, and it doesn’t work if I switch it.
hmm, strange they would have that option, doesn’t mac support the seperate jvm parameter?
<param name="separate_jvm" value="true" />
ok, seems this page clarifies things a little
so it seems if that option is ticked, Java Plugin2 is used, which doesn’t work because of the offscreen rendering. If that option is off then Java Plugin1 is used and no offscreen rendering takes place, which is why lwjgl applets continue to work.
Now the question is are separate process applets enabled by default or do they have to be enabled by the user?
Chrome doesn’t work with java plugin1, so explains why it uses java plugin2 thus causing lwjgl applets to fail.
Apple do suggest in the above link that they are working to allow awt with opengl to work on plugin2 in the future but I wouldn’t hold my breath and is likely to have a serious performance impact even if it does work.