@Sigmund Froid Sad to hear that you won't come back in a long time cause you seem to be the only one capable to make scripts funktion with WC weapons. Whip's TCES is basicly a newer version of this mod but he won't make any Wc support for it sadly.

The github project also still exists, so if anyone wants to update this, they are more than free to do so

I haven't touched this game in like a year, tbh, and I don't have any intention of returning any time soon...

Also, not gonna lie, people just sending a Friend Request uninvited is not making me any more interested in keeping up with this either.

Does it still works? the PB says target detected and looks fine, but rotors doesnt move at all

This script hasn't been updated in a while, and its the only WC turret script like this. is it still alive?

WeaponCore custom turret with Homing missiles (Large Destroyer) with this script tracking targets but not firing ... But y can manual fire from cockpit using WeaponCore HUD. JUst want automated SAM.

right the script has an issue where it crashes when the turret loses a target

So, this might be a bit out there, but I'm wondering if there's a way to use this script to automate targetting and firing of the Fleet Support weapons from the Star Trek MOD pack found here:
https://steamhost.cn/steamcommunity_com/workshop/filedetails/?id=2634862322

I'm trying to find a way to automate this particular style of weapon, but it's proving to be challenging.

i just flat out cannot get it to work PB says its managing a group and detects targets but nope it just sits there and does nothing,using WC btw

Are you using this for Vanilla or WC? WC shouldn't need a dedicated Designator per turret anymore. Hinges might cause erratic behaviour if the Weapons are on the wrong side, I'm still investigating how to fix that. However in a lot of cases using the invert Elevation in the turret config helps with these issues

I am running into a problem where the script does not want to use more then one Designator. Even if i add them to the group at the same time. the second the first Designator moves out of its arc the turret go haywire until the original Designator has re-acquired LOS. Am i doing something wrong?

@Sanguin Adding them to the block group should work

is there a way to setup separate desginator turrets for each group.

No the PDC don't need to be included in the group. And yes the range will be limited to a bit above the range of the PDCs from what I understand that's currently a limit of the API.

So my main grid has a ton of WC PDC turrets https://steamhost.cn/steamcommunity_com/sharedfiles/filedetails/?id=2036872575 . Do I need to include them as part of the "Turret Group", or at least one of them, to be used as a designator? Furthermore, those PDC turrets have a much shorter firing range than the railguns https://steamhost.cn/steamcommunity_com/sharedfiles/filedetails/?id=2530716039 I'm using on the rotor turret, so does this mean that the railgun rotor turret will be limited in range to that of the PDC? Also, I assume that the PDC must be kept powered on in order for it to work as a designator?

As an additional request, I'd be delighted if you'd let me friend you on here or discord to do some live troubleshooting, though it won't hurt my feelings if you prefer not to. =P

The main grid still needs at least one WC weapon to setup the GridAI system WeaponCore uses, and I highly recommend using a turret for that as Static Weapons seem to return inconsistent results for the detection range, but the rotor turrets will now swap targets if another target is closer to them even with only one turret on the grid.

with the "New Update: Turrets choose their own target now"
does it still need Designator in a ground or just get target from AI turrets on the grid?

That's a bummer about your drive. And no worries about taking a while to respond. The rest angle I'm using is indeed a whole number. Maybe the problem is that you haven't been able to work the kinks out with hinges yet?

Sorry for the long respnse time. Rest angle should be respected althou it only accepts integers. Hinge's always act a bit weird I'm still trying to figure out a reliable way to handle those. Due to several things I haven't really been able to launch the game recently though as my hard drive got fried.

Actually it seems to be ignoring the manual rest angle values input into the custom data of rotors and hinges. I tried setting the manual rest angle of an azimuth rotor from 0 to 45, and nothing is happening. To clarify, "use manual rest angle" is set to "true" for all rotors and hinges.

I've set the Manual Rest Angle to 90 in my Elevation hinge's custom data. The min and max angles for the hinge are 15 and 90 degrees, respectively. There are no hostile targets in sight. But my turret keeps elevating to 15 degrees, instead of returning to the manual rest angle of 90 degrees. I'm not sure how to make the elevation turret return to 90 degrees as the rest angle.

Yes. The script should read any number entered into the Custom Data of the Azimuth rotor

Is there a way to change the default rest angle of an Azimuth rotor?

well originally i was using the AC54 from aryx i think and i tested alot of the settings but to no avail i gave up but just wanted to know how i could fix it

Ok first of all make sure the engagement distance is correct. Additionally I'd like to know which weapon you where using. Was the turret tracking the target? Because if it's tracking the target but not shooting you might have to increase the maximum rotation speed as it can't align fast enough.

It was working very temperamentally and seemed to say it was working half the time but the turrets only seemed to shoot at 100Meters

In what way? What does the PB print out in the terminal?

idk its broken for me it seems

Hey if possible please add a invert azimuth sometimes it happens and can be annoying to fix

Big update today, Turrets now work designator less as long as Weapons with sufficient range are on the main grid. Will update the description once I got some sleep.

Hi!. I have just installed the script on the grid and setup the azimutal and elevation rotors, but i cant get to aim. I am able to shoot but im unable to aim in any direction. I have checked the programmable block and everything seems fine. Pls Help.

No problem, I'm doing these mostly out of fun anyways. It just happens that I'm currently busy with another bigger project.

ok i will look at the video and see what elst i missed

and Sorry to have taken your time on this Sigmund Froid.

Fair enough then

Salvos are built into WeaponCore now. Watch this for how to do it
https://youtu.be/FOmeLkHtapE?t=677

thank you very much.

Don't know about one but a basic one is quickly written up. Might do that tomorrow if I find the time.

Cool thanks….

On a other note do you know of a script for a Weaponcore version of whiplash’s weapon salvo script?
Exemple of weapon: Northwind weapon, Aryx weapon..

Atm the detection range should be the range of the weapon with the highest range on the turret

What the detection range?

The first turret works, but after that none of them work.

Works flawlessly for me when using WC only weapons, but I'll add a screenshot with the group setup in the terminal once my internet connection allows it. Make sure you haven't misspelled anything.

I concur, this script does not seem to function properly at all. Constantly bitching about "no azimuth/elevation/weapons found", even though rotors and weapons are properly grouped and labeled.

is there a way to use weaponcore designators?

So, out of curiosity, does this mean that if I have WC installed, and am using some WC turrets, that I could conceivably get my WC fixed mount weapons to autonomously acquire the same target as my WC turret weapon?

How do I make this work, I wanted to make a Spotlight turret that follows me and lights up wherever I go, I was able to do that in Vanilla but with Weaponscore the same setup do not work,

Edit: Actually the problem really is that there isn't any vanilla designator turret mods that work anymore, and the only WC designator turret that I know of (from L.Y.N.X) Doesn't function properly either.

Does this work with weapons like the MA Tiger AC that is gimballed weapon

Any output on the Programmable Block?

doesnt seem to work for me rotors dont turn