On 17 March 2014 20:50, Nicolai Hess <nicolaih...@web.de> wrote: > 2014-03-17 18:09 GMT+01:00 Igor Stasenko <siguc...@gmail.com>: > > >> >> >> On 17 March 2014 16:57, Ben Coman <b...@openinworld.com> wrote: >> >>> >>> 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: >>> >>> >> What does it changes? This error is going from OpenGL itself. >> GL_FRAMEBUFFER_UNSUPPORTED is a constant reported by opengl.. >> are you going to introduce separate error-handling method for each and >> every possible error code which opengl produces (includes hundreds of >> extensions and more coming each year) ? >> If yes, then i wish you good luck! :) >> >> The complete error description can be found in corresponding OpenGL >> documentation. As well as recommendations what to do and what not. And i am >> not going to teach how to use OpenGL library. ;) >> >> >> >>> 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>: >>>> >>>> https://ci.inria.fr/pharo-contribution/job/NBOpenGL/ >>>>> >>>>> >>>>> 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. >>> >>> >>> >> >> >> -- >> Best regards, >> Igor Stasenko. >> > > > Ok, looks like it is a driver issue. On another windows machine, creating > the frame buffer object works > (no more GL_FRAMEBUFFER_UNSUPPORTED error). But the rendering looks > strange, this is not how > it is supposed to look, right? > > Screenshot attached: >
not quite, but at least it is functional. Maybe there was changes in code which causing artifacts. -- Best regards, Igor Stasenko.
