SmokeEffect

[TheLegoBoy]

Nothing to say in particular ... Just play your favorite music and go on journey into those colored fumes.

Just like Geiss-style smoke.

Do not click configure because your WACUP will crash the software!

This plugin made by Matthieu Chopin.

[sgard]

If it helps narrow it down: does WACUP produce a crash dump or an entry in Windows Event Viewer (Application log) when you hit Configure? A lot of old Winamp-era vis plugins call into the config dialog with an HWND/API assumption that doesn't quite match how WACUP hosts them (vs original Winamp), so the crash is often specifically in the config path rather than the visualization itself running fine otherwise. If you can grab the exception address/module from the crash (or just enable "keep debug info" if WACUP has that toggle under preferences) and post it here, that's usually enough for someone who knows the plugin API to tell whether it's a WACUP hosting issue or something in the plugin's own config code that never got updated for newer OS versions.

[dro]

Do not click configure because your WACUP will crash the software!

This isn't a WACUP issue as it also does it under a winamp 2.9x instance.

If it helps narrow it down: does WACUP produce a crash dump or an entry in Windows Event Viewer (Application log) when you hit Configure? A lot of old Winamp-era vis plugins call into the config dialog with an HWND/API assumption that doesn't quite match how WACUP hosts them (vs original Winamp), so the crash is often specifically in the config path rather than the visualization itself running fine otherwise. If you can grab the exception address/module from the crash (or just enable "keep debug info" if WACUP has that toggle under preferences) and post it here, that's usually enough for someone who knows the plugin API to tell whether it's a WACUP hosting issue or something in the plugin's own config code that never got updated for newer OS versions.

Firstly posting crash dmps onto the public part of the forum is a no-no for a number of reasons. Secondly WACUP's vis handling does things that Winamp didn't to try to better accommodate old plug-ins however a lot of them can & will crash as they either expect to be running in a folder that allows them to save their configuration (aka running as admin which doesn't help this plug-in) or were built in a manner that can conflict with DEP/NX-bit handling since the late XP days (this doesn't seem to be the case here but I'm not going to debug it further than a quick check to see why it might fail & the api handling doesn't seem to be it).