Goodbye fbalpha, welcome fbneo

saccublenda

IanDaemon

@saccublenda It's a 2D arcade game using sprites so I can't imagine it requires that much "oomph". Yes, there can be a lot going on at any one time, but still.

barbudreadmon

@saccublenda @IanDaemon among other things, it appears mame2003-plus doesn't implement the raster effects (this is especially noticeable on Nebulas Ray where the game ends up being heavily glitched), that explains why it's a lot faster.

Also, there is no reason for 2D being faster than 3D, if anything drawing 3D can be way faster than drawing 2D because you have the possibility of offloading it to the GPU.

Riverstorm

@barbudreadmon said in Goodbye fbalpha, welcome fbneo:

Also, there is no reason for 2D being faster than 3D, if anything drawing 3D can be way faster than drawing 2D because you have the possibility of offloading it to the GPU.

Hmmm, I know there's no absolutes but it seems like a impossible comparison if going for apples to apples.

If you look at it from a overview trying to calculate the graphics technical level they have some cross over. Generally speaking 2D and 3D are fundamentally different in their approach.

After a certain level 3D is an order of magnitude more complex with rendering, physics, poly counts, texture quality, FOV, field of depth, etc. I don't even know how a person could really compare the two with so many variables.

You would think they are generally more intensive, after a certain level. I know it's not that simple but I grew up with the idea 3D, generally speaking, is more "demanding" than 2D too if you compare 100 "generally" similar 2D to 3D games. :)

Graphics Engine	Tech Level
Text Based	0
2D Graphics V1	1
2D Graphics V2	2
2D Graphics V3	2
2D Graphics V4	3
2D Graphics V5	3
3D Graphics V1	1
3D Graphics V2	2
3D Graphics V3	3
3D Graphics V4	4
3D Graphics V5	5
3D Graphics V6	6
3D Graphics V7	7

barbudreadmon

@riverstorm initially, 3D might be more demanding than 2D, but from an emulation point of view :

for a given emulator, hardware rendering (drawn by GPU) is faster than software rendering (drawn by CPU), the only exception to that would be if your device is very unbalanced (very good CPU with very bad GPU)
unlike 3D games, the way old 2D games are doing things is totally different from how modern GPU work, so hardware rendering is basically unavailable for those old 2D games. Well, i'm saying that, but i've seen compute shaders being used to get around differences between modern GPU and old 3D games, so i've been wondering if using them would be possible for 2D games too.

DTEAM

@barbudreadmon

Hi, I would like to know if it's doable to add the driver stv.cpp (Manufacturer: Success, Altus, A wave inc. etc.) to lr-fbneo. The reason is that no emulator seems to work fine for Cotton 2. There is still choppy sound even with autoframeskip. I was wondering if lr-fbneo could fix that.

By the way excellent work. I have created personal theme for each of your systems. thanks a lot.

barbudreadmon

@dteam we don't take requests, furthermore we aren't interested in 3D arcade hardware in the first place (stv is sega saturn).

DTEAM

@barbudreadmon said in Goodbye fbalpha, welcome fbneo:

@dteam we don't take requests, furthermore we aren't interested in 3D arcade hardware in the first place (stv is sega saturn).

So, Cotton 2 (arcade) is running by Saturn driver. Thanks for the info.

barbudreadmon

@dteam to be more precise, stv is Sega Titan Video, the arcade version of Sega Saturn (exactly the same hardware)

Darksavior

@dteam I think some version of advmame has cotton (2 or boomerang) playable. It's been a while since I've tried it but it might've been near or around fullspeed. It also works on lr-yabasanshiro though it is slow so you need to enable frameskip but even then it can be choppy. yaba has no skipping audio, though.

DTEAM

@darksavior said in Goodbye fbalpha, welcome fbneo:

@dteam I think some version of advmame has cotton (2 or boomerang) playable. It's been a while since I've tried it but it might've been near or around fullspeed. It also works on lr-yabasanshiro though it is slow so you need to enable frameskip but even then it can be choppy. yaba has no skipping audio, though.

For lr-yabasanshiro i'm able to run the Saturn version of Cotton 2 but not the arcade version. It sticks on the cd driver menu.
Does a patch or something exist with lr-yabasanshiro for arcade games using stv driver like lr-flycast (Dreamcast) does for Naomi/Atomiswave.

Darksavior

@dteam I believe yabasanshiro only emulates saturn.

roslof

@barbudreadmon said in Goodbye fbalpha, welcome fbneo:

Namco NB-1 is now supported :

Nebulas Ray
Point Blank / Gun Bullet
Great Sluggers
Great Sluggers 94
Super World Stadium
Super World Stadium '96
Super World Stadium '97
J-League Soccer V-Shoot
The Outfoxies
Mach Breakers

I really recommend "The Outfoxies", it's a hidden gem.

Huge. Great to move these away from lr-mame2010, be able to .7z them, and get the performance benefits. Fan of a few of these.

Cheers!

roslof

@barbudreadmon said in Goodbye fbalpha, welcome fbneo:

Seibu SPI is now supported :

