Bug 9th April dev activator bugs

[NeonSturm]

1.
Try to make a ship with 2 weapon cpus (+ amcs), power, 1 activation block and 1 delay block.

link activation and delay to another.
link activation to weapon cpus.

Expected: Fire each 0.5 seconds. (This is too slow btw).
Got: Some XML Timeout exception.

2.
Link 2 delays to another.
Remove one.
50% chance to crash.

3.
Build an activation block and link it to a gravity block and a delay block.
Link the delay block to a gravity block and a second activation block.
Link the second activation block to the delay block and a third gravity block.
You may also link these three blocks to PlexDoors to see the activation events.

Only the first alters your gravity.

 

[AndyP]

1) didnt try this exactly, but 0,5 second seems okay for me. (think about scalable longer timers, with lower than 0,5 you Need hundreds of delays for a minute. - will try for XML
2) confirmed - added to list
3) there is a cooldown on activation blocks (inputs) like on any other (area trigger), so outputs should have a cooldown too, to prevent spamming with it.

- Andy

 

[NeonSturm]

AndyP "1) didnt try this exactly, but 0,5 second seems okay for me. (think about scalable longer timers, with lower than 0,5 you Need hundreds of delays for a minute"

Maybe we need then need the ability to scale logarithmic 2^(n-1). Array size = delay, but everything else works in the same way as now.

 

[AndyP]

NeonSturm In Suggestion Forum I would write:
Best would be: Press R and open a menu with slider settable to 0,5seconds to 60 minutes.

:P

But doubling the timeshift on every directly adjacent delay, should be ok too.

- Andy

 

[NeonSturm]

AndyP "Best would be: Press R and open a menu with slider settable to 0,5seconds to 60 minutes."
But I don't like to make an indirect way over the menu for a simple doubling :p

Though every improvement is an improvement not to be underestimate never the work.