![]() |
Radeon Shaders Broken. - Printable Version +- Forums (https://www.vdrift.net/Forum) +-- Forum: Community (https://www.vdrift.net/Forum/forumdisplay.php?fid=3) +--- Forum: Bugs (https://www.vdrift.net/Forum/forumdisplay.php?fid=7) +--- Thread: Radeon Shaders Broken. (/showthread.php?tid=1317) Pages:
1
2
|
- joevenzon - 08-04-2010 Dandel Wrote:I did a few more tests... It appears libGLEW v1.5.2 does not properly detect, and that is what causes the framebuffer object to not work Phew, glad that finally got sorted out. Quote:vdrift: include/cartelemetry.h:63: void CARTELEMETRY::Update(double): Assertion `file' failed. I think this is happening because it's trying to write telemetry to a file in whatever folder you're launching the executable from. It shouldn't be doing that (we should write any telemetry to the ~/.vdrift folder, and probably only with a command-line switch to enable telemetry). In the mean time you should be able to get this to work by running the executable from a folder where you have write permissions like /tmp or ~. - joevenzon - 08-08-2010 Should be fixed in R2842. - ilguido - 09-19-2010 Same problem in today svn code and an nvidia geforce g103m, nvidia driver 256.53. GLEW v1.5.1. Code: glewinfo | grep framebuffer Dandel's fix is the only solution that worked for me. - Dandel - 09-30-2010 I actually have a better fix for the overall problem... Integrate the latest release of glew into the source tree... glew v1.5.2 or older has bugs with GL_ARB_framebuffer_object. also ilguido, you can download the latest release of glew instead of applying the patch i stated. http://glew.sourceforge.net/ - joevenzon - 10-04-2010 Dandel Wrote:I actually have a better fix for the overall problem... Integrate the latest release of glew into the source tree... glew v1.5.2 or older has bugs with GL_ARB_framebuffer_object. That's not a bad idea. I'll look into it. |