So, does the 7950GX2 count as a single card solution?

Page 22 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.

nts

Senior member
Nov 10, 2005
279
0
0
Originally posted by: beggerking
Originally posted by: nts
Good job making yourself look even stupider. Read your own link, would be a start.

For simplicity lets quickly examine how an OpenGL video drivers works.

Your system has an opengl32.dll (and some others) which simply pass the called functions and arguments to the appropriate driver (usually a dll like nvoglnt.dll for nvidias driver). If there is no driver installed it simply goes to a microsoft software renderer. If howerer there is a driver installed this driver will take what you want it to do and directly communicate that to the hardware. The windows opengl dll is only based on version 1.0, so if you want any support higher then you need to map extensions which the driver exposes.

The OS can only communicate with the video card in a very limited fashion. There is base functionality that every video card must support (doesn't include 3D TnL or anything like that) and windows can only access this base functionality, nothing more. That's why you need a video driver to be able to use the other functionality of the video card.

Any modern video card without a driver installed is a useless piece of junk.

games(which runs under OS) cannot only directly communicate with video drivers(which runs above OS ) without OS intervention, else any keystrokes/mouse movement will not work.
What the hell are you on? Since when does keyboard and mouse input have anything to do with video drivers?

Ok this is the last example that I give,

1. You click on Doom3.exe
2. Doom3 is statically linked to opengl32.lib and dynamically loads opengl32.dll at startup
3. Doom3 calls 'glDrawElements' (residing in opengl32.dll) which then gets redirected to the NVIDIA drivers function (residing in nvoglnt.dll) by opengl3d.dll (simple function pointers).
4. NVIDIA drivers take the arguments to the function, check they are valid and communicates that to the hardware (ask it to draw something).

You game isn't directly communicating with the video drivers here, just the common OpenGL dll on your computer. If you want to use OpenGL extensions however (base dll is version 1.0 only) you can directly map those function pointers (if supported) to your video driver function calls (directly communicating with video drivers here).

 

thilanliyan

Lifer
Jun 21, 2005
12,040
2,255
126
Originally posted by: keysplayr2003
Dual GPU systems such as SLI and Crossfire take up two physical PCI-e slots for a "dual GPU system" until they developed a way to have SLI on a single PCI-e x16 slot. Cards such as Gigabyte and ASUS made actually required and SLI motherboard to utilize SLI functionality. The GX2 can run on just about any of the 51 non SLI single PCI-e Nforce4 boards available from OEM's. Sure, the extra width of the GX2 will cover any adjacent PCI/PCI-e x1 slot, but that also goes for any card with a hsf that takes up an adjacent slot as well.

If you got the number 51 from the NVidia website, those boards are not all non-SLI boards. At least 20 of the 51 are SLI boards so you almost have to get an SLI board to run the card. I think people's statements and assumptions that this card will run on just about any motherboard is grossly misrepresented. You'd probably run into less problems with SLI boards since they already have the PCI-e switch right?
 

beggerking

Golden Member
Jan 15, 2006
1,703
0
0
Originally posted by: nts

What the hell are you on? Since when does keyboard and mouse input have anything to do with video drivers?

Ok this is the last example that I give,

1. You click on Doom3.exe
2. Doom3 is statically linked to opengl32.lib and dynamically loads opengl32.dll at startup
3. Doom3 calls 'glDrawElements' (residing in opengl32.dll) which then gets redirected to the NVIDIA drivers function (residing in nvoglnt.dll) by opengl3d.dll (simple function pointers).
4. NVIDIA drivers take the arguments to the function, check they are valid and communicates that to the hardware (ask it to draw something).

You game isn't directly communicating with the video drivers here, just the common OpenGL dll on your computer. If you want to use OpenGL extensions however (base dll is version 1.0 only) you can directly map those function pointers (if supported) to your video driver function calls (directly communicating with video drivers here).
simple questions. If OS doesn't fetch data from HD how does it run games? If OS doesn't accept interrupt requests how does mouse / keyboard work in a game? All these are processes done by the OS before data are send to a video driver. I won't call all these tasks done by OS as "limited".

OPengl.dll is only a dynamic linked library contain a library of function calls. When a function call within the library is being called, it is the Operating system that does the execution of the library function call by supplying necessary parameters to it.

and please refrain from personal attacks.
 

beggerking

Golden Member
Jan 15, 2006
1,703
0
0
Originally posted by: josh6079
Fair enough, but nts's main point was about the HARDWARE directly communicating with drivers, not games. Trying to get you to understand the basic relationship between software and hardware is a task enough. nts wasn't talking about communication between software and software (i.e. OS and drivers like you so explained) on that level. He only mentioned how there is a very simple and basic relationship between the OS and driver, unlike the very dependent relationship between the driver and its corresponding hardware.
Hardware directly communicating with drivers DOES NOT imply hardware has anything physically related to software. Any hardware can take any input from any driver(software). Invalid output will be produces but the hardware won't "know" that, all it does it process and output.
you can run dualcore CPU on win 95, just that you will only get the performance of a single core CPU.

Which defeats the entire purpose. Why do it if it really doesn't do anything beneficial?

everything after the bolded part in your post are simply garbage and your own agenda.

really? so the same dualcore that work so well in winxp, would suddenly "defeats the entire purpose" when we format and reinstall the system with windows 95? The cpu itself won't even "know" the OS has been changed, it will continue to work the same way as it did with XP installed. I don't see how switching from winXP to win95(software) has ANYTHING TO DO WITH HARDWARE yet you claim a software change would defeat the purpose of hardware??? its simply a software change to "better use" the 2 cores in a dualcore CPU.





 

Ackmed

Diamond Member
Oct 1, 2003
8,498
560
126
Originally posted by: keysplayr2003
Ok here goes:

"Except its not that simple. The GX2 takes up more than just one slot, the one its plugged into, and another. A dual core CPU does not.

Dual CPU systems (not dual core systems) took up two physical sockets and was a "dual processor system" until they developed dual core CPU's, two sockets were needed for multiprocessor systems. Now two CPU's only take up one socket.

Dual GPU systems such as SLI and Crossfire take up two physical PCI-e slots for a "dual GPU system" until they developed a way to have SLI on a single PCI-e x16 slot. Cards such as Gigabyte and ASUS made actually required and SLI motherboard to utilize SLI functionality. The GX2 can run on just about any of the 51 non SLI single PCI-e Nforce4 boards available from OEM's. Sure, the extra width of the GX2 will cover any adjacent PCI/PCI-e x1 slot, but that also goes for any card with a hsf that takes up an adjacent slot as well.

True. The point was, a DC CPU takes up the same amount of space as a single core CPU. The GX2 takes up more than one "slot". So in that aspect, they are not comparable to a dual core CPU.

Originally posted by: keysplayr2003
The GX2 has two seperate PCB's, two seperate GPU's, two seperate fans, two seperate amounts of ram. The dual core CPU is nothing like it in that regard.

Yes, the GX2 has what you listed above. That is how it is packaged. Nvidia could have made it into one very large card but it would have been impractical to market a product that wouldn't fit into most PC cases. As for the Dual core CPU reference, some DC CPU's are two physical and separate chips in the package, such as the Smithfield or Presler. X2's I believe are part of the same piece of sillicon. It's all in the way it is packaged. Core 2 Duo's are part of the same silicon. The way nvidia created the GX2 was the most practical way to implement it. Rather than have a very huge single PCB, limiting the number of people who can actaully buy it and use it in their case, two smaller PCB's were used side by side making it much more user friendly. And it still has SLI performance while only utilizing a single PCI-e slot making SLI performance available to all those people who only opted for a single PCI-e x16 motherboard. (If I am on the wrong track here, let me know. Commenting as best I can as per the context I see.)

The way they are packaged is not even close. As you mentioned, all of the DC CPU's "parts" are inside. But they are not really alike in how they are setup to work. There are some similarities, looking from the outside in, one looks the same, the other looks like to bolted together.


Originally posted by: keysplayr2003
The only thing they have in common, is that they both plug into one "slot". Looking at the outside of a dual core CPU, and a single core, you cannot tell the difference. You can with a GX2 and a single 7900 card very easily.

Yes, one slot/socket is used for both a Dual Core CPU and a GX2. Like I stated above, it was the most practical way for Nvidia to design the GX2. They can market it to almost anyone with a single PCI-e motherboard. It is just the packaging. For example, Nvidia could have sealed the GX2 in some sort of plastic/aluminum air tunnel with a different fan design. Think of the 5900 series from Leadtek Winfast cards. All you could see were fans and a large enclosure, and could not see the PCB at all. Now because it could not be seen, and still only utilized one PCI-e slot, do you think anyone would still even pose the question whether or not it was a single card solution or not? I don't know for sure, but my guess is not really.

Yes the one slot was much easier for them. And it makes a lot of sense. The point is, when he said "dual-core cpu = single socket, dual-gpu graphics adapter = single slot", and then saying that they are the same thing, is pretty silly. They look nothing alike. As I mentioned, a single core CPU looked exactly the same, as a DC CPU. No matter if they made an enclosure or not, it would not look like a single card. Its just too big. But I get your point.

Originally posted by: keysplayr2003
The votes are pretty much dead even, with a very small percentage leaning towards it being two cards. Thats my opinion on it. I can easily see two cards "bolted" together.

Yes, two PCB package. Connected together. It doesn't really matter if we decide the GX2 is one or two cards.
It brings 7900GT SLI level power to single PCIE slot motherboards, and is the most powerful single PCIE slot graphics solution on the market today. It's widely available, reasonably priced, uses less power than a single X1900XT, is quieter, and offers far higher framerates. (not to mention the additional AA modes and HDCP)
What I mean to say is, we can dispute endlessly about why the GX2 is two cards that can mysteriously be run on single PCIE boards, lots and lots of of people are buying them and enjoying SLI levels of performance.

I agree, and have said the same thing. Its a fine card for the price. There are a lot of good things about it. There are some negatives too, but there always is.


Originally posted by: keysplayr2003
It doesnt matter what it is really, all that matters is that its here, and aside from some bugs, works very well. The rest is not relevant. Most people here are not going to buy one, and some just want to claim a "victory" for the fastest "single" card out."

It's true, it really does not matter. They are selling extremely well. I see quite a few people here who either have one or are waiting in eVGA's step-up queue. Those that have one, can claim "victory" (if so desired) of having the fastest single PCI-e slot solution (my bold) available (right now). Something faster is always up the pike and around the corner.

I hope this is more like the response you were looking for. I think I addressed all of the points one way or another.

P.S. I never got to see Superman yesterday. :( My little girl suddenly got a fever. She is doing better today so we shall see.

Keys

Yes, "fastest single PCI-e slot solution". To me, not the fastest "single card". Because I think its SLI on a stick, so to speak. I do think the Asus card with both GPU's on a single card, is a single card however. Its just a difference of opinion. But as I said.. it doesnt matter. Its here, its available, and it works fairly well.

Much better resoonse, thanks. I just had issues with him posting "dual-core cpu = single socket, dual-gpu graphics adapter = single slot", and stopping there. And then a few people only singling out the one point, out of several I felt I made. Thats not looking at the big picture, not even close to it.


Originally posted by: thilan29
Originally posted by: keysplayr2003
Dual GPU systems such as SLI and Crossfire take up two physical PCI-e slots for a "dual GPU system" until they developed a way to have SLI on a single PCI-e x16 slot. Cards such as Gigabyte and ASUS made actually required and SLI motherboard to utilize SLI functionality. The GX2 can run on just about any of the 51 non SLI single PCI-e Nforce4 boards available from OEM's. Sure, the extra width of the GX2 will cover any adjacent PCI/PCI-e x1 slot, but that also goes for any card with a hsf that takes up an adjacent slot as well.

If you got the number 51 from the NVidia website, those boards are not all non-SLI boards. At least 20 of the 51 are SLI boards so you almost have to get an SLI board to run the card. I think people's statements and assumptions that this card will run on just about any motherboard is grossly misrepresented. You'd probably run into less problems with SLI boards since they already have the PCI-e switch right?


One of the more popular boards is not a gurarantee to work either, sadly.

Which leads me to the next note: try as I might I couldn't get the 7950 GX2 to run in dual-GPU mode on the A8N-SLI (even with the beta BIOS(s) that supposed added support for the card). I ended up benchmarking the GX2 on the A8R32-MVP instead, which worked fine.

http://www.rage3d.com/articles/preydemoperf/
 

Keysplayr

Elite Member
Jan 16, 2003
21,211
50
91
Originally posted by: Ackmed
And thats how you have a discussion like adults!! :)


Originally posted by: Ackmed
And thats how you have a discussion like adults!! :)

