[Bug 50594] New: Surge 1.6.6 VST works but shows only blank window

[WineHQ Bugzilla]

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

            Bug ID: 50594
           Summary: Surge 1.6.6 VST works but shows only blank window
           Product: Wine
           Version: 6.1
          Hardware: x86-64
               URL: https://github.com/surge-synthesizer/releases/releases
                    /download/1.6.6/Surge-1.6.6-Setup.exe
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
          Assignee: wine-bugs at winehq.org
          Reporter: and3md at gmail.com
      Distribution: ---

Created attachment 69279
  --> https://bugs.winehq.org/attachment.cgi?id=69279
Wine log

Steps to reproduce:
1. Install LMMS -
https://github.com/LMMS/lmms/releases/download/v1.2.1/lmms-1.2.1-win64.exe

2. Download and install Surge -
https://github.com/surge-synthesizer/releases/releases/download/1.6.6/Surge-1.6.6-Setup.exe

3. Open LMMS
4. Change plugin embedding in Settings to No embedding (this is workaround of
https://bugs.winehq.org/show_bug.cgi?id=48527).
5. Restart LMMS
4. Open the instruments plugins tab
5. Drag VeSTige to Song Editor window
6. Click Vestige in Song editor to show Vestige GUI
7. In Vestige Window click green folder icon
8. Go to Surge.dll
9. Click Open
10. Empty window appears

On Windows 10 works ok.

There are in log a lot of lines like: 

017c:fixme:dwrite:dwritefactory_CreateMonitorRenderingParams (0x1): monitor
setting ignored
0188:fixme:d3d:state_linepattern_w Setting line patterns is not supported in
OpenGL core contexts.
0188:fixme:d3d_shader:print_glsl_info_log Info log received from GLSL shader
#3:
0188:fixme:d3d_shader:print_glsl_info_log     Vertex info
0188:fixme:d3d_shader:print_glsl_info_log     -----------
0188:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050:
"vs_out[0].zw" might be used before being initialized
0188:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050:
"vs_out[2].zw" might be used before being initialized
0188:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050:
"vs_out[3].zw" might be used before being initialized
0188:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050:
"vs_out[5]" might be used before being initialized
0188:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050:
"vs_out[6]" might be used before being initialized
0188:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050:
"vs_out[7]" might be used before being initialized
0188:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050:
"vs_out[8]" might be used before being initialized
0188:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050:
"vs_out[9]" might be used before being initialized
0188:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050:
"vs_out[10]" might be used before being initialized
0188:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050:
"vs_out[11]" might be used before being initialized
0188:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050:
"vs_out[12]" might be used before being initialized
0188:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050:
"vs_out[13]" might be used before being initialized
0188:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050:
"vs_out[14]" might be used before being initialized
0188:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050:
"vs_out[15]" might be used before being initialized
0188:fixme:d3d_shader:print_glsl_info_log     
0188:fixme:d3d_shader:print_glsl_info_log     Fragment info
0188:fixme:d3d_shader:print_glsl_info_log     -------------
0188:fixme:d3d_shader:print_glsl_info_log     0(37) : warning C7050: "R1.yzw"
might be used before being initialized

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.