keltoigael Posted February 24, 2015 Share Posted February 24, 2015 Currently running the beta 1.0.0.3 of retroarch just so I can run the advance shaders and new cores. I have never had an issue with crt royale before, I used to run it on a nightly build before I even ever tried the official 1.0.0.2 version. For some weird reason, every time I make changes to the settings via menu, none of the changes I make stick. It wont even save my custom settings via the save as menu. Never had this happen before. It is consistent, I have even went back to deleted core.cfgs, deleting the shader "shaders/crt/" path out of retroarch.cfg and it happens every darn time. I even edited the system.dll.gdp files with the settings I want and it still wont show them. Is there something I am missing? Link to comment Share on other sites More sharing options...
Awakened Posted February 24, 2015 Share Posted February 24, 2015 I never use the menu for changing shader settings. I prefer to edit them in the shader's files myself. I never have any issues with things not sticking that way. For Royale, all it's settings can be handled by editing the user-settings.h file in it's folder. After opening that in your text editor of choice, change: #define RUNTIME_SHADER_PARAMS_ENABLE to //#define RUNTIME_SHADER_PARAMS_ENABLE That disables changing this shader's settings from the menu. It makes the shader run better too. Now all your settings are handled in the user-settings.h file. Basically, any line in that file that doesn't have a // in front of it is a setting you can change, and there's documentation above each one describing what they do. Link to comment Share on other sites More sharing options...
keltoigael Posted February 24, 2015 Author Share Posted February 24, 2015 I never use the menu for changing shader settings. I prefer to edit them in the shader's files myself. I never have any issues with things not sticking that way. For Royale, all it's settings can be handled by editing the user-settings.h file in it's folder. After opening that in your text editor of choice, change:#define RUNTIME_SHADER_PARAMS_ENABLE to //#define RUNTIME_SHADER_PARAMS_ENABLE That disables changing this shader's settings from the menu. It makes the shader run better too. Now all your settings are handled in the user-settings.h file. Basically, any line in that file that doesn't have a // in front of it is a setting you can change, and there's documentation above each one describing what they do. Holy moly! Never knew that, thanks man. This should certainly fix the issue. I will try it out tonight after work. Link to comment Share on other sites More sharing options...
keltoigael Posted February 24, 2015 Author Share Posted February 24, 2015 Hmm, I enabled the //#define RUNTIME_SHADER_PARAMS_ENABLE and now I just get a black screen. Havent changed any other settings yet. Link to comment Share on other sites More sharing options...
Awakened Posted February 24, 2015 Share Posted February 24, 2015 You can try opening a file from the crt-royale-settings-files folder with the name of whatever graphics you have (intel, nvidia, or ati/amd). Then copy the contents of that and paste it over everything in your user-settings.h. Then add the // to the beginning of that line again and see if it works. Link to comment Share on other sites More sharing options...
keltoigael Posted February 25, 2015 Author Share Posted February 25, 2015 Do I over write from Driver Capabilities to the bottom, User code path option or User Parameters? Link to comment Share on other sites More sharing options...
keltoigael Posted February 25, 2015 Author Share Posted February 25, 2015 Idk why but, when ever I enable the //#define RUNTIME_SHADER_PARAMS_ENABLE I just get a black screen. If I disable it, it works but will not accept changes. Such a weird predicament. This is one of two different PC's so it isn't pertained to just the one. I am using 1.0.0.3 beta x64, not a nightly. I am currently trying both GL and D3D video driver settings. If that fails, maybe I should try the x86 version even though I am on 7 64. Link to comment Share on other sites More sharing options...
keltoigael Posted February 25, 2015 Author Share Posted February 25, 2015 *Update* Switched over the x86 build and everything seems to be working as should. I was able to manually edit in the settings I wanted via the command you listed. I guess I will avoid the x64 build until official release. No idea what the conflict is or why the x64 would give a black screen and the x86 wouldn't. *shrugs* Link to comment Share on other sites More sharing options...
vampirolatino2 Posted February 25, 2015 Share Posted February 25, 2015 Hi! I had the same problems. I think the Nightly files of x64 fixed that ... I don't remember but I sure had those same exact issues I have it working on more than 10 systems now, more to come. I like the flexibility of changing things on the fly. Bezels. Shaders. Core options. Controls. I think I have used in the Consoles systems, to use the Xbox 360 controler better (can power on the controler AFTER the emulator)... this is a BIG PLUS!! Link to comment Share on other sites More sharing options...
Awakened Posted February 25, 2015 Share Posted February 25, 2015 *Update*Switched over the x86 build and everything seems to be working as should. I was able to manually edit in the settings I wanted via the command you listed. I guess I will avoid the x64 build until official release. No idea what the conflict is or why the x64 would give a black screen and the x86 wouldn't. *shrugs* That's quite strange, but at least you found something that lets you edit your settings. 32bit builds are somewhat limited, no PPSSPP core and Mupen64 32bit crashed the last time I tried it. Hopefully a nightly like vampirolatino2 suggests or 1.1 when that comes out fixes 64bit for you if you want to use those cores. The latest nightlies have a problem with hardware sampling in Royale, which I like to use with the shadow mask option, so I'm trying out crt-easymode as my default for a bit. Since it's a single pass shader it starts up much faster, but I'm not quite used to how much darker it is yet... Link to comment Share on other sites More sharing options...
keltoigael Posted February 26, 2015 Author Share Posted February 26, 2015 That's quite strange, but at least you found something that lets you edit your settings. 32bit builds are somewhat limited, no PPSSPP core and Mupen64 32bit crashed the last time I tried it. Hopefully a nightly like vampirolatino2 suggests or 1.1 when that comes out fixes 64bit for you if you want to use those cores. The latest nightlies have a problem with hardware sampling in Royale, which I like to use with the shadow mask option, so I'm trying out crt-easymode as my default for a bit. Since it's a single pass shader it starts up much faster, but I'm not quite used to how much darker it is yet... Does anyone know of a recommended nightly x64 build that works with the royale shader? I was thinking about checking out CRT Easymode, from the screens I saw I didn't care for the darkness like you mentioned. I am sure it can be adjusted. If you find a good setting could you take a screen and post your settings? Thanks! Link to comment Share on other sites More sharing options...
Awakened Posted February 26, 2015 Share Posted February 26, 2015 The last nightly that didn't have the issue I mentioned was 2015-02-18. I tried some modifications to easymode, but so far I like how it looks with defaults. Here are a few shots: Diddy Kong Racing - http://abload.de/img/retroarch-0226-1342048lu5j.png Ninja Gaiden II - http://i.imgur.com/cuLQoGh.png Holy Umbrella - http://i.imgur.com/iwlLmuN.png Sonic 2 Beta - http://i.imgur.com/uTQlSkl.png Rayforce - http://abload.de/img/retroarch-0226-1347474wu2r.png Ibara - http://abload.de/img/retroarch-0226-134919k6utf.png Gunbird 2 - http://abload.de/img/retroarch-0226-1349441kuyj.png Link to comment Share on other sites More sharing options...
keltoigael Posted February 26, 2015 Author Share Posted February 26, 2015 Sonic 2 Beta really pops with that shader Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.