Living Manual unchanged?

[HOTEC]

Is Living Manual version 1.21 not changed in new 01.02.52Beta version?

[Fraggo5]

if you open it it states it is at ver 01.02.50 currently , so no, it's not caught up with current Beta level

[Joel Billings]

There's only been one rule change since 1.02.50 so I didn't think it was necessary to put out a new living manual just for this one change:

• Set a maximum number of bombers and maximum number of fighters that can fly in any one mission during the air phase. The interface will not allow entering more than 200 for requested bombers or fighters. Missions automatically put together will be limited to around 200 bombers and around 200 fighters.

[DarkHorse2]

The living manual has some big issues, with many sections that have not kept up with the changes in mechanics.

Numerous sections are just wrong and need to be completely re-written.

For example, never have known "miles flown" to work like this.

18.3.2. Miles flown
There are several factors that determine how many missions and what type a
particular air group unit can conduct during a turn.

An air group unit can only fly a certain number of miles per turn based on its cruise
speed (37.16.1) and current unit morale and experience.

The miles flown are tracked as a percentage of maximum miles that may be flown. .
The miles flown logged by a group is increased substantially when operating in bad
weather. In addition, if planes operate over 25,000’ then the mileage will increase by
10% for each additional 1,000’.

An air group unit can continue to fly missions if miles travelled are less than cruise
speed times the number of aircraft in the air group unit times (10+ (morale/4) +
(experience/4))).

For example, a 10 plane JU-52 air group unit with morale of 20,
experience of 40, and a cruise speed of 160 could fly up to 40000
miles in a turn. The actual mileage flown is based on the type of air
mission.

Air transfer missions pay the range in miles, transport missions cost three times the
range in miles, and all other air missions, which are considered combat missions
and include fighter escort of air transport missions, pay four times the range in miles.
For example, an air transport mission to a target hex 12 hexes away would expend
360 miles per plane that flew on the mission, or 12 times 3 times 10 miles per hex
per plane, for the transport air group unit, but an escorting fighter unit would expend
480 miles per plane.

---

The following regarding "Airbase Supply Priority" has not worked like this in... forever?

16.6.5. Airbase Supply Priority
Remember that unlike depots and HQ units, if an airbase is set to #0 supply priority
it will receive no supply allocation. The supply priority can be changed in the
Commanders Report (35.7) or by right clicking on the map hex with the air base or
via the general information box (6.2.1).

---

Setting "Naval Only" for AOGs...

The term "Naval only" can only be found four(4) times in the Living manual. And then, it gives no explanation on how to set it. (there used to be a button in the UI that did it.... now, you have to enable a hidden colum in the CR to do it.)

---

WiTE2_NavalOnly.JPG (118.35 KiB) Viewed 829 times

---

Regarding "Fuel Store Req", "Oil Store Req", "Supply Store Req", those are not covered in the documentation at all. I could not even tell you, with any certainty, what "Req" stands for. (requirements? requisitions? ...)

---

WiTE2_Store_Reqs.JPG (17.35 KiB) Viewed 829 times

---

And most recently, the fact that "Effect" has been removed from various devices, yet nothing in the docs say anything about it being removed or have been updated.

[Joel Billings]

Naval only is not something you set, it's a feature of certain units that are pre-specified in the data, and this can be seen on the unit info screen.

I don't think anything was ever changed re miles flown for units. Doesn't it work this way? There were no changes here as far as I know since WitW.

I think the requirements have to do with what cities are calling for.

Thanks for pointing these things out. Next time we put out a living manual I'll try to account for some of these issues. Best to put these kinds of posts in the living manual thread so they don't get forgotten.

[DarkHorse2]

Another example of the manual being blatantly wrong.

WiTE2_ROF_Description_Incorrect.JPG (202.64 KiB) Viewed 759 times

---

The ROF displayed in the game is not a ROF modifier, but the actual resultant ROF, which is still not properly defined anywhere.

My best guess is that it is "operational" rounds per minute.

The negative ROF modifier being described is only visible from the game editor, not the base game.

---

WiTE2_ROF_Example.JPG (74.38 KiB) Viewed 759 times

[Zovs]

ROF as defined by the editor is listed in:

The Device tab and for each device.
The Ground Element tab which shows the true ROF for the main gun.

I think the Ground Element tab is the best place to view the ROF.

[DarkHorse2]

This has to be the Quinessential example of the Manual(s)....

---

WiTE2_Reliability_fromManual.JPG (330.32 KiB) Viewed 702 times

---

The "Living" Manual makes even less sense (if that was possible) in this regard.

---

WiTE2_Reliability_fromLivingManual.JPG (86.08 KiB) Viewed 702 times

---

I am baffled as to why the "Living" Manual excluded the bookmarks and uses big RED NUMBERS in place of the orginal graphics.

You have the original MS Word doc with all the graphics, correct? Why not include those in the "Living" manual, to begin with? Or simply update the original with corrected information? For the most part, most of the "Errata" is nothing more than text anyways.

Errata 01.02.14
Manual Addendum: Changing the Intensity setting shown on the Air Directive
(right side of map) Window for an air directive, changes the Air Doctrine
intensity setting for the given type of air directive, for the controlling Air
Command. Changing this, will also automatically alter all ADs of the same
type, within the Air Command, that are not using a Custom intensity. Players
wishing to alter the intensity of only one air directive, should set a Custom
value by manually setting the Strike Num for the air directive

At least this way the users would not go cross-eyed trying to read, in tandum, both a 500+ paged PDF along with a 800+ paged PDF - and eliminate 1 of 3 monitors now required to play WiTE2.

[Joel Billings]

Again, best to put these items directly in the living manual section thread so they don't get forgotten. As for reliability, I found this note in our task/bug system from 3 years ago. Looks like we missed it in the manual:

FV reliability is a 4 digit number. The reliability rating of an AFV is actually two different items. The first two digits represent the reliability of the AFV when moving (if only 3 digits are shown the assume a 0 in front of the first digit shown). The higher the number, the less likely the AFV will become damaged during movement. The third and fourth digits are survivability, and the higher the survivability the less likely the AFV will be destroyed in combat during a special survival check as opposed to just being damaged. New AFVs still suffer an additional reduction in their reliability when moving during their first few months in production.