As NBOpenBL gets broader use by end-users of applications like Roassal, there is a good chance of a flood of these reports.  Maybe too late to get into Pharo3, but it would good (if possible) for system checking be built in to determine the feature support of a user's graphic card.

Alternatively, such reports might be reduced with better indication its a lack of feature rather than an error.
For example:
    NBGLFrameBuffer(Object)>>unspportedFeature:
looks better than :
    NBGLFrameBuffer(Object)>>error:

cheers -ben


In another thread Ronie Salgado wrote:
Hi Nicolai,

What are your system specs?, specially your graphic card.
Roassal3D requires a graphic card with at least OpenGL 2.0 support. Try updating your graphic drivers

Greetings,
Ronie


This thread Igor Stasenko wrote:



On 17 March 2014 12:13, Nicolai Hess <nicolaih...@web.de> wrote:

2014-03-17 11:49 GMT+01:00 Igor Stasenko <siguc...@gmail.com>:



On 16 March 2014 00:02, Nicolai Hess <nicolaih...@web.de> wrote:
Is there a working version (maybe with examples)
for NBOpenGL on Windows?





--
Best regards,
Igor Stasenko.


Thank you Igor,

now the question is, what to do with this?
It looks like the same version I would get on installing Roassal3D, which doesn't
work (all windows are empty).

Running
GLViewportMorph new openInWorld
or
GLTTRenderingDemo new openInWorld
results in an error
NBGLFrameBuffer(Object)>>error:
'Frame buffer is incomplete: GL_FRAMEBUFFER_UNSUPPORTED'


so your graphics card/driver don't supports requested configuration of framebuffer used in demo.

all you have to do is to implement own, which will work on your machine.
since you got that message, the NBOpenGL works fine.
 

Nicolai






--
Best regards,
Igor Stasenko.

Reply via email to