Playstation classic

[vanditr]

forgot to mention i am using a 64gb hp usb 3.0 flash drive

 

[Advokaten]

If anyone want to do playlists etc for Retroarch.

 

[Gab75]

Hi guys,
observing the pcsx.cfg file inside the GameData folder I noticed that the frameskip value is set to 0 ( frameskip3 = 0 ). I can suppose that this value corresponds to "AUTO", what is the correct value to set the frameskip "off" ?

PS: I'm using BleemSync 4.1 and the default PCSX rearmed emulator.

 

[CrashBragecoot]

Hi guys,
observing the pcsx.cfg file inside the GameData folder I noticed that the frameskip value is set to 0 ( frameskip3 = 0 ). I can suppose that this value corresponds to "AUTO", what is the correct value to set the frameskip "off" ?

PS: I'm using BleemSync 4.1 and the default PCSX rearmed emulator.

1

 

[Gab75]

1

Thanks!
Using the value "1" (frameskip off) the issue related to the random frames that are skipped is solved, but the sound has (consequently) little distortions, so, at the end, it's better keep the frameskip to "AUTO" (0)...

 

[IwearHelmet4Bed]

I was able to fix this issue by deleting bleemsync and retroarch folders from SD - Kept games folder just added bleem and retro again.

Thank you very much, I’ll try this later on

 

[Deleted User]

That and the controller not working problems happen from time to time, don't reformat or change anything, just cut the power from the PSX and try again.

Not in my case. Controller wouldn't register.

What I noticed"

Install Bleemsync and controller works - When launching a game you'll see PS logo before game


Install Retroarch and Controllers will not work in Bleemsync

If you Install Bleemsync and Retroarch do this - Load up PS classic and load bleemsync 1st and controllers will work in Bleemsync and Retroarch without having to mess with button configuration



Note: Even after setting up controls in retroarch I would have this issue. Another thing to note: If you don't get the PS splash screen before loading a game in Bleemsync your controllers will not work

Hope this helps out

 

[szczuru]

Not in my case. Controller wouldn't register.

What I noticed"

Install Bleemsync and controller works - When launching a game you'll see PS logo before game


Install Retroarch and Controllers will not work in Bleemsync

If you Install Bleemsync and Retroarch do this - Load up PS classic and load bleemsync 1st and controllers will work in Bleemsync and Retroarch without having to mess with button configuration



Note: Even after setting up controls in retroarch I would have this issue. Another thing to note: If you don't get the PS splash screen before loading a game in Bleemsync your controllers will not work

Hope this helps out

Missing boot sequence means pcsx.cfg can't be loaded (that's why ps logo is missing - game is booting using hle bios and without binded controls). Check every games dorectories for correct pcsx.cfg

 

[Deleted User]

Missing boot sequence means pcsx.cfg can't be loaded (that's why ps logo is missing - game is booting using hle bios and without binded controls). Check every games dorectories for correct pcsx.cfg

cfgs are there, its bug with retroarch. Simply load bleemsync 1st then retro and all is well.

I'm sure this will be fixed in next few builds. 2 PS classics with diff flash/usb drives and same result.

 

[KiiWii]

https://twitter.com/nuagedan100/status/1079427094147420161?s=21

Has anyone got any dual analog controllers working on PSX games yet? Not Retroarch.

 

[Deleted User]

https://twitter.com/nuagedan100/status/1079427094147420161?s=21

Has anyone got any dual analog controllers working on PSX games yet? Not Retroarch.

That tool is really buggy and corrupted my install it seems. I wouldn’t use it quite yet

Plus you can’t move the window around for whatever reason..for now stick with the manual method

 

[KiiWii]

That tool is really buggy and corrupted my install it seems. I wouldn’t use it quite yet

Plus you can’t move the window around for whatever reason..for now stick with the manual method

Thanks @Sasori

I want to set mine up for gun games, I’m going to try aimtraks and dolphin bar later this week.

 

[Deleted User]

N64 on PSX Classic Proof of concept
Soon we can play Mario 64 on the Sony Playstation.

 

[Futurdreamz]

... Sure why not. I don't see us getting a N64 classic for the sole reason that Nintendo doesn't want to deal with the ip negotiations.

 

[Advokaten]

N64 on PSX Classic Proof of concept
Soon we can play Mario 64 on the Sony Playstation.

Hey. That’s my video! You already can play N64 games on it with RetroArch.

In the video I am just running RetroArch shortcuts from the Playstation Classic carousel. I wanted to make a proof of concept video because everything on the carousel originally has a fixed command line to boot into the PCSX emulator. This means that you now can practically run anything from the PSC carousel, such as this custom script!

 

[KiiWii]

@Advokaten nice work

 

[WD_GASTER2]

if this can be done with snes titles etc, it would put it pretty much on equal footing with the nes classic and snes classic no?

 

[subcon959]

Looks like the next BleemSync update is gonna be a good one..

General Updates

