[Bug 12060] New: Three bugs in MilkDrop Visualization in WinAMP 5.5.2

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

Summary: Three bugs in MilkDrop Visualization in WinAMP 5.5.2
           Product: Wine
           Version: CVS/GIT
          Platform: PC
               URL: http://download.nullsoft.com/winamp/client/winamp552_ful
                    l_en-us.exe
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: directx-d3d
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]

Created an attachment (id=11432)
 --> (http://bugs.winehq.org/attachment.cgi?id=11432)
The way it looks like (red lines are painted intentionally)

1) Direct3D window is not placed withing its parent window

2) Some visualizations cause Direct3D window to be split weirdly (vertically by
two regions, then left region is split into two, and so on).

3) F1 button which has to show a help window within Direct3D window shows
garbage

Screenshot is attached.

[Bug 12060] Three bugs in MilkDrop Visualization in WinAMP 5.5.2

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

--- Comment #1 from Artem S. Tashkinov   2008-03-16 08:31:40 ---
In full screen mode keyboard doesn't work at all.

[Bug 12060] Three bugs in MilkDrop Visualization in WinAMP 5.5.2

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

Artem S. Tashkinov  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |download

[Bug 12060] Three bugs in MilkDrop Visualization in WinAMP 5.5.2

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

--- Comment #2 from Lei Zhang   2008-03-16 11:40:37 ---
One bug per report please. Can you file a separate bug report for each problem?

It may be helpful to have screenshots from Windows for comparison.

[Bug 12060] Direct3D window is not placed withing its parent window

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

Artem S. Tashkinov  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Three bugs in MilkDrop      |Direct3D window is not
                   |Visualization in WinAMP     |placed withing its parent
                   |5.5.2                       |window

--- Comment #3 from Artem S. Tashkinov   2008-03-19 13:18:10 ---
OK, now this bug report should be read:

When running MilkDrop visualization in WinAMP, Direct3D window is not placed
withing its parent window.

See the attached screenshot.

[Bug 12060] Direct3D window is not placed withing its parent window

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

Artem S. Tashkinov  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

[Bug 12060] Direct3D window is not placed withing its parent window

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

--- Comment #4 from Roderick Colenbrander   2008-03-20 10:28:08 ---
Let me guess you are using either DRI drivers (intel, ati ..) or ATI's drivers?
If  so these drivers don't have proper GLX + XComposite support yet which
causes this issue. If this is indeed the case then the issue is a driver bug
and not a Wine one. Nvidia should work fine BTW.

[Bug 12060] Direct3D window is not placed withing its parent window

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

