Page MenuHomeSchine - Phabricator

Starmade | Docking un-dockable when wrapped with docked blocks.
Closed, DuplicatePublic

Description

When a rail is wrapped with docked blocks (for wedge-on-wedge action) it cannot be hit with docking beams and is thus un-dock-on-able:

http://i.imgur.com/4VnaaZg.png <- Caution blocks are a separate docked entity from the track, rail is part of the track.

This setup worked before the update and multiple players on the build server have experienced this bug.

Details

Task Type
Bug
Testing Results
Affected Gamemode(s)
none/unspecified
Reproducible
Yes
Last tested (version)
0.19476
Category
Control Block System: Rails/Docking
First occurrence (version)
0.19476
Hardware/Software/System
OS-Specific
No
Hardware-Specific
No
Video Card Vendor
AMD/ATI
Video Card Model
n/a
User/Reporter/Contact
URL to Starmadedock thread
n/a
Username on Registry
Weishaupt
Username/Profile on Steam
[borst]
URL to Steam thread
n/a
Serverconfig (server.cfg)
<replace this line with the file content>
Clientconfig (settings.cfg)
<replace this line with the file content>

Event Timeline

ToasterBorst updated the task description. (Show Details)Nov 3 2015, 3:48 AM
ToasterBorst changed Category from none/unspecified to Control Block System: Rails/Docking.
ToasterBorst set First occurrence (version) to 0.19476.
ToasterBorst changed Reproducible from uncertain to Yes.
ToasterBorst set Last tested (version) to 0.19476.
ToasterBorst changed Video Card Vendor from uncertain to AMD/ATI.
ToasterBorst set Video Card Model to n/a.
ToasterBorst edited Serverconfig (server.cfg). (Show Details)
ToasterBorst edited Clientconfig (settings.cfg). (Show Details)
ToasterBorst set URL to Starmadedock thread to n/a.
ToasterBorst set Username on Registry to Weishaupt.
ToasterBorst set URL to Steam thread to n/a.
ToasterBorst set Username/Profile on Steam to [borst].
ToasterBorst added a subscriber: ToasterBorst.
ToasterBorst created this task.
Restricted Application added a project: Issue Navigation. · View Herald TranscriptNov 3 2015, 3:48 AM
ToasterBorst updated the task description. (Show Details)Nov 3 2015, 3:51 AM
ToasterBorst set Task Type to Bug.
ToasterBorst set Affected Gamemode(s) to none/unspecified.
ToasterBorst set OS-Specific to No.
ToasterBorst set Hardware-Specific to No.
lancake added a subscriber: lancake.Nov 3 2015, 4:23 PM

-Validated-

Oddly specific, could just be that you can't hit docked entities with a docking beam? Could you provide a blueprint of this? Start a chat room with me (http://phab.starma.de/conpherence/) if you want to share your blueprints privately.

lancake shifted this object from the S1 Public space to the S3 Starmade space.Nov 3 2015, 4:23 PM
lancake changed the visibility from "Custom Policy" to "Public (No Login Required)".
lancake changed the edit policy from "Task Author" to "Starmade (Project)".
lancake claimed this task.
lancake triaged this task as High priority.
Restricted Application added a subscriber: AndyP. · View Herald TranscriptNov 3 2015, 4:24 PM
spunkie added a subscriber: spunkie.EditedNov 3 2015, 9:09 PM

This one seems to be the same bug as T687

https://youtu.be/WcBFngO-uoA

You will notice how I can still dock to the mother ship but only if the line of sight for the beam would not touch the docked entity.

SchnellBier removed a subscriber: SchnellBier.
SchnellBier added a subscriber: SchnellBier.

Maybe same issue with power supply beams. Seems that the priority to hit is higher for a entity behind the actual target.

example 1: http://i.imgur.com/KwTS5lM.gif
example 2: http://i.imgur.com/RiSt92u.gif

Restricted Application edited projects, added Starmade; removed Issue Navigation. · View Herald TranscriptNov 5 2015, 4:41 PM
Restricted Application removed a subscriber: AndyP. · View Herald Transcript
AndyP moved this task from Unclassed to Archived on the Starmade board.Nov 7 2015, 11:01 AM
Restricted Application added a project: CBS: Rails. · View Herald TranscriptMar 10 2017, 6:23 PM