Playstation classic

[fixingmytoys]

No. Yes. I'm waiting for the next Retrobot for Autobleem release.

Info files basically tell retroarch which core has what compatibility with extensions, and also might (not sure) tell it the core name to display.

Just read the latest KDFManiac changelog (from the release 11 hours ago), and PCSX cores for PSC were a little more optimized, and in regards to PSX CPU clockrate - hes talking about 70% as well. (As an alternative option to 57% default). Will have to play around with this.

In terms of actual usage - without confusing stuff. Next Retroboot for Autobleem release should include all the cores needed. Use one of the PCSX cores in that release. At least one of them should give you full speed. (Even at 70% PSX Clock (options), maybe - possibly).

Fullspeed PSX emulation even at 2x resolution shouldnt be an issue with those cores (/that core - depends on how many will be bundled in the next retroboot release) either.


If you want to exchange the .so files on your own (not waiting for them to be bundled with the next Retroboot release), just replacing the .so files is fine.

Especially if you edit your playlists by hand in which case you'd not even have to rename them. (Otherwise rename them to an existing cores name (if needed) - so Retroarchs "selection for that filetype (info files) menues" don't break. An updated info file hardly ever is needed. (It is, if a core starts to support a new file extension). You even could delete all info files and run retroarch that way, but then core integration in retroarch becomes "dumb" . Meaning, all cores will be shown for every filetype - core names in playlists might not be displayed correctly...)

I added more confusion than necessary here - because I was to lazy to check if the core I'm using actually is an extreme core. Afair it gets displayed that way in Retroarch - even though its filename doesnt include extreme. (Info file the cause?)
But thats just speculation.

Information needed is - "next Retroboot for Autobleem release will include all cores needed". Wait for that. (Or salvage the files from the current KDFManiac package and replace them on your own. Just replacing .so files is sufficient.)

sorry to bother you again i downloaded _km_psc_xtreme_core_injector_bleemsync_6-15-19 do i just run that and let it over wright what is in my bleemsysnc 1.1 first ( yes i am going to do a back up ) and that is it , happy to rescane playlist etc us delete the core floder?

 

[notimp]

I'm not dealing with either 'injectors', or Bleemsync. I think bundling stuff is an issue when people start to rely on cascades of delivery methods that depend on versioning of other bundles, and are supposed to allow them to do everything with a simple doubleclick of "do I just run this"?

I know how retroarch works (to a certain end user extend ). I know that Bleemsync has chosen to bet on a separate set of retroarch cores, that is not KDFManiacs.

I know that Retroboot for Autobleem is entirely separate from that (down to the point where even core names are different.)


And I know that depending on a simple tool from KDFManiac to replace the retroarch component in Bleemsync - to me sound like an issue in the making.

Could work (I dont know - I doubt many people are trying it out), but if it doesnt - you depend on support by KDFManiac because now you are dealing on dependencies on top of dependancies. And as even KDFManiacs changelogs read like spaghetti code in the making - I'm certainly not trying that. Guy is a genius in his own right. I'd still much rather depend on Retroboot for Autobleem for implementation (or replace a few cores by hand).

Going with the solution (Bleemsync) that doesnt use KDFManiacs stuff by default - and then depending on KDFManiacs injection solution - sounds like a support nightmare to me.

Try it out. Maybe its easy and painless. Who knows. Make a backup first.

 

[fixingmytoys]

i was gong to make a backup , what are the main reasons for Retroboot , dont know much about Retroboot

 

[notimp]

Looked at one of the injectors. Its just a simple 7zip .exe selfextracting archive. So anyone can extract it anywhere and use whatever they want from that archive.

If you "doubleclick use" the injector - it will overwrite all files of your retroarch installation. presumably resetting it back to default state.

If you go with the injector - you get no support from anyone, you support yourself. Again - the issue of cascades of dependencies. it is impossible to support "I used injector 6-15-19.7z on bleemsync 1.1 - which doesnt want to support it - now something doesnt work - what do I do?"

With Autobleem at least the dev supports KDFManiacs implementation.


Differences between retroboot for autobleem and Bleemsyncs implementation of retroarch are listed in this thread already. Differences (in game compatibility) once you've used the injector (not 'supported' by anyone 'officiall') probably are none. If it works.

Bleemsync does stupid and silly stuff with everything they do (flavor over substance) - but it has two major benefits. First is OTG support (which is why everyone should install Bleemsync and the OTG kernel first - then they are free to switch to autobleem), which translates to "use any capacity usb stick or harddrive on your PS classic (on the back port with a OTG adapter), no power issues whatsover, once the OTG kernel is installed). The second main benefit is better gamepad support. 8bitdo keeps sync. Original PS pads with an USB adapter work better throughout stock or retroarch interfaces.

Autobleem advantages are: Everything else. No useless skins, better Ui, turn off bilinear filtering in the stock emulator, KDFManiac cores by default...


So if you dont mind the hella ugly Bleemsync Logos and UI stuff, bleemsync with KDFManiac core injector might very well be "the best compromise". But thats a combination for which nobody will give you any support for. So not recommended for newbies.