I would just like to comment about the A8N SLI.

Rollo/Jethro had no problems with the 7950GX2 on an A8N SLI, check out his 7983 3DMark06 over at FS:
Firing Squad Forum thread.

With that score, we know it was using both cores.

So, we know it does work on the A8N-SLI board.
 

nts

Senior member
Nov 10, 2005
279
0
0
Originally posted by: beggerking
simple questions. If OS doesn't fetch data from HD how does it run games? If OS doesn't accept interrupt requests how does mouse / keyboard work in a game? All these are processes done by the OS before data are send to a video driver. I won't call all these tasks done by OS as "limited".
And what if anything does this have to do with video drivers? These tasks are independant of what the video driver does...
OPengl.dll is only a dynamic linked library contain a library of function calls. When a function call within the library is being called, it is the Operating system that does the execution of the library function call by supplying necessary parameters to it.
Ugh no you supply the parameters and the function to call... who cares how it actually happens on the OS level...

beggerking before you reply collect your thoughts and write something that makes sense, I don't understand what you are trying to say/argue here...

What is it that you are arguing, what point did you try to make?

 

Ackmed

Diamond Member
Oct 1, 2003
8,498
560
126
Heh, funny to see him post over there. His sig shows a 2405FPW, when he was so against mine... and LCDs all together, hmm. He is sure to see shimmering now, when in the past he has said it wasnt a problem. Wonder if he still feels that way.

