http://bugs.winehq.org/show_bug.cgi?id=10229
Summary: Serious Sam TSE 1.07 - network connection fails
Product: Wine
Version: 0.9.47.
Platform: PC-x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: wine-net
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: liquid.acid(a)gmx.net
Hi there,
I recently installed Serious Sam: The Second Encounter for some intense LAN
gaming experience with my friends. There were two linux boxes and 4 windows
boxes, me hosting the server.
The problem was that nobody could connect to the server. Connection attempts
always resulted in the error message "CRC error in DIFF" (explanation here:
http://forums.seriouszone.com/showthread.php?t=8556). This affected both the
windows boxes AND the other linux box.
If a windows box was hosting the server the other windows boxes could connect,
but the linux boxes couldn't (I have to look up the error message there).
The problem isn't related to the safedisc copy protection removal I had to do
to make the game run under wine. We double checked this by applying the removal
patch on the windows server and also on the clients (while the server was
uncracked), no difference at all.
This was all with SS TSE patched to the most recent offical version 1.07.
Now we somehow managed to evade the problem by updating to the public beta
patch 1.50 which let everyone connect to the linux server, again independent
from crack status of the clients. But we soon realized why the 1.50 patch was
marked beta. Network trouble en masse, resulting in highly instable connection,
spontaneous client drops and the server misbehaving (moving around the players
without the client pushing any buttons).
This problem exists both when running the server through wine or natively on a
windows box. Frankly, when running the 1.50 server on a linux box we
experienced fewer problems when running natively (speaks in favor of the linux
network capabilities *g*).
Now I'm asking how to analyze the problem. I don't get any network related
output on the console while wine is running, only a few things about D3D and
stuff, but nothing on network.
Going to attach some in-game logs when I have access to the server box again.
Thanks,
liquid
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=10023
Summary: Vaz Modular 3.03 OSS driver output broken.
Product: Wine
Version: 0.9.47.
Platform: Other
URL: http://www.software-technology.com
OS/Version: other
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-directx-dsound
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: a.hurst(a)shef.ac.uk
Using wine's OSS driver, Vaz Modular reports 'MME Device already in use' with
MME output selected, or 'Could not initialize DirectSound' with DirectSound
selected.
Both Vaz Modular's outputs work fine using Wine's ALSA driver.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=9465
Summary: WarCraft III causes OSS to emit loud noise
Product: Wine
Version: unspecified
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: test
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: sealage(a)gmail.com
Using WarCraft III, Wine 0.9.44 on OSS sound output, loud noise is emitted
regardless of the application outputting sound of any kind.
Using a wine built and run in place, 0.9.43 using OSS works as expected, as
does 0.9.44 ALSA. Of note may be that 0.9.43 ALSA does not output any sound at
all.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=11029
Summary: Black & White game does not respond to mouse clicks
Product: Wine
Version: 0.9.52.
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-directx-dinput
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: shacklein(a)gmail.com
Created an attachment (id=10026)
--> (http://bugs.winehq.org/attachment.cgi?id=10026)
WINEDEBUG=+dinput, on wine 0.9.52 with B&W v1.30. Several attempts to click to
start the first level were made
Black & White (original game, no expansion pack) does not respond to mouse
clicking. This happens with versions 1.00 (retail), 1.10 and 1.30.
I have tested so far with Wine versions 0.9.49 and 0.9.52. In both versions,
the game does not respond to mouse clicks, so it is completely unplayable.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=10951
Summary: Flashlight brightness in Half-Life 2: Episode 2
Product: Wine
Version: 0.9.52.
Platform: Other
OS/Version: other
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: wine-directx-d3d
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: atari(a)gabo.pl
Created an attachment (id=9881)
--> (http://bugs.winehq.org/attachment.cgi?id=9881)
windows screenshot
Flashlight in Half-Life 2: Episode 2 is not bright enough. It is much darker
then in Windows.
I attach 2 screenshots, from Windows and Wine for comparision
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=10684
Summary: Morrowind fails to restore pre-launch gamma
Product: Wine
Version: 0.9.50.
Platform: Other
OS/Version: other
Status: UNCONFIRMED
Severity: trivial
Priority: P4
Component: wine-directx-d3d
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: jschimke(a)gmail.com
TES: Morrowind fails to restore the display's gamma after exiting if it was
changed inside of the game. Have to use nvidia-settings to restore it after
testing.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=10620
Summary: PAF 5 help viewer hits unhandled page fault while
closing
Product: Wine
Version: 0.9.50.
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-shdocvw
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: rm.riches(a)verizon.net
Personal Ancestral File (PAF) 5 hits an unhandled page fault while closing the
help viewer if the viewer has navigated to around 10 topics or places in the
help documentation. The symptoms associated with this report have been visible
since at least Wine version 0.9.37 or 0.9.39. With some Wine versions it is
more (or less) difficult to reproduce the symptoms. Being as PAF's help viewer
didn't work at all until Wine version 0.9.32 and didn't work well until Wine
version 0.9.39, doing a git regression run would probably not be feasible.
To demonstrate the symptoms with Wine version 0.9.50, here's what I did:
1) Bring up PAF on a previously-created empty file (using the File->New
function). Also, install Wine Gecko.
2) Click on the yellow question mark in the toolbar.
3) Click on the first 10 topics (starting with "Introduction") in sequence,
letting the text paint each time.
4) Use the X/Linux window manager's menu to close the help window.
I plan to attach the log file from a run with environment variable WINEDEBUG
set to a value of "+mshtml,+shdocvw,+urlmon,+htmlhelp" in case that sheds light
on the problem.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=10437
Summary: Altium Designer crash
Product: Wine
Version: unspecified
Platform: Other
OS/Version: other
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: wine-gui
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: j.zolotarjov(a)gmail.com
I'll describe all my movements - step by step.
1. I installed latest (at the moment) wine-0.9.49 from sources on Fedora8.
2. I installed my application of interest - Altium Designer 6.7
3. Tried to run it wihtout luck.
4. Found in appDB some hints and installed using winetricks dcom98, fakeie6,
mdac28, corefonts, tahoma, cc580. All installations went well.
5. I tried to run Altium Designer again and it started, but crashed when trying
to open any file.
6. AppDB tells, that it was tested with wine-0.9.35. I decided to try it.
7. Uninstalled wine-0.9.49 and installed wine-0.9.35 from sources.
8. I did not change drive_c as it was installed previously with 0.9.49. Now
tried to run Altium Designer. And oh wonder! I can use it wihout any visible
problems.
9. I decided to find out - which version of wine caused the problem. I tried
one by one all versions from 0.9.35 to 0.9.43. Works just fine, except some
minor problems, which I can live with. The version, which causes problem is
0.9.44. All subsequent versions also have this problem.
Now to the description of behavior.
1. Starting the application like that wine "c:\Program Files\Altium Designer
6\DXP.exe"
2. I see splash screen and log of different components loading on it.
3. Application windows is opening and I can select to open or create new file.
4. On whatever type of file, this operation causes applcation to freese for 20
seconds, then I see in the wine log endless list of
err:region:CombineRgn Invalid rgn=(nil)
err:region:CombineRgn Invalid rgn=(nil)
err:region:CombineRgn Invalid rgn=(nil)
err:region:CombineRgn Invalid rgn=(nil)
err:region:CombineRgn Invalid rgn=(nil)
err:region:CombineRgn Invalid rgn=(nil)
err:region:CombineRgn Invalid rgn=(nil)
err:region:CombineRgn Invalid rgn=(nil)
This continues for 3-4 minutes.
After that I see in the wine log following:
And this all ends with at this point.
5. I tried to look at the sources, but as I am very new to wine, I could only
get to the source of this endless CombineRgn errors. It comes from
/dlls/gdi32/region.c file. Particularly function CombineRgn makes it. I could
not find a function, which calls this function.
This behavior is with all versions of wine from 0.9.44 to 0.9.49.
So at this point, I ask community to help solve this bug in wine.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=10539
Summary: Nocturne directx mode polygons are missing
Product: Wine
Version: 0.9.49.
Platform: Other
OS/Version: other
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: wine-directx
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: fuag155555(a)gmail.com
CC: fuag155555(a)gmail.com
When directx is enabled in nocturene (only way to make it play at acceptable
frame rates and resolutions) Polygons go missing on 70% of the actors, they are
transparent, this happens in directx 5, 6, and 7.
there are a lot of errors like this top bit repeating, i think the d3d_surface
errors are what are messing it up, but thats a blind guess on my part. This can
be tested via a demo, if anyone feels like takling this i can send them a copy
of the game as well.
.
.
.
fixme:d3d_surface:IWineD3DSurfaceImpl_BltZ (0x3606de0): Unsupp depthstencil
blit
fixme:d3d_surface:IWineD3DSurfaceImpl_UnlockRect Depth Stencil buffer locking
is not implemented
fixme:d3d_draw:drawPrimitive Using software emulation because manual fog
coordinates are provided
fixme:d3d_draw:drawPrimitive Using software emulation because manual fog
coordinates are provided
fixme:d3d_draw:drawPrimitive Using software emulation because manual fog
coordinates are provided
fixme:d3d_draw:drawPrimitive Using software emulation because manual fog
coordinates are provided
fixme:d3d_draw:drawPrimitive Using software emulation because manual fog
coordinates are provided
fixme:d3d_draw:drawPrimitive Using software emulation because manual fog
coordinates are provided
fixme:d3d_draw:drawPrimitive Using software emulation because manual fog
coordinates are provided
fixme:d3d_draw:drawPrimitive Using software emulation because manual fog
coordinates are provided
fixme:d3d_draw:drawPrimitive Using software emulation because manual fog
coordinates are provided
fixme:d3d_draw:drawPrimitive Using software emulation because manual fog
coordinates are provided
fixme:d3d_draw:drawPrimitive Using software emulation because manual fog
coordinates are provided
fixme:d3d_draw:drawPrimitive Using software emulation because manual fog
coordinates are provided
fixme:d3d_draw:drawPrimitive Using software emulation because manual fog
coordinates are provided
fixme:d3d_draw:drawPrimitive Using software emulation because manual fog
coordinates are provided
fixme:d3d_draw:drawPrimitive Using software emulation because manual fog
coordinates are provided
fixme:d3d_draw:drawPrimitive Using software emulation because manual fog
coordinates are provided
fixme:d3d_draw:drawPrimitive Using software emulation because manual fog
coordinates are provided
fixme:d3d_draw:drawPrimitive Using software emulation because manual fog
coordinates are provided
fixme:d3d_draw:drawPrimitive Using software emulation because manual fog
coordinates are provided
fixme:d3d_draw:drawPrimitive Using software emulation because manual fog
coordinates are provided
fixme:d3d_draw:drawPrimitive Using software emulation because manual fog
coordinates are
fixme:d3d_draw:drawPrimitive Using software emulation because manual fog
coordinates are
fixme:d3d_draw:drawPrimitive Using software emulation because manual fog
coordinates are
fixme:d3d_draw:drawPrimitive Using software emulation because manual fog
coordinates are
fixme:d3d_draw:drawPrimitive Using software emulation because manual fog
coordinates are
fixme:d3d_draw:drawPrimitive Using software emulation because manual fog
coordinates are
fixme:d3d_draw:drawPrimitive Using software emulation because manual fog
coordinates are
fixme:d3d_draw:drawPrimitive Using software emulation because manual fog
coordinates are
fixme:d3d:IWineD3DDeviceImpl_CreateAdditionalSwapChain The app requests more
than one ba
ck buffer, this can't be supported properly. Please configure the application
to use dou
ble buffering(=1 back buffer) if possible
fixme:d3d:IWineD3DDeviceImpl_CreateAdditionalSwapChain The app requests more
than one ba
ck buffer, this can't be supported properly. Please configure the application
to use dou
ble buffering(=1 back buffer) if possible
fixme:d3d:IWineD3DDeviceImpl_Release (0x4dc0ad8) Device released with resources
still bo
und, acceptable but unexpected
fixme:d3d:dumpResources Leftover resource 0x3606bd8 with type
1,WINED3DRTYPE_SURFACE
fixme:d3d:dumpResources Leftover resource 0x13ede0 with type
1,WINED3DRTYPE_SURFACE
fixme:d3d:dumpResources Leftover resource 0x13f9f8 with type
1,WINED3DRTYPE_SURFACE
err:d3d:IWineD3DDeviceImpl_Release Context array not freed!
fixme:d3d:IWineD3DDeviceImpl_Release (0xa6ecd68) Device released with resources
still bo
und, acceptable but unexpected
fixme:d3d:dumpResources Leftover resource 0x78555b0 with type
1,WINED3DRTYPE_SURFACE
fixme:d3d:dumpResources Leftover resource 0x4c2fe98 with type
1,WINED3DRTYPE_SURFACE
fixme:d3d:dumpResources Leftover resource 0x48ffe70 with type
1,WINED3DRTYPE_SURFACE
fixme:d3d:dumpResources Leftover resource 0xa24fe78 with type
1,WINED3DRTYPE_SURFACE
fixme:d3d:dumpResources Leftover resource 0x21fe68 with type
1,WINED3DRTYPE_SURFACE
fixme:d3d:dumpResources Leftover resource 0x8c9fea0 with type
1,WINED3DRTYPE_SURFACE
err:d3d:IWineD3DDeviceImpl_Release Context array not freed!
fixme:winmm:MMDRV_Exit Closing while ll-driver open
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.