I don't suppose you would be down for another feature suggestion, would you? Well, I say suggestion, so feel free to tell me no. I was wondering if it's at all possible to display the systems ontext panels or LCDs not in the cockpit?

The issue has now been fixed.

It's actually Planet 26. I can't code but if there is anything I can do to help I will. 'North' itself is relative to the sun's rotation. Maybe sneak a peak at Whip's compass or HUD scripts, sice I know he has Custom Data settings for the XYZ of the orbit to calculate 'North'.

Have you spawned the planet or is it the default one?
Im currently having similar issues myself on the Planet26 somehow, and I think it may have something with how the script locates North.

I'll post a screenshot if that's alright to show you what I mean. I have figured out why the angles were off in my previous post. It turns out if you have a remote control on a subgrid, the angle of the ILS and VOR will be off by however far that remote control is angled. For example, I have an angled flight deck, offset by 26.57 degrees with a remote at the end to tell the bridge crew what angle pilots need to approach.

I managed to fix that issue by removing the remote controls, but the localizer is still off on the ILS. In the picture, the runway GPS is just bow and stern, head on. Top left display is ILS, top right is VOR, just like your demonstration world. Runway heading is 133. What might I be doing wrong?

https://steamhost.cn/steamcommunity_com/sharedfiles/filedetails/?id=2176236469

Thanks for your comment, I think you can place the cockpit tag on the LCDs and it should work. If not please let me know :)

Very nice! But, :) anyway to make it work with custom made cockpits using lcds and text panels?

Thank you for your nice comment means a lot to us!
We do have some issues with the localizer scalloping or "jumping" a bit from side to side. I'm looking into the issue but its a slow process.
That being said I don't believe you'd need to be offset and a far distance away from the threshold.
Perhaps there's an issue with your GPS points to calculate the runway heading.

I hate to be the first one to ask this sort of thing considering how amazing this script is and how love I've been at this game, but is there something I am doing wrong with the ILS? When I use it, the glideslope works properly but the localizer is wildly off, where I have to be offset to the runway by 90 degrees and several kilometers away before it lines up. Am I using this wrong or did Keen break something?