Im sure it works in most A8N-SLI's. Rathets and rollos are different boards though. I doubt its a widespread issue, as its one of the best SLI boards out. I havent been following it though. I had three, the original A8N-SLI, then the Premium, then the A8N32-SLI version. All three were great boards.
 

beggerking

Golden Member
Jan 15, 2006
1,703
0
0
Originally posted by: nts
Originally posted by: beggerking
simple questions. If OS doesn't fetch data from HD how does it run games? If OS doesn't accept interrupt requests how does mouse / keyboard work in a game? All these are processes done by the OS before data are send to a video driver. I won't call all these tasks done by OS as "limited".
And what if anything does this have to do with video drivers? These tasks are independant of what the video driver does...

these tasks, along with driver support and control, are a big part of a operating system. You argued OS's part in graphic output is limited, and I have just proved to you that you were wrong. Driver is only a translator to attach protocoled info into data, so when the data reaches the hardware, it can be decoded and carried out.

OPengl.dll is only a dynamic linked library contain a library of function calls. When a function call within the library is being called, it is the Operating system that does the execution of the library function call by supplying necessary parameters to it.
Ugh no you supply the parameters and the function to call... who cares how it actually happens on the OS level...

beggerking before you reply collect your thoughts and write something that makes sense, I don't understand what you are trying to say/argue here...

What is it that you are arguing, what point did you try to make?
[/quote]

your "The OS can only communicate with the video card in a very limited fashion" is seriously flawed. OS IS the one that sends out all instructions and determines what to be displayed on to the monitor. The only thing a driver does is to translate (protocol) data to be processed by hardware. OS is the one that sends out data.

btw, you supply parameters to a function. it does matter what happens on the OS level since your "game" is basically an application executed and allocated by OS.
 

hans030390

Diamond Member
Feb 3, 2005
7,326
2
76
I recall the setup with the 7950GX2 (in real SLI) to be known as Quad-SLI.

Quad = four.

Therefore, there are four cards in the solution.

That means it is not a single card solution.

But then again, the term "7950GX2" refers to a set of cards...so maybe that means those two cards slapped together is equal to a single card solution?

Hmm...does it really matter?
 

Keysplayr

Elite Member
Jan 16, 2003
21,211
50
91
By the way guys, here is Nvidia's 7950GX2 motherboard compatability list.
It lists make, model and bios version tested so far.

"The NVIDIA® GeForce® 7950 GX2 architecture allows two graphics processing units (GPUs) to be employed on a single graphics card for an ultimate gaming experience. The following motherboards have been tested and passed NVIDIA's compatibility testing requirements with the GeForce 7950 GX2 graphics card."

