To update the case here, the ship has multiple rail controllers, all hooked up to run at different speeds. One of them was not connected to any rails, though it was connected to activation modules. When this rail controller was deleted, the rail lockup issue on the ship was instantly resolved. Disconnecting it from the activation modules, changing their state, etc, had no effect. Only deleting the rail controller block had an impact.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Mar 1 2017
Mirror cubes is definitely not working properly for most blocks but should be unrelated to this issue.
This replace/symmetry part can be seen as a feature request though. In some situations you would want to apply a single orientation replace on a larger area which can be accomplished by using symmetry to extend your build box size. If it also mirrors this you would get undesired results.
Hmfp, probably improved but still has issues. It's not exactly consistent so I'll need to spend some more time figuring out why it does this.
Feb 28 2017
-QA Testing-
Hm, none as far as I know. Most likely the blocks used in those templates were custom.
That's a different issue than this particular task though, if you have an example template that shows this corruption issue, please make a bug report about it and include the file in your description.
One of the older bugs, when a camera is used on a dock, it uses the default orientation (which is the front). Merging with existing task.
[2017-03-01 00:05:23] [ADMIN COMMAND] TERRITORY_RESET from RegisteredClient: AndyP (41) [AndyP]connected: true params: [62, 62, 62] [2017-03-01 00:05:23] [SEND][SERVERMESSAGE] [ADMIN COMMAND] [SUCCESS] unclaimed system: 62, 62, 62 to RegisteredClient: AndyP (41) [AndyP]connected: true [2017-03-01 00:05:23] [SERVER][FACTION] Territory: REMOVE SYSTEM Void(62, 62, 62) OWNERSHIP FROM FACTION null [2017-03-01 00:05:23] [DB] FORCE UPDATING SYSTEM (62, 62, 62) [2017-03-01 00:05:23] [SERVER][GALAXYMANAGER] galaxy zone has been marked dirty and has been removed from cache. Changed (62, 62, 62); [2017-03-01 00:05:23] [FACTIONMANAGER] trying to add news entry: FactionNewsPost [factionId=0, op=ADMIN, date=1488323123623, message=Ownership of System default(62, 62, 62) has been revoked by ADMIN., permission=0] on Server(0) -> fid(0) [2017-03-01 00:05:23] [FACTIONMANAGER] updated news on Server(0) for factionID 0; delete: false [2017-03-01 00:05:29] [ADMIN COMMAND] TERRITORY_MAKE_UNCLAIMABLE from RegisteredClient: AndyP (41) [AndyP]connected: true params: [62, 62, 62] [2017-03-01 00:05:29] [SEND][SERVERMESSAGE] [ADMIN COMMAND] [SUCCESS] made system unclaimable: 62, 62, 62 to RegisteredClient: AndyP (41) [AndyP]connected: true [2017-03-01 00:05:29] java.lang.IllegalArgumentException: cannot determine type: UNCLAIMABLE [2017-03-01 00:05:29] at obfuscated.Zk.b(SourceFile:163) [2017-03-01 00:05:29] at obfuscated.aik.g(SourceFile:2213) [2017-03-01 00:05:29] at obfuscated.aik.a(SourceFile:1844) [2017-03-01 00:05:29] at obfuscated.abl.updateLocal(SourceFile:584) [2017-03-01 00:05:29] at org.schema.game.server.controller.GameServerController.update(SourceFile:1358) [2017-03-01 00:05:29] at org.schema.schine.network.server.ServerController.run(SourceFile:275) [2017-03-01 00:05:29] at java.lang.Thread.run(Thread.java:744) [2017-03-01 00:05:29] [SEND][SERVERMESSAGE] [SERVERMSG (type 3): [250, IllegalArgumentException, cannot determine type: UNCLAIMABLE]] to RegisteredClient: AndyP (41) [AndyP]connected: true
Thank you for the feedback and upload.
Sector export uploaded. I went to the sector to investigate. The ship in question was in the sector, but not at the sector coordinates indicated in the log file.
Asked @Benevolent27 for a sector export.
Found this in the logs:
[2017-02-28 15:59:50] Exiting (normal) because of exception java.lang.NullPointerException: Added nonconform object {RigBExOrig@932909189Ship[LMC Everest III](11244);COLSHAPE:[CubesShape|SER Ship[LMC Everest III](11244)];AT(5072.4854, 755.9233, -986.6366)(SID: Sector[11201](8, 40, 38))} [2017-02-28 15:59:50] java.lang.NullPointerException: Added nonconform object {RigBExOrig@932909189Ship[LMC Everest III](11244);COLSHAPE:[CubesShape|SER Ship[LMC Everest III](11244)];AT(5072.4854, 755.9233, -986.6366)(SID: Sector[11201](8, 40, 38))} [2017-02-28 15:59:50] at obfuscated.agc.a(SourceFile:108) [2017-02-28 15:59:50] at obfuscated.aPm.a(SourceFile:391) [2017-02-28 15:59:50] at org.schema.game.common.data.world.SimpleTransformableSendableObject.onPhysicsAdd(SourceFile:1907) [2017-02-28 15:59:50] at obfuscated.XR.onPhysicsAdd(SourceFile:2469) [2017-02-28 15:59:50] at obfuscated.aup.a(SourceFile:427) [2017-02-28 15:59:50] at org.schema.game.server.controller.GameServerController.update(SourceFile:1257) [2017-02-28 15:59:50] at org.schema.schine.network.server.ServerController.run(SourceFile:275) [2017-02-28 15:59:50] at java.lang.Thread.run(Thread.java:745)
Still having the issue. This is problematic since the quests on our server require a player to NOT be able to claim the system that their quest instance is created in.
Merging into an earlier report.
-Fix confirmed-
Haven't seen it happening since, assuming the fix worked.
-fix confirmed-
-fix confirmed-
-fix confirmed-
-fix confirmed-
-fix confirmed-
-fix confirmed-
Works fine, although the damage display numbers seem to be off. Not only for explosive effect though so gotta take a closer look at that for another task.
One of the older bugs we have yet I can't find its older task. Maybe not exported from Redmine or I imagined we had that report.
I'll retest this one then.
Feb 27 2017
That is exactly my thought.
Regular clocks do not run in the "logic lag detection" and thus usually do not trigger the "emergency exit" from logic processing because it would affect global server performance.
So yeah, its a side effect of that exploit clock, buffering up signal or signal-changes that cannot be processed that fast.
Thank you for the report, but that is totally intended,
the testserver does not focus on survival and gathering stuff - its totally opt-in to play real survival.
We want to test the game, not the economy and first hours =)
I have not been able to reproduce this on non-rail clocks as their frequency is far too low for this to happen.