Quote:
I can't get it to work. What kind of graphics card do you have?

I can get the plugin to load. You have to put the supporting dlls in the same directory as winamp. You can also flash the plugin load cache by going to "Plug-ins" when selecting your visualization. Unfortuntely, I get an error message (something to the effect of an illegal operation) when I try to run the plugin. I think its my vid card (geforce 3).

Quote: Original post by llvllatrix

Quote:
I can't get it to work. What kind of graphics card do you have?

I can get the plugin to load. You have to put the supporting dlls in the same directory as winamp. You can also flash the plugin load cache by going to "Plug-ins" when selecting your visualization. Unfortuntely, I get an error message (something to the effect of an illegal operation) when I try to run the plugin. I think its my vid card (geforce 3).

Right. I followed the same procedure and get the errors. I have a Nvidia Geforce 440 MX.

Quote: Original post by tgraupmann
I followed the same procedure and get the errors. I have a Nvidia Geforce 440 MX.

It uses GLSL fragment shaders so I assume it will be FX class and up only.

This is my entry and my first participation. be kind ;)
Timing was short so I've not done something very new, just metaballs. (let's say christmas Metaballs ).

No OpenGL extensions needed.
Tested on AthlonXP1900/Geforce3 Ti 200 and P4 2.4Gz/Intel graphics
Fullscreen work. press ESC for exit.

Plugin log : [WINAMP root Directory]/Plugins/vis_metaballs_bourricot.txt

C code will be available soon. Need a lot of cleaning.

vis_winampcontest_bourricot.zip

Please share your remarks.

Thanks to Nehe and ||v||atrix.

I just looked at some of the nice visualizations and seems like when it's idling (at Winamp startup) it consumes 99% of the CPU. Is this true at other computers?
By idling I mean the contest banner-screen.

BTW: It seems Winamp doesn't recognize EternalPool.dll as visualization, at least, I don't see it in the list..

@Bourricot
Very nice metaballs.

I noticed you have the same problem as I do with using the config box to select a res in windowed mode (fullscreen works fine). I.e. if you select 1024x768, it will use whatever the window was last at (some arbitrary size). It seems that winamp "remembers" the last "dragged by the user" size somehow. Very frustrating to try and get round in code since I don't know what's causing it!

Quote: Original post by Custard Slice

Quote: Original post by tgraupmann
I followed the same procedure and get the errors. I have a Nvidia Geforce 440 MX.

It uses GLSL fragment shaders so I assume it will be FX class and up only.

Yeah, that seems to be the issue you guys are having; it requires a GeforceFX or a Radeon 9500+. I'll see if I can make it die more gracefully (with a more informative error message).

And thanks for the info about the DLLs as well - I wouldn't have caught that, as now that I think about it I probably do have the SDL DLLs in my system directory.

Quote: Original post by Bourricot
This is my entry and my first participation. be kind ;)
Timing was short so I've not done something very new, just metaballs. (let's say christmas Metaballs ).

No OpenGL extensions needed.
Tested on AthlonXP1900/Geforce3 Ti 200 and P4 2.4Gz/Intel graphics
Fullscreen work. press ESC for exit.

Plugin log : [WINAMP root Directory]/Plugins/vis_metaballs_bourricot.txt

C code will be available soon. Need a lot of cleaning.

vis_winampcontest_bourricot.zip

Please share your remarks.

Thanks to Nehe and ||v||atrix.

Very nice; your visualization looks quite professional, like one that would come with Winamp. :)

Quote:
I noticed you have the same problem as I do with using the config box to select a res in windowed mode (fullscreen works fine). I.e. if you select 1024x768, it will use whatever the window was last at (some arbitrary size). It seems that winamp "remembers" the last "dragged by the user" size somehow. Very frustrating to try and get round in code since I don't know what's causing it!

I think thats my fault :) . When the window gets deinitialized it writes the window size/post to the config file. So if you try to configure the dimentions while the plugin is runnig, your settings wont take. If however, you configure while the visualization is not running, and then open the window, your configurations will take. I think we need to destroy and recreate the window in order to get the configuration dialog to work. I'm glad fullscreen is working tho :)

Cheers,
- llvllatrix

Sweet plugin Bourricot :D

This roxorz,
- llvllatrix