It's still there. AHH!
And sometimes it can occur less than one song after starting the plugin.
it isn't due to:
- a specific preset
- switching between presets
- rendering mode/resolution/colour depth, etc.
- having any of the overlays on (song title, etc)
- anything running in the background
- driver version
- winamp version
I may have forgotten to list some things I've eliminated, but it basically comes down to three possible conclusions:
- There's something fundamentally wrong in the code for MilkDrop.
- There's something wrong with my hardware (I'm not ruling this out - I do know that my video card has some flaky bits)
- There's something wrong with MilkDrop with my specific hardware.
With this, I am making a request to Mr. Geiss - implement a hyper-extensive debugging mode. Where the program will output (either on-screen, or to a text file) an insane amount of data, including all the current values, the current name of the song and preset, and the procedure within the code that is currently being executed. This way, there will be alot more information in the event of a crash, and we can figure out what is actually going wrong. I could also use this to diagnose my Win2k-won't-run-milk-drop-for-more-than-one-frame bug.