And because most people have come to the conclusion that Bleemsync is best, because they loved a freaking youtube video - the disparity between "support needed" and "able to try stuff out and troubleshoot on their own" is highest for bleemsync users.

Then people like KDFManiac think - we make it easy for them - we build easy injector - and you have everything that could go wrong potentially neatly packaged into a thing. That depends on another thing. Which doesnt officially support it. People that try to enter the scene from "I doubleclicked, what do I do next" - and something thats not even a solution people would have a name for - so they could gather around and support each other structurally.

"I'm on injector 6-15-19 and stuff broke, what do I..."


I'm waiting for the next retroboot for autobleem release (becaus I'm dealing with an installation with several 10k of roms). There are reasons to do it differently, but people have to decide to do so on their own. There are pros and cons.

 

[BL4Z3D247]

You don't need to emulate the PSX CPU at that high speed, you are wasting CPU time. You can get better overall performance at 70.

I'm interested in how you came to that conclusion as well.

For me, 85% has always showed less drops in frames and fixed(to an extent) some minor audio stuttering that some games have even when you have the CPU clock to 70%. Certain games do run too fast when using 85% but lowering it to 84% would fix that.

 

[subcon959]

I haven't used mine in a while but I'm sure I kept it at 84% for everything.

 

[notimp]

Just finished the implementation of a MAME 2003, a CPS1/2/3, and a NEOGEO, full romset. With cover images. Took freaking days to filter out duplicates. (Using regex and a half automated approach.)

Impressions:

The Namco 3D Games (Arcade Versions) run nowhere near full speed, but its still cool to have them on the system.

All the other roms basically run fullspeed, if you choose the right emulator.


Non Arcade screenshoots I had laying around:

--------------------- MERGED ---------------------------

Games implemented so far: 15.598 (on a 256GB thumbdrive)

And I still have a few systems left to do. Once finished I'll still be below 20.000 tough.

Playing one game by day - would take 55 years.

With the total cost of the setup being at 60USD currently (including storage), this factors out to 0.3 cents cost per game.

 

[fixingmytoys]

Just finished the implementation of a MAME 2003, a CPS1/2/3, and a NEOGEO, full romset. With cover images. Took freaking days to filter out duplicates. (Using regex and a half automated approach.)

Impressions:

The Namco 3D Games (Arcade Versions) run nowhere near full speed, but its still cool to have them on the system.

All the other roms basically run fullspeed, if you choose the right emulator.


Non Arcade screenshoots I had laying around:

--------------------- MERGED ---------------------------

Games implemented so far: 15.598 (on a 256GB thumbdrive)

And I still have a few systems left to do. Once finished I'll still be below 20.000 tough.

Playing one game by day - would take 55 years.

Love your setup

 

[notimp]

Offtopic:

Tracked down a copy of a Snatcher MSX rom translation:

Played only on a PC so far (needs number keys 0-5 mapped as well as space and enter) - but the game is a vastly different experience from the Sega CD version. By todays sensibilities its almost unplayable. There are long load times between screens. Text scrolling is a tad slow. And if you play it in fast forward mode (which you will be tempted to), sound of course is distorted.

On the other hand - you are engaging much more with the text.

If you've never played the game and have ever wondered, if you should play it on MSX - play the Sega CD version first.

 

[Deleted member 42501]

Now that they are clearing these out real cheap is it worth grabbing one for emulation purposes? Also how is the lag?

Canoe on the SNES Mini is really good in that respect and its the main reason why I won't install the rest of the crap on there as I find RetroArch introduces a palpable amount of lag just due to how it works (same reason I dislike the rPi) as I'm a "feel" gamer and can feel when its off and its just nasty.

 

[the_randomizer]

Now that they are clearing these out real cheap is it worth grabbing one for emulation purposes? Also how is the lag?

Canoe on the SNES Mini is really good in that respect and its the main reason why I won't install the rest of the crap on there as I find RetroArch introduces a palpable amount of lag just due to how it works (same reason I dislike the rPi) as I'm a "feel" gamer and can feel when its off and its just nasty.

Canoe is only about ~80% compatible with SNES ROMs, many games that require precise S-SPC/SPC700 timing are completely broken with missing audio (Secret of Evermore, Earthworm Jim 2, Clay Fighter, etc), games with hi-res modes using 512 x 448 are broken, so I mean, I think people like crapping on RetroArch for completely unsubstantiated reasons *shrug*. Not really much choice, either low compat with Canoe or high compat with Snes9x 2010.

 

[Vorde]

Just finished the implementation of a MAME 2003, a CPS1/2/3, and a NEOGEO, full romset. With cover images. Took freaking days to filter out duplicates. (Using regex and a half automated approach.)

Games implemented so far: 15.598 (on a 256GB thumbdrive)

And I still have a few systems left to do. Once finished I'll still be below 20.000 tough.

Playing one game by day - would take 55 years.

With the total cost of the setup being at 60USD currently (including storage), this factors out to 0.3 cents cost per game.

How is Nintendo 64 emulation performance on these things? I don't currently have a setup to emulate the N64 on my UHD screen and have been looking at some

 

