Re: Any ideas on this?
- From: "Cor Ligthert [MVP]" <notmyfirstname@xxxxxxxxx>
- Date: Wed, 20 Sep 2006 18:26:51 +0200
Kevin,
I know, Herfried has given often the same answer in the newsgroup
language.vb.
However, thanks for your deep explanation, which reminds me again better to
it.
But it still is a gues in my opinion. While than in my idea it can be the
soundcard as well, for which is too DirectX support.
Cor
"Kevin Spencer" <uce@xxxxxxx> schreef in bericht
news:OniKY$K3GHA.1288@xxxxxxxxxxxxxxxxxxxxxxx
Well, it was an educated guess, based upon the very limited amount of
information provided, and my own experience with DirectX. DirectX sits
directly on top of the Hardware Abstraction Layer of the OS, and is
designed to work directly with the video card, which does most of the
actual drawing work. Most video cards these days have support for storing
and drawing 3D objects, to some extent or another. DirectX therefore has
quite a number of methods for getting video card support information from
the video card, as not all video cards support all of the same types of
operations, and vary in terms of video memory, etc.
If one builds a DirectX application that draws on one machine, and does
not include enough querying to the video card to find out what it
supports, one's code may attempt to use some function that is not
supported by a video card on a different machine. This would result in the
kind of behavior described by the OP.
The OP was somewhat unclear about what he was doing, but did mention the
term "scene," which is a DirectX term for a 3D "scene". Since he indicated
that the app works fine on one machine, but breaks on others, because
DirectX relies quite heavily on the video card's capabilities, and since
the OP didn't mention anything about the video cards on these other
machines, I concluded that it was most likely that the OP was not aware of
the intimate dependency of DirectX on hardware. Therefore, I somewhat
tentatively suggested that he look at the video card differences between
the machines.
--
HTH,
Kevin Spencer
Microsoft MVP
Software Composer
A watched clock never boils.
"Cor Ligthert [MVP]" <notmyfirstname@xxxxxxxxx> wrote in message
news:%230xTZzG3GHA.1256@xxxxxxxxxxxxxxxxxxxxxxx
Kevin,
Why not the sound card?
:-)
You are right with your answer but in my idea is this not resolvable by a
newsgroup than just guessing.
Cor
"Kevin Spencer" <uce@xxxxxxx> schreef in bericht
news:utmok7E3GHA.324@xxxxxxxxxxxxxxxxxxxxxxx
Video card?
--
HTH,
Kevin Spencer
Microsoft MVP
Digital Carpenter
A man, a plan, a canal,
a palindrome that has gone to s**t.
"Daniel" <DanielV@xxxxxxxxxxxxxxxx> wrote in message
news:ulCHWPE3GHA.324@xxxxxxxxxxxxxxxxxxxxxxx
Hey guys
I have a app that runs fine on my deve machine, in debug oe or straight
from my installer.
Stick it on another machine, similar spec and when i close a child form
it closes the whole app....essentially crashing but no crash message.
It's as tho i closed it.
On another machine it crashes on closing the second form that pops up.
This form is a directx scene.
So why on my dev machine does this never happen? But happens 100% of
the time on other machines, what difference could their be?
.
- References:
- Any ideas on this?
- From: Daniel
- Re: Any ideas on this?
- From: Kevin Spencer
- Re: Any ideas on this?
- From: Cor Ligthert [MVP]
- Re: Any ideas on this?
- From: Kevin Spencer
- Any ideas on this?
- Prev by Date: Re: Weird CultureInfo - DateTime.Parse() and Decimal.Parse()
- Next by Date: Re: What is the best way to do this...
- Previous by thread: Re: Any ideas on this?
- Next by thread: Re: Any ideas on this?
- Index(es):
Relevant Pages
|