Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Red Sith variants in K1 aren't Red in K2 #87

Open
N-DReW25 opened this issue Jan 23, 2023 · 1 comment
Open

Red Sith variants in K1 aren't Red in K2 #87

N-DReW25 opened this issue Jan 23, 2023 · 1 comment

Comments

@N-DReW25
Copy link

In K1, there exists a few name variants for Sith Soldiers including "Sith Trooper", "Sith Elite Trooper", "Sith Assault Trooper", "Sith Grenadier" and "Sith Heavy Trooper".

More often than not, the Heavy Troopers, Assault Troopers and Elite Troopers will done the red N_SithSoldier02 texture whilst the others will use either the white N_SithSoldier01 or shiny N_SithSoldier03 texture (In K1 and K2, the white texture is broken and displays the shiny N_SithSoldier03 texture so really it's either red or shiny Sith Soldiers).

In K2, the Heavy, Assault and Elite Troopers appear on Dxun, Onderon and the Ravager yet will either use the 01 or 03 texture which, due to the previously mentioned bug, results in most Sith Troopers in K2 appear shiny with the only red Sith Soldiers appearing is that one beast handler on Onderon and two beast handlers on Dxun.

I also have several Beta/Pre-Release screenshots of the Dxun tomb exterior fight which displays multiple red Sith Soldiers... this could suggest that the Sith Soldiers were switched to the silver appearance possibly to make the game run better on the old XBOX without all those variations slowing things down (there's probably a more direct technical term for what I'm referring to here).

@DarthParametric
Copy link
Contributor

Since textures are instanced (i.e. there's a single copy in memory), it makes no difference if there is one red trooper or ten. So removing them for performance reasons is unlikely in any place where at least one remains.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants