1.05 Patch

[jastaV]

News over scheduled patch 1.05 will be useful to move some mud here and apreciated by NCP users!

BTW, public release of work in progress patch versions, as 1.05b-beta, could help speed up patching process........
AFAIK, but minor troubles, as icons missing at F1 manu 2nd page, 1.05b-beta was stable and did not evidenced serious stability troubles!

Thanks in advance for clarification

[Pocus]

The 1.05b beta version is indeed rather stable, and correct several bugs spotted in the engine. So it can be out between october 1st and october 3rd.

[jastaV]

The 1.05b beta version is indeed [color="Red"]rather stable[/color], and [color="RoyalBlue"]correct several bugs spotted in the engine[/color]. So it can be out between october 1st and october 3rd.

note: Red and Blue edited by me!

- [color="Red"]AFAIK, pleased to confirm stability.[/color]
- [color="RoyalBlue"]A list of fixed bugs will be apreciated[/color], when you catch time to post it!

[Rafiki]

All patches published till now have been accompanied by release notes

[Pocus]

I need assistance for historical data fixes though...

[jastaV]

I need assistance for historical data fixes though...

The NCP-Develop. Team should have competences to provide you with any Hist. Data you need!

[Nikel]

I need assistance for historical data fixes though...

Do you need help searching historical data or you already have the info and the help is for fixing the scenarios?

[Pocus]

The NCP-Develop. Team should have competences to provide you with any Hist. Data you need!

[Pocus]

Do you need help searching historical data or you already have the info and the help is for fixing the scenarios?

The latter. If you see a bug in the data, like an event misfiring, report in this thread please.

[jastaV]

The latter. If you see a bug in the data, like an event misfiring, report in this thread please.

Ask ThilPhib for LocalStrings_NCP15d_e!
I suppopse it was "e"!

Search at NCP Dev. forum pages for it!

In LocalStrings_NCP15d_e You'll find fixes for Rhied Treaty notification & and a wrong duplicate unit model string fix!

[jastaV]

1813 Scenario is using wrong 1809-1812 models for French units.
OK COA models!
YOU SHOULD FIX THAT!
I suggested a corrected, working setup file edited for "1813 Hist. Mod scenario": unfortunately in more command lines I used new "units":

http://www.ageod-forum.com/showthread.php?t=10717

If it could help, I could provide you last ver. of 1813Hist Mod set up file.

[Pocus]

We won't create new models for now, we will have either to keep the current ones, or use the 1813 provided in the DB.

Thanks for the note about the strings, I'll use version e.

[jastaV]

Down here I enlisted some points worth to be investigated with next patch.
They have been already reported by a thread moved elsewhere from Rafiki!

1. AI Supply Wagoons often transit unescorted into enemy controlled regions.
I got impression AI uses Supply Wagoons as scout units.
In the same way Army Leader Forces are sometimes used as scouting units too.

2. AI make no use of small calvary units for screening own front and for scout enemy controlled regions.
Indeed it seems like AI is not used to detach small calvary units from Corps, usin' them later for the reported scouting and screening duties.

3. Calvary lossed are too high in combat: indeed calvary should be used for recon and screening duties, for enemy persuit after a victorious engagement, to force enemy infantry to form squares.
Only heavy calvary should be used as shock troops on the battlefield.....

4. AI is too much cautious when moving in enemy controlled regions. When AI have not knowledge of enemy or loose contact with enemy is overcautious with the result of beeing almost inactive.

5. AI besieging forces are overcautious, and do not storm besieged fortress or cities even when they have an overwhelming favourable force ratio.
Granting AI a major offensive attitude here is recommended.
That can be noticed at unfortified & poorely garrisoned towns.

6. Have doubts as regard Delayed Committement option: I tried higher delay time but I experienced plenty of blattles trigged anyway as soon as opposing forces enter in contact....no real delay observed.
see also:
http://www.ageod-forum.com/showthread.php?t=9961


7. AI supply and attrition, with hard attrition option enabled, are a trouble!
AI forces often move deep in enemy controlled areas, without a LOC to provide supplies.
Guess this aspect should be inproved with AI advancing only having controlled territory to the back and a working supply depots network.
AI seems not to be very confident with attrition rules.

