Skip to content
This repository has been archived by the owner on Mar 29, 2021. It is now read-only.

fMSX core is outdated #18

Open
gingerbeardman opened this issue Oct 8, 2017 · 20 comments
Open

fMSX core is outdated #18

gingerbeardman opened this issue Oct 8, 2017 · 20 comments

Comments

@gingerbeardman
Copy link

gingerbeardman commented Oct 8, 2017

In June 2017 I submitted some changes to the fMSX core that updated it to 4.9 and also add more configuration: RAM, VRAM and more: https://github.com/libretro/fmsx-libretro/pulls?utf8=✓&q=is%3Aclosed%20is%3Apr%20author%3Agingerbeardman%20

Is it possible those could be integrated here by you building using the latest source?

@gingerbeardman gingerbeardman changed the title fMSX outdated? fMSX core is outdated Oct 8, 2017
@pcm720
Copy link
Owner

pcm720 commented Oct 8, 2017

We'll see. First I'll need to resurrect the Linux VM used to cross-compile RetroArch and remember how to use the toolchain.

@gingerbeardman
Copy link
Author

gingerbeardman commented Oct 8, 2017

Thanks man! Whenever you can.

To run every MSX game it's necessary to have the ability to specify RAM & VRAM (the better defaults for MSX1/2/2+ I added go a long way to improving out-of-the-box compatibility).

@summoner40
Copy link

Hi, I would like to know if there is any update of the fmsx 3.9 hmod of the snes mini, I have seen since there is an update of this core, this core has some errors like that some games do not work and the cassette does not go, If you can help me, thank you

@gingerbeardman
Copy link
Author

@summoner40 an update to the latest libretro-fmsx 4.9 source will help with compatibility, mainly due to newer source but also better RAM & VRAM defaults that I created. See my comment above.

However, cassettes are still not working so you'll have to use disk images. If a game still doesn't work, try a disk image that has been proven to work. Disk images vary in quality and one rip of a game might not work whilst others do.

@pcm720
Copy link
Owner

pcm720 commented Oct 16, 2017

Okay, I updated the core.
Tested only with MSX BASIC and Metal Gear 2 *.mx2 image, so please check that everything else is working properly.

@summoner40
Copy link

Many thanks for the work you are doing for these computers that marked an era, the new core updated when it will be ready, I hope they can load the disks, the disk images as it does now I do not remember, with this core I have reached try several games in rom format what happens is that when I play with 2 players only a command and I do not know what can be, I have also passed with the core of spectrum and the amstrad, which I hope can also be updated , caprice fuse and fmsx, thank you very much for everything.

@summoner40
Copy link

the updated fmsx.hmod file where I can download it?

@gingerbeardman
Copy link
Author

gingerbeardman commented Oct 16, 2017

@summoner40
Copy link

thanks you

@summoner40
Copy link

I have the konami soccer and I can not play with two players one of the controls does not recognize me is normal ?, I have entered the retroarch and I have put the command but I do not recognize the user 2, if you can help me

@KMFDManic
Copy link

KMFDManic commented Oct 17, 2017

UPDATE: To keep controller from being lost, Quick Menu, Save Core Override must be used. Once activated, system can be powered off and back on, and Controller still works. Updated Version will be kept in my set along with the ReadMe notation that Save Core Override must be used to keep controller effectual.

I never updated the FMSX Core due to it conveniently losing Controller you choose, upon loading into a game from the main Gui. The version I stuck at was the last version to not have this issue. Every version after that, the moment you leave a game, controller needs selected, again, upon opening another MSX/MSX2 game. It is a minor inconvenience. But, with the version I left it at, the controller you choose always stays active. Other cores have specific issues that make them not worth updating, as well, such as Cave Story, which loses save ability, and MAME 2003, which loses the System 32 Support I was able to get going.

I updated it into my set, although into the dependencies and extras folder of my main release zip since it has proven to be less stable with controller configurations sticking.

@summoner40
Copy link

the dsk format is going to be able to run ?, and if it is possible that I can do to load that format, you said some disk image how can I do that, and finally the system spectrum and amstrad is going to update too, I am very happy that people like you take time to be able to execute these true jewels that have been spectrum, msx and amstrad together friend and comodore, thanks for everything again, and if I can I would be informed of everything that they do, greetings

@summoner40
Copy link

