2014-03-31 9:56 GMT+02:00 Nicolai Hess <nicolaihess@web.de>:
Hi Alexandre, Ronie, igor

it isn't solved yet. It works if I make the default extent
larger:

As I described here and on the NBOpenGL Windows thread,
on my machine(s) (both with ATI Graphics) ,the framebuffer objects
(all/one?) does not update its internal buffer sizes after they are initilialized with the
default Morph extent 50@40. Therefore, the rendering happens
only in the upper left corner with extent 50@40. (and some rendering artifacts
in the remaining area. not rendering artifacts actually, looks like texture wrap clamp to edge.
Although I can not find a place where this texture wrap mode is set.)

(on linux, phew, there are so many not working things, I don't know if it
is a driver issue: 
hardcoded libpath, some distribution don't put the libGL.so under /usr/bin
missing type (something with GLXDisplay ?, I don't remember)
errors in some NB calls,
If I fix the first two issues it still does not work, because I don't know how
to handle the NB call errors.)

Maybe it is easier to list OS and Hardware where R3D does work, than
to list the non working one.

What OS and graphic cards do you use and test for NBOpenGL and R3D, mac os only?



Nicolai









2014-03-30 22:07 GMT+02:00 Alexandre Bergel <alexandre.bergel@me.com>:

Is this problem been solved already?

Alexandre


On Mar 17, 2014, at 7:35 PM, Nicolai Hess <nicolaihess@web.de> wrote:

> As described in the "NBOpenGL on Windows" thread, I have a windows
> machine where NBOpenGL can not create frame buffer objects (driver issue maybe).
>
> But on another windows machine, there is no error but strange rendering results.
>
> On that machine, Roassals 3D IDE, still only shows empty windows. And other
> demos shows the same strange rendering (see screenshot, includes GL context driver info).
>
>
> (BTW, there is some class name missmatch in NBGLCurveRenderer in this NBOpenGL version.
> It referse to NBGLFragmentProgram although there is only a NBGLFragmentProgramARB class
> in the system).
>
>
>
>
> 2014-03-17 15:55 GMT+01:00 Ronie Salgado <roniesalg@gmail.com>:
> 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
>
>
> 2014-03-17 11:03 GMT-03:00 Alexandre Bergel <alexandre.bergel@me.com>:
>
> Oh� Have you tried to update Athens and NBOpenGL ? Maybe you are using an old version of them.
> Maybe an old version of OpenGL is installed on your Window?
>
> Ronie, any idea what�s going on?
>
> Alexandre
>
>
> On Mar 17, 2014, at 10:55 AM, Nicolai Hess <nicolaihess@web.de> wrote:
>
> > Thank you Alexandre,
> > this was what I tried under windows, (I wasn't sure if this is still the right way to do it, I
> > read it the Roassal3dTutorial.pdf).
> > But it doesn't work. Either I am getting empty windows or (with an other
> > NBOpenGL version)
> > Frame buffer is incomplete: GL_FRAMEBUFFER_UNSUPPORTED')
> >
> > I tried this once with linux too, and it didn't worked. But I am not sure how long ago :)
> > I'll try it again and report back.
> >
> > (Another note, after downloading the configuration, this:
> > (Smalltalk at: #ConfigurationOfRoassal3d) loadDevelopment
> > takes awfully long on windows (~ 5 min).
> > I am sure it was much faster on linux, any idea how that can be?)
> >
> >
> >
> >
> >
> >
> > 2014-03-17 14:34 GMT+01:00 Alexandre Bergel <alexandre.bergel@me.com>:
> > Hi Nicolai,
> >
> > Roassal3d works well with the last Pharo 3.0.
> > You just need to execute the following incantation:
> >
> > -=-=-=-=-=-=-=-=-=
> > Gofer new smalltalkhubUser: 'ronsaldo' project: 'roassal3d'; package: 'ConfigurationOfRoassal3d'; load. (Smalltalk at: #ConfigurationOfRoassal3d) loadDevelopment
> > -=-=-=-=-=-=-=-=-=
> >
> > This does not work for you?
> > It works well on OSX and on Linux
> >
> > Alexandre
> >
> >
> > On Mar 15, 2014, at 10:52 AM, Nicolai Hess <nicolaihess@web.de> wrote:
> >
> > > Hi,
> > >
> > > what could be the reason, that any Roassal3d example from the
> > > Roassal3DTutorial.pdf only shows white empty windows?
> > >
> > > I loaded ConfigurationOfRoassal3d-RonieSalgado.10 and
> > > (Smalltalk at:
> > > #ConfigurationOfRoassal3d) loadDevelopment
> > >
> > > Any ideas?
> > >
> > >
> > > regards
> > > Nicolai
> > >
> >
> > --
> > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> > Alexandre Bergel  http://www.bergel.eu
> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
> >
> >
> >
> >
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>
>
> <PharoScreenshot.png>

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.





So, I finally solved this issue for me. Instead of making the initial framebuffer large enough, I
changed the code in NBGLFrameBuffer>>extent: 
to reattach all attached Renderbuffers. ( I don't know if this is a driver issue or 
if it is a failure in NBOpenGL)

Again, someone can tell me where (OS, graphic-card) Roassal 3D runs out of the box?

And even now, that I solved this issue and all(many) Roassal examples are working,
The R 3D IDE still only shows a black screen. And I still don't know what this is supposed
to be, any tutorial screenshot or video, showing what R3D IDE is?


Nicolai