Latest topics
» Impromptu Games
by Uncle Billy Today at 4:23 pm

» Wargaming in the military
by Martin Yesterday at 10:41 pm

» Presentation
by Uncle Billy Wed Oct 10, 2018 6:54 pm

» DarkRob's Video of the KS Napoleon Mod
by Uncle Billy Mon Oct 08, 2018 4:43 pm

» Set Up for SOW ACW GAMES For Kriegspiel style
by Uncle Billy Fri Oct 05, 2018 4:55 pm

» September 23rd 2018 face to face game at Little Gaddesdon
by henridecat Wed Sep 26, 2018 8:21 pm

» November 25th 2018 face to face game at Little Gaddesdon
by Mr. Digby Wed Sep 26, 2018 5:55 pm

» October 21st face to face game at Little Gaddesdon
by gunboat diplomat Wed Sep 26, 2018 4:49 pm

» Autumn schedule of face to face games at Little Gaddesdon
by gunboat diplomat Mon Sep 10, 2018 4:49 pm

» 1828 dice tables
by Tim Carne Sat Aug 25, 2018 2:42 pm

» Kriegsspiel revised rules 1828
by Tim Carne Thu Aug 23, 2018 3:32 pm

» Other PC games - Command Ops 2
by Martin Thu Aug 16, 2018 5:58 pm

Statistics
We have 1030 registered users
The newest registered user is afcwfan

Our users have posted a total of 25149 messages in 1991 subjects
Log in

I forgot my password


Cannon Fire v Musket Fire

Page 2 of 2 Previous  1, 2

Go down

Re: Cannon Fire v Musket Fire

Post  risorgimento59 on Wed Aug 30, 2017 4:50 pm

Good remark, Kevin.
I think you mean the output produced by ReEval/Tactics and one can retrieve later through TACType/TACObj/TACLoc/GetOrders/GetStance/etc., right?
From your experience, is it possible to entirely ignore that data when trying to force a behaviour or there's a degree of control that - to same extent - escapes the AI module's code?
I know the offset of that data in CUnit's memory too, nevertheless. We may overwrite/patch it from the DLL probably, in the case.
Thanks.

risorgimento59

Posts : 20
Join date : 2015-06-19

Back to top Go down

Re: Cannon Fire v Musket Fire

Post  Uncle Billy on Wed Aug 30, 2017 5:42 pm

The first four, TACType/TACObj/TACLoc/GetOrders are used sparingly, mostly in the division commander logic. GetStance is quite useful for determining the tactical response of infantry and cavalry to various situations. The problem arises when it cannot be set to some other value due to changing tactical circumstances, i.e. no SetStance(). If stance information were only used by the dll code, this would not be a great problem. However, it is entirely unknown if and how those values are used when the game engine decides on brigade movements and behavior.

The strategic AI is quite static. It only responds to a situation where a division is in trouble and requests help. For the most part, it does not change it's strategy based on the actual situation it confronts.

_________________
I can make this march and I will make Georgia howl.
avatar
Uncle Billy

Posts : 3183
Join date : 2012-02-27
Location : western Colorado

Back to top Go down

Re: Cannon Fire v Musket Fire

Post  risorgimento59 on Wed Aug 30, 2017 6:29 pm

Valuable informations. Thank you sir. I know where the stance is set in the code... but not if it's used peripherically either. I'm going to investigate it and report here.

risorgimento59

Posts : 20
Join date : 2015-06-19

Back to top Go down

Re: Cannon Fire v Musket Fire

Post  risorgimento59 on Fri Sep 01, 2017 9:13 am

Had a try with a "dummy" DLL module (Think functions body commented out).
Couldn't find any external/exe unexpected interference, so far.

risorgimento59

Posts : 20
Join date : 2015-06-19

Back to top Go down

Re: Cannon Fire v Musket Fire

Post  Sponsored content


Sponsored content


Back to top Go down

Page 2 of 2 Previous  1, 2

Back to top

- Similar topics

 
Permissions in this forum:
You cannot reply to topics in this forum