there are some games that need a virtual keyboard to be able to run them, is it implemented?

@ArieKindicator
Copy link

Thanks for updating the fmsx core.
Some games (i.e. Antarctic Adventure) can't be played because to start a game you need to press 1 or 2 on the keyboard and those are not mapped to a gamepad (A of B button for example).
The ZX Spectrum and all other home computers with keyboard have similar issues.
Can you add a remapped configuration file?

Depending on the download source, some .rom games have .mx1 or mx2 extensions. Is it possible to symlink those extensions to the msx binary (/bin/msx) and renaming them is no longer required?

@KMFDManic
Copy link

@ArieKindicator I will check into those specific games and see if there is anything that can be done, as a temporary solution til further keybinds or keyboard ability is implemented as a possible recourse. I already jumped on getting Commodore 64 fixed to work with better keybinds correlating to the virtual keyboard! As far as the extensions for .mx1, .mx2, very easy to add!

I am glad to find others are interested in this excellent Core that I have been playing around with for quite some time! On the NES & SNES Classics, several Cores have nuances to adjust to due to their special environment. NX Engine, with recent Core Updates, moved the save location, which broke save ability on NESC/SNESC. A few other specific Cores, not many, mind you!...have similar conflicts of interest. I will do a little more testing with the latest Update you recommended me to get onto my Github! And, I will think about the best way to proceed as far as fixing the controller issue. It may be a very trivial thing, indeed, and not really require much effort to resolve! I have already jumped onto Commodore 64 with its lack of keybinds, and the great guys who work with that Core, helped implement keybinding!, like so...

NESC/SNESC: Commodore 64 Keybinding

https://www.youtube.com/watch?v=dBn9MkHUA_E

And, of course, I have also done FMSX Videos:)

NESC MSX Test Part 1:

https://www.youtube.com/watch?v=w0F2JlFHn4I

NESC MSX Test Part 2:

https://www.youtube.com/watch?v=nL1ToAUmcSM

Thanks again for your input! I would love to see compatibility progression with more optimal controls that stick:)

@summoner40
Copy link

I am very glad that people like you are working in these colors as msx was my first computer and I have very good memories, I would love to have a virtual keyboard and the casette function, the controls have not yet understood because the games two players the other command does not work, worse good if it is soon solved, and at the same time spectrum and amstrad I would like to update it too, I will be attentive to everything you are putting on the page

@KMFDManic
Copy link

UPDATE: To keep controller from being lost, Quick Menu, Save Core Override must be used. Once activated, system can be powered off and back on, and Controller still works. Updated Version will be kept in my set along with the ReadMe notation that Save Core Override must be used to keep controller effectual.

@KMFDManic
Copy link

@summoner40 MSX is fine, if you read my UPDATE Notes, as far as saving controller. But, as far as CPC Amstrad, unfortunately...There are severe control issues when updating the Core. Dragon's Lair auto attacks and other weird stuff happens! The version I have in my set works very nicely and does not auto attack! I can look into CPC Amstrad a little more to see what is going on with the weird controls!

And, @ArieKindicator, let me know the exact extensions you would like accounted for. I will update them into my Core, as I am sure @pcm720 will do, as well. By the way, nice to see you again @pcm720! Long time no see! Keep in touch!

Lastly, these being Computer Emulators, in essence, will definitely require extra initiative to truly get to the level of emulation we desire! But, we can knock out one thing at a time til we are all happy with the end result! Something similar to what was done with Commodore 64 Keybind video I linked to above, would be perfect!

@ArieKindicator
Copy link

ArieKindicator commented Oct 19, 2017

... let me know the exact extensions you would like accounted for. I will update them into my Core, ...

Some rom download sites use .mx1 and .mx2 as file extension for msx .rom files and fMSX supports these since v3.9 ("New in fMSX 3.9: Added support for .MX1/.MX2 ROM files.")
These extensions are 'unique' and could be assigned to a msx emulator.
However, I'm not sure if this should be added to the updated fmsx core or by adding some sort of file detection routine to hakchi/2 (i don't know how hakchi/2 dectects other rom formats as .nes, .sfrom, etc.) or to RetroArch (see comment of @gingerbeardman below)

@gingerbeardman
Copy link
Author

RetroArch interface has its own list of file extensions aside from those in fMSX

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants