Latest topics
» SOW Replay Viewer
by Uncle Billy Today at 12:00 am

» Sunday 20 May 2018 Napoleonic Kriegsspiel
by Martin Yesterday at 9:25 pm

» Impromptu Games
by Morsey Mon May 21, 2018 11:36 pm

» Discussion on Formations
by Grog Mon May 21, 2018 8:42 pm

» ✯ TWC - PBEM Strategy Wargaming Club ✯
by Lancier Mon May 21, 2018 8:05 am

» OOB accuracy of standard scenario's
by Uncle Billy Thu May 17, 2018 3:36 pm

» The Groghead Crew just finished a 1 1/2 year of Vol de a'igle III
by Iconoclast Wed May 16, 2018 9:16 pm

» 1914 WW1 Kriegsspiel
by Iconoclast Wed May 16, 2018 1:10 pm

» Experimenting with the KS Mod sound files
by Didz Tue May 15, 2018 1:45 pm

» A gift from the Southern California Kriegsspiel Society to the Kriegsspiel community of Little Gaddesden
by Martin Mon May 14, 2018 11:51 am

» Kriegsspiel in Battles Magazine
by Martin Sat May 12, 2018 9:53 pm

» SOWWL Napoleon Mod 1.27 Released
by Uncle Billy Fri May 11, 2018 6:41 pm

Statistics
We have 1013 registered users
The newest registered user is GeeDub

Our users have posted a total of 24764 messages in 1972 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 : 3064
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