Template talk:Config: Difference between revisions

Jump to navigation Jump to search
m
Cleanup
No edit summary
m (Cleanup)
Line 21: Line 21:


::Sorry for the troubles that was caused, the 19121 edit wasn't intended to cause problems, but a merge error in my text editor broke many things... I'll commit it again when I figure out what is going on on my editor, and after this the template will be as was on 19121 but without the compatibility issues and without breaking any new introduced features... [[User:Jhonn|Jhonn]] 21:18, 21 June 2011 (CEST)
::Sorry for the troubles that was caused, the 19121 edit wasn't intended to cause problems, but a merge error in my text editor broke many things... I'll commit it again when I figure out what is going on on my editor, and after this the template will be as was on 19121 but without the compatibility issues and without breaking any new introduced features... [[User:Jhonn|Jhonn]] 21:18, 21 June 2011 (CEST)
== Virtual EFB ==
I have a quick question, and don't really know where to go with it. In r7626, and assuming beyond, there are some [http://img535.imageshack.us/img535/8610/efboptions.png new options]. Instead of EFB copies to ram/texture, it has checkboxes, "Virtual" and "Ram". There is nothing in the TODO on how to do this. How should this be shown? Should I just wait for the TODO to be updated? [[User:MaJoR|MaJoR]] 18:19, 26 June 2011 (CEST)
==22715 rollback==
This appears to have broken the config template on many pages.  Some attributes were in the page source, but were not showing up on the rendered page (something that, by my understanding, we're trying to avoid).  Many pages had a Graphics heading with no entries.  Feel free to undo my undo if there's a bigger project going on here that I'm not aware of. --[[User:Keller999|Keller999]] 09:02, 11 August 2011 (CEST)
:I'm reverting it back, the Native Mipmaps and Accurate Texture Cache options doesn't exist anymore on Dolphin, so I commented out these options on template source until we think in a solution (mantaining these options for reference in older revisions or dropping it at all). [[User:Jhonn|Jhonn]] 21:17, 11 August 2011 (CEST)
:Jhonn (or anyone up for some template fiddling), if you refer to the ratings template you'll see a method of generating categories for erroneous pages. I'd advise we revise the template to handle these options similarly until pages using them can be cleaned up.[[User:Kolano|Kolano]] 03:12, 12 August 2011 (CEST)
::The ratings template is using the same method that I've implemented here for handling errors (checking the input parameters with "if" and adding the pages using the outdated (or deprecated) parameters on their respective category), for the outdated entries, I was thinking in some way of putting them in a small spoiler (for reference of older revisions), but probably implementing this would cause other issues... Should we maintain it or drop at all? [[User:Jhonn|Jhonn]] 21:25, 12 August 2011 (CEST)
:::I would say that most users are using latest SVN (which the template is already being updated for) or 3.0.  The overhead of maintaining every possible old variable would be a lot of work for little payoff.  I'd suggest adding another section for Release 3.0 variables only, in spoiler form.  I would say any release before 3.0 is out of luck.  I may try to work up something in the template sandbox, we'll see what you think.  --[[User:Keller999|Keller999]] 07:29, 14 August 2011 (CEST)
:Just as a suggestion, keeping references for older revisions *only* when the games calls for it, meaning by this that the main pages, for example config and performance, should always be kept with cutting edge revisions and only when the game specifically calls for it, older revisions should be mentioned specifically on X game page needing those, of course this calls for a user looking to use X revision of dolphin for his favorite game.[[User:Otomo|Otomo]] 18:39, 12 August 2011 (CEST)


==Further improvements==
==Further improvements==
Line 86: Line 75:


::Thanks! --[[User:Keller999|Keller999]] 04:08, 17 August 2011 (CEST)
::Thanks! --[[User:Keller999|Keller999]] 04:08, 17 August 2011 (CEST)
==fpsforlimit ?==
There's a conflict with the current (and my proposed) Template:Config.  fpsforlimit is both in the current variables section and the "Pages with deprecated config template parameters" section.  I infer that fpsforlimit would indicate what FPS number should be set for FPS limiter, which is definitely still an option in Dolphin.  However, you could also argue that that information should be under Framelimit.  Is this an option we should keep?
In the meantime, I'm going to remove it from [[Template:Config/doc]] so that pages aren't being added to that category left and right.  We can alter [[Template:Config]] once we know which way we fall on this one. --[[User:Keller999|Keller999]] 07:56, 14 August 2011 (CEST)
It's still a valid config setting in recent Dolphin releases, so it should be kept. [[User:Kolano|Kolano]] 07:53, 15 August 2011 (CEST)
:: I propose that we merge fpsforlimit into framelimit, much in the same way realxfb has been merged into xfb.  Since the variables are basically a free-form text field, it would be simple to indicate what fps the game should be limited to either in framelimit or framelimit notes.  I also think that the variable 'fpsforlimit' is somewhat confusing, and may throw off novice wiki editors.  --[[User:Keller999|Keller999]] 22:07, 15 August 2011 (CEST)
::Two options are needed as they are separate options, one specifies the framelimit to set (Off,Auto,10-120) the other specifies to use FPS for limiting rather than the games internal frame rate. In theory, since I don't think "framelimit" will ever be relevant to compatibility, it could be dropped, but it's probably best to not get into such fine grained analysis of this (i.e. it would likely be painful to work out which settings are compatibility related vs not). [[User:Kolano|Kolano]] 22:27, 15 August 2011 (CEST)
:::Okay, then there's the confusion.  There are THREE options.  framelimit, limitbyfps, and fpsforlimit.  I totally agree that framelimit and limitbyfps need to stay.  I think that fpsforlimit overlaps with framelimit.  framelimit should be used to indicate Off, Auto, or 10-120.  fpsforlimit should be deprecated.  --[[User:Keller999|Keller999]]
:::Ah, now I see and agree. fpsforlimit should be deprecated, and limitbyfps preserved. [[User:Kolano|Kolano]] 22:45, 15 August 2011 (CEST)


==Skip EFB Access from CPU==
==Skip EFB Access from CPU==
This option was renamed from "EFB Access from CPU" to "Skip EFB Access from CPU", but the current config wasn't changed to align with such. I just got done aligning pages using the option as best I could, but we should rename the option here to prevent confusion and add it to the deprecated list.[[User:Kolano|Kolano]] 21:25, 16 August 2011 (CEST)
This option was renamed from "EFB Access from CPU" to "Skip EFB Access from CPU", but the current config wasn't changed to align with such. I just got done aligning pages using the option as best I could, but we should rename the option here to prevent confusion and add it to the deprecated list.[[User:Kolano|Kolano]] 21:25, 16 August 2011 (CEST)
:It seems to be a performance option, at the expense of compatibility, it can be mentioned it in the performance guide and nowhere else.[[User:Otomo|Otomo]] 21:49, 16 August 2011 (CEST)
:It seems to be a performance option, at the expense of compatibility, it can be mentioned it in the performance guide and nowhere else.[[User:Otomo|Otomo]] 21:49, 16 August 2011 (CEST)
=="Dolphin 3.0 Specific Settings" section deprecated==
According to GIT revision [http://code.google.com/p/dolphin-emu/source/detail?r=f2848b6a2554dd9bbd7ff91f45e1a8622882fda9 f2848b6a2554] (see the comments), the options of this section are back on the master branch since all texcache-rewrite work was moved to a new branch... Should we merge these options back on "Graphics" section? [[User:Jhonn|Jhonn]] 23:43, 24 August 2011 (CEST)
1,411

edits

Navigation menu