quote:
Originally posted by benoit.hudson:
<STRONG>The usual Unix (and thus OSX) behaviour is to report the % of time that the process is on-CPU. So 100% means it's using an entire core. 200% means it's using two.</STRONG>
Yeah, at its most extreme, the game lags at about 100%, with both cores reporting about 30-50% down time. As far as the game's workload goes, from ~50-52% on the menu, the game hits 70-90% during play with spikes up to 101% or so (OS X reports 4 threads associated with DF, so that's probably what puts it over the edge, but only one of them is the workhorse -- it's being balanced across both cores, but is not seeing much parallel action). When paused it still rests at 60-70%. I'm not sure if it's code running slowly, or something wrong with the way it's yielding time when idle, or both.
Incidentally, I don't know if this is "as intended" at the moment or not, but I don't see any difference in the game's speed when I change the init setting on FPS and G_FPS from 1 to 10 to 15 to 100. I thought maybe 1 FPS was below the minimum and it was just doing a default, but just eyeballing it, I'm pretty sure even at 15 it's going faster than how I've set it. It's very hard to tell for sure though, since I know the FPS indicator doesn't work on the port.
But I don't want to sound complain-y, just trying to help! Whatever speed or workload issues there might be, at the end of the day, the game runs much, much smoother and faster than it did under emulated Windows for me. Thanks a ton for this.