5 replies to this topic

[Suicide machine]

Since, I just got "corrected", I think it'd be a nice time to bring another matter - forcing settings from a level of graphics drivers. At the moment, if there is a case, where some setting can be forced from the level of graphical drivers (namely Vsync, Anisotropic Filtering or Anti-aliasing), most of pages tend to mark it as hackable. There are however also pages, that mark it as false - which, is actually what I personally prefer. However, as much as I like marking them as false (yup!), I feel like this is something we need to standardize. I'm not sure, if this is something that requires a poll - depends.

 

So, if a setting can be forced from the graphics drivers panel, should it be hackable or false? Why?

 

Whatever the result is - this leads me to a second problem. We should have a page with screenshots of Graphical Drivers Panels (Intel, AMD and nVidia) - unless we have something like this, already - in which case, I can't find it. Anyway, knowing how much less reliable forcing settings Catalyst Panel is, comparing to Nvidia's Control Panel - we should have informations about alternatives like RadeonPro in that page. Then we could (and should) make links from every note that states it can be forced from graphical drivers panel to such page.

 

Answering my questions and why I'd prefer false? Mainly because nearly every game can have these settings forced - which gives us a lot of hackable (not a very good reason, I know). And if a setting can be forced from a level of graphics drivers - one may ask, then what's the point in writing about how to edit config files of a game or enable a console and type something in it, etc. if most often than not - these solutions are more complicated than simply forcing one setting. Yes, I've seen multiple times on a forum of Thief, System Shock 2 and Dark Souls - how forced settings cause problems, but that won't stop anyone from trying them anyway. So my thought about it, would be to mark them as false and state in notes they can be forced from a level of graphics drivers. If not - hackable and same note will do.

[AussieGav]

I suggest:

Possible = can be enabled in menus or config files.
Hackable = works with external program including CCC.
Impossible = can cause problems even if it might be hackable.

[Nicereddy]

I think hackable is proper because the graphics driver panel is still technically a hack, false generally implies it's impossible/incredibly glitchy even with a hack. I do agree that a page on the Graphics Driver panels would be a really nice addition. Should we make separate pages for each company or have a single page with multiple sections?

[Mirh]

I think hackable is proper because the graphics driver panel is still technically a hack, false generally implies it's impossible/incredibly glitchy even with a hack. I do agree that a page on the Graphics Driver panels would be a really nice addition. Should we make separate pages for each company or have a single page with multiple sections?

i think that the each company solution is the best

because there you could also talk about tools like radeonpro, ati tray tools, alternative drivers (this would be awesome for sound cards too).. and so on

 

btw editing .ini files shouldn't be hackable?

[Suicide machine]

i think that the each company solution is the best

because there you could also talk about tools like radeonpro, ati tray tools, alternative drivers (this would be awesome for sound cards too).. and so on

Actually, to be honest, we have:

• http://pcgamingwiki.com/wiki/AMD_VISION_Engine_Control_Center
• http://pcgamingwiki.com/wiki/Graphics_Filtering#Forcing_Anisotropic_Filtering_via_AMD_Catalyst

All of this pages could use plenty of work, especially the ons from AMD.

 

btw editing .ini files shouldn't be hackable?

For me? It definitely should stay hackable, as it is.

[Nicereddy]

 

btw editing .ini files shouldn't be hackable?

This should definitely stay as hackable, since it's not a toggle in-game/in-launcher and therefore not officially supported.

 

 

Actually, to be honest, we have:

• http://pcgamingwiki.com/wiki/AMD_VISION_Engine_Control_Center
• http://pcgamingwiki.com/wiki/Graphics_Filtering#Forcing_Anisotropic_Filtering_via_AMD_Catalyst

I think we may want to think about creating a "Graphics Driver" section, e.g. Graphics Driver:AMD, Graphics Driver:NVIDIA, etc. However, there may be better solutions to this problem.

 

Creating a project page which lists all the pages we have/need-to-create that are relevant to Graphics Cards, etc. might be a good idea. We could do the same with Controllers and Emulation, since there's really not much organization for those either.