Mode: Survival Mode: Dedicated Server SERVER NAME: non-public SEED-ID: n/a MODIFIED PLAYFIELDS: Yes Reproducibility: Always Severity: Crash Type: Global Summary: Wreckage CVs, when claimed and factioned, produce CoQ errors when: salvaging engines with Multi-Tool, sitting in passenger seats, and various other tasks, including just being in proximity. Description: See Summary Steps to Reproduce: Claim wreckage CV in orbit by placing a core. Attempt to salvage engines, sit in a passenger seat, and just generally hang around doing things like hitting the O2 station, etc. Save Game: https://drive.google.com/open?id=1ipcnAEhV--O12UL4pQzreIpBoVoyH-ys Server Logs: https://drive.google.com/open?id=19tl6dm-XA6p73rkSqTgYbxfzwd-ZC6io
-- edit -- Still getting this same in 2697 build (server down, removed all bin file, server up - tried, still getting error) -- /edit -- Survival, dediserver, game started on previous A 10 build. reproduce: always severity: major / gamebreaking (can't build a working HV) trying to place a thruster (tried the low tier 1 block and 2 block thrusters) on HV causes CoQ error and the thruster disappears. Tried this both on a HV that was built (successfully) on previous game build, and a new HV started on this build. This happened with two players on server, both in player made faction. Tried first on HV owner privately then on HV owned by faction. Step to reproduce: 1) try to place a thruster After unsuccessfully trying to place a thruster, placed a regular metal block on ship. This caused the thruster to become visible on the HV, but trying to remove the thruster (using multitool) resulted in another CoQ. At that point, gave up. Attaching Dedicated log from the session, from the server.
@Nogitsune Appears to be the same issue as this https://empyriononline.com/threads/near-constant-coq-errors-near-space-wreckage-6905.91107/ Merged threads
@Pantera - I followed this same procedure as @Nogitsune . I downed the server before deleting the .bin files, etc. Edit: this savegame was started on the 30th with the fresh 10.6 patch.
Build Alpha Ex 10.6.0.2697 seed 905518. Fresh Game. Tested both Single Player and COOP. Default config. Error 100% reproducible. Error does not occur when playing Single Player. Error only occurs when playing COOP. Dedicated not tested. Building SV: placing a Thruster S (did not test other engines) produced a CoQ. An invisible block was placed where engine was specified. Invisible block not present after server restart. RCS, Cargo Controller, Ammo Controller, Generator, Fuel, Steel blocks all worked as expected. Logs attached.
Reported same issue on earlier build (2695 I think), that one was dediserver started on that build, and carried over to 2697 (bug still present). This one was on HV though, with both 1 block and 2 block thrusters - so it does.. 1) happen on both HV and SV 2) happen on both dedicated and coop multiplayer (but not single player) 3) is not new to 2697 build, but was already present in 2695 4) occured in fresh game both on 2695 and 2697 Symptoms were similar (CoQ, invisible block appearing when thruster was placed) - also when I placed regular block on the same HV, the invisible thruster became visible. The thruster could not be removed with multitool even after it became visible (trying to remove caused another CoQ).
I've also been experiencing this. Co-op game. Often when the person I'm playing with is shot/shooting a Zirax base, I will get the errors, and when I'm fighting one, he will get them. We were in an SV and HV, and errors were coming when the base was being shot. Sometimes it was when we got shot also, a shield reduced the error significantly. Shall I PM you the logs on discord after it happens again, or do the email thing?
Sent in the ones from a couple days ago. I'll send another set this evening when we get a chance to play some more. It seems like the error is also happens when shooting at a drone or zirax turrets, sometimes when I hit them, sometimes when it hits me...unless there's a delay in the error popping up, i'm not sure.
Thanks I replied to your email. The logs you supplied are what has been reported here in this thread I moved your post here also.