Hi,
Multiple times a day you encounter people who can't get 3D working in Wine. I'm getting so sick of these questions, that I decided to start a new page on the Wiki. http://wiki.winehq.org/3DDriverIssues
Feel free to add more information to it. I don't want it to give detailed instructions on how to install drivers but more a page which gives hints on what is wrong and which points people in the right direction to solve the problems. In case there is a distribution specific issue like LIBGL_DRIVERS_PATH on Ubuntu, such a thing could be described there in short.
Roderick
Am 08.03.2010 um 13:23 schrieb Roderick Colenbrander:
Hi,
Multiple times a day you encounter people who can't get 3D working in Wine. I'm getting so sick of these questions, that I decided to start a new page on the Wiki. http://wiki.winehq.org/3DDriverIssues
Feel free to add more information to it. I don't want it to give detailed instructions on how to install drivers but more a page which gives hints on what is wrong and which points people in the right direction to solve the problems. In case there is a distribution specific issue like LIBGL_DRIVERS_PATH on Ubuntu, such a thing could be described there in short.
Attaching a 32 bit glxinfo binary might be helpful for debugging 64 bit multilib issues.
On Mon, Mar 8, 2010 at 10:41 PM, Stefan Dösinger stefandoesinger@gmx.at wrote:
Am 08.03.2010 um 13:23 schrieb Roderick Colenbrander:
Hi,
Multiple times a day you encounter people who can't get 3D working in Wine. I'm getting so sick of these questions, that I decided to start a new page on the Wiki. http://wiki.winehq.org/3DDriverIssues
Feel free to add more information to it. I don't want it to give detailed instructions on how to install drivers but more a page which gives hints on what is wrong and which points people in the right direction to solve the problems. In case there is a distribution specific issue like LIBGL_DRIVERS_PATH on Ubuntu, such a thing could be described there in short.
Attaching a 32 bit glxinfo binary might be helpful for debugging 64 bit multilib issues.
A few months ago I added a 'winediag' channel which tries to detect incorrectly setup opengl drivers. It catches situations but I didn't know that 'direct rendering=yes' can also mean software rendering. That's a case I still need to add.
I still think it would make sense to have a 'wglinfo' in Wine.
Roderick
Stefan Dösinger wrote:
Am 08.03.2010 um 13:23 schrieb Roderick Colenbrander:
Hi,
Multiple times a day you encounter people who can't get 3D working in Wine. I'm getting so sick of these questions, that I decided to start a new page on the Wiki. http://wiki.winehq.org/3DDriverIssues
Feel free to add more information to it. I don't want it to give detailed instructions on how to install drivers but more a page which gives hints on what is wrong and which points people in the right direction to solve the problems. In case there is a distribution specific issue like LIBGL_DRIVERS_PATH on Ubuntu, such a thing could be described there in short.
Attaching a 32 bit glxinfo binary might be helpful for debugging 64 bit multilib issues.
Would this also include use Mac users??? If not, then please mark the file for the Operating System that it is a target for.
James McKenzie
On 3/13/10 8:23 PM, James McKenzie wrote:
Stefan Dösinger wrote:
Am 08.03.2010 um 13:23 schrieb Roderick Colenbrander:
Hi,
Multiple times a day you encounter people who can't get 3D working in Wine. I'm getting so sick of these questions, that I decided to start a new page on the Wiki. http://wiki.winehq.org/3DDriverIssues
Feel free to add more information to it. I don't want it to give detailed instructions on how to install drivers but more a page which gives hints on what is wrong and which points people in the right direction to solve the problems. In case there is a distribution specific issue like LIBGL_DRIVERS_PATH on Ubuntu, such a thing could be described there in short.
Attaching a 32 bit glxinfo binary might be helpful for debugging 64 bit multilib issues.
Would this also include use Mac users??? If not, then please mark the file for the Operating System that it is a target for.
It can't cover Mac users, because Mac OS has a different ABI with a completely different object-file format (Mach-O vs ELF). If they do attach a glxinfo binary, it would probably be for Linux.
X11 on Mac OS comes with a universal glxinfo anyway, so it's really not necessary for Mac OS. You can forcibly run the 32-bit glxinfo on Mac OS like so:
arch -i386 glxinfo
If you installed mesa from MacPorts, make sure you built it +universal. If you installed whatever the equivalent package is from Fink, make sure it's a universal binary by running:
file /sw/bin/glxinfo
It should say:
/sw/bin/glxinfo: Mach-O universal binary with <n> architectures
or some such.
Chip
On Sun, Mar 14, 2010 at 4:23 AM, James McKenzie jjmckenzie51@earthlink.net wrote:
Stefan Dösinger wrote:
Am 08.03.2010 um 13:23 schrieb Roderick Colenbrander:
Hi,
Multiple times a day you encounter people who can't get 3D working in Wine. I'm getting so sick of these questions, that I decided to start a new page on the Wiki. http://wiki.winehq.org/3DDriverIssues
Feel free to add more information to it. I don't want it to give detailed instructions on how to install drivers but more a page which gives hints on what is wrong and which points people in the right direction to solve the problems. In case there is a distribution specific issue like LIBGL_DRIVERS_PATH on Ubuntu, such a thing could be described there in short.
Attaching a 32 bit glxinfo binary might be helpful for debugging 64 bit multilib issues.
Would this also include use Mac users??? If not, then please mark the file for the Operating System that it is a target for.
James McKenzie
The page as it is right now makes most sense to Linux/FreeBSD/Solaris. The situation on OSX is quite different, so I'm not sure if it belongs there but the page could be reformatted if there is a need. I don't know what the issues on OSX are these but I guess it is mostly related to the X11 server.
Roderick