That sounds like an ownership issue. Make sure all blocks on your base have the correct ownership

I seem to only get allies to show up on screen when I am physically in a cockpit. I'm trying to set up my base to have a main radar screen.

If they are being actively targeted by your turrets, yes

Will it detect biological threats like wolves/pigs and spiders?

The range is global across all screens.

sorry if this ha been answered already, BUT, is it possible to have this on multiple screens with each screen set on either a different orientation and/or range?

The autonomous detection range is based upon what your turrets (and custom turret controllers) are targeting. The default turret AI scan radius is 800 meters; however, via target locking and /orAI blocks, you can extend that range out to the max projectile range of the turret (or custom turret), so up to 2km for large grid railguns.

Additionally, any ship that detects a turret target using this script will broadcast that targeting data to any other scripts within its antenna transmission range. So your detection range can be augmented by other platforms networking their target data.

ok so if im understanding this right the max range of this radar is space engineers is only 800 meter? and there is no way to change this really or am i misunderstanding something?

In the Radar PB, find the following settings and change them as follows.

Draw title screen=False
This turns off the white Radar logo that you mentioned..

Show on screen 0=true
This puts the live radar display on the first screen of the PB.

so i threw it in a programable block. that same block is displaying the radar, but the radar is white and looks absolutely nothing like yours

Thank you for the explanation.

The way that AI block turret range boosting works is that it can boost a turret range all the way up to the max distance that the ammo it fires can fly.

Artillery turrets (custom or premade) can be boosted up to 2km as a result, but gatling turrets can only be boosted to 800m.

Oh, OK, I'm a bit confused now.
Am I correct in concluding the following when adding AI combat blocks to a grid with radar?
1. The usually 800m "sensor net" range offered by turrets is then extended to ~ 2.5 Km?
2. Enemy grids within the 2.5Km range of the AI enhanced "sensor net" range, but outside of the turrets 800m range will show up on radar screens.

If we can see the 2.5Km space surrounding a radar installation on radar, it definitely makes adding AI combat blocks to a radar installations a no brainer.

For clarity: the script can only see what your turrets (or custom turret controllers) can see. This does include the range boost afforded to them by AI blocks, but there is no direct access to the AI block target.

That's a no, scroll down about half a dozen comments.

@Whiplash141 Is there any way to use the AI offensive block to see targets up to 2.5km?

Thought I separated the title text from other text, but apparently not. I'll try and fix that when I have time to breathe

@Whiplash141 wouldn't the range meter dissapear than too?

Change the color of the title bar and text to transparent

@Whiplash141 is there a way to disable the Title "WMI Radar System"? I use Splitsies Nav Console and it gets cut off.

There is no API for that sadly

This is an idea for someone smarter than me.

If there is a way in the scripting API to get target locking data for the current grid.
1. We have a target lock and/or we are being target locked.
2. The coordinates of the grid involved.

We could then use the AI combat blocks to extend the sensor net out to 2.5K around us. by sending the coordinates into the radar comms net. This could be a feature in a future version of WMI Radar or a third party script like the WC script. As stated, for someone smarter than me, I have no idea how to implement this, or if it is even possible.

You're welcome, absolutely love using the scripts from WMI. :-)

That is a solid explanation, I'm overloaded with work, so it is certainly more detailed than I have the bandwidth for, so thanks!

Of course AI defensive blocks on both base & ship will shrink invisible space to ~ 5K, but I won't see them on radar until a sensor net does and is able to send the data to the radar screen I am looking at.

One can't see players at "unrealistically vast distances" with this script alone.
One would need a comms / sensor net (turrets and/or sensors) covering the same " unrealistically vast distances" in order to see someone that far out.

For instance, enemy not broadcasting, my base 10K out.

I see them 10K out only if.
1. They fly within base sensor net.
2. The ODL (Optical Data Link / laserantenna) feed from base is not disrupted.

If they are outside base sensor net and ship sensor net, they could be anywhere between in the 8.4 KM of space not covered by sensor nets.

If they are 10K out in another direction, then they won't show up on radar until ship sensor net sees them.

