Starting a cooperative game using ANY player-made/custom scenario is not possible. Steps to reproduce the problem: 1) Start Game - Co-op 2) Select "Scenario" 3) Pick any workshop-custom scenario. (Built in scenarios seem okay) 3a) Set up however, it doesn't seem to matter. 4) Click "Start". Results: The server starts, and runs in the background but nothing can connect to it, gives Cannot retrieve server information error if additional clients try, the main client hangs. If you exit the server, and try to resume the game - the created game does not appear on the game list. The normal work-around isn't working: Which is: Start solo, load in co-op. *(Editing dedicated.yaml as needed for password/server name) I've tested 5 different scenarios all with the same/similar results: Exactly the same: https://steamcommunity.com/sharedfiles/filedetails/?id=2276751921 https://steamcommunity.com/sharedfiles/filedetails/?id=2154284616 https://steamcommunity.com/sharedfiles/filedetails/?id=2430434643 https://steamcommunity.com/sharedfiles/filedetails/?id=1996210393 https://steamcommunity.com/sharedfiles/filedetails/?id=2113096697 Additional requested test file: https://steamcommunity.com/sharedfiles/filedetails/?id=2400441199 (Workaround works on this one) Close, but still broke: https://steamcommunity.com/sharedfiles/filedetails/?id=2070644465 That scenario at least starts, but none of the custom data comes through (Plays vanilla game) and it just starts a normal game. Which, after starting, the game list says that it's no longer usable and must be deleted. I suspect this scenario is too old and is incompatible. Attached is the server-log assiciated with the attempt to start the server from a new game.
Thank you for reporting this! This fails even using the test scenario I had made for coop testing so it's likely to be a game bug, not s problem with the scenarios themselves.
Uhm... can this be true? Your VRAM is stated to be 128 MB(?) Is it possible to give your Engines Specification or run a DxDiag and attach it here?
It only happens on custom scenarios and it seems to happen to everyone on the live branch so I doubt it's something wrong with his PC. I would have reported this myself but I just haven't had the time to test.
There are always Possibilities... Well, if we cancel out Hardware Problems the Software issue can be focused upon. The old fashioned Way of Fault finding...
If this is standard COOP and not dedi server, of course it does. But after reading the thread a few times I'm not even sure it's the "simple COOP" or a dedi game. The OP does not seem to "save and exit" as required when closing server in simple coop, this might be the reason why game does not show in list on reload. Since default multiplayer modes seem to work OK, this makes me think it's a simple COOP setup (game run from host player machine, no dedicated server).
As I stated, I would like to rule out Hard ware issues so the focus could be laid on Software. And what I saw in the attached Client was VRAM 128 and a Processor first mentioned 2011 in a PC Test Magazine... That made me wonder..
Thanks for the report this will be looked at. What you can do for now is either run the scenario from the standalone dedicated server (add a password to keep it private) or create a copy of the scenario folder which can be found in your workshop folder: "Steam\steamapps\workshop\content\383120" & name it to whatever you like or have it as the same name as it is on the workshop & create a coop session using a non-workshop copy of the scenario (I just tried this & both methods work) The standalone dedicated server is free to download from steam library > tools > "Empyrion - Dedicated server" when using this make sure you have the dedicated.yaml setup properly (port forwarding) & the gameoptions.yaml in the scenairo folder is setup how you want it under " - ValidFor: [ MP, Survival ]"