Jump to content
Cyprian_K

Handy emulator - the latest version and source code

Recommended Posts

What is the benefit of removing support for the ROM?

I have a loader which relies on it, for example for block selection. So, an emulator w/o original ROM is useless.

 

 

If you'd like to test it out, PM me.

Share this post


Link to post
Share on other sites

What is the benefit of removing support for the ROM?

I have a loader which relies on it, for example for block selection. So, an emulator w/o original ROM is useless.

Did you try?

Share this post


Link to post
Share on other sites

Rebouncing on Cyprian original post, should https://github.com/b...rc-0.95-patched be considered the latest/most up-to-date windows version?

 

From this thread it seems that is has more features (EEPROM support), more bug fixes and such. So apart from the sounds bug, it looks like the most advanced version, am I correct?

Edited by LordKraken
  • Like 1

Share this post


Link to post
Share on other sites

Rebouncing on Cyprian original post, should https://github.com/b...rc-0.95-patched be considered the latest/most up-to-date windows version?

 

From this thread it seems that is has more features (EEPROM support), more bug fixes and such. So apart from the sounds bug, it looks like the most advanced version, am I correct?

 

 

This is the version we decided to treat that way.

 

We did a pull request last week.

 

So far we have

  • updated the Windows shell to the 2019 version of the compiler
  • we have either fixed a bug or made a patch (depending on perspective) in Mikie.cpp to support 32BPP Android ARGB mode.

 

We're working on load/save state related issues this week.

 

There are at least 2 core bugs that we have logged (in our internal Jira) against it:

  • Gates of Zendocon "Laughing Spider" sound not playing
  • Ms. Pac-Man uneven speed issue (the game runs faster as you clear more dots - not present on Lynx II actual hardware)

Share this post


Link to post
Share on other sites

Ok nice, this is the version I'm planning to use (for EEPROM support actually).

Is there a specific reason to upgrade the toolset to v142 (deprecating vs2015 and 2017)?

 

I'm preparing a short PR to remove most warnings, if not all, from the code, as well as a modest contribution to have much better texture for the console background.

Share this post


Link to post
Share on other sites

Ok nice, this is the version I'm planning to use (for EEPROM support actually).

Is there a specific reason to upgrade the toolset to v142 (deprecating vs2015 and 2017)?

 

Since we had 2013 on the machine, we needed to do *something*. Community Edition 2019 is free, which makes it an easier decision.

 

 

I'm preparing a short PR to remove most warnings, if not all, from the code, as well as a modest contribution to have much better texture for the console background.

 

Might be nice to have them available in debug builds...

 

 

Share this post


Link to post
Share on other sites

Could you give me a concrete example of the bugs/warnings you would like to get rid of?

 

I'm in no way a very technical programmer, so most of the handy code is like voodoo magic to me, but it could be fun to dig into that :)

Share this post


Link to post
Share on other sites

Also on a side note, if this patched version is de facto the latest of latest version of Handy, woulnd't that be easier to have a main repo and working with branches instead of each of us forking the repo?

Share this post


Link to post
Share on other sites

Also on a side note, if this patched version is de facto the latest of latest version of Handy, woulnd't that be easier to have a main repo and working with branches instead of each of us forking the repo?

I definitely agree.

Multiplying Handy's repos could be a bit misleading.

Share this post


Link to post
Share on other sites

I definitely agree.

Multiplying Handy's repos could be a bit misleading.

 

 

The sage patched version is de-facto becoming the master. Perhaps sage should just rename it?

 

We're currently working on making it 64-bit safe (it wasn't) and adding support for Big Endian/Little Endian 32BPP.

  • Like 1

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...