[TEC] Adding new sensors

[tater]

Should I change the IDs, THEN export it (without saving), then open the original copy again and import?

I have to admit, this confuses me, lol

I can change the IDs on 2 nodes, but the stuff below belongs to them, and I only have a link, nothing I can edit.

[tater]

Ah ha!

export them.

change IDs in working version for new sensor.

import them, since they have old IDs, they nest

The trick is you need to switch from tree to list for it to show!

tater

[skwasjer]

With id's shown as links, use CTRL + click on link to switch to edit mode.

I know the export/import procedure is a bit wonky but it should work.

[tater]

Right now I've done some control tests to start. Single large merchant amd a SC in a line. I approach from the front quarter. I tested stock, and the stock sensors DAT combined with the 2 cfg files from TM1.6. All at 8 knots.

In both control cases, the detection is VERY sensitive to aspect ratio. If I keep my nose at the SC, I can get inside 500 yards before I get a reaction. I can steam parallel at 1nm with no problem in either., too. With the TM cfgs, I get detected showing more than the bow at 0.7nm. I haven't even tried the altered dat yet since I got so damn close in both stock and TM values.

I think I need to make a bigger convoy so I can't control what I present to the target so easily, this is very hard to test.

tater

[tater]

Convoy of 8 merchants in 2 columns, 800m apart, escorted by 4 Minekaze (all set to AI=3). The escorts were at 12, 3, 6, and 9 o'clock. Radar fix mod in place to assure visual not radar sighting.

Control (TM cfgs), stock dat:

DD detected me ~2000 yards at 8 knots.

Modded dat (AI sensitivity set to 0.03, range set to 6000 max), TM cfgs:

DD detected me (quartering aspect) at 1400 @8knots.

Note that I didn;t set the DDs to have better AI, everyone was using the dumbed down version. So if the mod was done right now, the warships would have detected me at 2000, and the merchants at 1400 in the last example. This was in the default weather conditions, so pretty easy viewing.

I think I coudl have gotten closer to the DD had I given him less to look at, but at some point I'd have to show him a broadside.

You'd have to play this many times to get a feel. I noted with the dumbed down sensors, the DDs kept their lights on when I was in the convoy, but didn't shoot as much as I'd expect. Another test would be the same convoy minus the DDs, then also try various AI levels and see how that moderates things. If AI skill has any bearing at all, I bet you can get withing spitting distance of "Novice" merchants.

[tater]

I'll make a quick mod with 2 sensors, AI_Visual, and AI_Visual_Naval insde the dat, and I'll throw in a DD sns with Naval set, and maybe a merchant with Naval set. I can make a mission with the "Naval" merchie convoy north, and a dumbed down visual merchie convoy south. That will simplify testing because it'll all be in 1 mission.I can even have it generat a convoy every 2 hours or something, so we can test a few times with 1 mission load.

Then we can test different AOBs, etc, and see how the sensitivity affects detection on the good vs crappy AI settings. More eyeballs on this are better, and I have other stuff I need to do, lol.

If it appears to be about right, then a 2d mission can be in there with the same convoys, but with escorts set to "Naval."

[tater]

Tested a convoy (no escorts) with "naval" visual sensors (current stock setting renamed), and another with the sensitivity dropped to 0.03 and range 600 max.

The naval (stock) I got detected at 1500 yards (EDITED, i remembered wrong) , and the dumbed down version was under 1000 yards. Both were about 45 degrees AOB and 8 knots using the TM cfg settings.