TRACE_(d3d_caps)("Hardware vertex shader version 3.0 enabled (NV_VERTEX_PROGRAM3)\n") TRACE_(d3d_caps)("Hardware pixel shader version 2.0 enabled (ARB_PROGRAM)\n") * Shader Model 2.0 requires at least 32 pixel shader constants */ TRACE_(d3d_caps)("Hardware pixel shader version 3.0 enabled (NV_FRAGMENT_PROGRAM2)\n") Src\VBox\Additions\WINNT\Graphics\Wine\wined3d\arb_program_shader.c PCaps->VertexShaderVersion = WINED3DVS_VERSION(3,0)
||*/ gl_info->limits.arb_ps_instructions VertexShaderVersion = WINED3DVS_VERSION(2,0) PCaps->PixelShaderVersion = WINED3DPS_VERSION(3,0) ||*/ gl_info->limits.arb_ps_instructions PixelShaderVersion = WINED3DPS_VERSION(2,0) If (/*(gl_info->supported & !gl_info->supported) Src\VBox\Additions\WINNT\Graphics\Wine\wined3d\glsl_shader.c: In addition to the 2 extensions listed above, there are numerous other extensions used by wined3d (in src\VBox\Additions\WINNT\Graphics\Wine\wined3d\directx.c) that are also not passed through to the guest, although I don’t know for sure what or if anything else is being broken by this.
I was able to get around this by commenting out the checks for these extensions in the wined3d files of the OSE, and rebuilding/reinstalling the win.x86 guest additions, however there do appear to be some compatability and performance issues with this (unsurprisingly). These extensions are used by wine to determine whether nvidia cards support Shader Model 3, and when it cannot detect these extensions in the guest, wined3d downgrades the capabilities it reports out to shader model 2.
#This game requires at least shader model 3.0 windows#
Using in my windows guest I was able to determine that both the NV_FRAGMENT_PROGRAM2 and NV_VERTEX_PROGRAM3 extensions were not supported in the guest despite being present on the host. I've been able to track down the problem to a lack of pass-through on OpenGL extensions used by wind3d.
0 kommentar(er)
