technolaha.blogg.se

So here comes the trick: just press on " Convert to ship" and the hinge moves again! I'm really sorry to say, that you would have to repeat this every time after closing and merging these two structures, BUT: I could repeat it several times - it WORKS FINE!ĭEAR programmers! WHY? Why did you keep this secret so many years for yourself?!! Why don't you just let us move this hinge WITHOUT the extra step of "ship-y-izing" the structure again? PLEASE don't torture us anymore! Fix it! Even though it LOOKS the same (both buttons "ship" and "station" are not activated - as initially), INTERNALLY it is considered a station - which is NOT movable. The system doesn't "know" anymore, that this structure was "movable". "Static structure" is only a name, but in this case it is CAUSED by an internal function of SE. So the system actually (internally!) still "remembers" that this is a separate structure. If you take a look at the Info-Tab you can now see that the system changed your "door" into a static structure. Open the K-menu of the HINGE (Not (!) ANY control block of the MAIN structure!!). So if you try to deactivated the merge blocks ( =unmerge) and reverse the hinge block ( =open the door), this doesn't work anymore, because the two structures seem to "stick" to each other. When closed the two structures MERGE into the MAIN structure. place a merge block on the inside of your door so that it will close with a merge block on the main structure (NO other blocks around the merge block - so they must "stick out" of the door AND of the main structure)įor the programmers: Until now you don't have any problem! You have a main structure and a no name substructure. construct your door so that if you close it ONLY the edges of all blocks touch the edges of the blocks in your main structure piston) to an edge of your MAIN structure place a whatever connecting aid-block (e.g. So, first: what's necessary to reproduce it (it's the old idea of a huge hangar door closing airtight): You are good guys! Don't misunderstand me! But this is an urgent priority ONE bug, which keeps all these wonderfull Engineers from proceeding!īUT - here is a workaround WITHOUT flexing away anything! YES! This is for the actual version 1.20 and may work for others.ĪND - maybe I even found the reason for you programmers. it's over 5 YEARS old and nobody was really interested in fixing it.

This problem is not 17 months, not 2 YEARS.

Hi Ondrej, hi QA, hi Yandila and all the suffering people out there!