I donīt know what you use, and most controllers today are USB, which should guarantee a smooth performance.
However, a bugged driver can cause that.
I had a usb printer at work, that, when plugged in, it would ear about 80% of cpu ,without being used.
I would try to disconnect every single non-necessary thing.
Like, controllers, cameras, pen drives, printers anything that might be started when DOSBOX starts.
My bet would be a faulty controller driver.
I guess itīs worth the shot.
Also, what soundcard do you use?
Try swtiching between ASIO and WDM drivers.
For my SB, it has to be ASIO, otherwise, performance is shit. (but since i use my pc to record, soundcard performance is big to me).
> Ok, so running that I see Hardware Interrupts bumping up past everything and
> sucking down 15-45% of CPU time....sometimes. When it's happening, DOSbox runs
> like doodie. When it doesn't happen, DOSbox runs smooth as a baby's ass (in and
> out of game).
> More often than not, the hardware interrupts are running as soon as I fire up
> DOSbox (like, there's only been a small handful of times when they weren't).
> If I manually set the cycles to max, timesynched to on, and core to auto in the
> GUI after firing up DOSbox then it runs ok, though at that point it's sucking up
> over half of my CPU....no telling if it'll still be "ok" when I try to play a
> more demanding game than Duke Nukum or Raptor... I'd do more performance
> testing, but at this point I'm honestly happy that I can just play Duke Nukum
> reliably for the time being.
> Thinking that it just might still be driver related, I went ahead and
> reinstalling my graphics and sound card drivers with the latest versions.
> Figured it was worth a shot but it didn't change anything. I'm teh stumped.