Mesa 5.0 Released 142
Eugenia writes "Mesa 5.0 has been released. It implements the OpenGL 1.4 specification." There's more information as to what's been fixed/added/changed on their SF.net project page.
The explanation requiring the fewest assumptions is the most likely to be correct. -- William of Occam
The question now is... (Score:1, Troll)
Re:WTF mods?!?! (Score:2)
My guess is that some moderator thought that asking on the availability of a package is automatically an insult. To all moderators; if they aren't explicitly being insulting, then it's probably a genuine question! It's pretty sad when our hides get so thick that our immediate answer to a request for help is to try and ignore them.
To answer the original question, my guess is that it'll probably go into the latest unstable, which is Sid. (If it isn't in there already.) My guess is that it's probably not going to be around long enough to make the testing release, Sarge, before Sarge gets bumped to stable. From what I understand, to make Sarge, it'd need to be in for 3 months. If they bump Sarge to stable in less than 3 months, it won't make the next stable release. I could be wrong, here, though.
I don't personally run Debian anymore (Windows), so.. maybe someone from Debian could offer some insight here, on just how much work needs to be done to get this hooked in with the latest X, and what it would take for it to make it into Sarge.
cute (Score:5, Funny)
So that's all it takes, eh?
<grin>
How does it compare on windows? (Score:5, Interesting)
Why Windows? It's always interresting to see how any open software solutions stack up versus their proprietary cousins on a proprietary system.
Re:How does it compare on windows? (Score:5, Interesting)
Re:How does it compare on windows? (Score:4, Informative)
Why would you want to see that comparison? nVidia's Linux drivers are hardware accelerated. Generic Mesa is not.
Dinivin
Re:How does it compare on windows? (Score:2)
Re:How does it compare on windows? (Score:3, Informative)
Dinivin
Re:How does it compare on windows? (Score:2, Interesting)
Re:How does it compare on windows? (Score:2)
Re:How does it compare on windows? (Score:2)
Uh, no it's not. The Mesa you download from the projects' website is "vanilla" Mesa. There's nothing limiting about that at all. I'm not saying anything bad about it (in fact, I use it every day), but Mesa and DRI are two separate projects, even if some of code (and some of the developers) overlaps.
Dinivin
Mesa and hardware acceleration (Score:2)
***
1.2 Does Mesa support/use graphics hardware?
Yes. Specifically, Mesa serves as the OpenGL core for the XFree86/DRI OpenGL drivers.
***
Now, Mesa does *include* a software rendering engine...
This could be what you meant, but this is the first post along the "Mesa is nothing more than a software renderer" lines, and there are a *lot* on here, some of which are definitely wrong.
Re:Mesa and hardware acceleration (Score:2)
Vanilla Mesa does not support hardware acceleration. It never has and it never will.
The Mesa that's included in the DRI does. That is not vanilla Mesa. If you were to go to the Mesa website, download the latest version, compile and install it, you wouldn't have hardware acceleration (unless you compiled the DRI or compiled Mesa against the Glide libraries, in which case it's no longer vanilla Mesa).
Dinivin
Re:Mesa and hardware acceleration (Score:2)
Let me amend this previous post. I can't say, with any knowledge, that vanilla Mesa will never support hardware accleration.
Dinivin
Re:How does it compare on windows? (Score:1)
I think the more interesting question will be 'when will DRI begin to develop with Mesa 5?' Only when libGL.so is hardware accelerated and, therefore, usable does anyone care about feature sets. Unfortunately, the DRI with X4.2 is based on Mesa 3, which doesn't cut the mustard these days.
Hopefully X4.3 will be released with a very recent trunk build of DRI. TCL support for R100s, at least, should be supported.
p.s.
Does anyone from Deb or perhaps the XSF currently package CVS snapshots of the XFree86 tree. Sure, packaging X is not nice, but an unstable package of X for i386 would still be kind of cool for the lazy twiddlers.
Re:How does it compare on windows? (Score:3, Interesting)
Re:How does it compare on windows? (Score:2)
Re:How does it compare on windows? (Score:2)
Re:How does it compare on windows? (Score:3, Informative)
Re:How does it compare on windows? (Score:1)
Re:How does it compare on windows? (Score:1)
Dual boot Linux/Win2k, palomino@1667, 512 megs, Geforce4Ti4600.
Same framerates on Q3/RTCW under win2k and linux (using the same breed of drivers from nVidia).
You are prolly not using hardware acceleration under linux. Check your drivers.
cheers.
Re:How does it compare on windows? (Score:3, Informative)
Assuming you mean when running under X and Linux, run glxinfo from a shell. Near the top will be "direct rendering: yes" (or no). If it's no then you're running software OpenGL instead of hardware accelerated OpenGL.
Re:How does it compare on windows? (Score:1)
Re:How does it compare on windows? (Score:1)
Compares how? In performance? Or in accuracy?
Performance numbers wouldn't mean much, since Mesa is software-based.
As for accuracy, from what I've heard from colleagues, it's sometimes annoying to program OpenGL for Windows since it's not very compliant. I have not seen results of running the standard OpenGL conformance tests on Windows.
I don't know what they did (Score:5, Informative)
glxgears running in a small window - 200 fps, average 2% cpu load(with Mesa 4.1 it was 800 fps 100% load),
running maximized in 1600x1200 - 80 fps, 100% load(exactly as with Mesa 4.1).
And all the games and etc run at exactly the same speeds with less cpu load.
All I can say is this is great - nobody needs insane fps numbers above 100 and it saves cpu for my poor apache running in the background
Re:I don't know what they did - NVidia ? (Score:2)
Re:I don't know what they did (Score:3, Informative)
Which means that your GPU now isn't accepting above some level for some reason.
I don't get it (Score:3, Interesting)
Re:I don't get it (Score:1, Informative)
Re:I don't get it (Score:2)
Re:I don't get it (Score:3, Informative)
But if you have an OpenGL driver, what does Mesa do?
a) Shows you how is it done, since you can peer at the source, and b) gives you an alternative if OpenGL is not good enough for you. Small benefits, and you may not care, but for some people these are good qualities.
Re:I don't get it (Score:2)
XFree86 (Score:2, Interesting)
I'd like to try this out and see if I can finally get some decent FPS on my Radeon 7000, but I don't want to sacrifice stability by messing with Mesa if I don't know what I'm doing.
Re:XFree86 (Score:3, Informative)
It will probably get included in 4.3.1 since it is an important feature to many users.
Re:XFree86 (Score:2)
Mesa is not hardware accelerated (Score:3, Informative)
I am not sure why non-developer should download Mesa, probably only if he/she need to run OpenGL application (like Blender for example) and hardware accelerated driver works bad or not exist.
Re:Mesa is not hardware accelerated (Score:4, Informative)
You mean Mesa's software driver is not hardware accelerated. Take a look at the Mesa FAQ, point 1.2.
I can't believe it! (Score:1)
"Me-sa like it. Me-sa good!"
Re:I can't believe it! (Score:1)
Re:mesa sucks compared to dx 9 (Score:5, Informative)
In fact, there are only two 3D APIs that are standardized and (more or less) widely used: OpenGL and OpenInventor.
Re:mesa sucks compared to dx 9 (Score:1, Interesting)
As for OpenGL being standartized, if you want to support newer features like pixel (fragment) shaders or vertices in AGP memory, you NEED to use vendor extensions, which means separate code for nVidia and ATI.
Re:mesa sucks compared to dx 9 (Score:2)
Re:mesa sucks compared to dx 9 (Score:2)
dx doesn't come on straight on backwards compatibility btw. try playing master of orion 2 on win2k.. it either works or doesnt, most probably you'll lose your cursor.
moo2 is dx2 btw..(the win32 vers).
Re:mesa sucks compared to dx 9 (Score:2)
it's vapor until it's final, packed, and shipping, and supported.
Re:mesa sucks compared to dx 9 (Score:4, Insightful)
Good, 'cos I'm having some problems trying to run GORILLAS.BAS on WinXP.
Still, I agree, MS is not going to shoot themselves in the foot
by breaking backward compatibility if they don't have to.
Yes, OpenGL is open, but do you think anyone cares?
The computer games industry is like any other business, it is run by economics.
The kids want games with bleeding-edge 3d, and unless you're name is John Carmack, the industry is not going to support anything else than DirectX.
Now OpenGL 2.0 has the chance to turn the tables;
If GL2 can equal DirectX,
the game industry will use it,
if not for other reasons than economic reasons. Why? One word: Portability.
Porting to the Mac (and maybe even linux) is no problem with OpenGL, but if your code depends on DirectX: forget about it.
Now which game developer would knowingly limit themselves to the MS platform, if they had an equal alternative?
Which game producer would not want to be able to release a Mac or Linux port, at little extra cost?
who cares about "the lead"? (Score:5, Insightful)
So? Who cares? I'd much rather use an open API than some snazzy, proprietary thing.
Wait for 2.0 to come out. MS is going to lock Linux out of 2.0 as some of the api's are based on dx9
Again, who cares? If MS has the power to lock Linux out of OpenGL 2.0 (through patents?), then open source will just not use it and instead evolve OpenGL 1.* in a different direction.
Re:who cares about "the lead"? (Score:4, Insightful)
By whatever well-documented graphics hardware there is going to be in five years.
It's a losing battle. Just like with DRM enabled hardware. Open Source operating systems can only be run on pre-DRM hardware which will become obsolete in a few years.
Come on, wake up. The world doesn't work according to Bill Gates's pipe dreams. First of all, DRM-enabled hardware doesn't exclude open source software: you can either run it without DRM, or you can sign it. Even if it did, there is going to be plenty of non-DRM hardware going to be out there.
Open source is going to be here decades from now. I wouldn't be so sure about Microsoft, however.
Re:mesa sucks compared to dx 9 (Score:4, Informative)
Scientists tend to use grown-up OSes (i.e. no Windoze) and code in Fortran 95 or HPF, pure C or occasionally Lisp - all languages with OpenGL bindings.
You can learn OpenGL+SDL basics in an afternoon, and have flocks of teapots flying across your screen the following morning. Just beginning to learn DirectX and Direct3D means taking on board all the bizarro-world Microsoftian "C++" and COM cruft.
OpenGL's going to be around for some time.
Now, it is inappropriate for hardware raytracing cards [art.co.uk], but us people in the scientific graphics community (and movie-making-community) are only getting to play with them now, don't expect them to trickle down to the gaming market for a while yet.
Re:mesa sucks compared to dx 9 (Score:1)
This is wrong. In fact, Direct3D supports hardware acceleration (AGP memory, etc.) for high-res models natively through vertex buffers, while with OpenGL 1.* you need to use vendor extensions - nVidia VAR, ATI VAO, etc. Which, believe me, you can't learn in an afternoon.
You can learn OpenGL+SDL basics in an afternoon, and have flocks of teapots flying across your screen the following morning. Just beginning to learn DirectX and Direct3D means taking on board all the bizarro-world Microsoftian "C++" and COM cruft.
For fsck's sake, the stuff that JC wrote about OpenGL vs. DirectX is extremely outdated. Today, using OpenGL's easy-to-learn, flock-of-teapots immediate mode (i.e. glBegin(), glEnd()), will give you a really measly fps for scientific visualization. You have to use vertex buffers if you want performance. So you might just as well do it for exactly the same amount of time with Direct3D 8.1. Also, stop the FUD about Direct3D being "Microsoftian C++" only, you can use it just as fine with C, and *gosh* even under MinGW.
Re:mesa sucks compared to dx 9 (Score:2)
in the long run, that will change (Score:5, Insightful)
A flashy game with a lot of graphics may need a big budget. But those games are not necessarily good, nor do good games necessarily need flashy graphics. For example, many of the movie-tie-in 3D games are financed heavily and anywhere from mediocre to horrible. On the other hand, excellent games like chess or go are of utmost graphical simplicity, and they have been refined over centuries and millenia in a process akin to open source. Furthermore, there are quite a few excellent open source games with minimal graphics and excellent gameplay.
Closed source, heavily financed games satisfy a yearning for novelty. They spend a lot of money on eye candy and pushing technology to the limit. But really good game design is a long-term, open process. For computer games, that has barely begun. I suspect that in another few years, you are going to see open source games whose graphics is simpler than Doom but whose gameplay beats anything commercially available. And closed source games won't be able to compete with that because they simply can't have thousands of game players contributing directly to the evolution of the game.
Open source is slow--but eventually, it gets there, and it usually ends up doing a better job.
Re:in the long run, that will change (Score:5, Insightful)
No, it's implementation-by-contributors, which is very different. Design-by-committee is what happens in many companies: a lot of people who don't have to do any of the real work sit around and talk a lot, then dump some non-sensical specification on their programmers. Design-by-committee is bad. Implementation-by-contributors is good.
It takes a long time and if it ever finishes it's a compromise.
Making a good game or good piece of software always takes a long time--because it requires extensive feedback from users. Open source is actually better at that because the users are the developers.
As for being a compromise, of course it is. However, if it's a compromise a substantial number of people can't live with, the project forks. This, again, is good. Closed source doesn't have that option: just because many people think MS Office sucks doesn't mean they can take it, split it off, and fix it.
Re:in the long run, that will change (Score:1)
Re:in the long run, that will change (Score:1)
Sorry, can't resist this one:
Just have a look at nethack!
Re:Real gamers use Win32, not linux (Score:1, Informative)
The "problem" with DX from a developers point is that you can't be sure about what MS decides to do with the API in the next revision
I've spent time developing for both APIs and my personal favourite is still OpenGL, mostly because i can use the same code on different platforms.
Re:Real gamers use Win32, not linux (Score:2, Informative)
Re:Real gamers use Win32, not linux (Score:1)
http://www.microsoft.com/ddk/
Why did they do that? Beats me.
silic
Re:Real gamers use Win32, not linux (Score:2)
Re:Real gamers use Win32, not linux (Score:1)
Re:Real gamers use Win32, not linux (Score:1)
In a way this troolhoor is right. I was using Mesa on Sun and Linux machines years ago, when SGI was about the only place you could find OpenGL professionally. It wasn't OpenGL that cost anything, it was those damn SGI boxes and high-end video cards! Mesa was also the first to provide OpenGL for the 3fx Voodoo, the first consumer-level 3d video card. The really funny thing is, if you've ever done anything 3d in Linux, you've almost certainly used Mesa before, but I'm taking this troll too seriously.
Now mod this and the parent post into oblivion.
Re:Real gamers use Win32, not linux (Score:1)
Re:Real gamers use Win32, not linux (Score:1)
Re:Real gamers use Win32, not linux (Score:1)
Re:Real gamers use Win32, not linux (Score:2)
Re:Tsarkon WARNS: Eugenia is a Fat Fucking Pig (Score:2)
Whoa, hold on a second! I wasn't talking about your mom!
Re:Tsarkon WARNS: Eugenia is a Fat Fucking Pig (Score:2)
PS. Goatse.cx? Are you a regular? Judging by your intelligent response, you sound like you might be the owner!
Re:Tsarkon WARNS: Eugenia is a Fat Fucking Pig (Score:2)
Childish? Talk about the pot calling the kettle black.
Judging by your 'eloquent' response, it seems you are the source of your own amusement.
The only thing I can agree with you on is this - it's over. You can go back to AOL now, playing The Sims: Hot Date and fantasizing about your virtual girlfriends. Does your 'shield of intellect' give you a hard on?
Stylistically, you're a putz.
Re:Tsarkon WARNS: Eugenia is a Fat Fucking Pig (Score:2)
In other words - KMA.
In all seriousness - why don't you idiots get off the fucking board (no, that means leave... I don't literally mean get off on while reading
So like, fuck off or something.
Re:Tsarkon WARNS: Eugenia is a Fat Fucking Pig (Score:2)
A Windoze brat... running Debian Linux 3. Yeah, ok. You're "insightful" Have fun with your regular accounts. You're still a Troll, thus by definition "a lower form of life" and guilty of most of the things you've said about me already.
Re:Tsarkon WARNS: Eugenia is a Fat Fucking Pig (Score:2)
I'm sure you'll write another novel in response, but you became predictable about 3 posts ago and this is getting really really old.