7950GX2 Motherboard Compatability
 

Rangoric

Senior member
Apr 5, 2006
530
0
71
your "The OS can only communicate with the video card in a very limited fashion" is seriously flawed. OS IS the one that sends out all instructions and determines what to be displayed on to the monitor. The only thing a driver does is to translate (protocol) data to be processed by hardware. OS is the one that sends out data.

Sorry but your programs are not interpreted, they are assembly level. Windows would have crashed and burned in the gaming department if Windows had to be relied on for performance in terms of graphics and sound.

Also, Wrong on the mouse/keyboard. Especially in windows. In Linux/Mac you could say otherwise but...

If you use Direct Input you access the keyboard and mouse directly, without intervention with windows. In fact DirectInput can (and typically does) suppress Windows keyboard messages.

Same with sound. Direct Sound is a direct interface to the sound card.

Just like DirectDraw/3D (now combined into just Direct3D) is a direct interface to the graphics card (via the driver).

Before argueing against this, write a game using only Windows and not DirectX/Opengl, when write it again with DirectX/Opengl. You will very easily notice the performance increase.

Direct X was Microsoft's answer to people having to include their own interface scheme for every video/sound card/keyboard/mouse/joystick on the planet they wanted to support. It provides direct access because nobody would have started using it to make games unless it had simliar performance to dos based games.
 

nts

Senior member
Nov 10, 2005
279
0
0
Originally posted by: beggerking
these tasks, along with driver support and control, are a big part of a operating system. You argued OS's part in graphic output is limited, and I have just proved to you that you were wrong. Driver is only a translator to attach protocoled info into data, so when the data reaches the hardware, it can be decoded and carried out.

Unfortunately you haven't proven anything. Tell me this, can an Operating System access TnL functionality (or anything else 3d, shaders for example) on the graphics card directly? The answer should be an obvious no.

your "The OS can only communicate with the video card in a very limited fashion" is seriously flawed. OS IS the one that sends out all instructions and determines what to be displayed on to the monitor. The only thing a driver does is to translate (protocol) data to be processed by hardware. OS is the one that sends out data.

The OS provides the functionality for the video driver to communicate with the hardware, the OS itself can not do much with the video card directly. Uninstall your video drivers and try it out...

btw, you supply parameters to a function. it does matter what happens on the OS level since your "game" is basically an application executed and allocated by OS.

Ok... who does it matter to? Yes in certain situations there can be optimizations made for the calling convention but ... what are you trying to say here?

 

beggerking

Golden Member
Jan 15, 2006
1,703
0
0
Originally posted by: nts
Unfortunately you haven't proven anything. Tell me this, can an Operating System access TnL functionality (or anything else 3d, shaders for example) on the graphics card directly? The answer should be an obvious no.
[/b]
Operating system provides the command to "access Tnl functionality" to driver, which trasnlates to invoke TnL functionality in hardware, simple as that. Driver doesn't access any function on videocard directly...the driver simply encodes data to be send to the videocard, which will be processed by videocard bios, which will then be decoded and processed by GPU. There is no "direct" connection between driver and videocard.
The OS provides the functionality for the video driver to communicate with the hardware, the OS itself can not do much with the video card directly. Uninstall your video drivers and try it out...
and driver cannot do much with vidoecard directly if videocard itself without OS providing data. Uninstall your Os and try it out....
Ok... who does it matter to? Yes in certain situations there can be optimizations made for the calling convention but ... what are you trying to say here?
just to clarify and correct the wording. thats all.


 

