I’m fairly sure the tutorial is for installing it from scratch, before it was included with clockwork OS. The current clockwork OS has it installed in a different directory to this tutorial.
Have a look at this post I made, and give the instruction a go.
Also check this too: (all from posts above)
(The extra neon switch I mentioned isn’t 100% necessary - but useful, since the newer versions of RA have access to the repositories that have cores that support additional neon instructions)
Right. So can you please let me know what you have done? If you can give me exactly what you typed; not just what you followed, but what you typed into your command line, we can go from there.
I have a feeling that your shortcut that you have in your homescreen is directing towards the old installation. If you scroll up you can see a few solutions.
But to be honest, if you just want 1.7.8 for the XMB interface, don’t bother. We will be here for another 20 posts getting it into a useable state. The resolution really isn’t suited to it. You’ll need to change the font, interface scaling, and goodness knows what else. I just fiddle and tinker by nature, and enjoy doing so. The other benefits are also great, eg AI on screen language recognition, but again, you will have to do a lot of fiddling that is far more difficult than what it takes to move a directory; not to mention things that inevitably “break” that you will need go find your own workarounds fo fix.
You’re not missing out on any performance gains sticking to 1.7.7.
Since I assume (maybe incorrectly!) that all the XMB settings and feature settings are stored in the Retroarch configs, is it worth trying to save the configuration files from your working install, and then using those on a clean install rather than trying to document all the steps required to create those configs?
Why RetroArch on GameShell don’t have “shader” option?
In my opinion, RA on any plantform should have the same functions and abilities.
I’m really confused.
In the event that features are added/removed between versions, I’d be careful with doing that. You can inadvertently break things.
Keeping a spare copy, and comparing sections that are similar and replacing them subjectively would be the best bet. That said, it shouldn’t be that difficult to just redo your config files from scratch.
The steps documented above are actually documenting how to do a clean install, including all of the assets etc to actually use XMB and other things. They just so happen to include how to update to the latest version of retroarch. Just copying the config file over to a stock setup unfortunately won’t give you the XMB interface. Think of it like putting a Ferrari steering wheel on a VW beetle, and expecting it to go faster.
As for the settings to make XMB look nice, I guess it’s more not many people use it, since the screen resolution is honestly a bit too small. Potentially I could upload my settings, but that would also include uploading the font I used, and instructions on how to install them etc. and would no doubt not be to everyone’s liking. (I enjoy squinting at tiny UIs)
@AznableMiao If you install/update the shader assets, you can use them. The stock installation doesn’t haven’t them installed to keep it lightweight and fast, I’m assuming.
That said, I remember reading somewhere that the initial choice of the screen for the Gameshell was made to be one that without using software, almost mimics the display of a retro game device.
It’s not a power horse machine, so honestly; don’t expect things to run smoothly with shaders. It probably isn’t worth your trouble. Consider using filters instead.
Finally, I managed to update RA, but now I have 1.7.9
And it doesn’t work with lima, screen just freezes
But works with FBturbo and gl driver set in RA settings. Any suggestions?
P.S. About changes I noticed: Core provided aspect ratio fixed with MAME games which have vertical screen orientation, now everything fits screen perfect again.
I just did everything completely manually, from a clean installation of 0.4, updating just the launcher.
You shouldn’t need to do any of the things I wrote below this. I’ll keep it here just in case.
You should have gotten a few prompts to stop/start services if you did it correctly.
Summary
Out of interest, when doing the first step, building the environment;
sudo apt-get build-dep retroarch
Did you try using this switch, as the verbose output suggested?
sudo apt-get build-dep retroarch --fix-missing
Also, before doing anything, try running:
sudo apt-get update
Perhaps also try running this too:
sudo apt-get install build-essential checkinstall
Don’t worry about enabling neon for now. I’m just doing a build from scratch on a freshly installed image. It gave this output:
Checking presence of predefined macro __ARM_NEON__ ... no
Build assumed that __ARM_NEON__ is defined, but it's not. Exiting ...
When I installed it, it was on my heavily tinkered image where a lot more instructions had been defined etc. You’re not missing out on much not having this.
@podmaz - I installed 1.7.9 on a fresh 0.4 installation today, and tried loading it using lima. With the default settings, it terminates immediately. This would be using the gl driver. Same thing happens with the glcore and video drivers.
Editing the config so that the video drivers are “sdl2” allows it to run.
You may need to specify the video scale as 1.0 to not have it zoomed in like crazy.
video_scale = "1.000000"
Changing it to “gl1” seemingly hangs on a black screen; however, upon pushing the assigned exit key, it will exit back to the launcher. Looks like you’ll need to define which output it’s going to for video.
Sure thing! Sorry for the delayed reply! Just had a “madfest” convention. I’ll put it up right away. Watch this space.
I had to put a drop box link - the character limit was hit trying to copy paste it here. Send a DM if you need this, like a year down the track, in case I take it down for auditing reasons.
This is the config file I made on a freshly installed CPI OS, freshly updated to 1.7.9 Retroarch. It is operational as of the 7th of October 2019.
For the record, everything was installed according to instructions on this page as of the 2nd of October 2019. If anyone can’t get it working, it’s possibly to do with user syntax errors.
Also, in this config, I haven’t optimised it in any way. Eg, Bi linear filtering is on, because I was experimenting with it. Also, I’m using the standard rgui menu driver; not the XMB, since it just run better for testing purposes. Don’t use this as a base line for a configuration. This is just here because @podmaz requested it.
@javelinface Tried your config everything is working now (except correct aspect ratio with “core provided” option on lima driver with some systems, same issue as always, but with fbturbo aspect ration on arcade vertical games now fine). I tried to find what is the difference with 1.7.7 config and why 1.7.9 is not loading with it but failed. Had to set up from scratch to make everything look as it was set up before.
P.S.: SCUMMVM core is working glitchy, something wrong with controls, pressing A (left mouse button) doesn’t do anything until you press it in some specific weird way simultaneously with down button