Pcsx2 Plugins Gsdx 890 Movies
Pcsx2 Plugins Gsdx 890 Movies List
Yeah, basically. I don't really change any other settings myself, but there might be other settings that other users might change depending on what renderer they're using so it might still be a good idea to have two separate.ini files. I mean even if those are the only two settings people change when switching renderers (there might be others like the HW Hacks, for example) it would still be a good idea to have two files IMO, because if you get users used to their IR setting or CRC Hack setting changing on a renderer switch, they might think all settings are saved on a per-renderer basis and it might lead to confusion if this is not the case.I do like your solution though, it takes care of my specific issue very quickly and simply.:):. Forking seems a bit extreme for such a small issue. Not sure how the developers would feel about that.
I don't want to have to use CLI commands or a third-party program to solve this issue. That seems unnecessary. Having.ini files for each renderer is not unheard of. That's how Dolphin does it.Fixing my issue would also fix the CRC Hack Level issue that you mentioned in without having to do much more than having two sets of variables like suggested.
I was actually making this request as it bugged me some time and would be part of your solution.The two parallel ini-Entries was something avih added after I posted. At least this is now the first time I saw it.The problem I would see is that somebody might request the same for different gpu adapters. If he is mobile he wants to use the internal gpu and lower IR and for sure no OGL but while he is connected he wants to have OGL and use his dedicated nvidia gpu.So I think to solve that issue internally you would need to implement some kind of profile system where you can declare different sets of settings and can switch between them by some gui elements. (I would like to mention again that pcsx2 frontents allow that - but sure who really likes 3rd party software?).
The problem I would see is that somebody might request the same for different gpu adapters. If he is mobile he wants to use the internal gpu and lower IR and for sure no OGL but while he is connected he wants to have OGL and use his dedicated nvidia gpu.That's exactly why I want two.ini files so that people can change any setting they want on a per-renderer setting, not just the settings we're talking about here.So I think to solve that issue internally you would need to implement some kind of profile system where you can declare different sets of settings and can switch between them by some gui elements.That sounds a bit more complicated than it needs to be. Per-renderer.ini files should be fine IMO. I don't know how pcsx2 read the ini files but if it's this way.read the ini which is in category1 and has key name something1(that's how autohotkey works),then how about using the existing keys(settings)and just duplicate them in the ini but place them in different categories.You're suggesting implementation details of a specific solution, but it's not even agreed that the problem needs solving, and even if it was agreed, it wasn't agreed which solution would be best.
Implementation details are relevant only after it's agreed that this problem needs solving and a solution was chosen, possibly from several solutions, and we're not there yet.The 'problem' is that he wants different set of configurations chosen according to whether the renderer is D3D or OGL.The problem with this problem is that it addresses only the OP's concerns, but one could easily imagine other cases where settings are desirable according to HW/SW renderer, or many other 'triggers'.But another problem is that even this is not really 'the problem'. More generally, and ultimately, what he wants is different settings per game. The different settings for D3D/OGL is just a compromise he's willing to take.PCSX2 in general (and specifically GSdx too) takes an approach where all the settings are configurable, but there are no per-game settings (except internally to fix game issues), as well as no 'dependent' settings (except the presets system, but that's not the same as this issue). PCSX2 is not likely to become a settings manager, and so is GSdx. It's just too much effort which could easily be implemented externally, like with 3rd party launchers.To manage different settings, or different settings per game, etc, one should use external tools. Or stick to a single set of settings and that's it.
I don't see why it should be an issue, but if it is, it's an issue with the front end which doesn't 'support' it.That is correct, it's a problem with support from the frontends. I did not mean to imply the issue was gzip compression itself or PCSX2's implementation of it, I'm truly sorry if that's the way it came across. I love PCSX2's gzip support.:)The problem with this problem is that it addresses only the OP's concerns, but one could easily imagine other cases where settings are desirable according to HW/SW renderer, or many other 'triggers'.What other settings did you think of that could be desirable if one is switching between a HW or SW renderer? Other than shader stuff, the hardware and software renderers essentially already have separate settings within GSdx.From what I can see, the only thing that would really be useful is different settings for the OpenGL and Direct3D hardware renderers. Although 's comment (what if someone gets OpenCL working really well) made me think that we should just make every renderer have its own.ini file, not just the OpenGL and Direct3D hardware renderers.
That way any renderer that might come along in the future has its own.ini file. This also takes care of your concern, of separate settings being desirable based on if it's a HW renderer or a SW renderer, even though like I said, I don't think that's needed since SW renderers basically have their own settings anyway.More generally, and ultimately, what he wants is different settings per game.
Pcsx2 Plugins Gsdx 890 Movies Free
The different settings for D3D/OGL is just a compromise he's willing to take.That's incorrect. What I want is different GSdx settings per renderer. My apologies if that's how it came across but I have little to no desire for per game settings to be implemented into the GUI. There's already a CLI switch that takes care of that particular need (-cfgpath) quite beautifully so I don't think its really necessary to have it exposed in the GUI. Although less technical users might find it handy.Per renderer.ini files, ladies and gentlemen. That's all I want.
GSdxOGL.ini and GSdxD3D.ini. My apologies if that's how it came acrossIt didn't, but I had to make an educated guess since you didn't really describe what the actual problem is.Per renderer.ini files, ladies and gentlemen. That's all I want. GSdxOGL.ini and GSdxD3D.ini.No. On its own no one would care how many ini files are used and for what. This 'solution' solves a problem which you have. And it might not be the best solution.Describe exactly what the problem is.
In which cases exactly you would you like the IR and CRC hacks to change when you change renderer, and why would you change renderer? Describe exactly what the problem is. In which cases exactly you would you like the IR and CRC hacks to change when you change renderer, and why would you change renderer?I thought I had done that in the OP. My apologies. The problem is that when I'm switching between the D3D11 hardware renderer and the OGL renderer (mostly for testing purposes), I have to go in and change my IR setting since performance tanks when I switch to the OGL renderer (yay AMD OGL support).
This makes testing that requires switching renderers slightly annoying and I'd rather have it where each renderer has its own IR value.Otherwise we need to support by game setting.Why would we need to support per game settings if we do per renderer settings? That seems like a slippery slope fallacy.
Hello everybody,I managed to get PCSX2 0.9.6 to run under Snow Leopard 10.6.5.Well this is nothing new for you guys, BUT:in this version of mine you can use the GSdx (DirectX Plugins of Gabet)!!!In the package you have three GSdx plugins:- GSdx 890 (MSVC 15.00 SSE3) 0.1.14- GSdx 890 (MSVC 15.00 SSE4.1) 0.1.14- GSdx 1611m (MSVC 15.00 SSE2) 0.1.15.