All rail systems stopped working on the ship attached below, and the entire line if blueprints regardless of the date or the version that was saved. Certainly worked 2 patches ago. Rails no longer move or rotate the entities docked on them, be it old block or freshly placed on the main entity. Blueprint attached. If this bug is not fixed, I'll have to abandon an entire design I worked months on...
Description
Description
Details
Details
- Task Type
- Bug
Testing Results
- Affected Gamemode(s)
- Single and Multi
- Reproducible
- Yes
- Last tested (version)
- 0.199.234
- Category
- Control Block System: Rails/Docking
- First occurrence (version)
- 0.199.234
Hardware/Software/System
- OS-Specific
- No
- Hardware-Specific
- No
- Video Card Vendor
- uncertain
Steps to reproduce
Just extract the blueprint provided in the attached file and load it. Try to operate any of the inner ship remotes or place rails and move any entity docked on them.
Serverconfig (server.cfg)
<replace this line with the file content>
Clientconfig (settings.cfg)
<replace this line with the file content>
Event Timeline
Comment Actions
-Feedback-
You did that on NFD .. right ?
i have the same problem with Blueprints created there. Rails are failing regulary on NFD ... mostly while the server isnt responding ...and after its responding again they are broken.
took a BP from there to the Testserver and it had weird problems.
can you tell me what button to push and what to expect to move.
can be done on the test server if you want
Comment Actions
on the WIP blueprint there are 4 inner ship remotes in the 2nd quickbar. The first on the left was supposed to operate the shootout rail clock chain drive but I noticed the rail fail while trying to load the pendulum entity onto it. Second from the left should open the drive pods at the back of the ship, third is supposed to extend the docked reactors (which I removed after power aux update) and the last should open the missile silo doors on top of the ship, as well as the docking arms on the bottom.
Strange enough, ALL versions of this ship, even those saved in blueprint form weeks/month ago, also don't work any more. Yes, it is the NFD buildserver Infinite Havoc.
Comment Actions
Ok .. as far as i can see the Wireless and inner ship remotes broke (thats not a new thing at all)
the rail rotator from the rear door is still working fine (activated with the button above it)
the elevator moves fine (Just not through the wireless links)
i cant find the other things in your build (no clue where they are placed. its a bit big ;) )
maybe check and see if they are working when activated by hand.
if not i need a stripped down version where we can see what is supposed to do what. (we could do that obn the testserver thenmaybe )
Comment Actions
OK, so after conversing with AtraUnam about this, she also encountered the bug before and the only way to save something of the ship was taking the Data folder of the blueprint and replacing the Data folder of a blueprint of a core with it. Essentially deleting all block metadata and attached entities. That makes the rails work again, but resets all blocks connections and settings on the entity.
it also ONLY and EXCLUSIVELY happens on large entities with many docked entities. I suspect metadata corruption.
Comment Actions
Yes .. killing all metadata would make it possible to fix that problem.
but this isnt about fixing the problem its about finding the cause for it to happen in the first place.
and i do have to see a report from anything that isnt originating from NFD to verify that this is a reproducable problem somehow.
i stopped building on NFD because i did run into these rail problems there myself and took a blueprint of it for investigation (part of it is handled in another report). no one seemed to be worried about the server not running stable when i did ask around back than and tried to get logfiles from around the events happening however.
Didnt had any problems with my blueprint after fixing it on the testserver after that.