8. Military Options relative to "replacements" should be reworked to give sides replacement types actually matching unit models used in the campaigns.
For example we have a mess of Militia replacement for French, in campaigns where French side has not chance to use it.
Most gun replacement are "light gun type", while medium guns is mostly used by on field forces.

9. I already reported activation troubles with Military Options enlisted after the first seven ones:

http://www.ageod-forum.com/showthread.php?t=10124
http://www.ageod-forum.com/showthread.php?t=10120

Hope to see it fixed!


12. I seems like AI does not build up new depots although can have at hand plenty of supply wagoon units.
...a thing to be checked!

13. In the available replacements page of Germany 1813 Campaign, later to Bavaria jointing COA, some French artilery replacemets figure out!
very strange!
......That has been investigated and fixed with my "1813 Hist Mod Scenario": do not mind details, but there's something wrong in replacement command lines at events exc. foil.

[jastaV]

We won't create new models for now, we will have either to keep the current ones, or use the 1813 provided in the DB.

Thanks for the note about the strings, I'll use version e.

Here's a scheme showing matching unit per years.
1812 > 1813
New units I edited included too: do not search for them in official DB!


uni_FRA_LightBde12 > uni_FRA_LightBde16
uni_FRA_LightBde15 > uni_FRA_LightBde19

uni_FRA_MixteBde7 > uni_FRA_MixteBde25
uni_FRA_MixteBde8 > uni_FRA_MixteBde17
uni_FRA_MixteBde9 > uni_FRA_MixteBde18
uni_FRA_MixteBde10 > uni_FRA_MixteBde19
uni_FRA_MixteBde12 > uni_FRA_MixteBde19
uni_FRA_MixteBde13 > uni_FRA_MixteBde21

uni_FRA_LineBde13 > uni_FRA_LineBde57
uni_FRA_LineBde14 > uni_FRA_LineBde58
uni_FRA_LineBde15 > uni_FRA_LineBde66
uni_FRA_LineBde18 > uni_FRA_LineBde67
uni_FRA_LineBde19 > SAME
uni_FRA_LineBde20 > SAME
uni_FRA_LineBde21 > SAME
uni_FRA_LineBde23 > uni_FRA_LineBde65
uni_FRA_LineBde24 > uni_FRA_LineBde60 x1/2
uni_FRA_LineBde27 > uni_FRA_LineBde68
uni_FRA_LineBde29 > uni_FRA_LineBde57
uni_FRA_LineBde30 > uni_FRA_LineBde64
uni_FRA_LineBde35 > SAME
uni_FRA_LineBde39 > SAME
uni_FRA_LineBde40 > SAME

uni_FRA_ChasseurBde11 > uni_FRA_ChasseurBde12
uni_FRA_ChasseurBde1 > uni_FRA_ChasseurBde8
uni_FRA_CuirassierBde2 > uni_FRA_CuirassierBde4
uni_FRA_HussardBde3 > uni_FRA_HussardBde10
uni_FRA_CavMixteBde7 > uni_FRA_CavMixteBde9
uni_FRA_CavMixteBde2 > Uni_FRA_CavMixteBde10

[jastaV]

[color="Red"]IMPORTANT![/color]

http://www.ageod-forum.com/showthread.php?t=10352

Do not forget to check that!

Should $Regular = 0 not work you are in big troubles!
|$Regular| is used in many "events files", many times......see Spanish Ulcer.

DO NOT FORGET THE KAT!
Not with patch 1.05, too!
Nik' could help as regard!

[jastaV]

Kat troubles.

I collected down here pictures that could help to fix Wellington's Katjusha trouble!
No doubt Nikel could do something better!

Here his as it looks in default and "fixed" conditions:





Rocket figures have been edited by pasting existing NCP DB figures: you do not need special authorization to use them.

[color="Red"][SIZE="4"]NOTE![/size][/color]
Uploaded new version with resized files!
This one should work correctely.

[FM WarB]

As reported here, and never commented on, there is an apparent problem with the Russian campaign
http://www.ageod-forum.com/showthread.php?t=9835

[Nikel]

Hi FM WarB, welcome back!


