Issue with lighting on DTS model (TGEA 1.7.1)
by Frank Bignone · in Torque Game Engine Advanced · 01/27/2009 (5:32 pm) · 11 replies
I was trying to solve this issue for few weeks already, but still stuck. The next screenshot depicts current issue. Models do not light correctly inside TGEA 1.7.1, compared to how they display inside TorqueShowTool Pro. For information, there were no issue in TGEA 1.0.3.
Here is a link of the model shown in the previous screenshot.
All help is welcome...
Here is a link of the model shown in the previous screenshot.
All help is welcome...
About the author
Real programmers don't waste time recompiling; they patch the binary files... ... Real programmers don't waste time patching binary files; they patch memory.
#2
01/27/2009 (8:04 pm)
A comparison of the model in 1.7.1 and the model in 1.0.3 would be very much appreciated.
#3
01/27/2009 (8:23 pm)
Same as in Torque Show Tool Pro. Here is a screenshot on TGEA 1.0.3 of the same model from an old build.
#4
01/28/2009 (10:48 pm)
This is an art issue. Your model has broken normals, or may not even have normals at all (!). TST is showing that absolutely no lighting is happening, while TGEA 1.7.0 and later are using broken/nonexistant normals to do lighting. I'm going to say that we require correct normals for correct lighting.
#5
01/31/2009 (12:48 am)
@Alex: thanks for the info. Nevertheless as I'm not an artist, I wonder how it is possible to not have normals inside a model. Every soft package do not create normals when editing 3d models? Can it be an issue during the export process in DTS file format?
#6
01/31/2009 (12:53 am)
I'm not sure how the model could lack normals as well, but that certainly seems to be what's going on. Something having gone wrong during export is extremely likely. There was another lighting issue which was resolved by reexporting the mesh with a more recent exporter, you may want to try the same.
#7
How the ugliness happened for me:
I had exported from Max with the 2-sided setting on my max-material slot. Everything looked like shite. The only way I resolved the ugliness was to remove the 2-sided setting of the max material slot prior to export.
Reference image:
click to enlarge
...is your material 2 sided prior to export ?
Perhaps this is just a max2dts related issue ?
[ ..edited so people can understand better. ;) ]
01/31/2009 (10:26 pm)
I thought this was an issue of normals as well but TGEA does this with a 2 sided material. How the ugliness happened for me:
I had exported from Max with the 2-sided setting on my max-material slot. Everything looked like shite. The only way I resolved the ugliness was to remove the 2-sided setting of the max material slot prior to export.
Reference image:
click to enlarge
...is your material 2 sided prior to export ?
Perhaps this is just a max2dts related issue ?
[ ..edited so people can understand better. ;) ]
#8
01/31/2009 (11:31 pm)
I wasn't really sure what eb was trying to say in his above post. But I did want to note that there is a doublesided material flag in TGEA that might help. If memory serves correct you just add a doublesided = True; or a doublesided[0] = True; to the material definition in the material.cs file.
#9
I exported 2 korks from max: 1 as anyone normally would and 1 with a 2-sided max-material.
Here is a 30 second video of the oddity of which I speak. There are 3 segments to the video.
1.6MB Divx Vid
The Kork on the right is the 2sided export. ;)
02/01/2009 (12:19 am)
Sorry if I am not on the same track as you Frank...but if I am, then ;) .I exported 2 korks from max: 1 as anyone normally would and 1 with a 2-sided max-material.
Here is a 30 second video of the oddity of which I speak. There are 3 segments to the video.
1.6MB Divx Vid
The Kork on the right is the 2sided export. ;)
#10
Unfortunately it's too late to try and address this for 1.8.1. It's also quite possible that the max exporter is causing the problem, in which case there's not much I could do anyways.
02/02/2009 (2:19 am)
I bet Frank's mesh was exported as two sided to deal with the... kilt?Unfortunately it's too late to try and address this for 1.8.1. It's also quite possible that the max exporter is causing the problem, in which case there's not much I could do anyways.
#11
The link is to an image that shows the same files in TGE and showtoolpro.
example image
02/02/2009 (3:28 am)
I would guess the max exporter unless this has been an issue that no one has ever spoken about. The link is to an image that shows the same files in TGE and showtoolpro.
example image
Torque Owner Surge
MDNAMEDIA
Which Im guessing would be totaly different.