[notimp]

KDFManiac just fixed 4 out of 6 N64 cores in the latest release and I havent tested them yet.

One below 720p resolution so far seems to be the max for most games - Zelda OOT runs full speed. So at 540p performance is not the greatest issue. Most games should work.

Once I've updated to the latest coreset I'll test more demanding games like KI Gold, but dont wait for it.

As 720p seems to be out of question the answer is most likely "good enough" for most games but more performance would be nicer. With N64 the more timeconsuming part is to try out several cores (emulators) with every rom if emulation issues arise. But thats always been an issue, and not one that you solve by throwing cpu power at it.

 

[Vorde]

KDFManiac just fixed 4 out of 6 N64 cores in the latest release and I havent tested them yet.

One below 720p resolution so far seems to be the max for most games - Zelda OOT runs full speed. So at 540p performance is not the greatest issue. Most games should work.

Once I've updated to the latest coreset I'll test more demanding games like KI Gold, but dont wait for it.

As 720p seems to be out of question the answer is most likely "good enough" for most games but more performance would be nicer. With N64 the more timeconsuming part is to try out several cores (emulators) with every rom if emulation issues arise. But thats always been an issue, and not one that you solve by throwing cpu power at it.

Sounds like I'm still better off running it off of my gaming laptop although it's not as convenient, thank you though

 

[notimp]

It depends what you want out of it. 720p internal resolution scaling - its not beefy enough. Compatibility - is as good as on anything else out there - it depends on the cores. Can every N64 core run fullspeed at nativ (low) resolution? Yes.

Do all games just work flawlessly? No - they never do, its N64. If you need something to compare against - the most promising cores currently are Glupen and Mupen Plus Next - use any device that runs Retroarch and check against those.

People will never get a glowing endorsement of "everything runs well" for N64 games because emulation development was so fragmented. The rest is just - I've only tested maybe 4 N64 games for longer than a few minutes on the system - because until the latest release the best core (and a few others) were broken. Now they arent. Which means I'll look into it later.

Among the cores broken until a few days ago also was the most performant one - so maybe youll get full speed 720p output - it was close. Someone else update, and test. I'll do it in due time.

edit: Also controller lag is an issue with 8bitdo and N64 (using a PS4 controller). You need both analog sticks to be mapped as analog sticks, whicht the 8bitdo only does in XPAD mode (green controller LED), and in XPAD mode, input lag is higher. Stil very playable - but doesnt feel perfect.

Other solutions such as wired PSone pad with wired USB adapter and Bleemsync 1.1 or other controllers might work better.

That said PS4 controller with 8bitdo wireless usb dongle is very, very good for about every other system that doesnt need true analog input (everything except N64 and DC) - in PS controller mode (Low input lag, Analog sticks are emulating digi cross input).

 

[Deleted member 42501]

Canoe is only about ~80% compatible with SNES ROMs, many games that require precise S-SPC/SPC700 timing are completely broken with missing audio (Secret of Evermore, Earthworm Jim 2, Clay Fighter, etc), games with hi-res modes using 512 x 448 are broken, so I mean, I think people like crapping on RetroArch for completely unsubstantiated reasons *shrug*. Not really much choice, either low compat with Canoe or high compat with Snes9x 2010.

Good job all the games I want to play are in that 80% eh? As for Evermore wasn't there a Hi Res text patch that fixed it for Canoe? Also from what you've said I take it you're willing to accept RAs lag or just don't notice it as its a major thing for me.

 

[the_randomizer]

Good job all the games I want to play are in that 80% eh? As for Evermore wasn't there a Hi Res text patch that fixed it for Canoe? Also from what you've said I take it you're willing to accept RAs lag or just don't notice it as its a major thing for me.

Secret of Evermore doesn't use that mode 7, it uses SPC700 specific timing. Yoshi's island's emulation is messed up in Touch Fuzzy Get Dizzy, the BG layer isn't supposed to completely disappear when you touch the fuzzies, so yeah, that fuzzy effect is botched. Seiken Densetsu 3/Trials of Mana hi-res font is botched as well, as it uses 512 x 244 res for the text boxes, so *shrug*. But again, people unnecessarily crap on RA for no reason.

 

[Deleted member 42501]

Secret of Evermore doesn't use that mode 7, it uses SPC700 specific timing. Yoshi's island's emulation is messed up in Touch Fuzzy Get Dizzy, the BG layer isn't supposed to completely disappear when you touch the fuzzies, so yeah, that fuzzy effect is botched. Seiken Densetsu 3/Trials of Mana hi-res font is botched as well, as it uses 512 x 244 res for the text boxes, so *shrug*. But again, people unnecessarily crap on RA for no reason.

Two words:

Input. Lag.

 

[the_randomizer]

Two words:

Input. Lag.

*Shrug* I'm done anyway, trying to show my side of things is a waste of time.

 

[Deleted member 42501]

*Shrug* I'm done anyway, trying to show my side of things is a waste of time.

Of course it is when you keep on banging the drum you want to and totally ignore what the other person is saying! Keep quiet now and let someone else speak who actually reads.