About the thread topic, it was already commented several times before. But just in case, remember the problems with the notificacion of events when playing with the french in the PW.

[Pocus]

As reported here, and never commented on, there is an apparent problem with the Russian campaign
http://www.ageod-forum.com/showthread.php?t=9835

Ok, thanks for the detailed info.

To everybody, in order to fix something, we need a precise report (for the AI problems, we need a save each time). thanks all!

[jastaV]

Here is LGE_Setup_scenar_1813r_JVmodded Exc. file based over LGE_Setup_scenar_1813r Exc. file from last NCP DB available.


1. I checked the two columns: Col. D, (sub units number per unit) & Col. G, (Sub units name/definition).
2. I compared data from Col. D to Col. G: I intruduced a correction any time data from two columns were not matching.
3. I assumed data in column G to be always correct, beeing them based over sub unit names as resulting from historical OOB we can check!

some examples:
1.
line 283: 2;139e Ligne|NULL|NULL

We have just one SU: "139e Ligne", but 2 SU in column D.
I corrected to 1;139e Ligne|NULL|NULL, so to have data matching.

2.
line 285: 1;Leib-Garde Hessois|2e Ligne Hessois|NULL
We have two SU enlisted in col.G: "Leib-Garde Hessois" & "2e Ligne Hessois", but just 1 SU is encoded in col. D.
To have data matching I corrected all to:
2;Leib-Garde Hessois|2e Ligne Hessois|NULL

3.
Some times data from Col. D & Col. G were not matching becausea NULL was missing in Col. G.
I checked matching unit into LGE_DB_Units_LGE035, then I added the missing NULL entry.

NOTE
TO EVIDENCE, AS REQUESTED by POCUS, ALL CHANGES OVER LGE_Setup_scenar_1813r EXCEL FILE:
1. I marked any corrected line with WHITE background colour.
2. I marked any corrected line with [color="Red"]RED bold type characters[/color]: RED BOLD TYPE OVER WHITE BACKGROUND CREATE A GOOD VISIBILITY EFFECT!


I PRAY USERS TO RETURN COMMENTS!
In particular, if you should add new corrections on your own, send me a copy of the file: It will be usefull to fix same troubles over my modded Campaign for the year 1813!

[Pocus]

Thanks for the retouching, it is a fine work, which will be added into the official patch.

[jastaV]

Thanks for the retouching, it is a fine work, which will be added into the official patch.

Here is a second, updated version.

I worked second foil, too: "Events 1813".
I evidenced as usual corrections!

1. Changes to columns D and H to have their data matching, for reinforcements.

2. Changes to Saxon betrayal event: lines 129; 131.....Column D: Syntax changes!
Please check these last corrections.


I'm at work over NCP_inc_HistOptions13 Exc. file, too
Coming soon!

[jastaV]

Added NCP_inc_HistOptions13_JVmodded edited over NCP_inc_HistOptions13 from last NCP_DB version.

1. line 247-248:
Fixed Russian artillery replacements: [color="Red"]RUS|$famLightArty|2 & RUS|$famMedArty|2[/color]

In the original they were unproperly encoded as French: [color="Blue"]FRA|$famLightArty|2 & FRA|$famMedArty|2[/color].


2. Column K: added NULL to all empy cells.





[color="Red"]AT LAST, a note over Sudden Death rules![/color]

See lines 54 & 62 in Setup 1813 foil from LGE_Setup_scenar_1813r_JVmodded2.
As in the original LGE_Setup_scenar_1813r file Sudden Death option is disabled!
May be worth to activate the options being Sudden Death enlisted into Campaign F5 menu......users already reported the trouble.
The decision is up to you!

[Pocus]

Thanks for all, I'll check the changes and see to incorporate them!

[jastaV]

Here are re-worked files for 1815-Waterloo Campaing.

LGE_Setup_scenar_1815t_JVmodded has been worked over LGE_Setup_scenar_1815t file from last NCP_DB version.
NCP_inc_HistOptions15_JVmodded has been worked over NCP_inc_HistOptions15 from last NCP_DB version.

1. LGE_Setup_scenar_1815t_JVmodded
Checked "Setup 1813" and "Events 1813" sheets so to have data in columns D/G and D/H matching.
Introduced few corrections in "Setup 1813" sheet.

