As I recall, you can also use multiple AI to cause weapons to aim at different blocks on the target vehicle, even if they're sync-firing, which can be handy for some specific purposes.
most of my construction have 2 or 3 AI in them, it is wonderful especially if you have both hitscan and conventional weapons on the same craft also it's amazing for multi-role jet fighters with remote guided missiles
huh i never thought about letting 2 brains control my dakka cool! also im definitely gonna yoink that AA turret design 1 more thing uh cool muzzle flash and tracer still invisible :(
@@youraverageengineer6957 that is because when you stress the game it goes into degraded mode and tracers and flashes get turned off better off turning your graphic down to get them back though that only does so much
The thing I want is that ability to have a weapon completely ignore targets over a certain size. I like to use AAA CIWS, but I don’t want those guns firing constantly, I only want them to target small things, and if there are only big things I want them to wait for incoming missiles. The weapons don’t have enough input feeders to fire constantly, but they can fire continuously for a few minutes which is long enough to sweep away small craft and intermittent missile salvos. Anyone have a way to do that?
@@Basshead004 LWC only has option to filter small units, but not big units. ACB can recognize large units and turn LWC off. 'If target of AI-2 is >3000 vol, turn LWC 'AA control' off'. AI-2 should prioritize smallest targets first, if it runs out of small targets, then the ACB will turn the guns off. Don't forget to put a 2nd ACB to turn it back on.
@@BorderWise12 found the problem. i had my turret ring set to a max of -5 elevation on my very roll heavy ship. so every time the ship rolled to far it canceled the aiming.
There already has, kind of. One of my more recent CRAM tetris videos discusses 6-connection tetris, which is 3D out of neccesity. But I should do a specific video on it, yeah. 😁
Does this video predate the lwc option to control target parameters? If you just want your crams to not shoot at small/fast stuff, that would be enough.
No, and that doesn't work in every situation because sometimes you do want that. When a small enemy is moving predictably or has been immobilized, for instance.
Added point, you can reduce detection radius by connecting an AI straight to your Weapon Controller, (eliminates the transmitter/receiver combo). It's very dumb, but hey, who said you *can't* have three/four AI in a small ship :P
how would you set up detection with multiple mainframes? would 1 receiver per detection component set work or would you need 1 receiver per ai channel? or would it be multiple transmitters on the mainframes?
Detection info is shared across separate mainframes, so you really only need to match transmitters/recievers when you want trackers to move separately from each other.
@BorderWise have you tried the new wireless weapon controllers? The ones that has integraded recievers and safe? Man those are an genius add since you can save space with them.
i would have thought that rather than trying to use an entire ai to deal with different targets it would be more effective to set up the local weapons controllers to do the same? multiple ai still useful for redundancy of course, but the lwcs can usually do a better job of prioritising or ignoring target types i think.
LWCs can only ignore certain values, they can't prioritize. Which is a problem if you still want your secondaries to finish something off when your main guns are busted.
As I recall, you can also use multiple AI to cause weapons to aim at different blocks on the target vehicle, even if they're sync-firing, which can be handy for some specific purposes.
most of my construction have 2 or 3 AI in them, it is wonderful especially if you have both hitscan and conventional weapons on the same craft
also it's amazing for multi-role jet fighters with remote guided missiles
Slick!
huh i never thought about letting 2 brains control my dakka cool!
also im definitely gonna yoink that AA turret design
1 more thing uh cool muzzle flash and tracer still invisible :(
Yeah I never get tracers of flashes cause I am almost always in degraded mode
@@hypernovamkvi715 problem is i can turn on every single thing and have my fps go to -1 and yet i still cant get tracers or muzzle flash effects
@@youraverageengineer6957 that is because when you stress the game it goes into degraded mode and tracers and flashes get turned off better off turning your graphic down to get them back though that only does so much
@@hypernovamkvi715 OOF even when i turn it all down i see nothing
Thank you for this. I have like three ships that could really benefit from this
The thing I want is that ability to have a weapon completely ignore targets over a certain size. I like to use AAA CIWS, but I don’t want those guns firing constantly, I only want them to target small things, and if there are only big things I want them to wait for incoming missiles.
The weapons don’t have enough input feeders to fire constantly, but they can fire continuously for a few minutes which is long enough to sweep away small craft and intermittent missile salvos.
Anyone have a way to do that?
ACBs controlling the LWC?
i just set the range low. though my cwis doesnt hit much further than a km away, i just set them to only shoot things closer that that.
I think the local weapon controller has an option for that
@@Basshead004 LWC only has option to filter small units, but not big units. ACB can recognize large units and turn LWC off. 'If target of AI-2 is >3000 vol, turn LWC 'AA control' off'. AI-2 should prioritize smallest targets first, if it runs out of small targets, then the ACB will turn the guns off. Don't forget to put a 2nd ACB to turn it back on.
@@chillbuilder1011 year later, LWCs now can have a range of acceptable target sizes.
Do you need detection for each AI? my main guns cant decide on a target, switching back and forth and missing.
Nope, detection is shared across AI. Sounds like your target prioritization needs tweaking.
@@BorderWise12 thank you!
@@BorderWise12 found the problem. i had my turret ring set to a max of -5 elevation on my very roll heavy ship. so every time the ship rolled to far it canceled the aiming.
You made a point talking about how that cram wasnt using "3D Tetris". Will there be any future cram videos about 3D crams?
There already has, kind of. One of my more recent CRAM tetris videos discusses 6-connection tetris, which is 3D out of neccesity. But I should do a specific video on it, yeah. 😁
Does this video predate the lwc option to control target parameters? If you just want your crams to not shoot at small/fast stuff, that would be enough.
No, and that doesn't work in every situation because sometimes you do want that. When a small enemy is moving predictably or has been immobilized, for instance.
Added point, you can reduce detection radius by connecting an AI straight to your Weapon Controller, (eliminates the transmitter/receiver combo).
It's very dumb, but hey, who said you *can't* have three/four AI in a small ship :P
vlw ae mano
how would you set up detection with multiple mainframes? would 1 receiver per detection component set work or would you need 1 receiver per ai channel? or would it be multiple transmitters on the mainframes?
Detection info is shared across separate mainframes, so you really only need to match transmitters/recievers when you want trackers to move separately from each other.
@@BorderWise12 Nice. I did not know that. Thanks man love the content
Multiple AI for multiple type of weapon u have NICE tips for newbies !!!!!!!!!!!!!!!!!!!!
another use of multiple mainframe! to sneak through wireless snooper
@BorderWise have you tried the new wireless weapon controllers? The ones that has integraded recievers and safe? Man those are an genius add since you can save space with them.
Exactly what I was needing rn, thanks!
i would have thought that rather than trying to use an entire ai to deal with different targets it would be more effective to set up the local weapons controllers to do the same? multiple ai still useful for redundancy of course, but the lwcs can usually do a better job of prioritising or ignoring target types i think.
LWCs can only ignore certain values, they can't prioritize. Which is a problem if you still want your secondaries to finish something off when your main guns are busted.
Milm