Page MenuHomeSchine - Phabricator
Create Task
Maniphest T2163

Starmade | Bricked button/activation module after logic activity with rails
Closed, FinishedPublic
Actions

Description

After some logic activity, the inputs that swap rails blow out, their visual connections retain but the block itself is bricked and reconnecting to the rails will create a duplicate connection visual on-top of the ones before it bricked.
This bug can happen anywhere with rails and logic connected.

Details

Task Type
Bug
Testing Results
Affected Gamemode(s)
Single and Multi
Reproducible
Yes
Last tested (version)
0.199.357
Category
Logic Gates
Hardware/Software/System
OS-Specific
No
Hardware-Specific
No
Video Card Vendor
uncertain
Steps to reproduce

(Most reliable/easy method to reproduce, although it is not similar to a usual environment)
1. set FPS limit to 30, this is crucial as higher FPS limits cannot reproduce it in this manner

  1. Build Alterintel's shootout rail clock (Instructions on how to build said clock)
  2. Activate it if you haven't already
  3. Observe the clock. However, you won't have to wait long for the entity to come off and the logic blocks to brick.

Event Timeline

Endal created this task.Jan 13 2017, 11:09 AM
Endal edited Steps to reproduce. (Show Details)
AndyP shifted this object from the S1 Public space to the S3 Starmade space.Feb 23 2017, 9:19 PM
AndyP changed the visibility from "Custom Policy" to "Public (No Login Required)".
AndyP changed the edit policy from "Task Author" to "Starmade (Project)".
AndyP edited Serverconfig (server.cfg). (Show Details)
AndyP edited Clientconfig (settings.cfg). (Show Details)
AndyP moved this task from New / Unconfirmed to Feedback on the Issue Navigation board.
AndyP changed the task status from Open to Feedback.
AndyP claimed this task.
AndyP triaged this task as Normal priority.

-Feedback-

Can you reproduce this without using an exploit clock?
As any signal triggering more than usual updates (especially visual active updates) it will run into an anti-spam mode and if it does not recover from slower operation it will stop working completely.

Restricted Application added a project: Waiting on Author. · View Herald TranscriptFeb 23 2017, 9:19 PM
Endal added a comment.Feb 27 2017, 10:43 AM

I have not been able to reproduce this on non-rail clocks as their frequency is far too low for this to happen.

Restricted Application edited projects, added Customer responded; removed Waiting on Author. · View Herald TranscriptFeb 27 2017, 10:43 AM
Restricted Application changed the task status from Feedback to Open. · View Herald Transcript
AndyP added a comment.Feb 27 2017, 10:06 PM

That is exactly my thought.
Regular clocks do not run in the "logic lag detection" and thus usually do not trigger the "emergency exit" from logic processing because it would affect global server performance.
So yeah, its a side effect of that exploit clock, buffering up signal or signal-changes that cannot be processed that fast.

I'm inclined to reject the report then, as we cannot allow higher limits to logic processing without allowing a way larger impact on server performance.
(As their actual use is rarely for precise timing, mostly for running jumpdrive charge circuits.)

Restricted Application added a project: Logic. · View Herald TranscriptMar 10 2017, 5:42 PM
AndyP closed this task as Closed.Mar 15 2017, 2:28 PM

Fixed together with other issue.

AndyP moved this task from Unclassed to Archived on the Starmade board.Apr 28 2017, 8:39 AM