![]() ![]() 23:47:22.769 java -: unrecognized selector sent to instance 0x7fd1e3cb0510 The natural replacement for PBuffers are FBOs, so is there any plan to replace the native pbuffer offscreen implementation in JOGL with an equivalent FBO-based counterpart? This is particularly important for me to know, because this issue is kind of a deal breaker in Processing since a large portion of users are on the OSX platform.Īfter installing OSX 10.8, my (OSX 10.7 previously working) program crashes at launch with: Is there any reason for this? Is the onscreen rendering path non-functional at this time, or should I do some other additional initialization steps?Ģ) With PBuffers deprecated already, the situation would probably deteriorate even further in OSX 10.8. ![]() However, JOGL apparently still tries to use offscreen rendering with pbuffers. I have a couple of observations/questions related to this issue:ġ) I tried to enable the onscreen/no pbuffer path by setting my GLCapabilities with setOnscreen(true). I think the reason for this bug is the fact that PBuffers have been deprecated in OSX 10.7 (as indicated in this release notes: ), so they are starting to behave unreliably. I doubt that any users would miss it if Arduino 10.xx ditched the high definition video support in a text-based development environment.I have been chasing a bug that appears to affect only OSX Lion with integrated Radeon video cards (the details are available in this bug entry: ). ![]() I also hope that the Arduino developers team would fix this in future releases. I hope this information may help, and I will try the solution posted in this thread also. I am still on 10.7.5, but this problem is said to get worse on the newer OS's. My search for a solution led me to a utility called gfxCardStatus, which can be used to force the OS to use either the integrated or the discrete GPU, so it can prevent the crashes and save power for me. The problem I have had with it was that the discreet GPU is known to cause system crashes due to heat (Mac has issued an extended recall for those with the worst symptoms, but mine only crashes when running Arduino in warm room). The issue of Arduino 10.8 using my MacBook's discrete GPU (and thus more power, as original posted says) instead of the integrated GPU has plagued me for a few weeks this summer. Opened file for editing rMBP:Arduino.app miha$ vi Contents/istħ8 -file-dialog-packages=trueĨ0 =trueĨ2 =$JVM_RUNTIME/Contents/Home/lib/ext/:$JVM_RUNTIME/Contents/Home/jre/lib/ext/Ĩ4 .=ArduinoĨ9 -splash:$APP_ROOT/Contents/Java/lib/splash.png #Osx gfxcardstatus portableFor iMac this is not issue but for portable (like rMBP) consuming less power is the key. Using my MacBookPro plugged in is not always possible. My opinion is that app needs to be recompiled to use less resources. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |