Trouble with directx

dc_wmj · Post by **dc_wmj** » Tue Feb 14, 2012 10:49 am

I used wine to install 3DSMax 7 in ubuntu. Unlike other versions, this one is known to run with wine. Even though the software indeed is starting and running, I'm facing trouble with directx and my ATI-graphics-card now: The viewports just don't refresh (see screenshot below). Changing to OpenGL causes ubuntu to freeze. Software-rendering doesn't work either. Are there any tricks I could try to get directx to work somehow? I of course installed the newest version (directx 9.0) in crossover already.

This website is showing a lot of registry-tweaks to adjust the graphics-settings in wine. However, I just don't know where to begin - the list is really long. Which component could cause the graphics-issues? Should I better try some settings in the catalyst-driver instead? Someone please help.

[img=http://postimage.org/image/vmtwc78uf/]Screenshot[/img]

Post by **dimesio** » Tue Feb 14, 2012 8:48 pm

dc_wmj wrote: I of course installed the newest version (directx 9.0) in crossover already.

You've already been told that Crossover is not supported here. I'll assume you meant to say plain Wine and tell you that installing directx is neither supported nor recommended. Some individual dlls may be needed by some apps, but according to the detailed howto in the AppDB entry you linked to, that is not the case for this app.

What I suggest you do is reinstall to a clean wineprefix using plain Wine and following the instructions in the AppDB entry that you linked to.

dc_wmj · Post by **dc_wmj** » Wed Feb 22, 2012 9:30 am

I didn't see the instructions on that page at all. Thanks for the hint. However, 3D Studio unfortunately even is crashing in OpenGL-Mode. As I wrote before, The whole system is crashing when switching to opengl. The mentioned tweak (creating this key: HKEY_CURRENT_USER/Software/Wine/OpenGL/DisabledExtensions = GL_KTX_buffer_region) didn't help.

John Drescher · Post by **John Drescher** » Wed Feb 22, 2012 9:39 am

The whole system is crashing when switching to opengl.

Then you have a problem with your hardware, OS or drivers.

See here:
http://wiki.winehq.org/FAQ#head-7f5c965 ... 7eadaff31a

--
John M. Drescher

dc_wmj · Post by **dc_wmj** » Wed Feb 22, 2012 10:17 pm

Aah thank you. That did help. I just installed newest ATI-catalyst-drivers. Graphics card gets identified wrong now - but nothing crashes anymore.

Unofficial ATI-wiki says my card is officially not supported but may work nevertheless. So at least software-rendering is working now in 3DS.

OpenGL doesn't crash but shows the same error as both directx-modes now: Non-refreshing viewports showing gibberish.

dc_wmj · Post by **dc_wmj** » Thu Feb 23, 2012 12:17 am

I tried it with plain-wine now - on first startup the program crashed with some DLL-missing-errors. Afterwards, 3DS7 didn't start up at all. I chose OpenGL-mode and applied the tweak (HKEY_CURRENT_USER/Software/Wine/OpenGL/DisabledExtensions = GL_KTX_buffer_region) in advance.

dc_wmj · Post by **dc_wmj** » Thu Feb 23, 2012 5:34 am

For some reason 3D Studio is running in plain-wine now. However, in both modes (OpenGL and DirectX9) the viewports just show gibberish. Hence there is no difference to a crossover-installation. Somebody has any idea what tweak to apply now?

dc_wmj · Post by **dc_wmj** » Fri Feb 24, 2012 7:52 am

Starting 3d studio from the terminal gives some error-messages at least. This is the output:

Code: Select all

wine ./3dsmax.exe
err:ole:CoGetClassObject class {d27cdb6e-ae6d-11cf-96b8-444553540000} not registered
err:ole:CoGetClassObject no class object {d27cdb6e-ae6d-11cf-96b8-444553540000} could be created for context 0x1
err:wgl:X11DRV_WineGL_InitOpenglInfo  couldn't initialize OpenGL, expect problems
---------------------------
 Havok - Build (0)
 Base system initialized.
----------------------------
---------------------------
 Havok - Build (0)
 Base system initialized.
----------------------------
---------------------------
 Havok - Build (0)
 Base system initialized.
----------------------------
---------------------------
 Havok - Build (0)
 Base system initialized.
----------------------------
---------------------------
 Havok - Build (0)
 Base system initialized.
----------------------------
---------------------------
 Havok - Build (0)
 Base system initialized.
----------------------------
---------------------------
 Havok - Build (0)
 Base system initialized.
----------------------------

It seems there is some opengl-error. Outside wine glxgears is running fine. Other programs can use opengl without problems. I googled around a bit: OpenGL-trouble with wine often is caused by missing ia32libs. They are installed on my 64bit-ubuntu. What else could do the trick?
[/code]

dc_wmj · Post by **dc_wmj** » Fri Feb 24, 2012 8:16 am

This website says I need to install the following libraries in a 32-bit-version to run wine with opengl on 64-bit:

On 64-bit systems, you may have to install the 32-bit versions of the following libraries, which can most likely be found in your distribution's package manager:

libjpeg-turbo
libmpg123
libsdl
libldap

They are all installed on my system. However, I don't know if they are 32 or 64-bit. How do I check this and can both versions co-exist? In addition libsdl has several versions, depending on graphics-card. It's too confusing! Is this the right attempt anyway?

dc_wmj · Post by **dc_wmj** » Fri Feb 24, 2012 2:21 pm

I found out: after upgrading wine, it is neccesary to also reinstall the catalyst-drivers. I didn't mention that I indeed did update wine from 1.2.2 to to 1.2.3.

So after reinstalling catalyst a 2nd time, the opengl-error-message is gone. Also the error-messages in 3d studio are gone now. The problem with the broken viewports however, is back again. I'm sure it's just some tweak to make opengl finally work in wine. Any ideas?

dc_wmj · Post by **dc_wmj** » Fri Feb 24, 2012 2:44 pm

Could this be the answer? The bug-report is from 2008! Can't believe it shall not be solved in current catalyst-driver.

Post by **dimesio** » Fri Feb 24, 2012 3:11 pm

dc_wmj wrote: I didn't mention that I indeed did update wine from 1.2.2 to to 1.2.3.

1.2.3 is almost a year old, and it's really just a handful of "safe" patches on top of a version that's over 18 months old. The current development release is 1.4-rc5. Upgrade.

dc_wmj · Post by **dc_wmj** » Sat Feb 25, 2012 2:47 am

Yes - and the bug-report for ATI-driver is 4 years old. Current development-version can break compatibility with working programs in stable-version. Since I seem to have a driver-related graphics-issue upgrading seems to be a not so good idea.

dc_wmj · Post by **dc_wmj** » Sat Feb 25, 2012 2:55 am

For people too lazy reading the bug-report: The interesting part is this one:

"The Mesa software renderer supports all the necessary OpenGL
extensions which are needed for this application to work. In Debian / Ubuntu, one just needs to install the libgl1-mesa-swx11 package and everything works perfectely graphicswise. The downside is that accelerated graphics is lost", as written by Teemu Ikonen on May 2008.

Unfortunately accelerated graphics are the reason for using opengl anyway. So this "workaround" in fact is no. Software-rendering is provided by 3D studio itself already.

dc_wmj · Post by **dc_wmj** » Sun Feb 26, 2012 7:34 am

This is so frustrating: Searching on the net for

"fixme:d3d:swapchain_init Add OpenGL context recreation support to context_validate_onscreen_formats"

gives so many different forum-results, most of them not solved. In many cases they end up in bug-reports. Some threats recommend updating wine. Others recommend switching off opengl at all.

Since the wine in crossover already is 1.3.9, I don't see a reason to upgrade my plain-wine (now 1.2.3) again, risking even more compatibility-issues. OpenGL is just not working in the three wine-versions I tested up to now for my ATI-card. Wine 1.2.2, Wine 1.2.3 and Crossover-Wine 1.3.9 are all giving the same error. I really don't think another update would fix it. The bug doesn't seem to be known.

Post by **dimesio** » Sun Feb 26, 2012 8:30 am

dc_wmj wrote:Yes - and the bug-report for ATI-driver is 4 years old.

And it was closed as invalid, with no indication in the bug report that anyone ever filed a bug with ATI.

If you really think this is an ATI driver bug, you need to file a bug with them. But I'd suggest testing the latest Wine first to make sure it is not something in Wine that has already been fixed. I doubt ATI will care about problems with an obsolete version of Wine.

dc_wmj · Post by **dc_wmj** » Sun Feb 26, 2012 10:35 am

Man, I can see your faith is strong. I doubt ATI cares about anythin related to linux at all. It's a miracle they publish drivers anyway.

If I filed a bug-report there their first answer was: "This is a wine-related-problem - contact the developers. Linux is not actively supported." I'm sure they don't even know what the error-message means.

After (re-) installing so much, I only have 500MB left on my drive. There is just no place for a fourth wine-version, including additional libraries.
I'm sure it also will need an own set of 32Bit-libraries, once it was installed (if it was successfull at all). Synaptics doesn't support upgrading wine to the unstable version. Only an additional installation is possible - propably along with conflicts... or maybe only self-compiled...

Sorry no. I'm convinced ATI is just not supported by wine now. It's my 2nd notebook with ATI-graphics - I never saw Wine-OpenGL up to now.

The Wine-AppDB is listing 3D Studio 5 and 7 working on nvidia. No word about ATI - anywhere. Unless I see some changelog explicitly mentioning something about a fixed ATI- or OpenGL-bug, I don't believe any version works - even if it was beginning with 2.x.

Post by **dimesio** » Sun Feb 26, 2012 11:33 am

dc_wmj wrote:Man, I can see your faith is strong.

Not really. There's a reason I only buy Nvidia. I am merely pointing out that if everyone thinks like you, and no one ever bothers to report the problem to ATI, none of you have any right to complain about them not having fixed something in 4 years.

dc_wmj · Post by **dc_wmj** » Mon Mar 05, 2012 2:34 pm

I don't care about your reasons buying this or that graphics card. I at least report an old wine-problem to the developers. You want me to also file a bug report to a hardware-manufacturer. I'm not the graphics-pope. Why don't you make yourself useful and find me some solution?

John Drescher · Post by **John Drescher** » Mon Mar 05, 2012 2:41 pm

Why don't you make yourself useful and find me some solution?

The solution are to either replace your graphics card with a nVidia
one or complain to AMD to fix their bugs.

John

jjmckenzie · Post by **jjmckenzie** » Mon Mar 05, 2012 5:04 pm

On Mon, Mar 5, 2012 at 12:34 PM, dc_wmj <[email protected]> wrote:

I don't care about your reasons buying this or that graphics card. I at least report an old wine-problem to the
developers. You want me to also file a bug report to a hardware-manufacturer. I'm not the graphics-pope. Why don't
you make yourself useful and find me some solution?

Because the Wine project is not and cannot be responsible for poorly
written/implemented video drivers. That is the responsibility of the
video card manufacturer or another open-source project to correct.

As it has been said here, multiple times, if you can replace your
video card, replace it with an nVidia card as they have the best Linux
drivers. Until AMD/ATI vastly improve their drivers, that is the
only, best answer you are going to get.

James

dc_wmj · Post by **dc_wmj** » Mon Mar 05, 2012 11:40 pm

The fact that I even have to reinstall the ATI-drivers after upgrading wine to make it behave shows that OpenGL it is obviously a wine-related problem. Other programs have no trouble with catalyst-drivers. Wine does.

Post by **dimesio** » Tue Mar 06, 2012 8:33 am

dc_wmj wrote:The fact that I even have to reinstall the ATI-drivers after upgrading wine to make it behave shows that OpenGL it is obviously a wine-related problem. Other programs have no trouble with catalyst-drivers. Wine does.

The fact that you have to reinstall your graphics drivers at all indicates they weren't installed correctly in the first place.

Wine is more demanding of graphics drivers than native apps, and will expose bugs in them that nothing else will.

Looking back over this thread, I see that you are using an obsolete version of Wine, were told to upgrade, and refused. That's your choice, but then there's nothing anyone here can do to help you.

Topic closed.