Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 22 Apr 2022 21:23:31 +0000
From:      bugzilla-noreply@freebsd.org
To:        ports-bugs@FreeBSD.org
Subject:   [Bug 263475] emulators/wine 6.0.4 update seems to have broken i386 opengl/wined3d
Message-ID:  <bug-263475-7788@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D263475

            Bug ID: 263475
           Summary: emulators/wine 6.0.4 update seems to have broken i386
                    opengl/wined3d
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: gerald@FreeBSD.org
          Reporter: alt2600@icloud.com
          Assignee: gerald@FreeBSD.org
             Flags: maintainer-feedback?(gerald@FreeBSD.org)

Created attachment 233404
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D233404&action=
=3Dedit
Lunar Magic OpenGL issues.log

so first noticed when I attempted to install a local poudriere build, but
assumed it was my setup, as I've never had one work from a local poudriere
build. But when I noticed Latest had updated on the official repo I
re-installed wine and mesa-dri from the official repo to get the i386 packa=
ge
installed using the pkg32.sh script. I cannot get anything using i386 and
direct3d to work at all. Pure 64-bit mode works fine. Anything i386 unity w=
ill
just crash, bascially with cannot allocate memory to the framebuffer. 32bit
Things like Lunar Magic (super mario world rom editor) will load, but give
OpenGL/wined3d errors and cannot display anything once a rom is loaded, whi=
ch
is odd as I didn't even think that would be using directx. running dxdiag j=
ust
crashes itself never going beyond console messages finally indicating a mis=
sing
midi sequencer but the app never displays a window, and gives tons of error=
s on
the framebuffer device for Dirextx11

not sure what is going on. amd64 13.0-p10 nvidia drivers. Everything worked
fine under the older version of wine. I even reinstalled nvidia-driver to be
sure as wine used to run some script post-install that would mangle the nvi=
dia
drivers that thankfully doesn't seem to run anymore.

00e4:err:d3d:wined3d_debug_callback 0x15bdfc0: "GL_OUT_OF_MEMORY error
generated. Failed to allocate memory for buffer object.".

00e4:err:d3d:wined3d_debug_callback 0x15bdfc0:
"GL_INVALID_FRAMEBUFFER_OPERATION error generated. Operation is not valid
because a bound framebuffer is not framebuffer complete.".
00e4:fixme:d3d:wined3d_context_gl_check_fbo_status FBO status
GL_FRAMEBUFFER_UNSUPPORTED (0x8cdd).

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-263475-7788>