On 27/02/07, Chris Robinson [EMAIL PROTECTED] wrote:
I thought it was added to the registry because Wine can't figure out the video
memory amount itself from OpenGL or X, and that allows the user to make it
report the proper amount (or at least, more proper). Before it was hard-coded
to 64MB.
Am Sonntag 25 Februar 2007 21:57 schrieb Rok Mandeljc:
Hey all,
Now, when the game is run with 64MB of VideoMemorySize, upon reaching
the same point, IDirectDrawImpl_CreateNewSurface returns
WINED3DERR_OUTOFVIDEOMEMORY (because of
IWineD3DDevice_GetAvailableTextureMem(iface) = _size check in
Rok Mandeljc wrote:
Hey all,
I've been experiencing an odd behavior in Baldur's Gate 2; when
VideoMemorySize registry key for wined3d is set to anything greater
than 64MB (69MB, actually), it stops before playing intro movie,
printing following line:
err:clipping:CLIPPING_UpdateGCRegion hVisRgn
Robert Shearman [EMAIL PROTECTED] writes:
CreateCompatibleDC should be made to fail if the CreateRectRgn call fails.
Yes, I committed a fix for that.
--
Alexandre Julliard
[EMAIL PROTECTED]
On Sunday 25 February 2007 03:36:02 pm Vitaliy Margolen wrote:
The memory size setting is only in registry because you should not touch
it in the first place.
I thought it was added to the registry because Wine can't figure out the video
memory amount itself from OpenGL or X, and that allows
Hey all,
I've been experiencing an odd behavior in Baldur's Gate 2; when
VideoMemorySize registry key for wined3d is set to anything greater
than 64MB (69MB, actually), it stops before playing intro movie,
printing following line:
err:clipping:CLIPPING_UpdateGCRegion hVisRgn is zero. Please
Submit proper bug report to Wine bugzilla.
The memory size setting is only in registry because you should not touch
it in the first place.
For any user support problems - use wine-users mailing list.
Vitaliy
Rok Mandeljc wrote:
Hey all,
I've been experiencing an odd behavior in Baldur's
