0001644: Texture Replacement and Model Swapping incompatible

ID	Project	Category	View Status	Date Submitted	Last Update

0001644	FSSCP	graphics	public	2008-03-30 04:26	2008-03-31 09:00

Reporter	Galemp	Assigned To	taylor
Priority	normal	Severity	major	Reproducibility	always
Status	resolved	Resolution	duplicate
Product Version	3.6.9

Summary	0001644: Texture Replacement and Model Swapping incompatible
Description	The texture replacement code doesn't work properly when the model is swapped out after mission load, for instance, if the player assigns his squad a different ship class. The swapped texture is kept in memory and replaces whatever textures are supposed to be applied to the new class. See attached screenshot for reference.
Additional Information	The desired effect is to be able to paint squadrons in the same colors, even if they change ships. For example, in a mission file, at the end of each fighter entry in Red wing, we have this: ;;FSO 3.6.8;; $Texture Replace: ;;FSO 3.6.8;; +old: xwing ;;FSO 3.6.8;; +new: xwing-red ;;FSO 3.6.8;; +old: ywing ;;FSO 3.6.8;; +new: ywing-red etc... And for Gold wing, we have this: ;;FSO 3.6.8;; $Texture Replace: ;;FSO 3.6.8;; +old: xwing ;;FSO 3.6.8;; +new: xwing-gold ;;FSO 3.6.8;; +old: ywing ;;FSO 3.6.8;; +new: ywing-gold etc... This is supposed to cover all our bases no matter what ship the player chooses, but it's not working properly.
Tags	No tags attached.

Date Modified	Username	Field	Change
2008-03-30 04:26	Galemp	New Issue
2008-03-30 04:26	Galemp	File Added: texrepscreen.jpg
2008-03-30 05:46	taylor	Note Added: 0009068
2008-03-31 09:00	taylor	Relationship added	duplicate of 0001616
2008-03-31 09:00	taylor	Duplicate ID	0 => 1616
2008-03-31 09:00	taylor	Status	new => resolved
2008-03-31 09:00	taylor	Resolution	open => duplicate
2008-03-31 09:00	taylor	Assigned To	=> taylor

2008-03-30 04:26	texrepscreen.jpg (85,327 bytes) texrepscreen.jpg (85,327 bytes)

taylor 2008-03-30 05:46 administrator ~0009068	Try this in an Xt build. I rewrote all of the texture replacement code, so this may be a problem which already has a fix.