Beginning modder requesting help with AI_Sensors

Warden · 07-21-07, 08:07 AM

Hi
I'm new at modding and I'm trying to slightly reduce the AIs visual acuity (Using the 1.3 patch). In an attempt at doing this I've tried reducing the number two MaxRange variable (The one that is after AI_Visual) in AI_Sensors.dat (using SH3 Minitweaker), but during game testing I can't seem to detect any difference. Using a HEX editor I have been able to confirm that the variable is indeed being changed so I'm assuming that I'm modding the wrong variable.
Can someone help me and let me know what I'm doing wrong and how I can accomplish my goal?

WernerSobe · 07-21-07, 08:37 AM

data\cfg\sensors.cfg

check that file

Warden · 07-21-07, 08:47 AM

My apologies, I was unclear. I wish to reduce the visual acuity of the enemy AI, not of my already nearsighted watchmen.

tater · 07-21-07, 09:15 AM

some of the AI settings are in a cfg as i recall. Do a forum search here, there is a lot about it. Ducimus has a great description of what each value in each files actually does, required reading to mess with this stuff starting out, really.

Warden · 07-21-07, 10:42 AM

Is this the post you're reffering to Tater?
http://www.subsim.com/radioroom/showthread.php?t=111395

If so it's a very useful post to be sure, but it doesn't help me much at the moment.
But thanks for pointing it out, it was interesting reading.

Jace11 · 07-21-07, 01:01 PM

sim.cfg contains modifiers for AI unit sensors.

sensors.cfg contains modifiers for SUB sensors.

AI_sensors.dat contains all AI sensor types.

Sensors_sub_US.sim contains all the SUB sensors radar/hydrophone/peri etc..

One problem in 1.2 was that AI-sensors.dat had a very low sensitivity (a high value in the file!!) for their AI_visual sensor, this could be offset a little by lowering modifiers (like waves /light etc) in the sim.cfg. Changing the sensitivity to SH3 GWX levels and assigning the correct corresponding modifiers in the sim.cfg led to me being extremely happy with the detection ranges in all conditions.. Plus editing the sensors.cfg led to to get a nice balance where my crew would see a ship that I could also see at long range (I had an edited horizon range too!!), shortly before the enemy ship saw me... they could spot periscopes too..

It was perfect, then came 1.3...

They have obviously changed various things..

One REAL problem is that AI_sensors.dat cannot be opened in Minitweaker to give legible values now, so I can't check what they have done without going through it all in a hex editor.

There is a new sensor in the sensors_sub.sim it has been inserted near the top of the file so minitweaker reads it but assigns the name of the sensor below it, therefore they all have the wrong name after that but at least the values are correct.

As it stood I tried importing my values to SH4 1.3 but wasn't happy, I will try again later when new tweak files come out...

We also need to nerf JAP surface radar.. and I think their AIR radar still has the same problem as the US Sub air radar used to have, so A Jap DD fitted with air radar can detect a US sub as though it has surface radar.... just like the reverse situation in 1.2...

I don't thing the dev team thought to fix that... theats why you get DD's charging over horizon at you mid-war..

Ducimus · 07-21-07, 03:20 PM

Quote:

Originally Posted by Jace11

s

One REAL problem is that AI_sensors.dat cannot be opened in Minitweaker to give legible values now, so I can't check what they have done without going through it all in a hex editor.

I never did get around to parsing out the entire tweak file. I only have a partial one i used to adjust the variables i wanted (and neglected the rest). If you follow the syntax you can parse out the whole file. Im pretty sure the names ive placed are correct based on familiartiy with the statistics of the sonars.

Code:

[50]
DropDownName=Type3-2A
search,MinRange,50,single,>2,MinRange
search,MaxRange,50,single,>2,MaxRange
search,MinHeight,50,single,>2,MinHeight
search,MaxHeight,50,single,>2,MaxHeight
search,MinBearing,50,single,>2,MinBearing
search,MaxBearing,50,single,>2,MaxBearing
search,MinElevation,50,single,>2,MinElevation
search,MaxElevation,50,single,>2,MaxElevation
search,MinSurface,50,single,>2,MinSurface
search,Sensitivity,50,single,>2,Sensitivity

