hello all
after not touching a working gem-compile for a few weeks now, i tried Gem again for a course in my study. but it seems. it doesn't work correctly anymore. whenever i have a patch open with a [pix_texture] in the render-chain and i try then to create the the gem-window ('create'->[gemwin]), the window border appears, but the window-content is not redrawn (the desktop from behing is still shown) and i see the following message in the pd-window: 'fglrx: Failed to map back buffer!' and i get this message when turning rendering on: 'GL: invalid enumerant'
my version of gem is: GEM: ver: 0.91-cvs GEM: compiled: Nov 30 2006
i am on ubuntu dapper with the fglrx-driver from the ubuntu-repository. it worked in earlier days and i did not recompile gem since then. i tried to recompile a checkout from today, but when gem is loaded during pd-startup, i get:
/usr/local/lib/pd/extra/Gem.pd_linux: /usr/local/lib/pd/extra/Gem.pd_linux: undefined symbol: glUniform2i
(can i avoid this by disabling a certain switch in ./configure?)
all other apps that i have installed and use opengl (armagetron, blender, mplayer -vo gl) work without any problems and are able to show textures. gem is the only app, that doesn't work as expected. but when start X without dri enabled, [pix_texture] works.
any help very appreciated.
roman
___________________________________________________________ Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de
hi
Roman Haefeli wrote:
my version of gem is: GEM: ver: 0.91-cvs GEM: compiled: Nov 30 2006
so you have not changed Gem but you have updated your driver and now it doesn't work any more?
i am on ubuntu dapper with the fglrx-driver from the ubuntu-repository. it worked in earlier days and i did not recompile gem since then. i tried to recompile a checkout from today, but when gem is loaded during pd-startup, i get:
/usr/local/lib/pd/extra/Gem.pd_linux: /usr/local/lib/pd/extra/Gem.pd_linux: undefined symbol: glUniform2i
(can i avoid this by disabling a certain switch in ./configure?)
yes, finally there is! use "./configure --with-glversion=1.5" or - even better - get drivers that provide header-files which match.
all other apps that i have installed and use opengl (armagetron, blender, mplayer -vo gl) work without any problems and are able to show textures. gem is the only app, that doesn't work as expected. but when start X without dri enabled, [pix_texture] works.
does the rest of Gem work or is it just the textures?
in any case, please file a bug-report at http://sf.net/projects/pd-gem
mfa.dr IOhannes
hi IOhannes
thank you for the fast reply. in the meantime i tried the binary from Pd-0.39.2-extended-test7-ubuntu-dapper-i386 and: it worked well.
On Wed, 2007-02-21 at 16:42 +0100, IOhannes m zmoelnig wrote:
hi
Roman Haefeli wrote:
my version of gem is: GEM: ver: 0.91-cvs GEM: compiled: Nov 30 2006
so you have not changed Gem but you have updated your driver and now it doesn't work any more?
exactly, at least iirc, ubuntu's package manager once update some fglrx-packages
i am on ubuntu dapper with the fglrx-driver from the ubuntu-repository. it worked in earlier days and i did not recompile gem since then. i tried to recompile a checkout from today, but when gem is loaded during pd-startup, i get:
/usr/local/lib/pd/extra/Gem.pd_linux: /usr/local/lib/pd/extra/Gem.pd_linux: undefined symbol: glUniform2i
(can i avoid this by disabling a certain switch in ./configure?)
yes, finally there is! use "./configure --with-glversion=1.5" or - even better - get drivers that provide header-files which match.
hm... how can i make sure, that i have the correct headerfiles? as far as i can tell i didn't install new headerfiles manually. the fact, that the the binary from hcs' pd-extended works, makes me think, that the problem is specific to my system (wrong headers?). what do i need to do in order to make sure, that i the ./configure of gem looks at the correct headers, respectively that i only have the correct headers installed?
all other apps that i have installed and use opengl (armagetron, blender, mplayer -vo gl) work without any problems and are able to show textures. gem is the only app, that doesn't work as expected. but when start X without dri enabled, [pix_texture] works.
does the rest of Gem work or is it just the textures?
with my own compile i didn't try everything, but i tried some of the help-patches and i had troubles with [pix_texture] (resp. any file that contains [pix_texture] like pid_image.pd, pix_video.pd and pix_film.pd and the like) and with [model]. but i only tried an obj-file with around 5000 polygons, that worked on another ubuntu-ppc machine with the gem-install from the distro.
in any case, please file a bug-report at http://sf.net/projects/pd-gem
yes, thank you for the link. i'll do so, if things really look like not me/my system being the problem but gem.
roman
mfa.dr IOhannes
___________________________________________________________ Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de
Roman Haefeli wrote:
hi IOhannes
thank you for the fast reply. in the meantime i tried the binary from Pd-0.39.2-extended-test7-ubuntu-dapper-i386 and: it worked well.
which version of Gem is this?
use "./configure --with-glversion=1.5" or - even better - get drivers that provide header-files which match.
hm... how can i make sure, that i have the correct headerfiles? as far as i can tell i didn't install new headerfiles manually. the fact, that the the binary from hcs' pd-extended works, makes me think, that the problem is specific to my system (wrong headers?). what do i need to do in order to make sure, that i the ./configure of gem looks at the correct headers, respectively that i only have the correct headers installed?
the problem is, that your packageing system installs headers which conform to openGL-2.0 but your driver (this is: the binary library) doesn't. this is a known issue with ati-drivers, but it appeared to happen with mesaGL too in recent versions. i am not sure whether this could be considered really a bug on the driver (header) side, but i tend to think so.
i could of course create tests during the configure process that test for each and every openGL function used by Gem whether it is really supported by the driver. but this is like writing the headers yourself, and i don't see a reason to do that (why are headers provided?)
i don't know of any other way to test these things at (configure or) compile time, therefore i leave it to the user to decide. (it is not that i haven't tried to find a generic way to check; but i haven't found any working solution, so i did the configure-flag; thanks to ico for the trigger)
some my advice is: if you experience problems with unresolved openGL-symbols, try to lower the maximum openGL-version manually via the "--with-glversion" argument until Gem runs.
on the long run Gem will switch to glew (this has been around for years) which might fix these problems.
with my own compile i didn't try everything, but i tried some of the help-patches and i had troubles with [pix_texture] (resp. any file that contains [pix_texture] like pid_image.pd, pix_video.pd and pix_film.pd
so this means, that trivia like the red-square example did work?
mfga.dsr IOhannes
hi IOhannes
On Thu, 2007-02-22 at 11:13 +0100, IOhannes m zmoelnig wrote:
Roman Haefeli wrote:
hi IOhannes
thank you for the fast reply. in the meantime i tried the binary from Pd-0.39.2-extended-test7-ubuntu-dapper-i386 and: it worked well.
which version of Gem is this?
GEM: ver: 0.91-cvs GEM: compiled: Jan 5 2007
use "./configure --with-glversion=1.5" or - even better - get drivers that provide header-files which match.
hm... how can i make sure, that i have the correct headerfiles? as far as i can tell i didn't install new headerfiles manually. the fact, that the the binary from hcs' pd-extended works, makes me think, that the problem is specific to my system (wrong headers?). what do i need to do in order to make sure, that i the ./configure of gem looks at the correct headers, respectively that i only have the correct headers installed?
the problem is, that your packageing system installs headers which conform to openGL-2.0 but your driver (this is: the binary library) doesn't. this is a known issue with ati-drivers, but it appeared to happen with mesaGL too in recent versions. i am not sure whether this could be considered really a bug on the driver (header) side, but i tend to think so.
i could of course create tests during the configure process that test for each and every openGL function used by Gem whether it is really supported by the driver. but this is like writing the headers yourself, and i don't see a reason to do that (why are headers provided?)
i don't know of any other way to test these things at (configure or) compile time, therefore i leave it to the user to decide. (it is not that i haven't tried to find a generic way to check; but i haven't found any working solution, so i did the configure-flag; thanks to ico for the trigger)
some my advice is: if you experience problems with unresolved openGL-symbols, try to lower the maximum openGL-version manually via the "--with-glversion" argument until Gem runs.
ok. i'll try that. many thanks for all that info.
on the long run Gem will switch to glew (this has been around for years) which might fix these problems.
sounds good :-)
with my own compile i didn't try everything, but i tried some of the help-patches and i had troubles with [pix_texture] (resp. any file that contains [pix_texture] like pid_image.pd, pix_video.pd and pix_film.pd
so this means, that trivia like the red-square example did work?
yes, i didn't test too much, but many things worked ok, e.g all geos and 'standard' objects like [translate{XYZ}], [color{RGB}].
i'll try to compile again. many thanks again for all the help.
roman
___________________________________________________________ Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de
On Thu, 2007-02-22 at 11:13 +0100, IOhannes m zmoelnig wrote:
some my advice is: if you experience problems with unresolved openGL-symbols, try to lower the maximum openGL-version manually via the "--with-glversion" argument until Gem runs.
i tried: ./configure --with-glversion=1.5
the good news is: no undefined symbols anymore, when loading gem.
the bad news: the problems i had before recompiling persists. [pix_texture] still doesn't work.
roman
___________________________________________________________ Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de
On 2/22/07, Roman Haefeli reduzierer@yahoo.de wrote:
the bad news: the problems i had before recompiling persists. [pix_texture] still doesn't work.
Send 'mode 0' to pix_texture. Does it work then?
On Thu, 2007-02-22 at 10:25 -0600, chris clepper wrote:
On 2/22/07, Roman Haefeli reduzierer@yahoo.de wrote: the bad news: the problems i had before recompiling persists. [pix_texture] still doesn't work.
Send 'mode 0' to pix_texture. Does it work then?
no. i am aware of this problem. when i use the precompiled binary from Pd-0.39.2-extended-test7-ubuntu-dapper-i386 it works after sending it 'mode 0'. but when i load the Gem.pd_linux i compiled myself from cvs and i load a patch with a [pix_texture] in the render chain and i create the gemwin and then start rendering, i get:
GL: invalid enumerant
and the gem-window is not redrawn (doesn't get black or show any objects)
roman
___________________________________________________________ Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de
-
chris clepper -
IOhannes m zmoelnig -
Roman Haefeli