I seem to have a problem where the 3 separate parts of the Romulan singularity harness set or the Ancient obelisk technology set doesn't link up with each other. Has anyone noticed this, and does it affect the Set 2 and Set 3 abilities?
For the Romulan set: Experimental plasma beam array and hyper-plasma torpedo launcher
do not link to other parts (showing "0 of 3"), but Zero point energy console does.
For the Obelisk set: Omni-directional antiproton beam does not link to other parts (also showing 0 of 3) but Obelisk subspace rift core does.
People assume that time is a strict progression of cause to effect. But actually from a non-linear, non-subjective viewpoint it's more like a big ball of wibbly-wobbly timey-wimey ... stuff. --the Doctor, "Blink"
You are checking this while being in orbit of a planet (e.g. in a system)?
Because in sector space and on ground those thinks arent calculated, only if they are active in a system/combat-map.
You are checking this while being in orbit of a planet (e.g. in a system)?
Because in sector space and on ground those thinks arent calculated, only if they are active in a system/combat-map.
ww since you asked: I checked on both ground and space maps. I'm fully aware that console sets are only calculated (effective) in space but they should link up no matter what map I am in.
For example: my KDF has a Peghqu' Heavy Destroyer with the Reman Prototype Space Set, that's fully linked up on both ground and space. For the Romulan Singularity Harness (same ship) though I don't have the plasma beam array, the Hyper-plasma torpedo does not link to the ZP Energy Conduit on ground but it does in space. Guramba siege destroyer: as part of Omega Adapted Borg Technology, Kinetic Cutting beam does not link up with Assimilated Module on ground but is okay in space. I get similar results in my Fed-allied Romulan.
I don't understand why this is happening but like I said, they should link up in all maps and instances. It must have been caused by one of the updates or season packs, I did not see this problem when I first got the sets.
People assume that time is a strict progression of cause to effect. But actually from a non-linear, non-subjective viewpoint it's more like a big ball of wibbly-wobbly timey-wimey ... stuff. --the Doctor, "Blink"
edit: Never mind, I see what you're saying. Yeah, they're doing the 0/3 thing on Ground. Hrmm, it's uh - hrmmm - well, yeah...
Can clearly see the items are there - don't need some 1/2/3 thing to tell me that - and since none of it matters unless you're in space...
...but yeah, they used to show the 1/3, 2/3, 3/3, etc, etc, etc and now it's showing 0/3 as if the piece you're looking at is not there while on Ground (er, even though it's obviously there since you're looking at it).
Comments
Because in sector space and on ground those thinks arent calculated, only if they are active in a system/combat-map.
ww since you asked: I checked on both ground and space maps. I'm fully aware that console sets are only calculated (effective) in space but they should link up no matter what map I am in.
For example: my KDF has a Peghqu' Heavy Destroyer with the Reman Prototype Space Set, that's fully linked up on both ground and space. For the Romulan Singularity Harness (same ship) though I don't have the plasma beam array, the Hyper-plasma torpedo does not link to the ZP Energy Conduit on ground but it does in space. Guramba siege destroyer: as part of Omega Adapted Borg Technology, Kinetic Cutting beam does not link up with Assimilated Module on ground but is okay in space. I get similar results in my Fed-allied Romulan.
I don't understand why this is happening but like I said, they should link up in all maps and instances. It must have been caused by one of the updates or season packs, I did not see this problem when I first got the sets.
Can clearly see the items are there - don't need some 1/2/3 thing to tell me that - and since none of it matters unless you're in space...
...but yeah, they used to show the 1/3, 2/3, 3/3, etc, etc, etc and now it's showing 0/3 as if the piece you're looking at is not there while on Ground (er, even though it's obviously there since you're looking at it).