I’ve long thought my Bus error on many of the samples, and my own projects, aparently anything that sets up an off screen buffer, was because my graphics card (IntelGMA 950) sucks, so I simply used my other computer to run such apps. Today I discovered that specifying FrameBufferProperties, even just the default ones, prevents the BusError, and causes it to work as expected.
fbp=FrameBufferProperties(FrameBufferProperties.getDefault()) self.screenToModelBuff=self.win.makeTextureBuffer("screenToModelBuff", 0, 0,self.screenToModelTex,True,fbp)
self.screenToModelBuff=self.win.makeTextureBuffer("screenToModelBuff", 0, 0,self.screenToModelTex,True)
I haven’t tried this fix on the samples that exhibit the same issue.
Firstly, is makeTextureBuffer supposed to request the default FrameBufferProperties if none are passed, or does it use some other settings (and thus the lack of support for those could cause the crash)? Secondly, is there anything in particular that I should test or report about this?
Mac OS X 10.5 - IntelGMA 950
This fix causes my Windows version to fail (with the below errors), so for now I put an os.name dependent switch on it.
This is a virtual box install of windows 7. The hardware acceleration is questionable. (Last time I tried, my project would not run from source, but would run from p3d)