ilikecats/stk-code_catmod
1
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
6794670510
stk-code_catmod/data/graphical_restrictions.xml

42 lines
3.6 KiB
XML
Raw Normal View History

Added a config file which can be used to disable certain graphical options dependeing on card, os, driver version.
2014-11-14 18:06:54 -05:00
<?xml version="1.0"?>
<graphical-restrictions>
Avoid using fixed pipeline on newer intel graphics cards. The force legacy device graphics restriction is needed for ironlake graphics cards. But newer generations in pentium/celeron processors also are named just "Intel(R) HD Graphics" without any number. The newest drivers for ironlake graphics card is 8.15 and it's unlikely that it will get an update. So assume that all drivers older than 9.x are ironlake generation or that are too old to run STK anyway.
2017-02-17 15:23:22 -05:00
<card is="Intel(R) HD Graphics" os="windows" version="<9.0" disable="ForceLegacyDevice"/>
<card is="Intel(R) HD Graphics" os="windows" version="<9.0" disable="HighDefinitionTextures"/>
Add intel HD2000 to graphics restrictions. It's just slower HD3000 version, so disable the same features for it.
2017-02-17 13:50:50 -05:00
<card is="Intel(R) HD Graphics 2000" os="windows" disable="UniformBufferObject"/>
Disable srgb framebuffer for intel hd 2000 too
2017-10-11 14:53:49 -04:00
<card is="Intel(R) HD Graphics 2000" os="windows" disable="FramebufferSRGB"/>
Add intel HD2000 to graphics restrictions. It's just slower HD3000 version, so disable the same features for it.
2017-02-17 13:50:50 -05:00
<card is="Intel(R) HD Graphics 2000" os="windows" disable="HighDefinitionTextures"/>
Add advanced pipeline GR to hd3000
2015-01-22 19:00:05 -05:00
<card is="Intel(R) HD Graphics 3000" os="windows" disable="UniformBufferObject"/>
Add up-to-date restriction for hd3000 in windows
2017-10-10 23:25:28 -04:00
<card is="Intel(R) HD Graphics 3000" os="windows" disable="FramebufferSRGB"/>
Enable HD textures on newer intel graphics cards. It should work fine for intel HD4000 and newer, especially after recent memory management improvements in STK.
2017-02-17 13:44:28 -05:00
<card is="Intel(R) HD Graphics 3000" os="windows" disable="HighDefinitionTextures"/>
Add restriction for intel hd4600 on windows about compute shader Fix #1916
2017-02-17 00:52:50 -05:00
<card is="Intel(R) HD Graphics 4600" os="windows" disable="ComputeShader"/>
Fix #1793 by disabling global illumination on osx with intel graphics cards.
2015-02-19 00:21:37 -05:00
<card contains="Intel" os="osx" disable="GI"/>
Update graphics restrictions for mesa: - Increase version for sRGB-capable visual workaround because it doesn't look that it will be fixed anytime soon - Enable compute shaders because it works fine now - Enable texture compression because it works now too. Texture compression for intel should work fine also for older versions, but it's hard to say which one version is the first working one.
2016-05-03 15:45:43 -04:00
<card contains="Intel" os="linux" version="<11.2" disable="ComputeShader"/>
Fixed shadows and GI for mesa drivers. The check for GL_ARB_geometry_shader4 doesn't have sense at all because we don't use this extension and our geometry shaders use functionality which is available in core OpenGL 3.2. The reason that it wasn't working for older mesa versions must be a bug in mesa or maybe missing other functionality (but not GL_ARB_geometry_shader4). I checked it with mesa 11.2 and current git version and it works fine on intel, nouveau and with software rendering. It needs some testing because it potentially affects all drivers with OpenGL >= 3.2 on every platform. If someone could test it with Radeon drivers, I would be really happy to enable it in upcoming release, at least on linux.
2016-05-18 16:18:24 -04:00
<card contains="Intel" os="linux" version="<11.2" disable="GeometryShader"/>
Add a way to run STK without srgb framebuffer
2017-10-09 15:18:15 -04:00
<card contains="Intel" os="linux" disable="FramebufferSRGBWorkaround2"/>
Update graphics restrictions for mesa: - Increase version for sRGB-capable visual workaround because it doesn't look that it will be fixed anytime soon - Enable compute shaders because it works fine now - Enable texture compression because it works now too. Texture compression for intel should work fine also for older versions, but it's hard to say which one version is the first working one.
2016-05-03 15:45:43 -04:00
<card contains="Intel" os="linux" version="<11.2" disable="TextureCompressionS3TC"/>
<card contains="Intel" os="windows" disable="TextureCompressionS3TC"/>
<card contains="Intel" os="osx" disable="TextureCompressionS3TC"/>
Try graphical restrictions on nvidia old drivers
2014-11-14 21:10:23 -05:00
<card contains="NVIDIA" os="windows" version="<344.65" disable="BufferStorage"/>
Use graphic restrictions system for all CVS query
2015-01-06 17:46:36 -05:00
<card contains="NVIDIA" os="linux" version="<343.22" disable="BufferStorage"/>
<card contains="NVIDIA" disable="ShaderAtomicCounters"/>
<card contains="Mesa" os="linux" version="<10.3" disable="BufferStorage"/>
Add pop up for Mesa < 10.3
2015-01-20 16:50:39 -05:00
<card contains="Mesa" os="linux" version="<10.3" disable="DriverRecentEnough"/>
Fixed shadows and GI for mesa drivers. The check for GL_ARB_geometry_shader4 doesn't have sense at all because we don't use this extension and our geometry shaders use functionality which is available in core OpenGL 3.2. The reason that it wasn't working for older mesa versions must be a bug in mesa or maybe missing other functionality (but not GL_ARB_geometry_shader4). I checked it with mesa 11.2 and current git version and it works fine on intel, nouveau and with software rendering. It needs some testing because it potentially affects all drivers with OpenGL >= 3.2 on every platform. If someone could test it with Radeon drivers, I would be really happy to enable it in upcoming release, at least on linux.
2016-05-18 16:18:24 -04:00
<card contains="Mesa" os="linux" version="<11.2" disable="GeometryShader"/>
Update graphics restrictions for mesa: - Increase version for sRGB-capable visual workaround because it doesn't look that it will be fixed anytime soon - Enable compute shaders because it works fine now - Enable texture compression because it works now too. Texture compression for intel should work fine also for older versions, but it's hard to say which one version is the first working one.
2016-05-03 15:45:43 -04:00
<card contains="Mesa" os="linux" version="<11.2" disable="TextureCompressionS3TC"/>
Duplicate rule for gallium
2015-02-01 18:42:16 -05:00
<card contains="Gallium" os="linux" version="<10.3" disable="BufferStorage"/>
<card contains="Gallium" os="linux" version="<10.3" disable="DriverRecentEnough"/>
Fixed shadows and GI for mesa drivers. The check for GL_ARB_geometry_shader4 doesn't have sense at all because we don't use this extension and our geometry shaders use functionality which is available in core OpenGL 3.2. The reason that it wasn't working for older mesa versions must be a bug in mesa or maybe missing other functionality (but not GL_ARB_geometry_shader4). I checked it with mesa 11.2 and current git version and it works fine on intel, nouveau and with software rendering. It needs some testing because it potentially affects all drivers with OpenGL >= 3.2 on every platform. If someone could test it with Radeon drivers, I would be really happy to enable it in upcoming release, at least on linux.
2016-05-18 16:18:24 -04:00
<card contains="Gallium" os="linux" version="<11.2" disable="GeometryShader"/>
Update graphics restrictions for mesa: - Increase version for sRGB-capable visual workaround because it doesn't look that it will be fixed anytime soon - Enable compute shaders because it works fine now - Enable texture compression because it works now too. Texture compression for intel should work fine also for older versions, but it's hard to say which one version is the first working one.
2016-05-03 15:45:43 -04:00
<card contains="Gallium" os="linux" version="<11.2" disable="TextureCompressionS3TC"/>
Removed version number warning for Radeon cards on osx (since they have completely different version numbers).
2015-04-26 19:04:16 -04:00
<!-- On osx radeon appears to have different version numbers, e.g.
1.32.20 -->
<card contains="Radeon" os="linux" version="<14.300" disable="DriverRecentEnough"/>
<card contains="Radeon" os="windows" version="<14.300" disable="DriverRecentEnough"/>
Fix warning for cards without "Radeon" in string (#2523)
2016-06-21 19:38:44 -04:00
<card contains="ATI" os="windows" version="<14.300" disable="DriverRecentEnough"/>
Fixed typo in previous commit.
2016-08-20 02:35:08 -04:00
<card contains="ATI" os="windows" version="<=3.1.8787" disable="ForceLegacyDevice"/>
Add a graphics restriction for BGRA format on android. It causes issues with particles transparency.
2016-09-16 19:26:52 -04:00
<card os="android" disable="TextureFormatBGRA8888"/>
Restore SSAO on linux with GLES renderer.
2016-09-16 21:46:35 -04:00
<card os="android" disable="ColorBufferFloat"/>
Add a workaround for some qualcomm devices on android 4.4
2017-07-10 18:37:31 -04:00
<card contains="Adreno" os="android" version="<=19" disable="VertexIdWorking"/>
GLES: Make sure that we are using fixed pipeline when force legacy device is set in graphics restrictions. It is generally safe for GLES drivers. The driver often reports OpenGL ES 3.1 or 3.0 support even though we request only GLES 2.0. But we can still use GLES 2.0 / GLSL 1.0 functions on GLES 3.x context, so it shouldn't cause any issues. I also added Android Emulator to graphics restrictions.
2016-12-29 10:00:02 -05:00
<card contains="Android Emulator" os="android" disable="ForceLegacyDevice"/>
Add a possibility to use ubo on gles. Disabled by default on android, because it's been tested on only one device and it's a bit slower in most cases.
2017-08-21 18:02:34 -04:00
<card os="android" disable="UniformBufferObject"/>
Added a config file which can be used to disable certain graphical options dependeing on card, os, driver version.
2014-11-14 18:06:54 -05:00
</graphical-restrictions>
Reference in New Issue Copy Permalink