Then you can search for it using the Bluetooth utility and sync with it (hit the second option for the DualShock 4 after it syncs).Īfter that, restart your Raspberry Pi. For the NES30, hold down the power button on the front-left of the controller until it turns on. You’ll have to switch the controller into discovery mode-for the DualShock 4, hold down the Share and the PlayStation button at the same time until its light blinks. Using the keyboard, find the Bluetooth option and select it. This is the RetroPie setup program, a blue menu with lots of text options. I mean, there isn't even an android client, and that has a far broader appeal.Then hit enter. I'm just saying I wouldn't be too optimistic and, if it were me, I wouldn't put a lot of effort into a niche like that without knowing it would turn out well. Mind you, it's possible that it might just squeak by. Not sure if homebrew kicks the firmware out of memory and does all the low-level work itself, but even so, that's an overly-tight fit. The entire PSP memory space is 32MB, and 8MB of that is normally reserved for the firmware to use. Oh, and I dunno how much of this is OS bloat, but on Windows, if I just run PICO-8 without doing anything with it, it needs 41MB of memory. Even simple math ops that are a single cycle in the fantasy console are dozens or worse on the host CPU.Īlso, I'm pretty sure zep relies on SDL, so unless PSP homebrew has an SDL implementation, that's a stumbling block too. PICO-8 hides some Lua ugliness with single-cycle (well, fantasy cycle) table lookups that actually cost hundreds or worse on the host processor. I realize that, conceptually, a 333MHz processor ought to be able to run a fantasy console that supposedly only runs at 4MiHz, but it's not that simple. Lua's a fun language and it's portrayed on PICO-8 as a fast one, but it's not actually very fast unless you're super careful about how you create new GC objects (or preferably don't) and how you reference tables. I'm not sure the PSP has the CPU bandwidth to run PICO-8.
0 kommentar(er)
