It works fine for me in Winamp, but I noticed GF makes the CPU spike to 80% and memory usage to jump to 46 MEGABYTES.
After I close G-Force, the CPU drops to 30% and the memory drops to 18 MB. I do not know if this is normal.
markofkane wrote:It works fine for me in Winamp, but I noticed GF makes the CPU spike to 80% and memory usage to jump to 46 MEGABYTES.
After I close G-Force, the CPU drops to 30% and the memory drops to 18 MB. I do not know if this is normal.
the new WC crashed my winamp almost imediately it worked fine in all the other players i have but for some reason GF and WC lock up winamps playlist and cause it to crash upon exiting fullsreen.
its really buggin me as I had no problems right up until I first saw the error 18 .
Hey guys... Yeah, 3.8 no longer tells windows to force it to one CPU, so my theory is that Winamp is sending one more messages in a different thread causing the problems. I'll be looking into this.
Also, 3.8 now uses Direct3D by default, so the memory footprint for that is going to be larger. As for the CPU use, yes, G-Force uses the CPU. To see what mode GF is running in, press SHIFT+i and you can see at the top (OpenGL, Direct3D, or software mode) :^)
juxtiphi wrote:the new beta is still messing up big time the colormaps were flickering like crazy in all the players I tested and its still crashing winamp.
