Recent Posts

Pages: [1] 2 3 4 5 6 ... 10
1
FBN Development / Re: Game Consoles (Gab75 adds and more...)
« Last post by Gab75 on Today at 07:58:58 AM »
Added the support to 5 new NES/FDS titles:
Courier (HB, 2024)
Crater Song v1.03 (HB, 2024)
Mario Bros. (Euro, MC-0 Classic Series)(1993)
Return of Mario Bros.  (FDS, T-Eng 2021)
Squirrel Domino (HB, 2024)
2
FBN Development / Re: dink's FBN Development & Fixes thread
« Last post by dink on Today at 01:31:24 AM »
Hi weirdh,

I think only batsugun's format got changed in hiscore.dat, I mean, we don't really control the format of hiscore.dat - it's maintained by Leezer.
If something got changed, though, it's probably for the better :)

I added the coin fix to donpachi/dodonpachi, but, you really might want to fix your coin button.  I can think of about 200 other games that will cause this problem :)

In my experience, usually wiring isn't the problem when a switch is sticking for longer than it should.
I'd take it out, spray it with wd-40, then compressed air from all angles (to get wd-40 deep into the switch & button, but to also clean out any dirt as well), then wipe it with an alcohol-soaked cloth or papertowel to get any wd-40 off of the outside of the button.  then put it back in
If you have deox-it, spray it with that too, before the wd-40.  but seriously, remove the button&switch before spraying it with anything :)

best regards,
- dink
3
FBN Discussion / Re: Load game from Romdata
« Last post by taoenwen on Today at 12:49:35 AM »
Quote from: xerf84 on May 24, 2024, 10:30:19 PM
1. I change the name of the driver to the clone, it loads fine every time.
2. If the load fails, it no longer allows me to load another *.dat until I close the application and start it again.
3 and 4. Also works with the driver name changed.

Thank you.

Any specifics? Like the dat+ROMs you're having problems with?

I'd like to test it, thanks!
4
FBN Discussion / Re: Load game from Romdata
« Last post by xerf84 on May 24, 2024, 10:30:19 PM »
1. I change the name of the driver to the clone, it loads fine every time.
2. If the load fails, it no longer allows me to load another *.dat until I close the application and start it again.
3 and 4. Also works with the driver name changed.

Thank you.
5
FBN Discussion / Re: Load game from Romdata
« Last post by taoenwen on May 24, 2024, 09:33:46 PM »
Quote from: xerf84 on May 24, 2024, 08:33:12 PM
Very good, I was able to get it to work however I didn't quite understand some things:

1. On some occasions it sends me to the cross hatch test menu and on other occasions it sends me to the game.
2. If the rom loading failed due to some error in the data, I could no longer call the option but instead had to forcefully close the program and start again.
3. I managed to play kof games, but necessarily in DrvName I had to leave mslug instead of kof98, 99, etc.
4. Despite trying to associate the rom with a parent so as not to repeat the unmodified roms, I did not understand how to do it, I had to leave a *.zip with all the roms, the modified ones and those of the unmodified parent game.

1、I'm not sure I understand exactly what you mean by this, can you describe it further?
2、If the game of dat fails, we can choose in the menu to quit this game and then choose another dat file, the borrowed driver is within the list and must be restored.
3、As I said before, borrowing some common compatible driver, as far as ROMs loading order and initialization are consistent, we try to choose the set with the closest ROMs structure as possible, e.g., if we have a kof97-based modification in hand, we can try to use kof97h as the driver.
4、The rules for ROMs in romdata are the same as for any other game.If your game is based on a clone set driver, it will inherit the ROMs from the parent set, and you only need to prepare ROMs that differ from the parent set. If your game is based on a parent set driver, you must set all the ROMs needed to prepare it.
6
FBN Discussion / Re: Load game from Romdata
« Last post by xerf84 on May 24, 2024, 08:33:12 PM »
Very good, I was able to get it to work however I didn't quite understand some things:

