> Using a sound device and stream_update may be a possibility. However, interrupts may
> be triggered too late. OK, one can use timers. This can become really complex and
> hides the way a device works.
That is exactly how it should have been done, it's the pattern we need for all chips (not just sound chips). Ideally the update would occur automatically when accessed from the memory map or when devcb2 callbacks happen.
> So I don't understand the issue here. Tempest is
> cycle exact now and runs at 400% on four year old hardware.
I suspect JSMAME might have problems as I can only manage 200% on my laptop natively. Even if we say it's fine to ignore JSMAME and force people to upgrade their computers, your pattern can't practically be used for anything more complex than tempest (which is pretty simple in hardware terms). Therefore we need a better pattern to handle this circumstance and we shouldn't have two patterns.
In comparison, I get around 200% for star sweep, which has a main cpu core that we're running around 15 mips and a sound cpu running at 16mhz and a sound chip running at 25mhz & a texture mapping gpu. I would like that to run quicker, but tempest should be able to run at 2000%.
Edited by smf (04/19/14 12:05 AM)
|
Index 
Flat 
Re: Noticed some slow-downs....
Reply
