All the new is here. sorry for breaking your stuff, but it was for a good cause.

Text Panel Custom Data was it, I've found these can be rather finicky where a space or a carriage return (invisible to the eye can make a world of difference) can make a big difference. I think one of the things, and you did mention it in the past posts was about the plus symbol (+) which is frequently used in the LCDS script. Thanks again for the help and efforts.

@hobbyman, you dont need [NAV] in the programmable block name.
your remote control block looks set up correctly.
the text panel custom data is where i think your issue is. you dont need to include + in your custom data tags, i was using them as dot points in the guide. the guide needs a full rewrite. you do need to include the right hand (space mode) tags though. if you dont intend to operate in space, just use the None tag.
try:
Lat None
Long None
in the custom data of the text panel.

So I eliminated the possibility of cockpit/block sharing issues, no other PBs even on the grid and gave the NAV PB its own Remote.

Name of Cockpit: Orbiter Cockpit
Cockpit Custom Data is blank, Reset all cockpit screens to No Content

Name of Text Panel: Orbiter [NAV] Text panel
Text panel Custom Data:
+ Lat
+ Long

Name of Remote Control: Orbiter [NAV] Remote Control
Custom Data of Remote Control: Origin

Name of Programmable Block: Orbiter [NAV] ProgBlock

Clear out all old, reinstall NAV script.
Text Panel content is Set to Text and Images (can't actually change that - nice) but does not display anything.
Also tried + Heading, same blank display, deliberately put in a garbage "command" in the Custom Data of the Text Panel and it briefly displays ONLINE then the Invalid Command fault. So it looks like the script is running, reading the Custom Data field in the Orbiter [NAV] Text panel, just not writing/rewriting to the Public title text and thus getting displayed?

added some clarification notes in the description to help with tagging.

@hobbyman, two issues i think. first, the Origin tag goes in the custom data of the cockpit or remote block, not in the name. second, this script doesn't like to share blocks with other scripts, at least where the custom data is concerned. if there is anything else in the custom data for one of the other scripts you are running it will cause this script to throw an error. a workaround is to use a dedicated remote block for this script.
i need to buckle down and get the selfishness beaten out of this thing and get it sharing cockpit screens as well. i wont have time for that until jan27th2021 though, i ask for your patience.

I run PAM, LCDS and some Whips scripts, having problems getting going with yours.
I keep getting "Operation Halted See WorkShop Page"
Been through the comments, instructions, etc. All items are owned by Me.

Name of Cockpit: Orbiter [NAV] Cockpit Origin
Name of Programmable Block: Orbiter [NAV] ProgBlock
Name of Text Panel: Orbiter [NAV] Text panel

Orbiter [NAV] Text panel Custom Data:
+ Lat
+ Long

Go to Edit, Browse Scripts, select Nav Sensors script, Check Code, (compiles no errors), OK,
"Operation Halted See WorkShop Page"
Text Panel Display is blank

Run, Recompile
"Operation Halted See WorkShop Page" persists/refreshes.

So what am I doing wrong?

Nevermind, got it working!

By "add the tag" do you mean in the name of the block or the custom data? How does this work with the [NAV] in the name. Could you give and example of, say a camera name? Is it [NAV] RangeFinder Top 10000?

i couldn't figure out how to get it to play nice with auto lcd 2 in cockpit screens so i skipped it. cockpit screens not supported.

Ok... so I have been trying to figure this out.. I have a fighter cockpit small block ship design. I have MMasters auto lcd 2 and it is all set up with the cockpit screens. I set up another programmable block with the Nav script compiled. I tagged the Cockpit as " Cockpit [LCD] [NAV] ".

The part I am having issues with is what to actually do after that. I go into custom data and add in this:

@0 AutoLCD
+ GPS
+ Vector
+ Attitude
+ Heading
+ Pitch
+ Roll
@1 AutoLCD
Tanks * Hydrogen
@2 AutoLCD
Echo Screen 3
@3 AutoLCD
Echo Screen 4
@4 AutoLCD
Echo Screen 5
@5 AutoLCD
Echo Screen 6

What am i doing wrong here?

@SinBad awesome! thank you!

thats got it working now. i need to learn how to do the cockpit screens as well, expect that functionality soon.

looks like they changed the way LCDs work. i dont really play anymore so i didnt notice. i'll do an update to fix it.

Hello! This mod is exactly what i was looking for... the only issue im having is getting it to work lol.

When i put it into a program block and check the code it throws a whole bunch of errors like this:

Program(332,24): Warning: 'IMyTextPanel.WritePublicText(string,bool)' is obsolete: 'LCD public text is deprecated'

There are 24 of these errors with each having a different number.

i think the 30-60 difference between worlds is due to one of the scenarios spawning the planet in a different orientation on the world grid (gps in game). i dont correct for it, i believe whips does.
the differences between mine and whips, dunno. mine aligns north to the gps axis. position is basically a cartesian to polar conversion between your position and the planet centre. pitch and roll work off the local gravity vector direction vrs the orientation of the cockpit. heading is fiddlier and involves some fiddly math that to be honest i havent thought about in the year since i wrote that part of the script and can only sort of understand what i did by looking at it now. if you want to have a look to see if i made a lapse in logic im happy to to post it here. i would sooner believe im in error rather than whip.
glad you like it.

I have noticed this mod and Whip's Artificial horizon do not share the same heading values, which are the correct set? Today is seems to be off 30 degrees but i would swear in another game it was 61 degrees off....

I like whips for instant sight on, for the artificial horizon, and yours for the mass details, So am hoping to find out what is off, it is me or on one of the scripts?


THANKS again for a super mod, been just loving it, finding near 2 font setting to be best with details on as many lines as i can fit.

Nice, TY for this!

Update is Up. see Change Notes for details.

i live with a vision impaired person (retinitus pigmentosa) so im familiar with the limitations that games can un-intentionaly have. if you have any more ease-of-use suggestions, please let me know and i'll see what can be done.

First, Thanks !!! with your help I now have the program working, at least the hard range finder part..

just an FYI, This mod https://steamcommunity.com/sharedfiles/filedetails/?id=806331071&searchtext=PANNING works great with yours. OMG it works great..

Solved my aiming issues with long distance asteroids.
Thanks for programing it to run multi cameras, as i can now have an asteroid cam, and a close cam.

Now i just need to learn how to set your tags and get the font right for my bad eyes.

Great mod with all the details and configurablity

i'll look into splitting the camera info into several commands so the information can be spread over multiple lines. that gives me an excuse to get into the code again and do the failsafe update ive been planningas well.

As a request can we get the charge line to move down one? So it is just name and distance on the first line?

To give you an idea, I have to set the font past 2 just to see stuff, and 3 or 4 is best.

As a request can we get the charge line to move down one? So it is just name and distance on the first line?

To give you an idea, I have to set the font past 2 just to see stuff, and 3 or 4 is best.

check that the LCD has 'show public text' enabled

LOL OMG this is so important..... and did mot have it checked for the first few hours

comments dont update live... ok.
glad you got it working. sounds like it was a spelling or capitalisation issue. maybe a leading space or something.

but I am surely typing something wrong, cannot seem to type RangeFinder Front 5000 right..... it keeps saying camera not found. But copy paste from your ship workd

ok, script basics first:
check spelling and capitalisation and bracket types on tags
check that the LCD has 'show public text' enabled
check the detailed info panel of the PB, the script gives feedback if it is running and hits a problem. not especially useful feedback, but it shows the script is running.
check you own everything and its turned on.
check that in game scripts are enabled in your world.

got it working, don't know why, but had to copy the text from custom data of your ship to mine.... my only excuse is I am seeing impaired....

Best Instructions ever !!
Thanks

Have the script loaded into PB.
Now on to making it work, in the name added [NAV] to a camera and lcd.
In custom data for camera i put in "RangeFinder Front 5000"
In Custom Data for LCD i pul "Range Front"
In cockpit wiith nav tag, added origin

And, Nothing happens... Did I miss a step?
Maybe I am running to many mods

the tags go in the custom data of the block. omit the "+" thats just what i was using as a bullet point. i can see how its misleading, i'll change it.
steps for camera functionality:
put the script on a programming block
add "Origin" to the custom data of your cockpit or remote control block
add "RangeFinder TheNameOfYourRangeFinder 5000" to the custom data of the camera you want to use. TheNameOfYourRangeFinder can be whatever you like, but no spaces. the 5000 is the maximum range it will scan to in meters. it can be whatever you like, but longer ranges take more time to charge between scans.
add "Range TheNameOfYourRangeFinder" to an LCD panel. you can have multiple cameras on one panel, just make sure each tag is on a new line in the custom data.
finaly, add [NAV] to the name of each of these blocks.
run the script.
an example is in this build https://steamcommunity.com/sharedfiles/filedetails/?id=1312093648

questions
in the "tags" they go in the name yes?
the + infront of many of the tags is to be omitted?

would you be willing to give step by step instructions on setting up the rangefinder, IE a 1, 2, 3 do this, name "that" exactly "this" for the first time, Sorry am having issues setting it up for the first time, after it works once I am sure I could handle it from there...

This script looks like what i am after, thanks in advance for any help...

PS Remethep mentioned a test miner ship that this is run on, could we use that? might be faster then writing out more details/instructions

Next update ill be concentrating on failure proofing the script. so if you lose a camera or LCD it wont crash the script.

Oh wow! I am so looking forward to testing this out. :)

