LCU Symbol clarification

Please post here for questions and discussion about scenario design, art and sound modding and the game editor for WITP Admiral's Edition.

Moderators: wdolson, MOD_War-in-the-Pacific-Admirals-Edition

Post Reply
Aawulf
Posts: 119
Joined: Thu Jul 14, 2005 1:22 am

LCU Symbol clarification

Post by Aawulf »

Have long used the "13" symbol for para capable units. Just read that there are "17" and "19" symbols that I never saw before. In one thread, "19" enables unit to be a commando unit capable of combat unloads from transport subs. In another thread, the author explain that "13" is for "commandos" and "19" is for "paras". In game, units with "13" are paratroopers and those with "19" are commandos but nothing describing the difference. In total, I'm only aware of 4 such symbols, "12", "13", "17" and "19". Have no clue for what purpose "17" is used and am not confident that I know the similarities and differences among the others. I do know "13" does allow units to be para capable.

Anyone have a more in depth understanding of the "sym" data field and what options are available to it's use?
Never ever ever ever let a day pass without remembering that we are fighting a war for our survival. God bless our troops.
User avatar
inqistor
Posts: 1813
Joined: Wed May 12, 2010 1:19 pm

RE: LCU Symbol clarification

Post by inqistor »

My guess is, that those are logical bits (1 2 4 8 16).

So, for 12, it will be 8+4 = 3rd, and 4th bit
For 13 you will get 8+4+1 = same as for 12, plus 1st bit (probably para capable, unless 12 also have this ability)
17 is 16+1, so it have one capability from 13, which is not present for 12 (1st bit), and some unspecified capability from 5th bit (16, probably assault from submarine)
19 is 16+2+1, so the same as 17, plus 2nd bit
User avatar
LargeSlowTarget
Posts: 4899
Joined: Sat Sep 23, 2000 8:00 am
Location: Hessen, Germany - now living in France

RE: LCU Symbol clarification

Post by LargeSlowTarget »

The "symbol" field in the editor only works for infantry type units and AFAIK the only values used are 12 for cavalry symbol, 13 for the para symbol and para ability (air droppable) and 19 for raider ability (i.e. loading on subs in combat mode).

The 19 value shows up as para symbol by default, but if you add an icon at the bottom of the "button_6" files, the game will use this icon.

Never heard or read of a "17" symbol - reference please?
Aawulf
Posts: 119
Joined: Thu Jul 14, 2005 1:22 am

RE: LCU Symbol clarification

Post by Aawulf »

ORIGINAL: LargeSlowTarget

The "symbol" field in the editor only works for infantry type units and AFAIK the only values used are 12 for cavalry symbol, 13 for the para symbol and para ability (air droppable) and 19 for raider ability (i.e. loading on subs in combat mode).

The 19 value shows up as para symbol by default, but if you add an icon at the bottom of the "button_6" files, the game will use this icon.

Never heard or read of a "17" symbol - reference please?
From SCEN 001 (both Allied LCUs)
5949 2/1 NAOU Det.
6052 2nd Recce

Never ever ever ever let a day pass without remembering that we are fighting a war for our survival. God bless our troops.
Aawulf
Posts: 119
Joined: Thu Jul 14, 2005 1:22 am

RE: LCU Symbol clarification

Post by Aawulf »

ORIGINAL: inqistor

My guess is, that those are logical bits (1 2 4 8 16).

So, for 12, it will be 8+4 = 3rd, and 4th bit
For 13 you will get 8+4+1 = same as for 12, plus 1st bit (probably para capable, unless 12 also have this ability)
17 is 16+1, so it have one capability from 13, which is not present for 12 (1st bit), and some unspecified capability from 5th bit (16, probably assault from submarine)
19 is 16+2+1, so the same as 17, plus 2nd bit
When I pulled it from hex addresses for the original Pac War and later for WitP, I'm pretty sure it was a 256 limited integer field. "12" and "13" were "00 0c" and "00 0d" respectively.

The following VBA code is what I used for WitP to extract the data for "sym" to Excel:
' Get _sym
CellY = 31
Counter = 88001 + (LocNum - 1) * 2
Get #1, Counter, VarData1
Get #1, Counter + 1, VarData2
curVal = CCur(VarData1) + CCur(VarData2) * CCur(256)
Worksheets("Allied LCUs").Cells(CellX, CellY).Value = curVal
Never ever ever ever let a day pass without remembering that we are fighting a war for our survival. God bless our troops.
User avatar
inqistor
Posts: 1813
Joined: Wed May 12, 2010 1:19 pm

RE: LCU Symbol clarification

Post by inqistor »

I don't know why, but Byte data type is never used in programming. They were declared as int, but I bet they still use only few bits.
User avatar
LargeSlowTarget
Posts: 4899
Joined: Sat Sep 23, 2000 8:00 am
Location: Hessen, Germany - now living in France

RE: LCU Symbol clarification

Post by LargeSlowTarget »

I have made a test with three infantry units and three tank units, one each with symbol 12, 13 and 17.

12 turned the tank unit symbol into a cavalry symbol but had no effect on infantry units, 13 turned the infantry symbol into a para symbol but had no effect on tank units, 17 had no effect whatsoever.
el cid again
Posts: 16982
Joined: Mon Oct 10, 2005 4:40 pm

Symbol 17 is used!

Post by el cid again »

It is associated with CMF cavalry. No idea why.

However, it may be associated with dragoons. The unit I found is listed as having mounted infantry,
which are, technically, not cavalry, but dragoons. See LCU slot 2727.
Norm49
Posts: 95
Joined: Fri Jun 05, 2015 3:59 pm

Re: LCU Symbol clarification

Post by Norm49 »

Dose the cavalry classification give any bonus like the 13 parachute and 19 commando?

Also is it possible to change the picture (not the symbol) or this is hard coded?
Aawulf
Posts: 119
Joined: Thu Jul 14, 2005 1:22 am

Re: RE: LCU Symbol clarification

Post by Aawulf »

inqistor wrote: Tue Mar 26, 2019 7:39 am I don't know why, but Byte data type is never used in programming. They were declared as int, but I bet they still use only few bits.
VERY delayed response.

In the 1990's, I visually analyzed the hexidecimal data to identify and construct what was all we had at the time for editing the scenarios in Pacific War. Rich Dionne made the first Excel editor and passed the project on to me. I believe he later developed the official editor released with the subsequent War In The Pacific (which preceded Admiral's Edition) in the early 2000's. He may have had the skills then to disassemble the data into numeric form, but I only knew Excel and could muscle my way through the hex hack with rudimentary skills in VBA.

Also, I discovered I was wrong about never seeing the "19" before. I noticed I referenced it in the old WitPExcel. Age affects the mind.
Never ever ever ever let a day pass without remembering that we are fighting a war for our survival. God bless our troops.
Cavalry Corp
Posts: 4105
Joined: Tue Sep 02, 2003 5:28 pm
Location: Sampford Spiney Devon UK

Re: LCU Symbol clarification

Post by Cavalry Corp »

Thanks for this - so in my mod, should I check that Para units are 13 and Commando units are 19, correct?

BTW the unit art for 13 and 19 is the same from what I can see???

Are there any other symbols and abilities that could be applied?

Mountain units for instance?

Cav
Post Reply

Return to “Scenario Design and Modding”