Sure, there have been threads on the DBPro forums regarding these or similar issues. andnbsp;I was just suggesting that Amabilis take the initiative to make 3DC into more of andquot;The Dream Modellerandquot; for DBPro, with features that make it simple to use models in DBPro that are made in 3DC and with complete features (like multi-texturing, etc.). andnbsp;We’ll see if there is any motivation in the upcoming updates to 3DC…
It’d be nice if 3DC had better built-in andquot;supportandquot; for users making models (animated or not) for DarkBasic Pro.
For example, it’d be nice if the .X exporter had an option copy any texture files the model needs to the destination directory where the .X file is being saved, convert the textures to BMP, rather than requiring the user to manually do this every time they export a model.
Another issue for DBPro users is the model heirarchy. andnbsp;There’s no way to know by looking at a model in 3DC what LIMB number a part of the model will have in DBPro.
These are just a couple of the things I can think of off the top of my head… I’m sure there are others. andnbsp;I realize that probably many of these things are not specifically missing features from either app, but given the relationship with 3DC and DBPro (TGC offers 3DC Pro from their site), users probably have expectations about 3DC working andquot;seemlesslyandquot; with DBPro. andnbsp;As it stands now, 3DC supports .X format, and DBPro users are andquot;on their ownandquot; to figure out what needs to be done to make a model in 3DC and load it into DBPro and figure out all the little intracacies about the object heirarchy, how bones work, why deformation doesn’t work with boned animations loaded into DBPro… the list of little issues goes on and on.
Ideally, it’d be nice if Amabilis would contact DBPro about the new object format DBPro is using internally (.DBO) and add features to 3DC to directly support that. andnbsp;Failing that, maybe some other format could be used that makes the apps work together more seemlessly. andnbsp;Currently I don’t think DBPro supports multiple textures for an object loaded via a .X files (i.e., lightmap/bumpmap/etc. textures in addition to the base texture). andnbsp;Before DBPro Update 4.X, I don’t think the material properties (like color) were supported – only the mesh and the base textures. andnbsp;Once DBPro starts supporting these features, it’d be nice to have 3DC include them in the .X export file. andnbsp;I’m not even sure if you have a material in 3DC that includes 2 or more textures whether the current .X exporter even attempts to write all the textures to the .X file or just the base texture…
Let me know if you need someone to help work on making these two apps work better together (new .X exporter plug-in, etc.) or just want to kick around ideas. andnbsp;I have limited time for more andquot;projectsandquot;… but the savings in wasted time would probably be worth the effort.
Ed andnbsp;Phillips [ed@u_d_e_l.e_d_u] andnbsp;(remove the underscores)
You must be logged in to reply in this thread.
