[Bug 7621] New: Fallout Tactics no longer starts up (worked in 0.9.31)

[Wine Bugs]

http://bugs.winehq.org/show_bug.cgi?id=7621

           Summary: Fallout Tactics no longer starts up (worked in 0.9.31)
           Product: Wine
           Version: 0.9.32.
          Platform: PC-x86-64
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: major
          Priority: P2
         Component: wine-directx
        AssignedTo: wine-bugs(a)winehq.org
        ReportedBy: martyspamtrap(a)comcast.net


Fallout Tactics had worked perfectly in the 0.9.31 release, but now it fails to
start up.  The application switches to full screen mode and then displays a
dialog box saying "C:\dev\phoenix\display\win32\win32window.cpp (873): **fatal
error**: Could not create display buffers".  After pressing ok, I get an
"Abnormal program termination" message from the MSVC runtime.  Clicking ok on
that shuts the app down.  I get the following output on my console where I ran Wine:

fixme:d3d:IWineD3DDeviceImpl_GetAvailableTextureMem (0x18d280) : stub,
simulating 64MB for now, returning 64MB left
fixme:ddraw:IDirectDrawImpl_SetCooperativeLevel (0x18c268)->((nil),00000008)
fixme:d3d:IWineD3DStateBlockImpl_Release Releasing primary stateblock
fixme:ddraw:IDirectDrawImpl_SetCooperativeLevel (0x18f300)->(0x20024,00000811)
err:ddraw:IDirectDrawSurfaceImpl_Release (0x18f640) Failed to uninit 3D
fixme:ddraw:IDirectDrawImpl_SetCooperativeLevel (0x18f300)->((nil),00000008)
fixme:d3d:IWineD3DStateBlockImpl_Release Releasing primary stateblock
fixme:d3d:IWineD3DDeviceImpl_Release (0x190980) Device released with resources
still bound, acceptable but unexpected
fixme:d3d:dumpResources Leftover resource 0x1d3cc0 with type 1,WINED3DRTYPE_SURFACE
err:d3d:IWineD3DDeviceImpl_Release Context array not freed!

I suspect the problem is in DirectDraw or D3D, but I don't know enough about
either to say for sure, so I'll file this under the DirectX category.

-- 
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.