Hope this sheds some light on what can be done at distance with this script vs what cannot be done.
I'm sure Whiplash can explain it better than me. :-)

I admire your work for its quality and utility. Keep it up!
Also, I was wondering how I can implement this script to a dedicated server. For balancing purposes, is it possible to hard limit its range so players can't see each other at unrealistically vast distances? For example, is it possible to have a upper limit in range at 50 km?

any way of locking onto long range targets like 10kms or so any use weaponcore weapons?

they do not

do searchlights function like turrets for the purposes of detecting neutrals/enemies?

anyone looking for WC compatibility run the script below on a different program block with this one on the same ship and it works:
https://psteamcommunity.yuanyoumao.com/sharedfiles/filedetails/?id=2232655829&searchtext=flight+control

The other person obviously hasn't networked TBR scripts together either.
It is absolutely possible to see things on the screen that are several kilometers away via networked radar installations. :-)

"What is the benefit of the radar if you cant see it on the screen until you see it with your own eyes and target it?"

I operate within the limitations of the script API. I can't magically change game rules, this is a script, not a mod.

If you have weaponcore loaded in your world, none of your weapons are vanilla any more. As such, see the FAQ entitled "Do WeaponCore turrets work with this script?" above

@whiplash141. I will give it a try. Thanks. I guess the weaponcore mod updates the ranges, but they are the vanilla blocks. Is there a way to make it show contacts vs targeted. A person may be flying around and an enemy approaches from the rear. What is the benefit of the radar if you cant see it on the screen until you see it with your own eyes and target it?

"I've got Vanilla turrets on my ship"

"I have 2 turrets with a 2500m range and another with a 3500m range."

These 2 statements are not congruent. Turrets in vanilla have a _max_ AI range of 800m and a max AI block extended range of 2000m. AI blocks only extend the detection range up to the max range of that weapon's projectiles.

If your turrets are not actively targeting something they will not show up on the turret based radar.

I have 2 turrets with a 2500m range and another with a 3500m range. 2000m should allow it to fall within the range of the turrets.

The default range that came in was 1m.

Changing the range doesn't automatically make the turret range higher. As clearly stated in the FAQ above, the only way things are detected by this script is via turrets. Changing the display range does not and can not somehow make turrets target further than the game allows.

I've got Vanilla turrets on my ship. I set this script up, I have the radar on my cockpit screen. I set range to 2000. Nothing is showing up. No friendlies, enemies or neutrals. 02/19/25

@joe lasagna for me it still works. The Radar script also works for me without the WC addon script by useing a player made turret and The WC-CT Block.

"is it necessary for turrets to identify enemies"

yes.

Hi, is it necessary for turrets to identify enemies, to have shells/ammo in inventory? I used satellite for detection enemies in wider range, which have one artillery turret without ammo but it doesn't see any enemy.

That would be a great feature!
Why did it take us nearly 6 years to think of that?! LOL! :-)

Happy New year !

Here is a small update suggestion for the new year that would improve the script usefullness:
I used to stack the command bar with different ranges values.
Is it possible to add 2 commands in the switch case : range_inc , and range_dec to change range by a step ?
(example: range_inc 2500 would increase current range by 2500m, so only 2 command slot are needed)

Thanks !

No. Defense blocks dont publish anything that scripts can read. The can indirectly increase turret range though.

Hello, does the radar script also take in infos from defence blocks ?

Is there an up-to-date/functioning WC integration addon? To my knowledge the Sigmund Froid addon is nonfunctional.

@iMurmis
This means that (1) your ship does not have an antenna, (2) your character's suit antenna is being used to relay targeting data to your local radar instance, and (3) your local radar instance is not detecting anything on its own, simply displaying IFF networked targets.

It might have something to do with the
Target fadeout interval (s)=
line in the PB's custom data.

Hello. I have using famous Whips Radar scrip for a long time. But now I can see targets only from control seat or capitans desk. When I stand up the target marks on radar screen are slowly fade out. No errors when compliling or checking script in PBlock. On Small grid all is working fine.
Does any one can tell me what it can be?