--- Comment #5 from Artem S. Tashkinov   2008-03-20 13:36:14 ---
Created an attachment (id=11516)
 --> (http://bugs.winehq.org/attachment.cgi?id=11516)
xorg.conf and glxinfo output

I'm not using composite window manager at all, though I have composite
extension enabled in my X.org configuration.

X Window System Version 1.3.0
Release Date: 19 April 2007
X Protocol Version 11, Revision 0, Release 1.3
Build Operating System: Fedora 8 Red Hat, Inc.
Current Operating System: Linux localhost.localdomain 2.6.24.3-k8l #1 SMP
PREEMPT Sat Mar 1 01:19:39 YEKT 2008 i686
Build Date: 12 February 2008
Build ID: xorg-x11-server 1.3.0.0-42.fc8
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
Module Loader present

[Bug 12060] Direct3D window is not placed withing its parent window

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

--- Comment #6 from Austin English   2008-12-30 09:59:40 ---
Is this still an issue in current (1.1.11 or newer) wine?

[Bug 12060] Direct3D window is not placed withing its parent window

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

--- Comment #7 from Artem S. Tashkinov   2008-12-30 11:50:57 ---
Nothing has changed in the newer Wine release.

[Bug 12060] Direct3D window is not placed withing its parent window

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

Artem S. Tashkinov  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
           Platform|PC                          |All
            Version|CVS/GIT                     |0.9.56.

[Bug 12060] Direct3D window is not placed withing its parent window

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

Vitaliy Margolen  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
           Platform|All                         |PC

[Bug 12060] Direct3D window is not placed withing its parent window

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

--- Comment #8 from Artem S. Tashkinov   2009-12-08 10:56:40 ---
Created an attachment (id=25127)
 --> (http://bugs.winehq.org/attachment.cgi?id=25127)
Milkdrop appearance in wine 1.1.34

Wine 1.1.34 is no different.

[Bug 12060] Direct3D window is not placed withing its parent window

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

--- Comment #9 from Artem S. Tashkinov   2010-05-25 16:30:34 ---
Created an attachment (id=28285)
 --> (http://bugs.winehq.org/attachment.cgi?id=28285)
WinAmp MilkDrop error in Wine (pixelshader 3.0)

In new Wine releases MilkDrop plugin for WinAMP doesn't work at all:

fixme:d3dx:D3DXCompileShader (0x11864a8, 4086, (nil), (nil), 0x7c9d8dc,
0x11c4f60, 65536, 0x11c4f30, 0x7da3f10, 0x7da4298): stub

At first Milkdrop says: "Error compiling ps_2_0 warp shader" then this error
window appears.

I'm running the latest released NVIDIA proprietary drivers:

OpenGL version string: 3.2.0 NVIDIA 195.36.24

[Bug 12060] Direct3D window is not placed withing its parent window

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

joaopa  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #10 from joaopa   2010-05-26 00:03:10 ---
To workaroud this crash, use a native d3dx9_36.

[Bug 12060] Direct3D window is not placed withing its parent window

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

Artem S. Tashkinov  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #11432|0                           |1
        is obsolete|                            |
  Attachment #25127|0                           |1
        is obsolete|                            |

--- Comment #11 from Artem S. Tashkinov   2010-05-26 01:46:16 ---
Created an attachment (id=28291)
 --> (http://bugs.winehq.org/attachment.cgi?id=28291)
WinAmp's windowed MilkDrop appearance in Wine 1.2-rc1

(In reply to comment #10)
> To workaroud this crash, use a native d3dx9_36.

Thank you, with this library Milkdrop works, bug then the bug persists.

[Bug 12060] Direct3D window is not placed withing its parent window

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

Bruno Jesus  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                URL|http://download.nullsoft.co |http://www.filehippo.com/do
                   |m/winamp/client/winamp552_f |wnload_winamp/5535/
                   |ull_en-us.exe               |
                 CC|                            |[e-mail]

--- Comment #12 from Bruno Jesus  2012-01-23 17:41:54 CST ---
Artem, can you retry this? It looks better in 1.3.37 than your last screenshot.

[Bug 12060] Direct3D window is not placed withing its parent window

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

--- Comment #13 from Artem S. Tashkinov  2012-01-23 18:35:31 CST ---
Created attachment 38519
  --> http://bugs.winehq.org/attachment.cgi?id=38519
MilkDrop in Wine 1.3.37

(In reply to comment #12)
> Artem, can you retry this? It looks better in 1.3.37 than your last screenshot.

Nay, no changes at all.

[Bug 12060] Direct3D window is not placed withing its parent window

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

--- Comment #14 from joaopa  2012-11-03 15:49:13 CDT ---
still a bug in current wine?

[Bug 12060] Direct3D window is not placed withing its parent window

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

--- Comment #15 from Artem S. Tashkinov  2012-11-04 04:20:41 CST ---
(In reply to comment #14)
> still a bug in current wine?

Yep, I won't post a screenshot this time.

Install and run WinAamp yourself - it takes like 3 minutes tops.

[Bug 12060] Direct3D window is not placed withing its parent window

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

--- Comment #16 from Artem S. Tashkinov  2013-06-19 16:32:07 CDT ---
MilkDrop no longer works in Wine (1.6-rc2):

fixme:win:EnumDisplayDevicesW ((null),0,0x1fcb8c8,0x00000000), stub!
fixme:d3d9:Direct3DShaderValidatorCreate9 stub
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.

[Bug 12060] Direct3D window is not placed withing its parent window

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

[e-mail] changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #17 from [e-mail] ---
I also get "Error compiling ps_2_0 warp shader" error

Then it says that your hardware supports but maybe your drivers are broken (not
exact these words,but this is the message).

wine 1.7.22

[Bug 12060] Direct3D window is not placed withing its parent window

https://bugs.winehq.org/show_bug.cgi?id=12060

[e-mail] changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #18 from [e-mail] ---
Created attachment 51604
  --> https://bugs.winehq.org/attachment.cgi?id=51604
Picture of Winamp visualization not in parent window

Bug still exists with wine-1.7.43, Fedora 21. Installed like so:

$ wget raw.githubusercontent.com/Winetricks/winetricks/master/src/winetricks
$ chmod +x winetricks
$ WINEARCH='win32' sh winetricks comctl32 wininet ie6 allfonts allfonts wmp9
d3dx9_36
$ wget winampplugins.co.uk/Winamp/winamp5666_full_en-us_redux.exe
$ wine winamp5666_full_en-us_redux.exe

[Bug 12060] Direct3D window is not placed withing its parent window

https://bugs.winehq.org/show_bug.cgi?id=12060

--- Comment #19 from [e-mail] ---
This issue still occurs on wine 2.14; however, the workaround is:

Winamp > Options > Preferences... > Plug-ins > Visualization > MilkDrop v2.25c
> Configure > WINDOWED settings > Uncheck Integrate with winamp skin

Obviously it doesn't look as nice as with the native skin, but at least it
doesn't look bad (and fullscreen looks splendid!).

Full build instructions:

$ wget
https://raw.githubusercontent.com/Winetricks/winetricks/master/src/winetrick...
$ chmod +x winetricks 
$ ./winetricks -q directmusic directplay directx9 gdiplus ie8 mfc42 wmp10
windowmanagerdecorated=n
$ ./winetricks winamp

Right click Winamp > Options > Preferences... > General Preferences > Playlist
> select Use font: MS Sans Serif

[Bug 12060] Direct3D window is not placed withing its parent window

https://bugs.winehq.org/show_bug.cgi?id=12060

--- Comment #20 from joaopa  ---
Still a bug in current wine (3.11) ?

[Bug 12060] Direct3D window is not placed withing its parent window

https://bugs.winehq.org/show_bug.cgi?id=12060

--- Comment #21 from Artem S. Tashkinov  ---
(In reply to joaopa from comment #20)
> Still a bug in current wine (3.11) ?

Cannot test due to bug 45370.

[Bug 12060] Direct3D window is not placed withing its parent window

https://bugs.winehq.org/show_bug.cgi?id=12060

--- Comment #22 from Artem S. Tashkinov  ---
(In reply to joaopa from comment #20)
> Still a bug in current wine (3.11) ?

Windowed Milkdrop doesn't work at all in Wine 3.11 (empty window) but this bug
is also valid.

[Bug 12060] Direct3D window is not placed withing its parent window

https://bugs.winehq.org/show_bug.cgi?id=12060

Artem S. Tashkinov  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
         Depends on|                            |45370

[Bug 12060] Direct3D window is not placed withing its parent window

https://bugs.winehq.org/show_bug.cgi?id=12060

--- Comment #23 from Artem S. Tashkinov  ---
002d:fixme:msg:ChangeWindowMessageFilter c03d 00000001
002d:fixme:msg:ChangeWindowMessageFilter 323 00000001
002d:fixme:msg:ChangeWindowMessageFilter 326 00000001
002d:fixme:msg:ChangeWindowMessageFilter 111 00000001
002d:fixme:dwmapi:DwmSetWindowAttribute (0x10050, 7, 0x86d370, 4) stub
002d:fixme:heap:RtlSetHeapInformation 0x1580000 0 0x86ac2c 4 stub
003c:fixme:win:EnumDisplayDevicesW ((null),0,0x248cce8,0x00000000), stub!
003c:fixme:dwmapi:DwmInvalidateIconicBitmaps (0x10050) stub
003c:fixme:d3d9:Direct3DShaderValidatorCreate9 stub
003d:fixme:d3d_shader:print_glsl_info_log Info log received from GLSL shader
#8:
003d:fixme:d3d_shader:print_glsl_info_log     Vertex info
003d:fixme:d3d_shader:print_glsl_info_log     -----------
003d:fixme:d3d_shader:print_glsl_info_log     0(22) : warning C7050:
"vs_out[1].zw" might be used before being initialized
003d:fixme:d3d_shader:print_glsl_info_log     0(22) : warning C7050:
"vs_out[2]" might be used before being initialized
003d:fixme:d3d_shader:print_glsl_info_log     0(22) : warning C7050:
"vs_out[3]" might be used before being initialized
003d:fixme:d3d_shader:print_glsl_info_log     0(22) : warning C7050:
"vs_out[4]" might be used before being initialized
003d:fixme:d3d_shader:print_glsl_info_log     0(22) : warning C7050:
"vs_out[5]" might be used before being initialized
003d:fixme:d3d_shader:print_glsl_info_log     0(22) : warning C7050:
"vs_out[6]" might be used before being initialized
003d:fixme:d3d_shader:print_glsl_info_log     0(22) : warning C7050:
"vs_out[7]" might be used before being initialized
003d:fixme:d3d_shader:print_glsl_info_log     0(22) : warning C7050:
"vs_out[9]" might be used before being initialized
003d:fixme:d3d_shader:print_glsl_info_log     0(22) : warning C7050:
"vs_out[11]" might be used before being initialized
003d:fixme:d3d_shader:print_glsl_info_log Info log received from GLSL shader
#12:
003d:fixme:d3d_shader:print_glsl_info_log     Vertex info
003d:fixme:d3d_shader:print_glsl_info_log     -----------
003d:fixme:d3d_shader:print_glsl_info_log     0(22) : warning C7050:
"vs_out[0].zw" might be used before being initialized
003d:fixme:d3d_shader:print_glsl_info_log     0(22) : warning C7050:
"vs_out[1].zw" might be used before being initialized
003d:fixme:d3d_shader:print_glsl_info_log     0(22) : warning C7050:
"vs_out[2]" might be used before being initialized
003d:fixme:d3d_shader:print_glsl_info_log     0(22) : warning C7050:
"vs_out[3]" might be used before being initialized
003d:fixme:d3d_shader:print_glsl_info_log     0(22) : warning C7050:
"vs_out[4]" might be used before being initialized
003d:fixme:d3d_shader:print_glsl_info_log     0(22) : warning C7050:
"vs_out[5]" might be used before being initialized
003d:fixme:d3d_shader:print_glsl_info_log     0(22) : warning C7050:
"vs_out[6]" might be used before being initialized
003d:fixme:d3d_shader:print_glsl_info_log     0(22) : warning C7050:
"vs_out[7]" might be used before being initialized
003d:fixme:d3d_shader:print_glsl_info_log     0(22) : warning C7050:
"vs_out[9]" might be used before being initialized
003d:fixme:d3d_shader:print_glsl_info_log     0(22) : warning C7050:
"vs_out[11]" might be used before being initialized
003d:fixme:d3d_shader:print_glsl_info_log Info log received from GLSL shader
#18:
003d:fixme:d3d_shader:print_glsl_info_log     Vertex info
003d:fixme:d3d_shader:print_glsl_info_log     -----------
003d:fixme:d3d_shader:print_glsl_info_log     0(22) : warning C7050:
"vs_out[0].zw" might be used before being initialized
003d:fixme:d3d_shader:print_glsl_info_log     0(22) : warning C7050:
"vs_out[1]" might be used before being initialized
003d:fixme:d3d_shader:print_glsl_info_log     0(22) : warning C7050:
"vs_out[2]" might be used before being initialized
003d:fixme:d3d_shader:print_glsl_info_log     0(22) : warning C7050:
"vs_out[3]" might be used before being initialized
003d:fixme:d3d_shader:print_glsl_info_log     0(22) : warning C7050:
"vs_out[4]" might be used before being initialized
003d:fixme:d3d_shader:print_glsl_info_log     0(22) : warning C7050:
"vs_out[5]" might be used before being initialized
003d:fixme:d3d_shader:print_glsl_info_log     0(22) : warning C7050:
"vs_out[6]" might be used before being initialized
003d:fixme:d3d_shader:print_glsl_info_log     0(22) : warning C7050:
"vs_out[7]" might be used before being initialized
003d:fixme:d3d_shader:print_glsl_info_log     0(22) : warning C7050:
"vs_out[8]" might be used before being initialized
003d:fixme:d3d_shader:print_glsl_info_log     0(22) : warning C7050:
"vs_out[9]" might be used before being initialized
003d:fixme:d3d_shader:print_glsl_info_log     0(22) : warning C7050:
"vs_out[11]" might be used before being initialized
003d:fixme:d3d_shader:print_glsl_info_log Info log received from GLSL shader
#21:
003d:fixme:d3d_shader:print_glsl_info_log     Vertex info
003d:fixme:d3d_shader:print_glsl_info_log     -----------
003d:fixme:d3d_shader:print_glsl_info_log     0(22) : warning C7050:
"vs_out[0].zw" might be used before being initialized
003d:fixme:d3d_shader:print_glsl_info_log     0(22) : warning C7050:
"vs_out[1]" might be used before being initialized
003d:fixme:d3d_shader:print_glsl_info_log     0(22) : warning C7050:
"vs_out[2]" might be used before being initialized
003d:fixme:d3d_shader:print_glsl_info_log     0(22) : warning C7050:
"vs_out[3]" might be used before being initialized
003d:fixme:d3d_shader:print_glsl_info_log     0(22) : warning C7050:
"vs_out[4]" might be used before being initialized
003d:fixme:d3d_shader:print_glsl_info_log     0(22) : warning C7050:
"vs_out[5]" might be used before being initialized
003d:fixme:d3d_shader:print_glsl_info_log     0(22) : warning C7050:
"vs_out[6]" might be used before being initialized
003d:fixme:d3d_shader:print_glsl_info_log     0(22) : warning C7050:
"vs_out[7]" might be used before being initialized
003d:fixme:d3d_shader:print_glsl_info_log     0(22) : warning C7050:
"vs_out[8]" might be used before being initialized
003d:fixme:d3d_shader:print_glsl_info_log     0(22) : warning C7050:
"vs_out[9]" might be used before being initialized
003d:fixme:d3d_shader:print_glsl_info_log     0(22) : warning C7050:
"vs_out[11]" might be used before being initialized
003c:fixme:msvcrt:__clean_type_info_names_internal (0x7f12afc) stub

[Bug 12060] Direct3D window is not placed withing its parent window

https://bugs.winehq.org/show_bug.cgi?id=12060

Gijs Vermeulen  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
         Depends on|45370                       |

[Bug 12060] Direct3D window is not placed withing its parent window

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=12060

--- Comment #24 from joaopa  ---
Does the bug still occur with wine-4.17?

[Bug 12060] Direct3D window is not placed withing its parent window

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=12060

--- Comment #25 from Artem S. Tashkinov  ---
Created attachment 65410
  --> https://bugs.winehq.org/attachment.cgi?id=65410
MilkDrop in Wine 4.17

(In reply to joaopa from comment #24)
> Does the bug still occur with wine-4.17?

Yep, it has even got worse.

[Bug 12060] Direct3D window is not placed withing its parent window

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=12060

Artem S. Tashkinov  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
         Depends on|                            |34143

[Bug 12060] Direct3D window is not placed withing its parent window

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=12060

--- Comment #26 from joaopa  ---
Does the bug still occur with wine-6.19?

[Bug 12060] Direct3D window is not placed withing its parent window

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=12060

--- Comment #27 from Artem S. Tashkinov  ---
Created attachment 70758
  --> https://bugs.winehq.org/attachment.cgi?id=70758
wine 6.19

(In reply to joaopa from comment #26)
> Does the bug still occur with wine-6.19?

Yep, the bug is still valid.

[Bug 12060] Direct3D window is not placed withing its parent window

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=12060

Stefan Dösinger  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #28 from Stefan Dösinger  ---
Is the d3d output displacement inside the window related to the location of the
window on the screen? In other words, if you move the window around, does the
d3d content move?

Does the problem also happen when you run winamp inside a virtual desktop?

[Bug 12060] Direct3D window is not placed withing its parent window

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=12060

--- Comment #29 from Artem S. Tashkinov  ---
Created attachment 70766
  --> https://bugs.winehq.org/attachment.cgi?id=70766
Displacement

(In reply to Stefan Dösinger from comment #28)
> Is the d3d output displacement inside the window related to the location of
> the window on the screen? In other words, if you move the window around,
> does the d3d content move?

Yes, they are linked. BTW displacement is seemingly random from invocation to
invocation. I've now launched it again and the displacement is so huge I can
only see 10% of the visualization.
> Does the problem also happen when you run winamp inside a virtual desktop?

What do you mean?

[Bug 12060] Direct3D window is not placed withing its parent window

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=12060

--- Comment #30 from Artem S. Tashkinov  ---
Created attachment 70767
  --> https://bugs.winehq.org/attachment.cgi?id=70767
Running in a virtual desktop
> Does the problem also happen when you run winamp inside a virtual desktop?

Yes, it's all the same.

[Bug 12060] Direct3D window is not placed withing its parent window

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=12060

Artem S. Tashkinov  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                URL|http://www.filehippo.com/do |https://www.download3k.com/
                   |wnload_winamp/5535/         |Install-Winamp-Full.html

--- Comment #31 from Artem S. Tashkinov  ---
WinAMP is free to download and use and takes literally 15 seconds to install.
:-)

$ sha256sum winamp5666_full_all.exe
d26d4c7e583a6a6f46011ea0cebd32e20499ce22c0058bb8b30e010d927221ec 
winamp5666_full_all.exe

[Bug 12060] Direct3D window is not placed withing its parent window

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=12060

--- Comment #32 from Stefan Dösinger  ---
(In reply to Artem S. Tashkinov from comment #29)
> Yes, they are linked. BTW displacement is seemingly random from invocation
> to invocation. I've now launched it again and the displacement is so huge I
> can only see 10% of the visualization.

But once started up, the displacement stays constant regardless of where the
window is placed?
> > Does the problem also happen when you run winamp inside a virtual desktop?
>
> What do you mean?

Winecfg->graphics->emulate a virtual desktop

Or wine explorer.exe /desktop=foo winamp.exe

What I want to get to with both questions: At least in ddraw (although reading
from the bug history I guess milkdrop uses d3d9), primary surface coordinates
are screen-relative, not window-relate. So when the app has a window placed at
123x3456 and wants to draw pixel 20x30 inside it, it actually draws pixel
(123+20 x 456+30), and wine sort of undoes this because in GL everything is
window-relative. We might get something wrong there in the way the application
has set up its drawing. Because window placement involves the window manager,
running inside a virtual desktop takes it out of the equation and lets wine do
things on its own.

[Bug 12060] Direct3D window is not placed withing its parent window

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=12060

--- Comment #33 from Artem S. Tashkinov  ---
(In reply to Stefan Dösinger from comment #32)
> But once started up, the displacement stays constant regardless of where the
> window is placed?

Yes.

[Bug 12060] Direct3D window is not placed withing its parent window

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=12060

--- Comment #34 from Stefan Dösinger  ---
Created attachment 70768
  --> https://bugs.winehq.org/attachment.cgi?id=70768
Misplacement illustration

I can reproduce this, but I don't think it is a d3d problem. It looks like a
window placement problem in user32 to me.

The problem doesn't happen if I disable "integrate into Winamp skin" (or
whatever the exact English phrase is - I have it set to German) in the
Visualization options. The behaviour also depends on the Winamp skin - Winamp
classic makes it most obvious, Winamp modern doesn't have the problem at all.
With "bento" I can move the visualization around by opening and closing the
right click menu inside the visualization window.

Furthermore I believe it depends on the initial window position. See the
attached screenshot that illustrates this. This might also explain why
winamp-modern doesn't have the issue. It initially places it at 0/0 of the
screen, then moves it into the right place inside the Winamp window. If I go to
winamp-modern, then winamp-classic, even winamp classic renders properly.

Overall I am not going to put any effort in this bug - it looks very Winamp
specific, is not breaking functionality and has a workaround, so all the other
open game feel more valuable to fix to me.

[Bug 12060] Direct3D window is not placed withing its parent window

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=12060

Stefan Dösinger  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever confirmed|0                           |1

--- Comment #35 from Stefan Dösinger  ---
Confirming

[Bug 12060] Winamp visualizations are placed incorrectly in their host window

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=12060

Stefan Dösinger  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Direct3D window is not      |Winamp visualizations are
                   |placed withing its parent   |placed incorrectly in their
                   |window                      |host window

[Bug 12060] Winamp visualizations are placed incorrectly in their host window

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=12060

Artem S. Tashkinov  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|directx-d3d                 |user32