Re: Mesh.LoadHierarchy in February Update
- From: "ZMan" <zman@xxxxxxxxxxxxxx>
- Date: Thu, 16 Feb 2006 12:35:23 -0800
February update has both 1.1 assemblies (1.0.290x) and 2.0 beta assemblies.
I will assume you are using the 1.1 files. If you are using the beta
assembly then it could well be a bug and you should post it in the beta
newsgroup http://msdn.microsoft.com/directx/beta/default.aspx
However really the only steps I can suggest you take are to closely examine
the code compared to the Simple Animation sample - I assume if you load your
mesh into simple animation then it renders correctly? If so then it might be
a 'line by line' examination to find out what is different in yours.
Sorry I don't have a more definitive answer and I still have no idea what
would have changed since October? Maybe they tightened up some error
checking in the native libraries (MDX does very little other than call the
native API).
You could try turning on the debug DLLs and upping the debug output in
control panel. Then if you start your program and enable unmanaged debugging
in the project option you will see a *lot* of debug output from directX.
Maybe there will be a better error in there.
--
Zman
http://www.thezbuffer.com - News and information for Managed DirectX
"beetofen" <beetofen@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:EACD10D2-2010-4653-BB6A-96E10B61A4E4@xxxxxxxxxxxxxxxx
I'm using the .NET 2.0 with VS2005 and the february update of the DirectX
SDK. The line
rootFrame = Mesh.LoadHierarchy(device, file, MeshFlags.Managed, alloc,
null);
throw a DirectXException. alloc is a CustomAllocateHierachy like in the
simple animation tutorial. I use the classes CustomFrame,
CustomAllocateHierarchy and CustomMeshContainer from the simple animation
sample.
When I put a break on the CreateFrame-method of the
CustomAllocateHierarchy,
it stops onetime with the first frame of the x-file. After this, the
DirectXException is throwing.
Thx for help, beetofen
"ZMan" wrote:
Which would indicate a problem in your code. (well apart from the fact
that
it used to work in Oct/1.1 but lets ignore that for a moment)
So what line of code does the exception actually happen on ? Is all the
code
your own or did you take any from a book or maybe the Simple Animation
sample (which is another good one to try to load your mesh into).
Has anything else changed? e.g. are you now using VS2005 instead of
VS2003,
are you using the beta assemblies or still on the 1.1 assemblies
(1.0.29xx
is 1.1 assemblies, 2.0.xxxx is beta assemblies)
--
Zman
http://www.thezbuffer.com - News and information for Managed DirectX
"beetofen" <beetofen@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:06006D0D-6311-4991-BF77-917DA89093DF@xxxxxxxxxxxxxxxx
Yes
"ZMan" wrote:
Does it load into the DirectX viewer application?
--
Zman
http://www.thezbuffer.com - News and information for Managed DirectX
"beetofen" <beetofen@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:185698B9-F577-469A-BB12-C3E74F87D048@xxxxxxxxxxxxxxxx
Was anyone able to load a framehierarchy from a X-File with the
february
update? I just have a DirectXException if I try it. The X-File I'm
using
is
loadable with .NET 1.1 and the October SDK.
Thx for help
.
- Follow-Ups:
- Re: Mesh.LoadHierarchy in February Update
- From: beetofen
- Re: Mesh.LoadHierarchy in February Update
- From: beetofen
- Re: Mesh.LoadHierarchy in February Update
- References:
- Re: Mesh.LoadHierarchy in February Update
- From: ZMan
- Re: Mesh.LoadHierarchy in February Update
- From: ZMan
- Re: Mesh.LoadHierarchy in February Update
- Prev by Date: Re: Rendering points, performance
- Next by Date: Re: Problem changing window size during Sample Framework for DirectX 9.0
- Previous by thread: Re: Mesh.LoadHierarchy in February Update
- Next by thread: Re: Mesh.LoadHierarchy in February Update
- Index(es):
Relevant Pages
|
