Author Topic: FB Neo Bugs Reports  (Read 89788 times)

Offline TaiToaplan

  • New Member
  • *
  • Posts: 5
  • Karma: +0/-0
Re: FB Neo Bugs Reports
« Reply #945 on: December 25, 2022, 02:00:14 PM »
Hi TaiToaplan,
Regarding bishi: the game had corrupted graphics roms, and the board owner/dumper did their best to get what they could.  The only way it can be fixed is if someone were to get/find a pcb and dump the gfx roms - unfortunately.

best regards,
- dink

I assumed so, thanks anyway

Offline Igor_Arabe

  • Newbies
  • *
  • Posts: 18
  • Karma: +0/-0
Re: FB Neo Bugs Reports
« Reply #946 on: January 10, 2023, 12:16:50 PM »
I compiled fbneo (commit 10a361d) using tutorial (VS) from fba old site.
in normal and debug version shows games from neogeo (461 normal / 462 debug) with or without marking "neogeo" in hardware filters.



Using VS17 IDE shows error (LNK2001 unresolved external symbol) in softx filters
hq3x_32, hq4x_32, hq2x_32, 2xScaline, superscale_line_75, eagle_mmx16, 2xSalSuper2xSalLine, 2xSalSuperEagleLine, superscale_line, init_2xSalMMX

I don't know since what version these bugs occurs.

Offline dink

  • Administrator
  • *****
  • Posts: 4743
  • Karma: +418/-1
  • pie? I nearly bought one!
Re: FB Neo Bugs Reports
« Reply #947 on: January 10, 2023, 06:14:01 PM »
Hi Igor,
Did you put nasm.exe somewhere in path?

best regards,
- dink

Offline Igor_Arabe

  • Newbies
  • *
  • Posts: 18
  • Karma: +0/-0
Re: FB Neo Bugs Reports
« Reply #948 on: January 10, 2023, 09:15:28 PM »
Yes. for both cases.

Offline dink

  • Administrator
  • *****
  • Posts: 4743
  • Karma: +418/-1
  • pie? I nearly bought one!
Re: FB Neo Bugs Reports
« Reply #949 on: January 11, 2023, 12:05:01 AM »
I use only gcc in bash (mingw) for compilation, so I can only guess at the problem..
Perhaps taoenwen (on github) can help, he use VS and does a good job at keeping it up-to-date.

best regards,
- dink

Offline the_maq

  • Member
  • ***
  • Posts: 114
  • Karma: +0/-0
Re: FB Neo Bugs Reports
« Reply #950 on: January 16, 2023, 08:57:53 PM »
@Dink - Raiden 2 just got guru'ed with the latest exe during load state?

Offline dink

  • Administrator
  • *****
  • Posts: 4743
  • Karma: +418/-1
  • pie? I nearly bought one!
Re: FB Neo Bugs Reports
« Reply #951 on: January 16, 2023, 09:14:30 PM »
the_maq, if this happens, it unfortunately is no longer compatible with current fbneo code.
Basically: that state will still load fine on the version of fbneo you saved it with.

some day I would like to figure out a good way to do proper versioning on the states - so problems like this won't happen

best regards,
- dink


Offline taoenwen

  • New Member
  • *
  • Posts: 2
  • Karma: +0/-0
Re: FB Neo Bugs Reports
« Reply #952 on: January 16, 2023, 11:38:27 PM »
I compiled fbneo (commit 10a361d) using tutorial (VS) from fba old site.
in normal and debug version shows games from neogeo (461 normal / 462 debug) with or without marking "neogeo" in hardware filters.



Using VS17 IDE shows error (LNK2001 unresolved external symbol) in softx filters
hq3x_32, hq4x_32, hq2x_32, 2xScaline, superscale_line_75, eagle_mmx16, 2xSalSuper2xSalLine, 2xSalSuperEagleLine, superscale_line, init_2xSalMMX

I don't know since what version these bugs occurs.

hi Igor_Arabe,
nasm is not configured in projects prior to vs2022, so if you want to use nasm, it is recommended that you use the vs2022 project files.
How to quickly configure nasm, you can find it at https://github.com/ShiftMediaProject/VSNASM, and the above is explicitly stated in building.txt in the vs2022 project.