Updated Released. please see description.

finding time to program while moving house is hard. i should get to refining this script in about a week.

thats good to hear. ill see what i can do to get it a little more flexible for installation and options.

So I was partially right about some stuff. Neat. :) And, the rangefinder ability alone makes it really usefull. So, 10/10 will use it for my grids down the line. :)

the speed indication in space mode isnt primarily intended as a speed indication. thats the polar vector magnitude component of your current motion vector. the other two components are bearing and elevation. thats there if you have a ship with most of its thrust in one direction, you can use the motion vector to align your thrust for efficient retro thrust (180 deg bearing and 0 elevation). its also useful for dodging things as it gives you the difference from ships head in degrees as you thrust sideways. you can maintain a heading while knowing you have dodged the thing in your way.
the heading, pitch and roll are usefull for tunneling (in space and on planets) for making nice straight tunnels, making sure you are pointed straight up when going to space, leveling terrain, that kind of thing. in space its from the XZ plane iirc.

nice spotlight, thanks. :)
max range on the rangefinder is 5000m, 10 km range would require a longer recharge time. the script is designed to fill in a few gaps in MMasters automatic LCD 2 script. the rangefinder is intended to compliment the stopping distance readout from auto LCD2, i felt the current recharge was a good balance between detection range and refresh rate. it uses the camera raycast functionality. i dont think turrets can do that. there is nothing stopping you from mounting it on a player made turret though.

looks like youtube is still loading it. looking forward to viewing

And, here's the spotlight I did on the script. :) https://www.youtube.com/watch?v=uNU6UCItIGc

now i feel dumb. i forgot that i had it set up that way on the grid i published it from. thanks for letting me know.

Got it! The cockpit needed to be named "Lifter Cockpit". :P

Thanks. Because just renaming the cocpit did not do the trick for me. Might well be me borked.

if you need an example craft with it working, its installed on this one
http://steamcommunity.com/sharedfiles/filedetails/?id=1312093648
this script was published directly from the PB in that blueprint.

The part with the cocpit I did not check. I'll give it a go later. :) Thanks

did you check the block naming? it needs cockpit named "Cockpit", camera named "Range Finder" and 3 LCD named "Nav1" "Nav2" and "Nav3"
i dont think i mentioned the cockpit... dang it i didnt. i'll fix that. sorry for for overlooking it.

Hm. Did not work for me, at all. :/ Error all the way.