[REL] SH3 Commander Release 3.1 is now available!

[melnibonian]

Originally Posted by JScones

It was a spur of the moment thing - I decided and started at 11pm last night and was finished by 2am. Had it tested internationally whilst I slept, and boom!, ready for public consumption in less than 12 hours.

Jaesen once more you took a great program and made it even better Thank you for all your help, support and of course for the greatest add-on of SH3

[Jimbuna]

Nice touch

[JU_88]

Excellent work Jaeson, love the handwritten info in the drop down menus, 5 stars for you.

[tomfon]

Hallo.
A small problem with SH3Cmdr 3.1. It doesn't show the icon for one of my officers at the crew manager screen. Also, when playing GWX the face of the officer appearing at the icon is not the one the officer has at the control room. Are these two related? Any suggestion of what is going wrong?
Thanks.

[JScones]

Originally Posted by tomfon

A small problem with SH3Cmdr 3.1. It doesn't show the icon for one of my officers at the crew manager screen. Also, when playing GWX the face of the officer appearing at the icon is not the one the officer has at the control room. Are these two related? Any suggestion of what is going wrong?

Nothing to do with SH3Cmdr. It uses whatever face icons it finds in SH3 plus follows SH3's indexing rules. So...any variations are most likely caused by:

a) applying a mod that modifies the officer face icons
b) editing the crew config file incorrectly. This is the usual cause of such problems - even in GWX - because not everyone understands the connection between various variables in the crew config files (for example, if your officer icon has a hat, the 3D image should have a hat and if your officer icon is dressed in beige, then your 3D uniform should be beige - these connections are usually broken the minute someone edits the default crew config files).

b) is the likely cause of both your problems (if I understand your second statement correctly). Perhaps set an officer face icon through SH3Cmdr to see if that corrects the indexing in game (it might, but it might not either depending on what other values have been changed for the crewman in the crew config files).

[Venatore]

Originally Posted by tomfon

A small problem with SH3Cmdr 3.1.

Originally Posted by JScones

Nothing to do with SH3Cmdr. It uses whatever face icons it finds in SH3 plus follows SH3's indexing rules. So...any variations are most likely caused by:

Hey JScones, can you make a SHIIICmdr that has a "Blame Button" :rotfl:sorry not funny

[JScones]

Originally Posted by Venatore

Hey JScones, can you make a SHIIICmdr that has a "Blame Button" :rotfl:sorry not funny

Hehe. I'm just impressed that someone has paid that much attention - I've never bothered to compare...I will though next time I run the game.

But yeah, a blame button might be a good idea:

[tomfon]

Originally Posted by JScones

Nothing to do with SH3Cmdr. It uses whatever face icons it finds in SH3 plus follows SH3's indexing rules. So...any variations are most likely caused by:

a) applying a mod that modifies the officer face icons
b) editing the crew config file incorrectly. This is the usual cause of such problems - even in GWX - because not everyone understands the connection between various variables in the crew config files (for example, if your officer icon has a hat, the 3D image should have a hat and if your officer icon is dressed in beige, then your 3D uniform should be beige - these connections are usually broken the minute someone edits the default crew config files).

b) is the likely cause of both your problems (if I understand your second statement correctly). Perhaps set an officer face icon through SH3Cmdr to see if that corrects the indexing in game (it might, but it might not either depending on what other values have been changed for the crewman in the crew config files).

Hallo JScones.

I'll try to clarify what i posted yesterday cause i haven't applied any mod that alters the officers' icon faces nor do i have changed the config. files.
Before starting my previous mission i decided to enlist a fifth officer. Before doing so i dismissed one of them and then enlisted another. After exiting the game i noticed that in the Crew Management screen of SH3Cmdr the icon of one my officers was missing. This means that clicking on his name his status was shown but the icon window displayed... no icon. I am still referring to the Crew Management screen of SH3Cmdr. This is the first odditity.

The second has to do with what i see when playing GWX. So, if i place officers' icon "A" to the WEs' post for example then the officer "A" is displayed with officers' "B" body and the other way round. This will happen for these two specific officers only.

I hope i haven't confused you.
Sorry for my English.

[Yorktown_Class]

Great work as usual,thank you

[JScones]

dupe post.

[JScones]

Originally Posted by tomfon

I'll try to clarify what i posted yesterday cause i haven't applied any mod that alters the officers' icon faces nor do i have changed the config. files.

Remember, GWX makes changes to the crew config files too; my earlier comment was not to suggest that *you* changed the crew config files, but that *someone* changed the crew config files and it appears that they were not aware of SH3's intrinsic indexing. Only a very keen eye such as yours and mine (observed when I was adding the feature to SH3Cmdr) would pick up the discrepency. In fact, IIRC even the crew config files I shipped with SH3Cmdr prior to R2.6 were not perfect. I've never bothered to check/compare GWX's though.

As you state that you have not installed any officer face mod, then as I posted above, b) looks like your problem. Try the solution I suggested to see if it works; it's possible that SH3Cmdr *may* be able to fix the problem, which, ironically, is not caused by SH3Cmdr at all. But as I said, don't hold your breath because other settings may have been changed in the crew config files that still conspire against an easy fix.

So, failing that, you can always edit the crew config files yourself to return the indexing and ensure that your 2D models match your 3D models correctly.

Whether this fixes your second problem, I don't know - it may be something else altogether.