Markus,<br> I am not at all familiar with Catia, but I can reenumerate my personal experiences with Intel on Linux. I am a basically normal student and tried to play counter strike on Linux through Wine. It had been ages since this piece of software runs perfect on wine. However, I met endless hours of frustration in trying to get it run. Initially, starting the game completely locked the computer, and since I don't know fancy ssh thing, all I could do was to reboot.
<br> I thought of blaming Wine, but things started magically working when I upgraded my OS to Ubuntu Gutsy. Those included a new set of drivers(for the same hardware), and now the game runs perfectly.<br> I also have other bad experiences with Intel Graphics. For example you cannot run Compiz along with a movie on any driver except those of nvidia. Is nvidia hardware superior(till level of playing a movie)? No, it's simply because the drivers from ATI and Intel are incomplete. Now what's more, X3000 is officially banned by Compiz for poor driver support.
<br> Another isuue is amount of support you can get. Remember when you buy Nvidia, you are paying not only for harware, but also for the support they offer.<br> Nvidia drivers are released approximately once in 2-3 months, and contains many bug fixes. God knows when Intel releases new drivers (both for Windows and Linux). And even if you somehow come to know about a new driver releases, chances are you don't know how to build and compile entire new intel graphics driver. So your only hope for getting an updated driver is your distribution, which makes a new release each 6 months, which is fine for me as a home user(atleast i can do whatever I want on my PC, reformat it as many times I want), but I fail to imagine consequences for a business user.
<br> In short, one pays no more than 3-4 $ for an Intel integrated graphics solution, and one should not really expect much out of it. If you are a critical business user, try switching to nvidia. A basic nvidia card cost less than Windows license, and is most you can make out of your money.
<br> BTW, did you know that our hardware supports OpenGL 1.5, but intel is yet to provides driver support, and it's nearly 3 years from release of X3000...... Being open source doesn't magically increases your programming skills, and I am damn sure that engineers at Tungsten Graphics(the people to which work of Intel drivers has been outsourced) are being paid less than those at Nvidia, which earns its bread and butter by Graphics market alone...
<br><br><div class="gmail_quote">On Nov 19, 2007 7:35 AM, Ove Kaaven <<a href="mailto:ovek@arcticnet.no">ovek@arcticnet.no</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Markus Hitter skrev:<br><div class="Ih2E3d">><br>> Am 18.11.2007 um 12:27 schrieb Ove Kaaven:<br>><br>>> None of the open source drivers support GLX 1.3 features, nor do most<br>>> support OpenGL 2.0 features (and I take it your applications want
<br>>> them). You could use glxinfo to see what your drivers do support.<br>><br>> glxinfo reports a "client glx version string : 1.4". Catia's software<br>> requirements read: "A Microsoft implementation of OpenGL libraries, as
<br>> delivered with with Windows 2000 or Windows XP". A specific OpenGL<br>> version isn't mentioned.<br><br></div>It is. It says "as delivered with Windows 2000 or Windows XP". That<br>means it wants features that comes with Windows 2000 or Windows XP.
<br><br>"Client GLX version string" does not say much. The way GLX works, is<br>that there's a "client" (the GL library that applications link to), and<br>there's a "server" (the X server). Both must support the desired
<br>features. Normally the problem is the server support. The standard WGL<br>features found under Windows correspond roughly to GLX version 1.3.<br><br>The "OpenGL version string" (or the more fine-grained "OpenGL
<br>extensions") is yet another detail to worry about, of course, as this<br>relates to the actual hardware features that an application can use.<br>This is probably less critical than the server GLX version string, though.
<br><br>Let's compare OpenGL with a Linux desktop: The "OpenGL version string"<br>is the version of the distro. The "OpenGL extensions" is the individual<br>applications available to the user (and typically, as you add more apps,
<br>a new version of the distro is released). The "client GLX version" is<br>the system libraries (like libc6). The "server GLX version" is the OS<br>kernel.<br><br>Now, compared to GLX 1.2, GLX 1.3 is an almost complete redesign (and
<br>far more in line with Windows functionality); let's consider GLX 1.2 the<br>equivalent of a kernel with OSS audio, and GLX 1.3 the equivalent of a<br>kernel with ALSA audio.<br><br>If you somehow decide to run version
1.2 of the Linux kernel, then is it<br>then an xmms bug that you can't configure it to use the ALSA dmix plugin<br>and get 5.1 surround sound? Your hardware may support surround sound.<br>Doesn't matter if your kernel doesn't even support ALSA, does it?
<br><br>Sadly, the open source OpenGL drivers have a "kernel" that don't<br>implement GLX 1.3. Implementing GLX 1.3, like implementing ALSA, doesn't<br>require any special hardware features, it's purely a software issue. But
<br>it's a software issue in the *drivers*. Not in Wine.<br><div><div></div><div class="Wj3C7c"><br><br><br><br>_______________________________________________<br>wine-users mailing list<br><a href="mailto:wine-users@winehq.org">
wine-users@winehq.org</a><br><a href="http://www.winehq.org/mailman/listinfo/wine-users" target="_blank">http://www.winehq.org/mailman/listinfo/wine-users</a><br></div></div></blockquote></div><br>