• USB payload completely redone from scratch, much better design and stable. Also with scope to run on the console's EMMC (coming soon!)
• 100% Headerless setup/config and UI support. (Adding games, mods, themes etc from UI) (Only BleemSync configuration available on initial release)
• Completely new and improved bootloader. Contains more sense checking and script vetting to ensure no broken boots.
• Auto deployment/install and update facility added.
• Added permanent safe USB lockout disable, telnet and ftp support. (Will enable these services on first boot so you don’t need a USB to load these services!
• Because of the USB lockout disable, you can now run psc from TVs and PC USB ports.
• Improved LED support, green = idle/OK, orange = BS function running, flashing red = attention needed see on screen. (You can now see exactly when something is running)
• Added function libraries so you can add your own scripts in to the boot sequence if you wish for extra tinkering
• Added boot profiler (Every function in the boot sequence will get timed and recorded so you can identify slow down issues within boot)
• Integration of RetroArch by default

Boot Updates

• Added the ability to fully customise your boot routine. You can select what functions/routines and extra debugging routines are run during boot time.
• Added customisable boot options, including quick load, Heath check disable and custom splash screen support.
• Added kickass BleemSync splash screen on load (Can be disabled or customised)
• Added new build of BootMenu as default, now with BleemSync theme and the ability to change the boot menu background theme too. (Just like the splashscreen)
• Added the facility so you can boot directly to the bootmenu, RetroArch or the stock UI. (Configurable from USB or UI)

Stock UI Updates

• Added folder support
• Added ability to add your own background music to the stock UI. (You can add multiple wavs and it will shuffle)
• Added ability to launch RetroArch directly from the stock UI
• Added ability to launch RetroArch games from the stock UI
• Added ability to load in original 20 games into the stock UI including your customs.
• Added ability to easily load in custom UI themes

RetroArch Updates

• Improved the RetroArch deployment method for the psc
• Improved playlist support to make it easier to use
• Added extra directories to the usb to allow easier core/bios loading
• Added overlay support with scanlines available by default

Misc Updates

• Added devtools like GDB, readelf, ldd and nano etc. Also made accommodations so you can easily mount your own binaries/libraries to the console. (SAFELY)

 

[BL4Z3D247]

I would urge you not to set it globally, but for every game individually.
(Still dont know what the "save as global config" setting does in the ESC menu, since I have NEVER used it - )

You remember the part, where BleemSync has you putting a pcsx.cfg file into every game folder? You can set it right there (psx_clock value).

Finished testing psx_clock = 55 value (= cpu clock 85% shown in esc menu) on 26 games - all with double resolution enabled.

For most it was spot on and 55 dindnt uncap the framerate (which would have made the games run too fast).
--

In 2 there was performance loss (dropped frames) - they were:
- Chrono Cross - when entering a battle (swirl)
- MediEvil - which would occasionally drop 2 frames in normal gameplay

In those cases youd have to either turn off double resolution, or reduce psx_clock - I guess.

Crash Team Racing might be another one, although it would drop frames in the overworld, and not in races - its hard to tell, maybe developers intended it that way. Sound doesnt get strange either.
--

For two games 55 triggered the "uncap framerate" issue, where the games would run too fast (identifyable by show fps showing frames in the 40s (first value) when youd either want to see them fixed at 30 (or 25 for a PAL game), or as close to 60 (50 PAL) as possible). They were:

- Final Fantasy 7 (all other numbered Final Fantasys where fine)
- Final Fantasy Tactics

In those two cases you'd have to reduce 55 to a value youd have to find out on your own. (optimal value currently unknown)
--

For Pal users: 55 in PAL game makes it break the framecap which you dont want. Unless you change game Region to NTSC - then 55 is fine.

In case you dont want to do that - use 46 for PAL games instead. The most prominet reason for why you wouldnt want a PAL game to run as NTSC is, if you get speed up audio as a result. In most games - you dont. But there are some where you do. Breath of Fire 3 for example, or Legend of the Dragoon (menu music).

Final Fantasy 8, 9 and Parasite Eve 2 for example, you almost want to run as NTSC - even if you are using PAL versions, because you basically only get benefits out of it (game closer to the NTSC speed, sound still sounding great. ). Those you'd want to run with 55 as well - as long as you set their region to forced NTSC.
-

There also are games running at native 60 (Tekken 3, as well as almost every beat em up (except for Ehrgeiz.. )) or native 50 (Discworld Noir) - that also benefit from 55 (=85%), but on those you can even experiment with psx_clock = 64 (=100%). As long as you are not droping frames - there should be no detriment.
-

Reason to set psx_clock higher than 39 (=57% default value), is mostly slightly reduced input lag (I swear its there.. - not as "good" as using the Retroarch core), and better perceived performance in some games. In RPGs for example, text might scroll faster. In Tekken 3 suddenly the Yoshimitsu (forest) stage doesnt lag. In other games certain scenes, or even FMVs stop stuttering. Although the games themselves will not exceed their intended framecap (ideally).
-

psx_clock = 55 is a good value to start with in every NTSC game or every PAL game you want to force to run at NTSC speeds - with it only causing 2/26 to jump their framecap.

psx_clock = 46 is a good value to start with in every PAL game you want to run at pal speeds.

I suggest you edit the individual games pcsx.cfg directly - as its faster than changing the percent values in the menu. As you have seen all along the last pages - the percent values do not match the numbered values for psx_clock - allthough they are "the same setting". Thats why I've always used the % symbol when refering to esc menu values, and no % symbol when refering to pcsx.cfg values.

Have fun.

Saving the configuration globally just saves the pcsx.cfg to the ".pcsx" folder within the numbered folder for the game loaded. You can drop the pcsx.cfg file into the "GameData" folder to load the newly saved settings upon the game starting.

It just enables you to adjust settings on the PSC(which is easier for beginners) and then just move the file over to the GameData folder when you're done. Easy peasy.

 

[yadspi]

Was going to finally do my full setup but seeing that a BleemSync mega update is coming I'll wait it out.