Offline Igor_Arabe

  • Newbies
  • *
  • Posts: 18
  • Karma: +0/-0
Re: FB Neo Bugs Reports
« Reply #953 on: January 19, 2023, 10:20:52 AM »
Thanks, i did testes with:
-fbneo src commit 71c0fc6

compiled with the three project files (vs2015/vs2019/vs2022)... And have the same bug too.

Shows neogeo games with or without marking hardware filters (see image).
Games affected have this tag: HARDWARE_PREFIX_CARTRIDGE


In old fba this bug don't occurs (i used tutorial for vs in old fba site).
« Last Edit: January 19, 2023, 10:23:17 AM by Igor_Arabe »

Offline dink

  • Administrator
  • *****
  • Posts: 4743
  • Karma: +418/-1
  • pie? I nearly bought one!
Re: FB Neo Bugs Reports
« Reply #954 on: January 19, 2023, 11:47:14 AM »
Igor_Arabe,
Hi, please zip your fbneo/config directory and pm a link to me, so I can investigate

best regards,
- dink

Offline taoenwen

  • New Member
  • *
  • Posts: 2
  • Karma: +0/-0
Re: FB Neo Bugs Reports
« Reply #955 on: January 20, 2023, 02:44:47 AM »
Thanks, i did testes with:
-fbneo src commit 71c0fc6

compiled with the three project files (vs2015/vs2019/vs2022)... And have the same bug too.

Shows neogeo games with or without marking hardware filters (see image).
Games affected have this tag: HARDWARE_PREFIX_CARTRIDGE


In old fba this bug don't occurs (i used tutorial for vs in old fba site).

For msvc use another method to check if the treeview is selected & if the game is neogeo.
https://github.com/finalburnneo/FBNeo/pull/1312

Offline dink

  • Administrator
  • *****
  • Posts: 4743
  • Karma: +418/-1
  • pie? I nearly bought one!
Re: FB Neo Bugs Reports
« Reply #956 on: January 20, 2023, 08:37:23 PM »
Igor_Arabe, today I installed vs 2022, and compiled [Debug] version - it doesn't have this bug.
Next I will compile non-[Debug] and let's see if I can find the problem!

Funny thing:
vs 2022 compiling fbneo and chkdsk on a very broken hdd are the only times I've ever seen out of memory on this 8gigabyte machine!

hmm, it will compile x64 debug or release no problem, but when compiling x86 (win32), it says the custom build has succeded, but generated file was not created errors.. hrmf.  any ideas?

best regards,
- dink
« Last Edit: January 20, 2023, 09:15:25 PM by dink »

Offline Igor_Arabe

  • Newbies
  • *
  • Posts: 18
  • Karma: +0/-0
Re: FB Neo Bugs Reports
« Reply #957 on: January 21, 2023, 06:35:28 PM »
I never tried to compile in x64, Always in x86. I never seen these errors. I got only errors as related above (unresolved external symbol in softx filters).
Now all is ok. Thank you guys.

Offline dink

  • Administrator
  • *****
  • Posts: 4743
  • Karma: +418/-1
  • pie? I nearly bought one!
Re: FB Neo Bugs Reports
« Reply #958 on: January 22, 2023, 10:58:56 AM »
I'm done with vs (it's de-installed) - it ran out of memory on my 8gigabyte machine while compiling fbneo and corrupted itself.  How handy!
*hugs gcc compiler*

luckily taoenwen figured out the real cause of the problem with the NeoGeo games showing up and solved it :)

best regards,
- dink
« Last Edit: January 22, 2023, 11:00:41 AM by dink »

Offline ClessxAlghazanth

  • Jr. Member
  • **
  • Posts: 97
  • Karma: +2/-0
Re: FB Neo Bugs Reports
« Reply #959 on: January 24, 2023, 05:15:22 AM »
Hi  :cool:

I'm not sure if it's an issue or just my memory being false but

I can't find the 'Difficulty' option in the dip switch settings of Armored Police Batrider

Playing version B which has guest fighters etc unlocked but it's same for A version too

I can vaguely remember having the difficulty setting in ds settings while playing this game on mame years ago (mame 0.130 or sth  :biggrin:) and turning the difficulty to easy because as much as I love Raizing games I suck at them badly  :p

Thanks and have a good one  ;p