From: Akula2 <akula2.shark@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Gaming Interface
Date: Wed, 10 Jan 2007 16:36:38 +0530 [thread overview]
Message-ID: <8355959a0701100306k84e322ci54155e9f7d3f3c46@mail.gmail.com> (raw)
In-Reply-To: <45A437C6.9040506@shaw.ca>
> On 1/10/07, Robert Hancock <hancockr@shaw.ca> wrote:
>
> How is that? id Software doesn't use DirectX (not for graphics, anyway)
> and you could hardly claim their engines have been technically inferior
> at the time of their release..
Direct3D meant for 3D hardware interface. The feature set of D3D is
derived from the feature set of what hardware provides. OpenGL meant
to be a 3D rendering system that may be hardware accelerated.
There are functional differences in how the two APIs work. Direct3D
expects the application to manage hardware resources; OpenGL makes the
implementation do it.
This makes it much easier for the user in terms of writing a valid
application, but it leaves the user more susceptible to implementation
bugs that the user may be unable to fix.
At the same time, because OpenGL hides hardware details, the user is
unable to query the status of various hardware resources.
The Direct3D model frustrated many programmers. I do remember a game
developer named John Carmack who urged Microsoft to abandon Direct3D
in favor of OpenGL!
> Robert Hancock Saskatoon, SK, Canada
~Akula2
next prev parent reply other threads:[~2007-01-10 11:06 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa./yEu+Q5zfyi+9Dt6KeRH/0YTv6M@ifi.uio.no>
[not found] ` <fa.lZ5ow3GVFhmIN84swduaYc/QGC8@ifi.uio.no>
[not found] ` <fa./w7HN6qfHdRrvVr4gQ41Yr6D2Zs@ifi.uio.no>
[not found] ` <fa.wzIAazh/K3RXZGwCv85z7hMkX9w@ifi.uio.no>
[not found] ` <fa.QdkEYH0MeusxZdKe4kSh6Svj6dI@ifi.uio.no>
[not found] ` <fa.j23ZZ5CMmxfxN0vEdIJJTHQ1MeE@ifi.uio.no>
2007-01-10 0:48 ` Robert Hancock
2007-01-10 11:06 ` Akula2 [this message]
2007-01-08 11:39 Dirk
2007-01-08 10:43 ` Trent Waddington
2007-01-08 12:13 ` Dirk
2007-01-08 11:17 ` Jay Vaughan
2007-01-08 13:04 ` Dirk
2007-01-08 14:09 ` Helge Hafting
2007-01-08 15:36 ` Dirk
2007-01-08 15:11 ` l.genoni
2007-01-08 19:31 ` Jan Dittmer
2007-01-09 7:14 ` Dirk
2007-01-09 6:16 ` Trent Waddington
2007-01-09 7:07 ` Adrian Bunk
2007-01-09 7:10 ` Trent Waddington
2007-01-09 16:08 ` Lennart Sorensen
2007-01-09 23:02 ` Valdis.Kletnieks
2007-01-09 23:05 ` Lennart Sorensen
2007-01-09 9:50 ` Kasper Sandberg
2007-01-09 12:15 ` Jesper Juhl
2007-01-09 16:07 ` Lennart Sorensen
2007-01-08 19:57 ` Adrian Bunk
2007-01-09 7:16 ` Dirk
2007-01-09 7:00 ` Adrian Bunk
2007-01-09 7:08 ` Trent Waddington
2007-01-09 9:51 ` Kasper Sandberg
2007-01-09 4:40 ` Kasper Sandberg
2007-01-09 7:22 ` Dirk
2007-01-09 9:48 ` Kasper Sandberg
2007-01-09 12:10 ` Helge Hafting
2007-01-09 16:04 ` Lennart Sorensen
2007-01-09 16:51 ` Adrian Bunk
2007-01-09 21:14 ` Akula2
2007-01-08 14:47 ` Alistair John Strachan
2007-01-08 20:39 ` Jan Engelhardt
[not found] ` <a06230924c1c7d795429a@192.168.2.101>
2007-01-08 11:42 ` Dylan Taft
2007-01-08 21:57 ` Tomas Carnecky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8355959a0701100306k84e322ci54155e9f7d3f3c46@mail.gmail.com \
--to=akula2.shark@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®