February 2, 2004 at 9:22 am /
#3264
It does look like its fixed now.
February 2, 2004 at 9:22 am /
#21225
It seems that 3DC models do not work properly in [img:12yhgc4o]http://www.3impact.com[/img:12yhgc4o]
3impact
becouse 3DC doesn’t exports vertex-normals properly to .x files. Or at least this is what the developers of 3impact replied to me when I asked about the problem. They also said that they can’t do much about. Is there anything that can be done to make 3impact and 3DC to wotk together?
The attachment is a shot from 3impact to show the problem.
‘Eat me! See if I care.’
February 2, 2004 at 12:47 pm /
#21226
This might be a workaround for you.
try to crease your model before you export it – try both extreams of the crease function and let us know if it helps ?
February 2, 2004 at 2:09 pm /
#21227
3DC exports vertex normals properly to X files. It’s easy to show that it does. Try exporting a smooth and creased cube and then import them with Microsoft’s X viewer program (mview.exe) that comes with the DirectX SDK.
I just tried it with a cube and sphere both creased and smooth and it worked fine.
Richard
February 4, 2004 at 11:52 pm /
#21228
The creasing doesn’t help at all, I’ve tried it. I have also tried a lot of different material settings, but none seem to help.
This is the reply I got:
[BLOCKQUOTE class=’ip-ubbcode-quote’][font size=’-1′]quote:[/font][HR]The way light is shaded on a surface depends on how the so called
‘vertex-normals’ are computed by the modeler and, in particular, whether
they are preserved when the model is finally exported to .x[HR][/BLOCKQUOTE]
Maybe the normals could be exported differently?
‘Eat me! See if I care.’
February 5, 2004 at 11:21 am /
#21229
As I said, the normals appear to be exported correctly and that has been confirmed by the use of the Microsoft viewer. I would say that the final word on whether the normals are correctly exported or not would be Microsoft’s since it is their format. Since their viewer shows them to be correct then they are very likely correct.
All I can suggest is that you get them (3impact) to indicate where there is a problem and why it is Microsoft’s viewer shows the normals correctly.
Richard
[This message was edited by Amabilis Support on Thu February 05 2004 at 11:31 AM.]
February 5, 2004 at 11:50 am /
#21230
Looking at your sample again I would suggest that you look at materials rather than normals. Try varying your materials to see if you can improve the appearance. If I recall correctly ‘diffuse’ is not actually supported by the DirectX format. Try varying ‘Ambient’ and perhaps ‘specualr’ to see if makes any difference.
Richard
February 5, 2004 at 12:47 pm /
#21231
OK, I’ll pass this information to them. But as I said above, the material settings do not seem to have any effect on the error. <!– s:( –><img src="{SMILIES_PATH}/icon_e_sad.gif" alt="
" title="Sad" /><!– s:( –> Thanks anyway. I’ll just keep on trying to find a solution. <!– s:) –><img src="{SMILIES_PATH}/icon_e_smile.gif" alt="
" title="Smile" /><!– s:) –>
‘Eat me! See if I care.’
February 6, 2004 at 5:02 am /
#21232
I also forgot say that this problem aplies for 3DC only. So there must be something differently in 3DC’s models than in the models from other modellers. They promised to look at problem, so I hope it gets fixed by them then. <!– s:) –><img src="{SMILIES_PATH}/icon_e_smile.gif" alt="" title="Smile" /><!– s:) –>
‘Eat me! See if I care.’
February 6, 2004 at 10:44 am /
#21233
I can confrim this.
THe best I’ve come is by setting diffuse to Zero.(Ambient seems to have no effect).
But the white shows in small corners still when the light is at the right angle to the model.
When I import the X model to MS3D an re-export it the problem is %100 fixed even with normal diffuse setting.
I’ve also tried creasing and any other material settings I could think of .
I think I even tested TS3.2 an no problem.
I really like using 3DC but, right now it’s a pain to have to convert everything.
This new impact game-engine is new but it could be big,bigger than DBP(it has excellent physics), would you please get in touch with them and try to solve this problem Richard? It would be much appreciated.
February 6, 2004 at 11:44 am /
#21234
I also think this 3impact has great potential! It has wonderful built in physics and great graphical capabilites. <!– s:) –><img src="{SMILIES_PATH}/icon_e_smile.gif" alt="" title="Smile" /><!– s:) –>
‘Eat me! See if I care.’
[This message was edited by Timo on Fri February 06 2004 at 12:16 PM.]
February 11, 2004 at 11:26 am /
#21235
Mogul, could you please tell what graphic card you have. It seems that this problem doesn’t happen to everyone.
‘Eat me! See if I care.’
February 11, 2004 at 5:13 pm /
#21236
Mogul,
Can you send me a X file exported from 3DC and the X file re-exported from MS3D so that I can compare and see what the differences are? The MS3D model would need to be in ASCII format for me to be able to compare. (<!– e –><a href="mailto:support@amabilis.com">support@amabilis.com</a><!– e –>)
Try to make it the simplest model possible.
Richard
February 12, 2004 at 2:11 am /
#21237
I’ll upload you some files from a 3DC user whose files work properly with 3impact. <!– s:) –><img src="{SMILIES_PATH}/icon_e_smile.gif" alt="" title="Smile" /><!– s:) –>
‘Eat me! See if I care.’
February 12, 2004 at 6:10 am /
#21238
The problem is solved! (I hope) The problem happens when specularity is set 0 in 3DC. I’m sure I checked that, but I it seems I didn’t, or then I messed up something else. Sorry, my fault. <!– s:( –><img src="{SMILIES_PATH}/icon_e_sad.gif" alt="" title="Sad" /><!– s:( –>
‘Eat me! See if I care.’
You must be logged in to reply in this thread.