hi
it seems that i have a problem with openGL. i can watch/listen the flyer until the blue lines appear. then i have a cpu overload and the sound gets more and more staccato-like with every new blue line. when all lines appeared, it's very slow (ta-ta--ta----ta---ta-----ta).
my system: -win 98 SE -P4 1.8GHz -Matrox G550 Millenium -pd-0.37.3 -Gem 0.90
i checked: -newest driver for G550 -hardware acceleration activated
i'm not quite familiar with graphics and stuff, but i think there may be a way to optimize openGL on my PC. the computer this flyer was tested on is slower than mine. so if anybody has some hints to check, or tells me, that my graphiccard sucks for openGL-stuff, it would be great.
roman
Hallo, Roman Haefeli hat gesagt: // Roman Haefeli wrote:
it seems that i have a problem with openGL. i can watch/listen the flyer until the blue lines appear. then i have a cpu overload and the sound gets more and more staccato-like with every new blue line. when all lines appeared, it's very slow (ta-ta--ta----ta---ta-----ta).
I have the same problem. :( Maybe our cards (I use a G450) are just too slow. You can also listen to the song without graphics by just not loading Gem, although that's not a real help...
ciao, -- Frank
I have a similar problem, with a radeon 9000 mobility (not quite newest of new, top of the line stuff, but fine) and 3ghz p4. Looking inside the patch, there seem to be a lot of [text2d] modules, which are the cause of the problem. If you delete (or otherwise stop) the _txtline modules in m/intro, it should work without too many troubles - at least it does for me.
it seems that i have a problem with openGL. i can watch/listen the flyer until the blue lines appear. then i have a cpu overload and the sound gets more and more staccato-like with every new blue line. when all lines appeared, it's very slow (ta-ta--ta----ta---ta-----ta).
I have the same problem. :( Maybe our cards (I use a G450) are just too slow. You can also listen to the song without graphics by just not loading Gem, although that's not a real help...
Quoting Peter Todd peter_todd82@yahoo.co.uk:
Looking inside the patch, there seem to be a lot of [text2d] modules, which are the cause of the problem.
[text2d] can be replaced with [text3d] in every instance I've encountered so far. 2d should be avoided because it uses an extremely slow call (glDrawPixels).
cgc
This message was sent using IMP, the Internet Messaging Program.
Quoting Peter Todd peter_todd82@yahoo.co.uk:
Looking inside the patch, there seem to be a lot of [text2d] modules, which are the cause of the problem.
[text2d] can be replaced with [text3d] in every instance I've encountered so far. 2d should be avoided because it uses an extremely slow call (glDrawPixels).
cgc
This message was sent using IMP, the Internet Messaging Program.
[text2d] can be replaced with [text3d] in every instance I've encountered so far. 2d should be avoided because it uses an extremely slow call (glDrawPixels).
OK, FWIW the patch seems to run smoothly and approximately correctly by modifying the file _txtline.pd to use [text3d] and fontsize 3 rather than 12.
Looking foward to seeing some more contributions to this (not that I made one myself...)
Peter
-
chris clepper -
Frank Barknecht -
Peter Todd -
Roman Haefeli