[needed] how do you make an AI submarine ?

[Ducimus]

Skimmed through the thread, sounds like other have pretty much covered it. Though i'll add:

- It is VITAL that the AI subs do not use ANY of the same sensory nodes, equipment, etc that the player uses. AT ALL, EVER. Not even a TAR node. (you'll know this happen if you notice all the dial needles stuck in the 12 O'clock position in the interior. Possibly super large file sizes for save games too, like 500 MB saves)

- You'll need to redo damage zones so they sink correctly. Admittidly, i cheesed, and just changed one zone into a BB keel zone and ran it the length of the boat. Does the job, but certainly not elegant.

[peabody]

Originally Posted by Ducimus

Skimmed through the thread, sounds like other have pretty much covered it. Though i'll add:

- It is VITAL that the AI subs do not use ANY of the same sensory nodes, equipment, etc that the player uses. AT ALL, EVER. Not even a TAR node. (you'll know this happen if you notice all the dial needles stuck in the 12 O'clock position in the interior. Possibly super large file sizes for save games too, like 500 MB saves)

- You'll need to redo damage zones so they sink correctly. Admittidly, i cheesed, and just changed one zone into a BB keel zone and ran it the length of the boat. Does the job, but certainly not elegant.

I did play with the zones on the two I made. They were sinking like helium balloons. And a minimum of two torpedoes to sink them. So that part I do understand.

I did NOT know about the sensory nodes, equipment etc. Now mine were the Porpoise and the Tambor, and Keltos used German subs to create the IJN subs. Do you know if this will encounter the same problems? I am not asking you to test it, only if you know the answer. I didn't notice any problems with dial in the sub not working. Possibly because we are using German "equipment" ??? I will check the file sized the next time I have them loaded in the game.
The other question is you say the "same Sensory nodes", does that mean we have to rename the node. for example change the H01 to F01 or we have to actually remove the Hydrophones from the sub, and use 'ship' equipment instead of 'sub' equipment?
There is so much I need to learn, thank you for the information. I NEVER would have figured that one out.
In fact if you are busy (you are always busy!!!) I can check your AI sub in TMO and see what you did and maybe figure out at least some of it.

Thanks again for the information.

Peabody

[Ducimus]

Originally Posted by keltos01

How ??? pm me if you don't want this public knowledge

keltos

I know you can make a submerged and surfaced version of the same submarine. Just set its draft to run below the surface. (sim and/or cfg file tweaks, i forget). You can also make "fake" torpeo's too. Clone a new gun, make it invisible. Take the node for this gun mount on the parent object and offset it so its above the surface. Tweak the gun's rotation and reload specs, and there you go. Someone thought this up way back in the day in SH3, i forget who. Anywho I should probably get off my lazy as and do this at some point.

Originally Posted by peabody

I did NOT know about the sensory nodes, equipment etc. Now mine were the Porpoise and the Tambor, and Keltos used German subs to create the IJN subs. Do you know if this will encounter the same problems?

The problem comes when the game has to instantiate two player objects at the same time. (parent or child objects). If your using it, and the game has to start a new instance of it while it's in use, the game gets confused i guess. Now mind you, the game has to start the instance for the error to occur. Just having it in the campaign files isnt enough.

You can totally clone the player object in every detail, but the game won't have a tizzy, UNTIL IT TRIES TO RENDER IT. (usually within 30 KM or so.). Which makes tracking down this error really hard. Sometimes there was an AI sub around and you didn't know it. Lucky for you, others have already done hours of this: ( ) so you don't have to.

The other question is you say the "same Sensory nodes", does that mean we have to rename the node.

No, I meant if its an AI object, you should use AI sensors. If your watch crew is using something like "crewWatchVisual" and the AI is using "AI_visual", then use "AI_Visual". Same for radar and hydrophones, etc.

edit: Some nodes are player specific and never used by the AI. TAR node for example. I mention this specifically because it was giving me issues. I let this one node slip by not realizing the game was trying to insantiate two instances of this player specific node. (its for submarine coatings)

[peabody]

Originally Posted by Ducimus

The problem comes when the game has to instantiate two player objects at the same time. (parent or child objects). If your using it, and the game has to start a new instance of it while it's in use, the game gets confused i guess. Now mind you, the game has to start the instance for the error to occur. Just having it in the campaign files isnt enough.

You can totally clone the player object in every detail, but the game won't have a tizzy, UNTIL IT TRIES TO RENDER IT. (usually within 30 KM or so.). Which makes tracking down this error really hard. Sometimes there was an AI sub around and you didn't know it. Lucky for you, others have already done hours of this: ( ) so you don't have to.



No, I meant if its an AI object, you should use AI sensors. If your watch crew is using something like "crewWatchVisual" and the AI is using "AI_visual", then use "AI_Visual". Same for radar and hydrophones, etc.

edit: Some nodes are player specific and never used by the AI. TAR node for example. I mention this specifically because it was giving me issues. I let this one node slip by not realizing the game was trying to insantiate two instances of this player specific node. (its for submarine coatings)

Thanks, I think I get it now. And I thank you guys for "doing hours of this" so I don't have to.
I usually do hours of something and end up empty handed. I think it should work but for some reason it doesn't. Sometimes the light comes on but a lot of times it doesn't. (and it's only a 25watt light so it's not too bright.)

Peabody

peabody,

I still doubt I know much more then you.
I just look at things a bit differently then many do.
People tend to get to serious and define things as a set standard.
Then they never push the bounds.
So if they believe a P0x is for placeing people?
They may never make the leap that most nodes are pretty much null.
(Yes, The K node is cargo placement but is interchangable)
And as Ducimus posted,
Watch the nodes when switching a Sub to an AI Unit with a Ship controller.
Also watch the zon file.
In GWX, We had to create new zones for AI Subs.
That was after massive testing.
ref created the base damage model for the AI Subs.
Testing showed a problem.
I re-tested and adjusted to solve the problem.
Team work!

[tater]

I tend to think in terms of compatibility as well. There are unused node names you could always use for random stuff. I like using the nodes as defined for others that may mod my mod

That way they just look and know what is at which point. A looong time ago I was using whatever node was handy to place guns, etc

[keltos01]

Originally Posted by privateer

In GWX, We had to create new zones for AI Subs.
That was after massive testing.
ref created the base damage model for the AI Subs.
Testing showed a problem.
I re-tested and adjusted to solve the problem.
Team work!

would you have such a model for us to use ? with due credits of course !

keltos

[tater]

There are AI subs in TMO and RSRDC you could clone, then replace the hulls, etc.

Originally Posted by keltos01

would you have such a model for us to use ? with due credits of course !

keltos

GWX 3 has all the files and info.
Special zones were created for the AI Subs
and damage models adjusted to use them on each AI Sub.
I can send you the zone.cfg and one of the AI Subs files to look at if you wish.
Any permissions and such needs to go to Jimbuna,
if you wish to use the files in future mods.
I really don't see any problems in that area.