See-through Tony

[ShrikeHawk 384]

Anybody know what causes this?

 

[+aleks 9]

if u use a custom made model , perhaps you mast reset x-form in 3d studio max for the piece

[ShrikeHawk 384]

Gosh I hope not. This is an A-Team model. It looked just fine in SF1. But when placed in SF2 it suddenly has this visual effect.

[Wrench 9,847]

I'll venture a guess ... XP and SF2 and DX9??

 

artifacts caused by how SF2 "reads" lods. We'd had some issues with that in KAW as well

 

OTH, it dosen't seem to be present in SF2 w/DX10 (although, the expected shadow artifacts are -the infamous 'tractor beam'

[ShrikeHawk 384]

I'll venture a guess ... XP and SF2 and DX9??

 

artifacts caused by how SF2 "reads" lods. We'd had some issues with that in KAW as well

 

Sheesh! Right on all points. So I guess I'm just screwed on this one, yes?

[Heck 496]

Sheesh! Right on all points. So I guess I'm just screwed on this one, yes?

 

No, there's an error for a missing material in the out file. Report it to Capun on his message board using the request for mods/fixes post in the tech support section and he can fix it. He did it for all the spitfires and the Ju88. In the meantime, copy and paste the following into your data.ini at the end of the [AircraftData] section. It's a quick fix that works on my system, and I'm using SF2 in Windows XP.

 

 

Component[010]=Move1

 

[Move1]

ParentComponentName=Fuselage

ModelNodeName=Panel2

DestroyedNodeName=Panel2

DetachWhenDestroyed=TRUE

HasAeroCoefficients=FALSE

 

 

 

 

[+russouk2004 6,958]

kev...does the tony use old shd lod?...doesnt the new shadow method cure it?

Edited June 16, 2011 by russouk2004

[Wrench 9,847]

the tractor beam is with the new (08+/SF2) shadow statement. It dosen't have a SHD of it own.

[ShrikeHawk 384]

No, there's an error for a missing material in the out file. Report it to Capun on his message board using the request for mods/fixes post in the tech support section and he can fix it. He did it for all the spitfires and the Ju88. In the meantime, copy and paste the following into your data.ini at the end of the [AircraftData] section. It's a quick fix that works on my system, and I'm using SF2 in Windows XP.

 

Component[010]=Move1

 

[Move1]

ParentComponentName=Fuselage

ModelNodeName=Panel2

DestroyedNodeName=Panel2

DetachWhenDestroyed=TRUE

HasAeroCoefficients=FALSE

 

Awesome! That worked great. Thanks very much, Heck!