Note:
[color="Red"][SIZE="3"]Enabling Sudden Death option is up to AGEod Team.[/size][/color]
At present it's disabled: RulSuddenDeath=0

2. NCP_inc_HistOptions15_JVmodded

2a. line 169, column D
Changed [color="Red"]Napoleon Iere[/color] with [color="red"]Napoleon Bonaparte[/color]: Note, "Napoleon Bonaparte" is Boney unit unique name used in "Setup 1815" sheet.
With this change "Option 5, Morale boost (Napoleon speech)" now properly works!
[color="red"]The option has been reported not working in past NCP version.[/color]

2b. Column K
Many empty cells in column D have been filled with "NULL".



[SIZE="3"]NOTE over $famLightArty Replacement points.[/size]

$famLightArty replacement points are added by Setup, Events, Military Options for different services in most Campaigns.
I checked Model and Unit DB, (see relative Exc. files): no $famLightArty figures out in the two files, (Models and Units), beeing $famMedArty commonly used!
During campaigns LightArty replacement accumulate but cannot be expended!

May be, you should evaluate changing usless $famLightArty replacement points with expendable $famMedArty ones, or anyother family used by game units!

[Pocus]

Horse artillery should be light artillery, but I agree that for the most part the replacements should be medium artillery.

I'm ok to activate Sudden Death also

[jastaV]

Horse artillery should be light artillery, but I agree that for the most part the replacements should be medium artillery.

I'm ok to activate Sudden Death also

I just checked Horse artillery units/models: all of them use $famMedArty!
No unit is employing the $famLightArty!
Guess it's better to ask ThilPhib before putting hands over Model/Unit DB files.
But all it's competent for Napoleonic Age weaponrs and equippement!



[SIZE="3"][color="Red"]WARNING ![/color][/size]

I did not put hands over [color="Red"]cities sheet[/color] in LGE_Setup Exc. files.
I know most of them are bugged by presence of NULL or 0, (zero) cells in columns, far to the bottom of last line!
As a result you get bugged, very heavy files when attempting to process them by CSV splitter.

With more times at hand I'll take charge to fix it too.
At moment guess we have not reason to put hands over cities sheets.

[jastaV]

Copy of two files are attached down here:

LGE_Setup_scenar_1813r_JVmodded3
LGE_Setup_scenar_1815t_JVmodded3

I fixed the troubles with cells reporting non-sence 0, (zero) entries, faraway down the bottom of last valid line in cities excel sheets.

As a result the files dimension is largely reduced!

Check it!
Hopely, now we'll have clean copies of LGE_Setup_scenar_1813 and LGE_Setup_scenar_1815.

[color="Teal"]Checking files relative to all other scenarios set up will be worth: a matter for future patches![/color]

[jastaV]

I just catched a couple of troubles with uni_PRU_Ldw1 and uni_PRU_NaCav1.

Both of them are 3 SU units and not 1 SU units as they looked at first glance!

So, for example, the original, wrong:
[color="Red"]uni_PRU_NaCav1; NULL; 3. Pommeran Nat. KR[/color]
or
[color="red"]uni_PRU_Ldw1; NULL; 1. Memel Ldw.[/color]
have been changed to:
[color="Blue"]uni_PRU_NaCav1; 1; 3. Pommeran Nat. KR|NULL|NULL[/color]
and
[color="blue"]uni_PRU_Ldw1; 1; 1. Memel Ldw.|NULL|NULL[/color]

[color="RoyalBlue"]I also checked August 1813 OOB![/color]

At all I had to correct less than ten lines: they have beem evidenced as usual!
Suggest you to search setup exc. sheet for uni_PRU_Ldw1 and uni_PRU_NaCav1 to quickly locate and check chages!

[Pocus]

I just can't follow this stream of modifications JastaV. This is part of the problem that led to the disparition of the NCP improvement team by the way. We only have time for stable fixes. So just post all the files modified when they are stable, with associated readme so that we can check the changes and validate them or not. Thanks!

I also believe you should post that either in the NCP beta forum, or at least in the 'help to improve NCP' one.