tag:blogger.com,1999:blog-68252810114948352952011-07-07T18:00:37.942-07:00Mistress Saekohttp://www.blogger.com/profile/11127278314231052342noreply@blogger.comBlogger41100tag:blogger.com,1999:blog-6825281011494835295.post-33018805133871019712010-09-01T19:44:00.000-07:002010-09-01T19:44:23.027-07:00Sorry for not posting for a while, but "Real Life" has popped up. :p <br /><br />As for what I said about Direct X? Yeah... you can forget that. I may wind up using Direct X after all. &gt;.&gt;<br /><br />It all boils down to this: After some research, it appears SDL doesn't want to play nice with the WinAPI (at least not without some hackish workarounds). So, I decided to go with Direct X after all.<br /><br />I decided to change build my build environment too, going from MinGW/Dev-Cpp to Visual Studio 2005. Oh, don't get me wrong; I won't be doing it in .NET, it'll still be C/WinAPI. I just like VS better than Dev-Cpp.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6825281011494835295-3301880513387101971?l=sx68kdev.blogspot.com' alt='' /></div>Mistress Saekohttp://www.blogger.com/profile/11127278314231052342noreply@blogger.com1tag:blogger.com,1999:blog-6825281011494835295.post-42656387112800262802010-07-19T16:26:00.000-07:002010-07-19T16:26:57.720-07:00Progress is slow going right now. Even with Keropi's source, I'm still learning the ins and outs of C/WinAPI programming and programming in general. I know for sure it'll use SDL (for portability reasons) for audio, video, and controllers.For all I care, Direct X/XNA/etc. can go screw itself.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6825281011494835295-4265638711280026280?l=sx68kdev.blogspot.com' alt='' /></div>Mistress Saekohttp://www.blogger.com/profile/11127278314231052342noreply@blogger.com0tag:blogger.com,1999:blog-6825281011494835295.post-29088359889242080132010-05-27T21:03:00.000-07:002010-05-27T21:09:16.726-07:00<span style="font-family: arial;">Okay, after doing some searching, I don't have to code it from scratch. :D<br />I found the source code to Keropi, another X68000 emulator. Working off of it, sx68k<br />development moves ahead.<br /></span><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6825281011494835295-2908835988924208013?l=sx68kdev.blogspot.com' alt='' /></div>Mistress Saekohttp://www.blogger.com/profile/11127278314231052342noreply@blogger.com4tag:blogger.com,1999:blog-6825281011494835295.post-4816065605523582272010-05-20T12:37:00.000-07:002010-05-20T12:56:29.783-07:00<span style="font-family: arial; color: rgb(204, 51, 204);">Welcome. This blog is focused on my Sharp X68000 emulator, sx68k. After realizing that most, if not all, X68000 emulators suck, I decided to create my own. The main focus of sx68k is:<br /></span><ul style="color: rgb(204, 51, 204);"><li>Accuracy first and foremost</li><li>Tools to assist the ROM hacking community (of which I am a proud member)</li><li>AVI recording for showing off X68000 games</li><li>Dynamic window for games that use certain resolutions</li></ul><a style="color: rgb(204, 51, 204);" href="http://code.google.com/p/sx68k/">Google code project page</a><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6825281011494835295-481606560552358227?l=sx68kdev.blogspot.com' alt='' /></div>Mistress Saekohttp://www.blogger.com/profile/11127278314231052342noreply@blogger.com0