How many people here are actually using D3DX meshes?
Author
I am a little curious about the rest of you. How many of you are using the D3DX implementation of the mesh class? How many of you are using your own custom mesh classes? I like the fact that there are some wonderful functions, such as the Insersect method, but I am not sure I like D3DX doing everything for me.
How about the rest of you?
Author
True enough, but don't you find it more difficult to load in meshes from different file formats? I would think it would be much easier to load in meshes from whatever file format if you have your own mesh implementation rather than using the D3DX mesh implementations and having to convert everything so it fits into the D3DX mesh.
Quote:Original post by Moe
I am a little curious about the rest of you. How many of you are using the D3DX implementation of the mesh class? How many of you are using your own custom mesh classes? I like the fact that there are some wonderful functions, such as the Insersect method, but I am not sure I like D3DX doing everything for me.
The only time I will use them is if I have to use one of the D3DX geometry functions that require an ID3DXMesh as input. Even then, this is usually in some pre-process, so it is ok to take the extra time to do it. However, I have heard this is changing in D3DX10, so that you can just pass in a block of vertex data, ect.
Do you mean the DXUT mesh class? D3DX just provides a function for creating a mesh. I wrote my own class for handling meshes, since I want a lot of control over them. I looked briefly at the DXUT mesh class, and did not see it as providing much that you cannot easily code yourself, like a routine to load a mesh and its materials and textures.
I use ID3DXMesh in my code, mainly due to simplicity but also due to the fact that I don't have anything else that's any better!
Cheers,
Jack
Quote:Original post by circlesoftThere's not much information to work with yet, but it seems to be going that way. The few D3DX mesh functions in the Feb CTP use pointers to D3DXVECTOR3's.
I have heard this is changing in D3DX10, so that you can just pass in a block of vertex data, ect.
Cheers,
Jack
Hi,
most of the time I use ID3XMesh too, because it usually makes things easier, and I rely on D3DX functions heavily. Of course, there are cases (like billboards, things built up from lines - and not wireframe meshes, etc..) when it's just simpler to use a plain vertex buffer instead.
kp
most of the time I use ID3XMesh too, because it usually makes things easier, and I rely on D3DX functions heavily. Of course, there are cases (like billboards, things built up from lines - and not wireframe meshes, etc..) when it's just simpler to use a plain vertex buffer instead.
kp
I have my own mesh class. I find the .x format too DX dependent. Since I use my custom exporter for MAX I can implement new functionality to the mesh as I need.
Quote:Original post by Dave
How easy is it to write a 3DS exporter.
Using the format = ok
Using the Max API = hell [bawling]
I guess using the IGame interface is managable, though.
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement
