This object is in archive! 

Dampners not calculating sub-grids

Dicen shared this bug 3 years ago
Won't Fix

This may be on here somewhere else and I apologize if it is but this is a HUGE pain, most of the time if you have a sub-grid on a ship using pistons or rotors their mass will NOT be calculated meaning your dampeners will never fully stop you, this is especially troubling in atmosphere because you will always be moving towards the ground. Is there any way you guys could fix this? I feel that its one of the more important issues at the moment.

Replies (7)

photo
1

Yes, I do! Have the same bug! :)

I think it's NOT a new bug and for me it does the exact same thing with connected (via Connectors and Merge Block) ship too!

It's really sad because it removes a lot a flexibility!

photo
1
  • Merge blocks is a clear case, alright.
  • Everything in a "locked" state (landing gears, connectors) acts a bit funny. Since not all grids may have thrusters in all directions this requires new code that treats all locked grids as one large dampened entity and can accept that there may be thrusters on it pointing in all kinds of directions. Should be straight forward to implement. (Famous last words.)
  • Rotors, wheels and pistons on the other hand that have a degree of freedom is a can of worms. Imagine a flyer with some sort of hammer arm rotating up and down on its side. When it moves down it counters gravity and thrusters go idle, when it comes back up it overwhelms the thrusters and the ship sinks swing-by-swing. You could argue that it should try to hold position, but that's not what dampers currently do, they just try to bring your current speed to zero.

photo
1

Is this still a bug?

photo
2

Yes this is still a bug, shockingly so.

photo
2

This still being a problem in the game does not reflect well on the developer - Keen, please pull up the socks here and fix this.

photo
1

Hello all!

I apologise that this thread is quite old. There have been a couple of threads that my colleague has been looking into. One has been marked as a duplicate as it should be fixed in the main thread. I believe these are all related in some way. If this is the case, the issue is now reproduced and awaiting a fix. Please have a look at the two here and here. If you're in agreement, I will mark this as a duplicate :)

Kind Regards

Laura, QA Department

photo
1

Hello Engineers,


Since there are no new comments in this topic, we are closing this thread as outdated.

In case anyone is encountering the same or similar bug, which is not already posted in a

different thread, please feel free to create a new thread with all relevant information.

Thank you.


Kind Regards

Keen Software House: QA Department

Replies have been locked on this page!