Hard Light Productions Forums
Community Projects => The FreeSpace Upgrade Project => Topic started by: Oddzball on May 26, 2006, 06:25:25 pm
-
Ok I was looking through the FS_Open Wiki and noticed something. A lot of the features that are being added say that they only work with direct x. So my question is, does everyone run the game in direct X now, or should we still run in opengl. I think Enviromental mapping was one thing that is a direct x only feature?
-
No, most features now work with OpenGL but not D3D, D3D doesn't work on a lot of machines either. (mine)
-
From the Wiki about Envir mapping....
-env
Enables environment mapping. Direct3D only. Environment mapping intensity will be determined from the intensity of specular maps.
-
That's outdated, now env mapping only works on OpenGL, I'm telling you, unless you have somthing wierd going on with you computer, OpenGL is better.
-
On another note, it seems that directx for fs2 is being abandoned.
-
On another note, it seems that directx for fs2 is being abandoned.
It was abandoned a year ago, when no one cared to work on it anymore. Now we are making the move to remove it from the code entirely. It's probable that at least all of my future builds will be built without D3D support (I've made it a build option now, but enabled by default).
-
To be honest the only reason D3D is still in is because there are some people who have problems with OpenGL and can only run in D3D.
But as D3D gets less and less attention it's becoming more likely that it won't work for anyone and should just be left out.
@Oddzball : Can I have a link to that wiki page? It needs to be edited :)
-
It actually doesn't work for me right now. If I start FSO up in D3D, I just get a big white screen.
-
It actually doesn't work for me right now. If I start FSO up in D3D, I just get a big white screen.
Yep, I noticed that too when I did a run test of my changes before commit. I thought it was my new changes until I went to an older build and it still didn't work. I can only assume that it was my envmap commit a couple of weeks ago that broke it, though playing around with those changes didn't reveal a fix today. I'll try and get it situated before the weekend is over.
-
Kara;
The wiki link is here... http://www.hard-light.net/wiki/index.php/Command-Line_Reference#-env
Thanks for the info btw.
-
@karajorma:
If you are editing the page anyway (and care to do this), here are some more changes...
1) -env is now a graphics option and not experimental
2) -cache_bitmaps has been moved to a game speed option rather than graphics option
3) -nobeampierce has been removed (per old post in the internal forum)
-
OpenGL.
-
I can use both, but unless a game requires it, I use OpenGL
-
I already edited it, but he can add in what you want him to (or I can if he doesn't want to.)
-
Feel free to edit it for me Mars. :) :yes:
The Team Loadout stuff is just eating up all my spare time! :eek2:
-
Speaking of which, why is the wiki so fugly lately?
-
Directx???????? what is that?? a bill production to make games slower and force people to upgrade its cards?
Search info about DX10 and his "DX9 emulator"...
OpenGL.
-
Uh... what?
DirectX (http://en.wikipedia.org/wiki/DirectX)
And I go back to the original question, why is the Wiki so ****ing ugly?
-
DX10 is not compatible which DX9, so its needs an emulator to run any DX9 game, which have a hit in the overall performance.
http://www.theinquirer.net/?article=25902 (http://www.theinquirer.net/?article=25902)
Also, I reading some worry information about OpenGL and the Windows vista..
As M$ does everything to destroy OpenGL I would not be surprised at all if DA will use DirectX, too.
Their new Windows will only work with all features if you have OpenGL disabled... that means many freeware tools will not work anymore, as they use OpenGL.
M$ is really good at what they are good at.
did some searching and found a news post about the new microsoft windows (visa/longhorn) might/will have opengl only implemented via direct3d. Which I think means that opengl will be translated into direct3d before going to the graphic card.
Allthough this might not be the case entirelly as people have said it is only a problem with windowed applications and not full screen ones. So games should mostly be uneffected by this.
I don't know if that's so cool... MS will have the complete controle over the speed of OpenGL.
If it's not directly accessing the hardware it could be unbearable slow (if MS wants it to be slow and/or if the translation isn't optimized for speed)...
-
That's outdated, now env mapping only works on OpenGL, I'm telling you, unless you have somthing wierd going on with you computer, OpenGL is better.
I've always ran FS2 open with DirectX/3d and have never had a problem with the game running and the graphics with d3d is simply astounding, i must have something wierd going on! haha
-
I have to use DirectX cuz my openGl version is 1.1 and u need 1.2 to play it. Im on Vista beta2 by the way. If use windows XP will I then be able to play with OpenGL?
-
No, you need to get a new video card.
Do you have an AGP slot?
If not you'll need to go with PCI graphics, I'd recomend a Radeon 9250.
-
I have an ATI 9800 Pro 128 MB.
-
Then OpenGL should work fine :wtf:. Have you tried running FS2O on OpenGL?
-
I tried many versions of FS2Open from v3.6.7 to the latest May 17th CVS build, but none of them will work with OpenGL, only DX.
My quess is that Vista is causing the problem here, but anywho DX works just fine for me and Im not planning to switch back to XP cuz i like Vista too much.
-
yes, im very sure of that. just search opengl+vista in google ...
P.D. You have the lastest graphic driver right?
-
Yep for Vista beta2 that would the ATI Vista beta2 driver
-
Problem is that D3D has been depreciated. You'll find that some coders won't even build with it compiled in as time goes by as it means OpenGL becomes more stable. Unless we get a D3D coder by the end of the year the only way you'll be able to play on D3D is likely to be to compile it yourself. And you won't get much support from the team cause the reason we're dropping it is to avoid spending time supporting the bug-ridden code.
Bear in mind that a couple of years ago the situation was completely the reverse so it's not like getting a good coder to do for D3D what Taylor did for OGL won't solve the problem but without one the future looks fairly bleak for D3D.
-
With vista, the reason is that in windows, OpenGL is supported in the graphics drivers. Since vista uses a new driver model, (WDDM) probably the graphics cards makers aren't including opengl support in their beta drivers for vista, that 's why OpenGL doesn't work. Hell they didn't even have a control panel for the drivers until Beta 2.
Also running Beta 2 as your main OS isn't a very smart idea.
-
Yeah, like, vista beta 2 is beta software. It's still in testing, and vista beta is not a complete operating system really. It works, but it doesn't have everything in there yet that's supposed to have everything working.
-
With vista, the reason is that in windows, OpenGL is supported in the graphics drivers. Since vista uses a new driver model, (WDDM) probably the graphics cards makers aren't including opengl support in their beta drivers for vista, that 's why OpenGL doesn't work. Hell they didn't even have a control panel for the drivers until Beta 2.
Also running Beta 2 as your main OS isn't a very smart idea.
yeah seriously, I'm 99.9% sure that OpenGL works on the final version on Vista, MS wouldn't be able to sell the damn OS to gamers if I didn't work.
-
But, like, instead right now, everyones like 50.0% sure that opengl works on beta2 :lol:
-
well, it depends on what card the user has and what drivers. Not everyone has the same hardware and not all hardware currently supports OpenGL under Windows Vista. I can say with 100 percent certainty that by the time Vista is production ready and Gold, it will suppport Freespace SCP in OpenGL mode.
-
yes, but I hear rumors about OpenGL will be converted to Direct3D in Windows Vista.
-
That's wrong, OpenGL will be fully supported in Windows Vista with the DWM and Aero Glass on. It's not going to be a problem.
-
yes, but I hear rumors about OpenGL will be converted to Direct3D in Windows Vista.
That doesn't make any whatsoever sense.
DirectX is an API, a programing interface that allows the usage of a variety of hardware with the same instruction set. Namely you order the program to draw things, make sounds, network in a manner you specified, but actual implementation with all the hardware idiosyncracies is left to the DirectX.
OpenGl is pretty much the same, but for graphics only. Unlike DirectX it's opensource, and will run on non-Windows machines.
OpenAl is the opensource, sound equivalent of OpenGl.
You can't convert one into the other as they have different standards and instruction sets, hence the reason why graphic cards use different drivers for OpenGl and Direct3D.
Right now as far as I see it, Microsoft tries to pull the same **** they did with windows-95 and Internet Explorer: bundling the OS with their own ****, and through sheer market dominance, expelling the other standards from the consumers PC.
In other words dominating your electronic environment even more by gaining a further monopoly.
-
yes, but I hear rumors about OpenGL will be converted to Direct3D in Windows Vista.
That doesn't make any whatsoever sense.
It's true actually, and not all that strange. Default OpenGL calls will be converted to Direct3D calls and used that way. That's what got everyone so upset. This isn't an issue for the graphics card makers which create true Vista ICDs though since that will be 100% OpenGL. If you use an ATI or NVIDIA card then there is nothing to worry about since you'll get full OpenGL and not have to sacrifice Aero. Those who use older Win2k/WinXP ICDs will get full OpenGL, but Aero will be disabled when it's in use. Other vidcard makers, like with embedded chipsets, may just use the OpenGL->Direct3D thing to avoid them having to commit the resources needed to write real OpenGL compliant drivers.
Doing what Microsoft is doing here isn't strange. It sucks because it's Microsoft doing it, but that's about it. OpenAL for instance is basically just converting a standard sound interface to a non-standard sound interface. You write your code for OpenAL and OpenAL will then translate it all to (as examples) ALSA for Linux, CoreAudio for OS X, or DirectSound for Windows. Microsoft is getting out of having to support any sort of real OpenGL tech, and instead it's left up to the video card makers (which is basically how it's been all along). On the plus side there will be half-way decent OpenGL support either way, even if it is getting routed to Direct3D. Previously, if you didn't have a good OpenGL ICD, then OpenGL on Windows was pretty much useless.
-
basically, you can only really run aero if you run on an ati or nvidia card anyway, since very few other cards (and woe be you if you run some weird parhelia or something) support shader model 2.0, which is a requirement.
So as Taylor has said, the vast majority of people who play recent 3d games use a ATI or Nvidia card, and they'll get solid OpenGL support in Windows Vista no matter what (see above post)
I remember that when this was first announced, everyone freaked out, but then when it was realized how it was going to be done, everyone calmed down. There was even a front page article on the opengl.org site about it, saying a sort-of thank you to microsoft... i'm not a graphics programmer so i don't exactly understand it, but i did get the impression it wasn't going the be the end of the world and taylor has made it more clear what is going on now.
Recently microsoft has announced that the way graphics cards currently use scheduling in the new WDDM 1.0 spec (the model for the new vista ICDs) needs to be overhauled in hardware for WDDM 2.0, which will come out after Vista's launch, for performance reasons. Currently there are some issues around apps that run 3D in a window with VSYNC enabled having exclusive access to the graphics card, which can interfere with the desktop compositing being responsive in the right way if another app needs access to the GPU :sigh:. And their roadmap indicates they have further improvement to a WDDM 2.1 level spec planned. So it seems the new driver model is semi-obsolete in windows vista before it's even been released :ick: