Instalează Steam
conectare
|
limbă
简体中文 (chineză simplificată)
繁體中文 (chineză tradițională)
日本語 (japoneză)
한국어 (coreeană)
ไทย (thailandeză)
български (bulgară)
Čeština (cehă)
Dansk (daneză)
Deutsch (germană)
English (engleză)
Español - España (spaniolă - Spania)
Español - Latinoamérica (spaniolă - America Latină)
Ελληνικά (greacă)
Français (franceză)
Italiano (italiană)
Bahasa Indonesia (indoneziană)
Magyar (maghiară)
Nederlands (neerlandeză)
Norsk (norvegiană)
Polski (poloneză)
Português (portugheză - Portugalia)
Português - Brasil (portugheză - Brazilia)
Русский (rusă)
Suomi (finlandeză)
Svenska (suedeză)
Türkçe (turcă)
Tiếng Việt (vietnameză)
Українська (ucraineană)
Raportează o problemă de traducere
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.
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?
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 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?
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?
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.
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 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.
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
To give you an idea, I have to set the font past 2 just to see stuff, and 3 or 4 is best.
To give you an idea, I have to set the font past 2 just to see stuff, and 3 or 4 is best.
LOL OMG this is so important..... and did mot have it checked for the first few hours
glad you got it working. sounds like it was a spelling or capitalisation issue. maybe a leading space or something.
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.
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
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
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
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.
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.
http://steamcommunity.com/sharedfiles/filedetails/?id=1312093648
this script was published directly from the PB in that blueprint.
i dont think i mentioned the cockpit... dang it i didnt. i'll fix that. sorry for for overlooking it.