beggerking

Golden Member
Jan 15, 2006
1,703
0
0
Originally posted by: hans030390
Quad = four. Therefore, there are four cards in the solution.

I'd say it meant 4 GPUs, not cards..since SLI is an interface for GPUs..
 

nullpointerus

Golden Member
Apr 17, 2003
1,326
0
0
Originally posted by: keysplayr2003
By the way guys, here is Nvidia's 7950GX2 motherboard compatability list.
It lists make, model and bios version tested so far.

"The NVIDIA® GeForce® 7950 GX2 architecture allows two graphics processing units (GPUs) to be employed on a single graphics card for an ultimate gaming experience. The following motherboards have been tested and passed NVIDIA's compatibility testing requirements with the GeForce 7950 GX2 graphics card."

7950GX2 Motherboard Compatability
Cool! My aging NF4 Ultra board is on the list. Too bad I'm all out of funds ATM. :(
 

nts

Senior member
Nov 10, 2005
279
0
0
Originally posted by: beggerking
Operating system provides the command to "access Tnl functionality" to driver, which trasnlates to invoke TnL functionality in hardware, simple as that. Driver doesn't access any function on videocard directly...the driver simply encodes data to be send to the videocard, which will be processed by videocard bios, which will then be decoded and processed by GPU. There is no "direct" connection between driver and videocard.

Ok answer me this, without a driver installed what can the OS do with the video card?

Does the OS need to know what TnL functionality even is or if your card supports it?
 

Rangoric

Senior member
Apr 5, 2006
530
0
71
Originally posted by: beggerking

and driver cannot do much with vidoecard directly if videocard itself without OS providing data. Uninstall your Os and try it out....

Xbox.
 

beggerking

Golden Member
Jan 15, 2006
1,703
0
0
Originally posted by: Rangoric
Originally posted by: beggerking

and driver cannot do much with vidoecard directly if videocard itself without OS providing data. Uninstall your Os and try it out....

Xbox.

xbox doesn't have an OS? I'm pretty sure I've heard something about a stripped down win2000 OS that is been used in xbox...
 

Ulfhednar

Golden Member
Jun 24, 2006
1,031
0
0
All consoles have an OS, as even firmware is a sort of ultra no-frills OS as far as I am aware. The Xbox is no exception.
 

beggerking

Golden Member
Jan 15, 2006
1,703
0
0
Originally posted by: nts
Originally posted by: beggerking
Operating system provides the command to "access Tnl functionality" to driver, which trasnlates to invoke TnL functionality in hardware, simple as that. Driver doesn't access any function on videocard directly...the driver simply encodes data to be send to the videocard, which will be processed by videocard bios, which will then be decoded and processed by GPU. There is no "direct" connection between driver and videocard.

Ok answer me this, without a driver installed what can the OS do with the video card?

Does the OS need to know what TnL functionality even is or if your card supports it?

Answer me this first , without an OS install what can the driver do with the video card?

Your game(which works under OS) needs to know what TnL is and your card needs to support it.
 

nts

Senior member
Nov 10, 2005
279
0
0
Originally posted by: beggerking
Originally posted by: nts
Originally posted by: beggerking
Operating system provides the command to "access Tnl functionality" to driver, which trasnlates to invoke TnL functionality in hardware, simple as that. Driver doesn't access any function on videocard directly...the driver simply encodes data to be send to the videocard, which will be processed by videocard bios, which will then be decoded and processed by GPU. There is no "direct" connection between driver and videocard.

Ok answer me this, without a driver installed what can the OS do with the video card?

Does the OS need to know what TnL functionality even is or if your card supports it?

Answer me this first , without an OS install what can the driver do with the video card?
I have no idea what you are trying to say/prove with this point. Without an OS you wouldn't have a driver, they are OS specific. The video card will still function however (eg BIOS screen on your computer) except you get very, very basic functionality about the same as an OS gets without a driver installed.

