Đăng ký để tải xuống
Nav Sensors

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.