tag:blogger.com,1999:blog-4912829343775728623.post640535627898484359..comments2024-03-19T00:12:12.258-07:00Comments on dingoo-scene: An interview with sweetlimreGadgetmiserhttp://www.blogger.com/profile/06733093995583288596noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-4912829343775728623.post-2292754396059354642009-09-23T13:56:06.163-07:002009-09-23T13:56:06.163-07:00@cax: I am not sure. I haven't noticed this my...@cax: I am not sure. I haven't noticed this myself and I've played Vice for sessions of up to 45 minutes. Maybe try a different SD card?<br /><br />@eule: Thanks :) Post some names of some demos that exhibit this behaviour, I'll try them out on my latest build and let you know. Good news on the 68000 core! I will keep an eye on that.Sweetlilmrehttps://www.blogger.com/profile/09298203937508653769noreply@blogger.comtag:blogger.com,1999:blog-4912829343775728623.post-51965341079861847492009-09-23T07:15:03.527-07:002009-09-23T07:15:03.527-07:00Great and informative interview, thx for that! :)
...Great and informative interview, thx for that! :)<br />Some thoughts: <br />In Demos, ReSID is always faster than FastSID for me. Weird, i know. :D<br />True Drive: As a demo lover, i´m very happy that these work now with true drive emulation. But it´s very choppy when the drive starts loading (of course). Is there room for optimizing? And is it slow because of the SD-card or because the CPU is just @ 100%?<br />Slaneesh plans to add some assembler to the 68000 core in FBA320 iirc, could that be usable for Amiga emulation?<br /><br />Enough bugging, thanks again for the good read and the great emulator. :)eulenoreply@blogger.comtag:blogger.com,1999:blog-4912829343775728623.post-60368435798524096092009-09-23T06:08:31.158-07:002009-09-23T06:08:31.158-07:00Well, this guy should know the answer to my questi...Well, this guy should know the answer to my question, which is: almost all ported games and emulators freeze for a moment from time to time, with or without overclocking. I don't believe all these programs are faulty, so can it be the problem is within Dingux itself ? What's that - caching, memory allocation issues ?Anonymousnoreply@blogger.com