Imagine a new block which is to be connected with (small) nav receiver. It upgrades them to use any insurance transfer points (either dev stations or player stations with a reconstruction machine you can point to) you linked up and can feed them with. It is customisable, meaning, not fixed IT stations, but the ones which you think serve best. The method using Origin 1,8,15,22 (copyright Erador) basically points into that direction, but problem is they are very close to each other and there is no ingame device using their numbers. I imagine if you put in an IT station in EOS belt, another at Elysium and a third on, say, Chemosh, your deep space readings will be much more reliable because triangulation references are being spread. Should be versatile enough also to use temporary positions of said reproduction machines in parked capital ships. So this system will only work with a minimum of three insurance transfer stations you enter in the yolol or user interface of that block. As with ISAN, you can derive readings from the device in x, y, z coords format for live monitoring on some screen in your cockpit.
#Deepspace Nav System using custom Insurance Transfer Stations
4 messages · Page 1 of 1 (latest)
I really like that idea! But I also want this to have for nav chips to be even more flexible: Some device with a slot, where you put a nav chip and it returns the distance in meters to this chip as yolol variable.
Btw, in 3D space you need at least four transmitters stations. With only three you get an ambiguity of two points.
🤔 Receiver with slot for nav chip sounds interesting and fits good for other game mechanics. If device could just get distance to coordinates, we could find out where is our station, make custom isan, will be a reason to make more nav chips for internal use, could make pirating more useful if you can steal coordinates of enemy base and siege it