[51]
DropDownName=Type3-1A
search,MinRange,51,single,>2,MinRange
search,MaxRange,51,single,>2,MaxRange
search,MinHeight,51,single,>2,MinHeight
search,MaxHeight,51,single,>2,MaxHeight
search,MinBearing,51,single,>2,MinBearing
search,MaxBearing,51,single,>2,MaxBearing
search,MinElevation,51,single,>2,MinElevation
search,MaxElevation,51,single,>2,MaxElevation
search,MinSurface,51,single,>2,MinSurface
search,Sensitivity,51,single,>2,Sensitivity

[52]
DropDownName=Type93-5A
search,MinRange,52,single,>2,MinRange
search,MaxRange,52,single,>2,MaxRange
search,MinHeight,52,single,>2,MinHeight
search,MaxHeight,52,single,>2,MaxHeight
search,MinBearing,52,single,>2,MinBearing
search,MaxBearing,52,single,>2,MaxBearing
search,MinElevation,52,single,>2,MinElevation
search,MaxElevation,52,single,>2,MaxElevation
search,MinSurface,52,single,>2,MinSurface
search,Sensitivity,52,single,>2,Sensitivity

[53]
DropDownName=Type93-3A
search,MinRange,53,single,>2,MinRange
search,MaxRange,53,single,>2,MaxRange
search,MinHeight,53,single,>2,MinHeight
search,MaxHeight,53,single,>2,MaxHeight
search,MinBearing,53,single,>2,MinBearing
search,MaxBearing,53,single,>2,MaxBearing
search,MinElevation,53,single,>2,MinElevation
search,MaxElevation,53,single,>2,MaxElevation
search,MinSurface,53,single,>2,MinSurface
search,Sensitivity,53,single,>2,Sensitivity

[54]
DropDownName=Type93-1A
search,MinRange,54,single,>2,MinRange
search,MaxRange,54,single,>2,MaxRange
search,MinHeight,54,single,>2,MinHeight
search,MaxHeight,54,single,>2,MaxHeight
search,MinBearing,54,single,>2,MinBearing
search,MaxBearing,54,single,>2,MaxBearing
search,MinElevation,54,single,>2,MinElevation
search,MaxElevation,54,single,>2,MaxElevation
search,MinSurface,54,single,>2,MinSurface
search,Sensitivity,54,single,>2,Sensitivity

tater · 07-21-07, 03:28 PM

This new tool (WIP) by skwasjer might well make the work of making a new tweak file wasted:

http://www.subsim.com/radioroom/showthread.php?t=118130

tater

skwasjer · 07-21-07, 05:28 PM

It will, but not in the first release :/ Probably takes a few more weeks after I've done an alpha/feedback round here.

leovampire · 07-21-07, 06:43 PM

and try to ram them and I have had DD's use their deck guns shootting into the water and nail my conning tower. But the planes seeing us before we see them is a killer LOL!

tater · 08-28-07, 10:47 PM

OK, with AI_sensors.dat we have

Type=
MinRange=
MaxRange=
MinHeight=
MaxHeight=
MinBearing=
MaxBearing=
MinElevation=
MaxElevation=

MinSurface=
Sensitivity=

On the visual sensor the last 2 are both 0, what do the numbers mean? Any ideas what I should set the merchant version to to nerf them?

tater

07-21-07, 08:07 AM	#1
Warden Watch Join Date: Jun 2005 Posts: 25 Downloads: 8 Uploads: 0	Beginning modder requesting help with AI_Sensors Hi I'm new at modding and I'm trying to slightly reduce the AIs visual acuity (Using the 1.3 patch). In an attempt at doing this I've tried reducing the number two MaxRange variable (The one that is after AI_Visual) in AI_Sensors.dat (using SH3 Minitweaker), but during game testing I can't seem to detect any difference. Using a HEX editor I have been able to confirm that the variable is indeed being changed so I'm assuming that I'm modding the wrong variable. Can someone help me and let me know what I'm doing wrong and how I can accomplish my goal?

07-21-07, 06:43 PM	#10
leovampire Eternal Patrol Join Date: Apr 2007 Location: Waterbury, CT. USA Posts: 2,336 Downloads: 0 Uploads: 0	but at least now DD's see parascopes and try to ram them and I have had DD's use their deck guns shootting into the water and nail my conning tower. But the planes seeing us before we see them is a killer LOL! __________________ AIR_BASE_NAV_MAP_MOD Reflections_on_the_Water

