Already a fantastic script but it would be even better if you could add a cycle/toggle for the screens based on the index. Maybe you could use the same tag and add a state so it would cycle between different ones with the same tag using an argument. Once again, awesome script.

Originally posted by MajorXAcE:

Already a fantastic script but it would be even better if you could add a cycle/toggle for the screens based on the index. Maybe you could use the same tag and add a state so it would cycle between different ones with the same tag using an argument. Once again, awesome script.

Thank you!
So you mean changing like a digital bilboard[pbs.twimg.com] showing different configs?

Exactly, it already looks like a proper cabin/cockpit but with that added functionality it would behave like one too. You could switch between them based on the need like real MFDs.

I like this idea. Having different stuff to show depending on the situation makes total sense. Maybe it could even use the hide condition and automatically switch based on data.
I'm definitely gonna look into this, but it might take some time.

I really like the customization with this script. I already created a screen solely for the copilot to monitor the Ship Systems (I will share it after finishing it).

Here are a few suggestions you could implement if you think it is worth it:

• Connectors: It would be cool to be able to use the Block Name of a connector to see if it is locked or unlocked rather than the number of connectors being connected. This way, you could do a screen for connectors if your ship has multiple ones.
  
• Pistons/Rotors: Retrieve the status of a Piston (how many meters extended) or Rotor (what degree it has turned) with Block Name and Value. Would enable for some cool screens and animations for e.g. if you have Landing Gears or Connectors on Pistons.
  
• Flight Seats/Cockpits: Same with the above. Being able to use Block Name to get a specific seat or cockpit, to see if someone is seated there.
  
• Turrets: Being able to see the on/off status of weapons or turrets would be useful for a Weapons Operator on a ship with multiple players.

Once, again, really love your script! For me its almost on the level of Automatic LCDs.

Lovely to hear, thank you!
These are all good suggestions, some of which I have considered already. The the problem right now is that it can't be done without a rework of the core. But I have other ideas that also requires that rework, so I'll probably do it once I figure out how to design it.

It would be great to be able to add an offset for the FFI Camera ruler, so when landed the distance registers 0.3m, then you could add "offset = -0.3m" to the cameras custom data and the display would then show the distance as 0.0m

Possible to get ForwardSpeed as new data? I want to be able to use the actions to trigger a large hydrogen thruster when speed > 100 and off below it, which this does already now, but I want it always on in reverse, something you can't tell it bc speed is an absolute value. Having a speed with a forward reference like the cockpit or remote that can go into the negatives for reverse speed would be great.

make finding sprites easier, either in script or in the guide.

Hey, man. This script is awesome! and I've been working for 3 days now (when I have time) on a custom cockpit setup for a small fighter (that will go in a bigger ship which will also get it's own custom cockpit) and I'm having a blast.

But this is the suggestion thread and I was thinking: Is there any way you could add a function to this script to pull data from one LCD to another? MMaster's Automatic LCDs 2 does this to some extent (pulling text from other LCDs or even from any block's custom data), but it's limited to text.
I would love to be able to create a screen with cargo weight like in your "propulsion" preset then in the same screen but in a different box, I'd have the current cargo scrolling from ALCDs2 whilst on another screen, I could have Whip's Turret Based Radar in the center, my coordinates in one corner (ALCDs2 again) and my speed and acceleration in another.

Speaking of Whip's scripts I've noticed that 1: a few people who use this script like to pair it with his (me included). And 2: your script already is able to use sprites from his scripts (also I agree with @Roasty_my_Toasty the sprites need to be easier to find, maybe have the list at the bottom of the custom data and have a limit on the line width).

Some other quick suggestions would be adding acceleration as data as well as thruster power (in kN or MN)

And the final thing I'd like is to be able to set block states as conditions. That way we could have custom sprites for all sorts of indicators. For example, I was going to have the power icon blink red rather than have a full red background in the power graph when I'm low on power. I was thinking I'd set up two timer blocks to start turning each other on and off when the script saw that I was low on energy which in turn would be the condition for the red power icon to show and hide (that's when I realized block states could not be used as conditions).

Sorry, it's a pretty long post but I really like this script and adding these things would really be awesome.

Originally posted by Daemar'Din:

Hey, man. This script is awesome! and I've been working for 3 days now (when I have time) on a custom cockpit setup for a small fighter (that will go in a bigger ship which will also get it's own custom cockpit) and I'm having a blast.

But this is the suggestion thread and I was thinking: Is there any way you could add a function to this script to pull data from one LCD to another? MMaster's Automatic LCDs 2 does this to some extent (pulling text from other LCDs or even from any block's custom data), but it's limited to text.
I would love to be able to create a screen with cargo weight like in your "propulsion" preset then in the same screen but in a different box, I'd have the current cargo scrolling from ALCDs2 whilst on another screen, I could have Whip's Turret Based Radar in the center, my coordinates in one corner (ALCDs2 again) and my speed and acceleration in another.

Speaking of Whip's scripts I've noticed that 1: a few people who use this script like to pair it with his (me included). And 2: your script already is able to use sprites from his scripts (also I agree with @Roasty_my_Toasty the sprites need to be easier to find, maybe have the list at the bottom of the custom data and have a limit on the line width).

Some other quick suggestions would be adding acceleration as data as well as thruster power (in kN or MN)

And the final thing I'd like is to be able to set block states as conditions. That way we could have custom sprites for all sorts of indicators. For example, I was going to have the power icon blink red rather than have a full red background in the power graph when I'm low on power. I was thinking I'd set up two timer blocks to start turning each other on and off when the script saw that I was low on energy which in turn would be the condition for the red power icon to show and hide (that's when I realized block states could not be used as conditions).

Sorry, it's a pretty long post but I really like this script and adding these things would really be awesome.

Thank you!
You have good ideas. The main reason I don't pull data from other LCDs is performance. Reading them manually several times a second isn't great. However, maybe I can run it less often.
I really like the block state idea!
I don't have much free time at the moment, but I'll see if I can take a look at it.

To be honest I suggested pulling data from other LCDs because it would be a bit ridiculous to ask you to virtually copy a bunch of other LCD scripts' functionalities. If you had plans to expand on this script a lot then adding some of these functionalities might be a good way to go about it but I would think you'd rather make something new.
I don't know how much of an issue it would be performance-wise to pull from other LCDs but maybe you could just put a warning in the setup so that people would know not to overdo it. You could also (like you said) "run it less often" or maybe somehow limit how much data is pulled rather than how often it happens? or a bit of both?
I honestly know nothing about programming so I'm really just throwing ideas out there.

Thx again for the mod and for indulging me!

Yea... i mentioned that in the comment section, but it's probably supposed to go here instead (oops..)

Readout block states (IS 'ON' or 'OFF', if destroyed value is 'OFF')

or

HP of a block

(or maybe both, lol)

that way I could make segments of my "Turret" turn red, if damaged or destroyed

https://imgur.com/a/wkR3Lx1

Great script!

Good script for personalize your ship, but very hard to understand.
Some suggestions: more data, like cargo, resorses and etc; group Widgets to move them together; more preloads, add exaple code to the guide and pictures of all sprites.

This looks like an amazing script! Would it be easy to add percentage full (volume) for all ship containers? This would be really useful for mining ships.