1. On some occasions it sends me to the cross hatch test menu and on other occasions it sends me to the game.
2. If the rom loading failed due to some error in the data, I could no longer call the option but instead had to forcefully close the program and start again.
3. I managed to play kof games, but necessarily in DrvName I had to leave mslug instead of kof98, 99, etc.
4. Despite trying to associate the rom with a parent so as not to repeat the unmodified roms, I did not understand how to do it, I had to leave a *.zip with all the roms, the modified ones and those of the unmodified parent game.
7
FBN Development / Re: Game Consoles (Gab75 adds and more...)
« Last post by xerf84 on May 24, 2024, 01:00:24 PM »
Quote from: Gab75 on May 24, 2024, 03:06:13 AM
Thanks for the tip! The related support will be added to the next NES/FDS update! :)

Perfect Gab75, thank you for the support.
8
FBN Discussion / Re: Load game from Romdata
« Last post by xerf84 on May 24, 2024, 12:58:30 PM »
Perfect, I try with a patch of kof99 dreamcast version and svc playstation version.
9
FBN Development / Re: dink's FBN Development & Fixes thread
« Last post by weirdh on May 24, 2024, 10:52:44 AM »
Yup, confirmed. Ah well, more Batsugun to play ;) Thanks for the replies

EDIT: just wondering, will there be many games affected by this hiscore format change? Or isn't that something one could easily determine?

EDIT 2: Okay, so I've been having trouble with my coin button lately (probably wiring), so maybe that's why I'm just now noticing these, but donpachi.zip and ddonpach.zip exhibit the same coin error for me. No idea if they did before though, as I updated FBNeo from source yesterday.
10
FBN Discussion / Re: Load game from Romdata
« Last post by taoenwen on May 24, 2024, 08:51:14 AM »
Quote from: xerf84 on May 23, 2024, 09:24:15 PM
Well, it would be good if he explained what the *.dat syntax is or what data goes there and in what order. I don't think the syntax is the same as the kawaks loader data, but the idea should be similar.

fbneo's romdata allows some romsets that are not on the list, but run with a common driver.

The format of *.dat is as follows:
Code: [Select]
///////////////////////////////////////////////////////////
// ZipName:  Zip names that are not in the game list     //
// DrvName:  Select which driver exists in the game list //
// ExtraRom: NeoGeo specific extra rom                   //
// FullName: Detailed name of the game                   //
///////////////////////////////////////////////////////////

ZipName:  cyborgforce
DrvName:  mslug
ExtraRom:
FullName: "Cyborg Force! (Homebrew)"

// romname romsize crc type
cyborg-p1.bin 0x0100000, 0x89e1c728, 1 | BRF_ESS | BRF_PRG
cyborg-p2.bin 0x0300000, 0xe4a8b27a, 1 | BRF_ESS | BRF_PRG
cyborg-s1.bin 0x0020000, 0x5bd29810, 2 | BRF_GRA
cyborg-c1.bin 0x1000000, 0x77078687, 3 | BRF_GRA
cyborg-c2.bin 0x1000000, 0xa5abdb83, 3 | BRF_GRA
cyborg-m1.bin 0x0010000, 0x06da3cec, 4 | BRF_ESS | BRF_PRG
cyborg-v1.bin 0x0800000, 0xdc50718c, 5 | BRF_SND
cyborg-v2.bin 0x0800000, 0x8135d5a8, 5 | BRF_SND

Cyborg Force! (Homebrew) as an example:

ZipName, the set we want to use, usually *.zip or *.7z.

DrvName, the driver we want to run from, it is recommended to use clone when possible, so that we don't have to prepare some ROMs that are common to the parent set;

FullName, well understood, the name of the game.

romname/romsize/crc/type，It's almost identical to the fbneo source code, and corresponds to the ROMs in our ZipName zip file, just write to *.dat.

The dat file can be saved anywhere we can find it, and romset can just be saved in one of the paths of the 20 recognizable ROMs.

After that, Ctrl+R, find dat and select it.

By the way, a graphical listing of romdata functions will be coming next to make it easier to use.
Pages: [1] 2 3 4 5 6 ... 10