Latest topics
» Just posted part 3 of my DARPA research presentation on tactical AI
by Martin Yesterday at 4:47 pm

» Impromptu Games
by Miko77 Yesterday at 3:15 pm

» SOWWL KS----Scaling Down Waterloo Map by 2/3rds
by Mr. Doran Sun Nov 19, 2017 12:26 am

» Gore or Glory: A brief ACW, AAR, 22/10/17.
by Martin Sat Nov 18, 2017 6:15 pm

» Set Up for SOWWL NAPOLEON GAMES For Kriegspiel style
by risorgimento59 Wed Nov 15, 2017 2:08 pm

» Trying to Make Scaled Down Waterloo Map
by Didz Sun Nov 12, 2017 8:12 pm

» British OOB and troop ratings
by Didz Sat Nov 11, 2017 5:31 pm

» 2017 k/spiel game schedule
by Martin Fri Nov 10, 2017 11:17 pm

» World War One - AAR
by oldfaithful68 Fri Nov 10, 2017 4:20 am

» Gettysburg map, can be scaled to KS size
by MRM Fri Nov 03, 2017 6:11 pm

» Southern California Kriegsspiel Society
by Father General Fri Nov 03, 2017 1:59 am

» IL-2, Cliffs of Dover
by Grog Thu Nov 02, 2017 7:55 pm

Statistics
We have 993 registered users
The newest registered user is mugendo

Our users have posted a total of 24207 messages in 1931 subjects
Log in

I forgot my password


Cannon Fire v Musket Fire

Page 2 of 2 Previous  1, 2

View previous topic View next topic 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 : 2884
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

View previous topic View next topic Back to top

- Similar topics

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