Senkyu / Battle Balls
E Jong High School
Viper Phase 1
Raiden Fighters
Raiden Fighters 2 - Operation Hell Dive
Raiden Fighters Jet
E-Jan Sakurasou

Note : no, we can't remove that 999 countdown, and you'll have to restart the game at the end of it, the good news is that you have to go through it only the first time you launch the game, sometimes there are also clones (single board PCB version) that don't have that countdown

Another big win. Performance is great after countdown hell.

roslof

@barbudreadmon said in Goodbye fbalpha, welcome fbneo:

Namco NA-1 is now supported :

Bakuretsu Quiz Ma-Q Dai Bouken
Cosmo Gang the Puzzle
Emeraldia
Exvania
Fighter & Attacker
Super World Court
Tinkle Pit
Knuckle Heads
Numan Athletics
Nettou! Gekitou! Quiztou!!
X-Day 2

@barbudreadmon for this earlier released set, there are some issues you should be aware of. FWIW, My test device is a Pi4B. Updated lr-fbneo to commit 578e85f. Let me know if you'd like me to file any of these issues in the fbneo git repo:

Bakuretsu Quiz Ma-Q Dai Bouken (bkrtmaq) controls do not appear to work/respond (eg. cannot add credits).
Cosmo Gang: The Puzzle (cgangpzl) SegFaults after rom is validated line 1285: 12660 Segmentation fault
Numan Athletics (numanath) SegFaults after rom is validated line 1285: 26458 Segmentation fault
Nettou! Gekitou! Quiztou!! (quiztou) boot screen displays Key Custom ERROR can't seem to advance

The rest of the games seem to be working as expected. Hope this is useful.

It's great to remove the lr-mame2015 emulator from these games. Thank you!

barbudreadmon

@roslof were those tests done with latest code ? i can't reproduce that issue on cgangpzl and numanath (i don't have a pi4 though, only a pi3 but that shouldn't make any difference). what do you mean exactly by "after rom is validated" ? could you maybe provide full log ?

I confirmed the issue with the 2 others, thanks for the report.

Riverstorm

@barbudreadmon said in Goodbye fbalpha, welcome fbneo:

for a given emulator, hardware rendering (drawn by GPU) is faster than software rendering (drawn by CPU), the only exception to that would be if your device is very unbalanced (very good CPU with very bad GPU)

What you said makes perfect sense. I guess I wasn't thinking so much about the methods or techniques used to render them. When I do my thought always leans more toward software rendering when it comes to arcade machines. I think of a bunch of discrete logic components slapped onto a circuit board and not so much CPU based architecture.

How to render all those chips? To me it seems to make more sense to emulate those types of hardware components on the CPU (software rendering) for portability vs. going the road of GPU (hardware rendering).

If you utilize and adhere to some platform specific graphical standard like DirectX , etc. or even some GPU manufacturer's proprietary technology (NVIDIA or ATI) you run the risk of that company going defunct or abandoning the technology line and you're back at square one.

I know both companies have developed some great technologies in the past only to ultimately abandon them at their discretion for one reason or another. Not to mention it probably leaves devs needing to maintain multiple code bases to cover all the platform technologies.

When I think of MAME I think of emulation vs. simulation. They both can have the same end result but under the hood they may have went about it in two completely different ways. I think some emulators get the job done and utilize those graphical advantages and/or shortcuts to great effect without much thought into code portability and compatibility. MAME is more about preservation hence emulation by definition vs. simulation may run it perfectly but you have no idea how the original actually worked under the hood. Most gamers probably don't care as long as they have a good experience.

I know their are always exceptions, to all games, but when comparing two similar games graphically and hardware wise from the same era hardware, rendered with the same techniques, I would generalize that the 3D games generally take more processing power than the 2D games for the purpose of shooting the breeze and generalized discussion.

I know it's a rabbit hole and these discussions have been going on for decades. I also see mitu up voted the reply. I do trust his discretion, expertise and impartial replies and may be completely off base on how I view emulation. I also know these discussions have been going on for decades but I do appreciate the explanation and the great games FBNeo supports.

DTEAM

@barbudreadmon
I'm not able to run namco na-1 and nb-1. The other stuffs run perfectly.

I'm using MAME romset 0.229
I'm using Up-to-date clrmamepro dat files from https://github.com/libretro/FBNeo/tree/master/dats

Did I miss something ? I run It on a Pi 4

WeirdH

@dteam said in Goodbye fbalpha, welcome fbneo:

@barbudreadmon said in Goodbye fbalpha, welcome fbneo:

I recommend using frameskip on low-end devices if you aren't already.

For that, the value must be 1 or auto
fbneo-frameskip = "0"
New edit
I put « 1 » and now, everything is fine

Does this setting reside in retroarch-core-options.cfg? When I change it there, then launch a game and check 'options' through RGUI, it still says 'no skipping' at frameskip, so I think I'm in the wrong file here...

DTEAM

@weirdh said in Goodbye fbalpha, welcome fbneo:

Does this setting reside in retroarch-core-options.cfg?

Yes It is.