07-21-07, 08:37 AM	#2
WernerSobe Commodore Join Date: Jul 2006 Posts: 625 Downloads: 5 Uploads: 0	data\cfg\sensors.cfg check that file

07-21-07, 08:47 AM	#3
Warden Watch Join Date: Jun 2005 Posts: 25 Downloads: 8 Uploads: 0	My apologies, I was unclear. I wish to reduce the visual acuity of the enemy AI, not of my already nearsighted watchmen.

07-21-07, 09:15 AM	#4
tater Navy Seal Join Date: Mar 2007 Location: New Mexico, USA Posts: 9,023 Downloads: 8 Uploads: 2	some of the AI settings are in a cfg as i recall. Do a forum search here, there is a lot about it. Ducimus has a great description of what each value in each files actually does, required reading to mess with this stuff starting out, really.

07-21-07, 10:42 AM	#5
Warden Watch Join Date: Jun 2005 Posts: 25 Downloads: 8 Uploads: 0	Is this the post you're reffering to Tater? http://www.subsim.com/radioroom/showthread.php?t=111395 If so it's a very useful post to be sure, but it doesn't help me much at the moment. But thanks for pointing it out, it was interesting reading.

07-21-07, 01:01 PM	#6
Jace11 Seasoned Skipper Join Date: Mar 2005 Location: UK Posts: 683 Downloads: 104 Uploads: 1	sim.cfg contains modifiers for AI unit sensors. sensors.cfg contains modifiers for SUB sensors. AI_sensors.dat contains all AI sensor types. Sensors_sub_US.sim contains all the SUB sensors radar/hydrophone/peri etc.. One problem in 1.2 was that AI-sensors.dat had a very low sensitivity (a high value in the file!!) for their AI_visual sensor, this could be offset a little by lowering modifiers (like waves /light etc) in the sim.cfg. Changing the sensitivity to SH3 GWX levels and assigning the correct corresponding modifiers in the sim.cfg led to me being extremely happy with the detection ranges in all conditions.. Plus editing the sensors.cfg led to to get a nice balance where my crew would see a ship that I could also see at long range (I had an edited horizon range too!!), shortly before the enemy ship saw me... they could spot periscopes too.. It was perfect, then came 1.3... They have obviously changed various things.. One REAL problem is that AI_sensors.dat cannot be opened in Minitweaker to give legible values now, so I can't check what they have done without going through it all in a hex editor. There is a new sensor in the sensors_sub.sim it has been inserted near the top of the file so minitweaker reads it but assigns the name of the sensor below it, therefore they all have the wrong name after that but at least the values are correct. As it stood I tried importing my values to SH4 1.3 but wasn't happy, I will try again later when new tweak files come out... We also need to nerf JAP surface radar.. and I think their AIR radar still has the same problem as the US Sub air radar used to have, so A Jap DD fitted with air radar can detect a US sub as though it has surface radar.... just like the reverse situation in 1.2... I don't thing the dev team thought to fix that... theats why you get DD's charging over horizon at you mid-war..

07-21-07, 03:28 PM	#8
tater Navy Seal Join Date: Mar 2007 Location: New Mexico, USA Posts: 9,023 Downloads: 8 Uploads: 2	This new tool (WIP) by skwasjer might well make the work of making a new tweak file wasted: http://www.subsim.com/radioroom/showthread.php?t=118130 tater

07-21-07, 05:28 PM	#9
skwasjer The Old Man Join Date: Apr 2007 Location: Netherlands Posts: 1,549 Downloads: 26 Uploads: 3	It will, but not in the first release :/ Probably takes a few more weeks after I've done an alpha/feedback round here.

08-28-07, 10:47 PM	#11
tater Navy Seal Join Date: Mar 2007 Location: New Mexico, USA Posts: 9,023 Downloads: 8 Uploads: 2	OK, with AI_sensors.dat we have Type= MinRange= MaxRange= MinHeight= MaxHeight= MinBearing= MaxBearing= MinElevation= MaxElevation= MinSurface= Sensitivity= On the visual sensor the last 2 are both 0, what do the numbers mean? Any ideas what I should set the merchant version to to nerf them? tater