10-12-2010, 03:50 PM
First I would like to say that Reader3ds library (used by Viewer3ds) is made for WPF (Windows Presentation Foundation) that also has some 3D support. It is not directly for DirectX. The WPF is internally using DirectX. It does not provide full features of DirectX and full performance. But on the other hand it is much easier to use - does not require c++ stuff but can be used in managed .net.
Also my library only works for 3ds file and does not support other file formats (.X, .dxf, etc.)
From only the 3ds file I cannot say why the textures are missing. There should be some texture images with the file also to check this. If you would like that I check the file in more details, please zip the 3ds file with its texture files together and attach them to you post.
The problem with transparencies in WPF is caused by way WPF (I am not sure for DirectX) draws transparencies. Generally speaking all transparent objects must be defined lastly. If there are some other objects defined after the transparent object, they will not be visible through the transparent object.
This must be taken into account when creating the model.
Also my library only works for 3ds file and does not support other file formats (.X, .dxf, etc.)
From only the 3ds file I cannot say why the textures are missing. There should be some texture images with the file also to check this. If you would like that I check the file in more details, please zip the 3ds file with its texture files together and attach them to you post.
The problem with transparencies in WPF is caused by way WPF (I am not sure for DirectX) draws transparencies. Generally speaking all transparent objects must be defined lastly. If there are some other objects defined after the transparent object, they will not be visible through the transparent object.
This must be taken into account when creating the model.
Andrej Benedik