The wireless blocks do connect to each other with a connection pipe
defeats part of there purpose and usefulness i think
additionaly
<replace this line with the file content>
<replace this line with the file content>
Have to change the priority for this.
The marker Beam is mostly useless for linking two wireless blocks on one entity because they overwrite the last input when used on the next set of blocks. The only way i found to prevent this is to relog to the game between linking blocks.
The wireless block should not be used as an alternative to the activation block as its method of sctivation is highly inefficient. I can make the pipe disappear, but wireless blocks still have a lot of overhead (because the potential information of having another UID + position)
Other type of link with much higher performance impact, so its not advised to use them, not even for "hiding" a few link-pipes
Putting back into Queue for the Following reason :
If this is a performance problem and not supposed to be used on the same Entity then:
could it be that this causes further wireless problems with links getting lost for example ?
The marker ability is is necessary when you want to connect two stations that are sectors apart. C-V probably won't work in that case
pulling this back, this needs some more investigation on link types as I heard from smiling about a possible problem related to reusable marker weapon and other stuff
-Confirmed-
Okay, gathered the details.
Its indeed as described:
They seem to be using some type of seed, per start, which causes issues, and may bloat meta, if someone manages to make thousands of wireless links inside one entity.
Links inside one entity should always use the "visible link" type, and thus avoid the expensive (and invisible) links through the wireless tables.
If there is a need for wires not being visible you can use a docked entity as some type of wireless router.
To reproduce:
Issue a) If you try to pair a second set on the same entity, the first link breaks, both wireless inputs will target the same new output, first output gets abandoned. (selecting any other entity or alike does not fix this problem)
Issue a) persists and breaks the new linked ones, the original ones are OK, and wont break again, unless issue b) kicks in:
Issue b) Fully restarting the game, will wipe all in-entity (wireless) links on the station
Stupid question :
Why not simply disable the logic links outside of Build mode ?
And disable the ability to connect wireless blocks on the same entity with the marker beam ?
The marker weapon is meant to do those links?
It was rather surprising C and V in astronaut mode work flawless to link between entities ^^
So the main problem is:
Need to prevent the use of the expensive connection type when marked object and target are the same.
Should be the easiest way to prevent any inconsistence.
(I would also like to disable C-V link between entities so people have to learn using the marker beam, and do not gamble on linking warpgates anymore, as they are used to that mechanic then, but may be too far :P)
If people are using wireless (expensive in game overhead) to get rid of logic pipes wouldn't the concept of eliminating the pipes except in build mode do the job best?
Now any other logic block connections with wireless module are invisible in both directions, not only wireless-wireless connections. Is it supposed to be like that?