Erroneous K-Space Tab Entries
When looking at a tab filtered on K-space, why does it sometimes show an extra k-space connection for every wormhole in a system? Picture attached.
Comments (4)
-
-
- changed status to open
K-space mapping is a bit of an awkward one. I would personally suggest you use regular mapping and set each system as a "wormhole". What you can do is make it a wormhole type sig, leave the sig ID as ??? and set the type to 'GATE'. That way you can map a chain which includes both kspace and wspace.
If you are planning on mapping several different chains from kspace then I suggest creating separate tabs.
-
Unfortunately that's not really a viable solution to give to >40 scanners in the same corp that operate predominantly in k-space. The K-space tab is one of the main ways we know what regions we have access to from our space.
-
- changed status to on hold
Placing on hold as it will need looking at well after current updates
- Log in to comment
It looks like it does it any time there are multiple WHs in the same Kspace system.