![]() I don't know if your problem comes from that but avoid using display lists. I had some problems with ATI Radeon Xpress 200 several years ago, it wrongly claimed to support VBOs, it was a real nightmare and I was not alone in this case: ![]() My main desktop computer uses an ATI Radeon 9250 Pro and ATI provides no driver for it under GNU Linux. Several manufacturers encourage planned obsolescence to sell more GPUs, it's a shame, I understand your frustration. ![]() Please go to "Debug Configurations." -> tab "Arguments" -> textfield entitled "VM Arguments" and copy/paste this: This kind of crash occurs with any Java binding for the OpenGL API, even Minecraft is concerned. I agree with Sven, this crash is probably caused by a driver bug but if you follow his advises, we might get some information which would be helpful to find a workaround. I renamed this bug report as it wasn't accurate enough. The log file w/ above DEBUG flags would help alot, I would not disregard the issue, Have you tried to run on of our applets on the test-applet page ? Since the crash happens with your GLCanvas AWT initialization. However, it appears that JOGL's own initialization has passed already, invalid drawable or shared context handle. That could give us a clue maybe why the crash happens, i.e. If anyhow possible, can you pls run what runs (eclipse - if you don't get the test_dbg.batįiles to work - which is sad), which DEBUG properties ? > I was already searching the Internet all day before I post the problem here. > said, I have incompatible hardware even if I use autodetect for installation. I wasn't able to install drivew from AMD. > GPU driver updated today, now I have version from 30 April 2011 (newest). I have tested the scripts, and they run fine > gluegen_652-joal_413-jogl_936-jocl_761/ fromĒ 10:01.įor whatever reason, the JARs were not being picked up. > OpenGL v4.0 (screen from Opengl Extensions Viewer as attachement) > Java 7u17 (latest) tried again both x86 and 圆4. > I have Win 7 Home, 圆4, SP1 (latest updates) ![]() > I tried all things on Wednesday, but I forgot about it, so I am posting it whatever more you think might be important. NV/Windows driver bug and Mesa8 already, just to be able to suite such machines.Īgain, please provide the test.log and test_dbg.log - this is very importantįurther more, please add detailed system information, like we wrote a workaround for a multithreading This is clearly a Windows/AMD driver issue, which we sadly do not reproduce Whatever we do, it shall not result in a crash by simply calling: Searching the net for 'Windows AMD crash atio6axx.dll DrvPresentBuffers' Please also update your Windows driver, i.e. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |