On 31/03/06, Stefan Dösinger stefandoesinger@gmx.at wrote:
fixme:d3d:IWineD3DDeviceImpl_SetRenderState >>>>>>>>>>>>>>>>> 500 from glStencilOp(...) @ device.c / 3809 fixme:d3d:IWineD3DDeviceImpl_SetRenderState >>>>>>>>>>>>>>>>> 500 from glStencilOp(...) @ device.c / 3809 fixme:d3d:IWineD3DDeviceImpl_SetRenderState >>>>>>>>>>>>>>>>> 500 from glStencilOp(...) @ device.c / 3809
These are harmless, they are fixmes from the direct3d initialization. Some render states aren't supported by wines d3d implementation, but when wined3d initializes, it sets them to the default value, which causes such messages. The last three fixmes are fixed in the current cvs version, and they are harmless too.
Unfortunately, no, that's not fixed yet. I suspect the problem is the three glGetIntegerv call slightly above that call, since they use constants only defined in OpenGL 2.0.