Jump to content

Gas Temperature Swapping Bug - Heat Deletion Bug


mathmanican
  • Branch: Live Branch Version: Linux Fixed

The gas heat transfer code implements some effects (apparently at random about 5% of the time).  One of these effects happens when a hot high mass cell is next to a cold low mass cell.  It appears that the code tries to instantly balance heat between the two cells, but an override was put in place to prevent the low mass cell from having its temperature rise extremely high. If that were to happen, then

  • instead of equalizing heat or doing nothing, the game swaps the temperature of the cells. 

This is the bug.  It always results in heat deletion. I can be massively abused to create an alternate Borg Cube.  You can find lots more details about this bug in the following forum post. 

Great thanks to @TripleM999 and @Manarz for doing the detailed testing to completely track it down. 

This bug affects gameplay in steam turbines setups, and has been a regular complaint for quite some time. You'll find our monstrosities that abuse this bug in the post above. 


Steps to Reproduce

See the forum post above for details.  Because the events of swapping occur randomly, you cannot reproduce it every time. However, if you build 20 of something, or just build a device that guarantees cold low pressure gas will always be next to hot high pressure gas, then the bug will kick in and you'll watch temps drop. 

Page 1 has @TripleM999's tests, in particular something like the following should help you quickly spot the issue. 

TestBed3.thumb.png.77264d31b896a9b24dc06

  • Thanks 1



User Feedback


A developer has marked this issue as fixed. This means that the issue has been addressed in the current development build and will likely be in the next update.

The level of abuse of this bug has reached monumental proportions.  @TripleM999 is begging us to end Borgie's existence.   I'm concerned we will need a support group for bug exploiters when this finally goes away. :) 

240kgReactorFreezer.thumb.png.700f116528

 

  • Thanks 1

Share this comment


Link to comment
Share on other sites

Changed Status to Known Issue

I've implemented a fix we're testing locally. Thanks for the detailed reports.

  • Thanks 3

Share this comment


Link to comment
Share on other sites

Changed Status to Fixed

Based on testing locally and in the preview branch, this seems to be fixed!

  • Thanks 3

Share this comment


Link to comment
Share on other sites



Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
  • Create New...