#Shenanigans With Cabling

1 messages Β· Page 1 of 1 (latest)

spare bone
#

Hi hi! So I was laying down fiber cable in the game, and figured out how to replicate-ish the bug to a certain extent. I was working on a new level 10 region when I decided to put down a Capacitor, instead of an Uplink, in the center of the region since the Uplink in the neighboring one was new, and still had a lot of capacity to give. I laid down fiber connecting the Uplink to the new Capacitor, across regional boundaries, and immediately, the new fiber connection became untargetable. I could not connect new fiber or regular cable to the fiber connection between the Uplink in one region, and the new Capacitor in the new region.

And then, when looking for other regions where this bug affected the fiber connection, I stumbled upon a slightly-olderish regional connection, also between an Uplink and a Capacitor, with the fiber connection going across regional boundaries. The quirk about this instance of the bug, is at a certain point in the connection, the fiber connection is targetable, so I can branch new regular cable or fiber off from the fiber line between the Uplink and the Capacitor. However, a large part of the fiber connection is untargetable, just like the newly laid connection in my newest regions, per the above.

In the screenshots, I have defined the regions where the fiber cable is connecting to the Capacitor, as BUG REPORT REGION A and BUG REPORT REGION B. I will attempt to upload the save file.

Thank you for the assistance Dev Team! This game is awesome!

drowsy sluice
#

Okay, I have a refinement of this.

spare bone
#

πŸ‘€

#

hot damn, that's a quick response. Jeez Trevor; do you sleep? LOL

drowsy sluice
#

It's about 2:30pm here. πŸ˜„ Totally reasonable time for me to be working! πŸ˜‰

spare bone
#

This isn't game-breaking. I think I can just kill the cable connection, re-lay it, and then it should function as normal? At least for the level 10 region?

#

It's just slightly inconvenient

#

unsure how saving -> exiting -> reentering affects the bug. I can try it right now.

drowsy sluice
#

Repro:

  1. Have two owned regions which share a border, with a network uplink in one region.
  2. Place a fiber starting from the uplink in the first region, going to an arbitrary point inside the second region.
  3. Notice that while the fiber works (it does transmit bandwidth from objects in region 1 to region 2), it cannot be accessed by editing tools inside the second region.

That is, the "destroy" tool can't see the parts of the fiber inside region 2, but does see the parts of the fiber which are inside region 1. Similarly, the cable placement tool cannot split new cables from the fiber within region 2, but can do so within region 1.

#

Placing the fiber determines which region is 'region 1' (where the fiber remains accessible) and which is 'region 2' (where it's inaccessible); the region where you start the fiber placement is always region 1.

spare bone
#

this is exactly the way to replicate the issue. o.o it's not necessarily just to a capacitor. I just wanted to create a Point-of-Reference.

drowsy sluice
#

(edit: having said that, now the 'destroy' tool isn't seeing it in either region. Huh. I was sure that was working in region 1 when I tested it 5 minutes ago)

spare bone
#

What complicated things with Bug Region B, was that the fiber cable also followed the regional border to a large extent, so I wasn't necessarily sure if the coding for the region borders was messing with the fiber cable coding. That's kind of why I went ahead with creating the connection for Bug Region A, just to make sure I wasn't being nutty.

drowsy sluice
#

This gets even worse because a single fiber can travel through more than just two regions in a single span. And it's only accessible for building off of in the region where you started drawing it.

#

Like in the southernmost fiber in this screenshot

spare bone
#

I haven't tested that, but I agree that by the logic to reproduce above, the number of regions the fiber passes through, wouldn't matter, since the bug starts at the boundary/ending of the first region. But also... bruh that looks like a mess LOL

#

I need to fix my cabling aiyaaaaaa

drowsy sluice
#

(I drew it from southwest, to north, then to southeast, all as a single cable. And I can only build off it in the southwest region)

spare bone
#

That's kinda nuts actually. Is that common practice among players LOL

#

am I the weird one?

#

... so I think I've been working around this bug for longer than a hot minute; I'm finding more instances of redundant fiber cabling in my older regions, now that I'm trying to clean up the mess LOL... wow this is awkward.

#

There's a random instance of fiber passing through fiber without a connection at the intersection, if you're interested πŸ‘€

#

I am unsure how that happened...

drowsy sluice
#

I assume it's another case of fibers not interacting with each other outside of their starting region.

spare bone
#

That's exactly what it is LOL

drowsy sluice
#

Should be fixed now with the latest build!