Without a computer (hardware), what can you do with the OS...

Your game(which works under OS) needs to know what TnL is and your card needs to support it.

No it does not. The game simply asks OpenGL/Direct3d to draw something, it doesn't care if TnL is present on the hardware or not (as long as the feature is supported in some form). You will simply get a software implementation (in the driver) if the card doesn't support it.

For example you can use basic vertex shaders on the GF4MX but the card doesn't actually support them (GF2), its just a software implementation in the driver. Doesn't matter to the game, they query the capabilities of the card and vertex shaders are present so it is free to use them (it does not care how it is implemented in the driver/hardware).

What are you still trying to argue?
 

beggerking

Golden Member
Jan 15, 2006
1,703
0
0
Originally posted by: nts
Originally posted by: beggerking
Originally posted by: nts
Originally posted by: beggerking
Operating system provides the command to "access Tnl functionality" to driver, which trasnlates to invoke TnL functionality in hardware, simple as that. Driver doesn't access any function on videocard directly...the driver simply encodes data to be send to the videocard, which will be processed by videocard bios, which will then be decoded and processed by GPU. There is no "direct" connection between driver and videocard.

Ok answer me this, without a driver installed what can the OS do with the video card?

Does the OS need to know what TnL functionality even is or if your card supports it?

Answer me this first , without an OS install what can the driver do with the video card?
I have no idea what you are trying to say/prove with this point. Without an OS you wouldn't have a driver, they are OS specific. The video card will still function however (eg BIOS screen on your computer) except you get very, very basic functionality about the same as an OS gets without a driver installed.

Without a computer (hardware), what can you do with the OS...

and I have no idea what you are trying to say/prove with "Ok answer me this, without a driver installed what can the OS do with the video card?".
Your game(which works under OS) needs to know what TnL is and your card needs to support it.

No it does not. The game simply asks OpenGL/Direct3d to draw something, it doesn't care if TnL is present on the hardware or not (as long as the feature is supported in some form). You will simply get a software implementation (in the driver) if the card doesn't support it.

For example you can use basic vertex shaders on the GF4MX but the card doesn't actually support them (GF2), its just a software implementation in the driver. Doesn't matter to the game, they query the capabilities of the card and vertex shaders are present so it is free to use them (it does not care how it is implemented in the driver/hardware).

What are you still trying to argue?
the game needs to be programmed to know what TnL is and make use of it. Your hardware needs to be able to support the TnL to correctly display it. software implementation is basically a rasterized form of the effect that is why DX9 effects don't look as good with a DX8 cards.

what are you still trying to argue now?
 

nts

Senior member
Nov 10, 2005
279
0
0
Originally posted by: beggerking
and I have no idea what you are trying to say/prove with "Ok answer me this, without a driver installed what can the OS do with the video card?".
The original argument was started with you saying that software (drivers) has nothing to do with hardware (independant of one another) and hardware doesn't need drivers (because it works fine without them) except to improve performance. Which is not true.

the game needs to be programmed to know what TnL is and make use of it. Your hardware needs to be able to support the TnL to correctly display it. software implementation is basically a rasterized form of the effect that is why DX9 effects don't look as good with a DX8 cards.

what are you still trying to argue now?

Umm no. The game needs to use a rendering API that supports TnL (Texturing and Lighting), it doesn't care how the end result is achieved (software or hardware). All rendering APIs (OpenGL/Direct3D/Glide...) have TnL support and the drivers ran it in software when it was not possible to run it in hardware. There are even software implementations supporting texturing and lighting (Quake 1,2...).

Please check some terms that you use before using them, like rasterize because your definitions for them are not correct. Having pixel shaders run in software can and will drop you to sub 1 FPS and no game out there has pixel shaders running in software.

Why some effects don't look so good on DX8 as apposed to DX9 is because DX8 does not support SM2. SM2 was a very big step up from SM1.x and a lot of what you can do with SM2 is not possible (feasable) to do with SM1.x.

Well this is getting pointless now so this will be my last post in this topic.