Latest topics
» Impromptu Games
by Uncle Billy Yesterday at 5:58 pm

» Set Up for SOWWL NAPOLEON GAMES For Kriegspiel style
by Mark87 Sat Feb 17, 2018 6:22 pm

» 2018 k/spiel game schedule
by Martin Thu Feb 15, 2018 1:17 pm

» 1914 WW1 Kriegsspiel
by Master of Europe Sun Feb 04, 2018 5:53 pm

» Hello, I’m back
by Master of Europe Sun Jan 28, 2018 10:42 pm

» Player v Player Push Map Campaign French v Austria
by MRM Sat Jan 27, 2018 3:13 pm

» Patch 1.01 No Found
by rschilla Fri Jan 26, 2018 10:55 pm

» KS Napoleon Mod 1.26 & KS Sprites 1.05 Released
by Uncle Billy Tue Jan 23, 2018 3:35 pm

» Newbie question on KS mod
by SirTurtleton Wed Jan 17, 2018 6:14 am

» 1809 Campaign on the Danube
by MRM Tue Jan 16, 2018 11:49 am

» conduct of an infantry assault
by lu zi shen Thu Jan 11, 2018 7:58 pm

» Bill Leeson RIP
by Pwp100 Mon Jan 08, 2018 6:31 pm

Statistics
We have 1006 registered users
The newest registered user is franzrudolf

Our users have posted a total of 24451 messages in 1951 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 : 12
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 : 2958
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 : 12
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 : 12
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