Re: [osg-users] Memory issues when using uniform shader variables on Intel HD graphics

2012-10-16 Thread Clemens Spencer
Hi, thanks for your response. The memory usage only increases if I add a uniform variable to the stateset and use it in the shader. I also noticed that the memory increases just once per osg::Program, so I can use the same program in multiple statsets, even with different uniform parameters.

Re: [osg-users] Memory issues when using uniform shader variables on Intel HD graphics

2012-10-16 Thread Bradley Baker Searles
Hi Clemens- What version of the OSG are you using? There was a bug fixed in OSG r13015 that would cause out of memory issues for our application. It still seems like the Intel driver uses more memory than the other drivers (AMD/nVidia), but it's workable now.

Re: [osg-users] Memory issues when using uniform shader variables on Intel HD graphics

2012-10-09 Thread Sergey Polischuk
Hi What exactly makes memory usage increase? What if you attach shader without uniform, or without adding uniform to stateset? Try to add #version 110 directive as first line of your shaders, does it make any difference? I think you'd better send bugreport to intel, best if you can reproduce

[osg-users] Memory issues when using uniform shader variables on Intel HD graphics

2012-10-08 Thread Clemens Spencer
Hi, I'm trying to use shaders on an Intel HD 3000 graphics chip (Windows7 x64, latest graphics driver). As soon as I pass a uniform variable to the shader (regardless of the type), the memory of my process increases by about 400MB. Other than that, the shader works fine. The size of the