My Scenario does not work in Local Co-Op

Discussion in 'Scenarios' started by Mia, Mar 22, 2019.

  1. Mia

    Mia Commander

    Joined:
    Jun 7, 2016
    Messages:
    164
    Likes Received:
    66
    I know nothing about server but apparently all other scenarios work in Local Co-Op.
    I was stuck in the loading screen and I don't know what's wrong.
    Please, is there anyone who can help me?
     
    #1
  2. ravien_ff

    ravien_ff Rear Admiral

    Joined:
    Oct 22, 2017
    Messages:
    6,291
    Likes Received:
    11,948
    The conquer one?
     
    #2
    Mia likes this.
  3. Mia

    Mia Commander

    Joined:
    Jun 7, 2016
    Messages:
    164
    Likes Received:
    66
    Conquer and Hard Survival as well
     
    #3
  4. shortybsd

    shortybsd Ensign

    Joined:
    Jul 21, 2017
    Messages:
    14
    Likes Received:
    7
    I will check later today. Problem should be in your dedicated server log or playfield log. Also check the client log. Might be a null object error which leads to lock up.
     
    #4
    Mia likes this.
  5. Mia

    Mia Commander

    Joined:
    Jun 7, 2016
    Messages:
    164
    Likes Received:
    66
    Thank You :)
     
    #5
  6. Pantera

    Pantera Administrator Staff Member

    • Developer
    • Moderator
    Joined:
    Aug 15, 2016
    Messages:
    3,249
    Likes Received:
    5,708
    #6
    ravien_ff and Mia like this.
  7. Mia

    Mia Commander

    Joined:
    Jun 7, 2016
    Messages:
    164
    Likes Received:
    66
    Thanks I appreciate your help :)
     
    #7
    ravien_ff likes this.
  8. shortybsd

    shortybsd Ensign

    Joined:
    Jul 21, 2017
    Messages:
    14
    Likes Received:
    7
    This is the error from the dedicated server. The error is not very specific
    Code:
    23-22:17:11.252 17_17 -EXC- System.ArgumentNullException: Argument cannot be null.
    Parameter name: s
      at System.Text.Encoding.GetByteCount (System.String s) [0x00000] in <filename unknown>:0
      at System.Text.UTF8Encoding.GetByteCount (System.String chars) [0x00000] in <filename unknown>:0
      at Assembly-CSharp.DriveScope.Write (System.String _value) [0x00000] in <filename unknown>:0
      at Assembly-CSharp.DeviceList.GenerateMenu (System.IO.BinaryWriter ) [0x00000] in <filename unknown>:0
      at Assembly-CSharp.DirectoryList.ResolveClient (System.IO.BinaryWriter ) [0x00000] in <filename unknown>:0
      at Assembly-CSharp.DiskList.IncreaseQueue (ToolboxInfo ) [0x00000] in <filename unknown>:0 
    Give me a few so I can find the typographical's or invalid settings in the playfields yaml.
     
    #8
    Last edited: Mar 24, 2019
  9. shortybsd

    shortybsd Ensign

    Joined:
    Jul 21, 2017
    Messages:
    14
    Likes Received:
    7
    It is your playfield.yaml for Vagish Asteroid Field. You copied the playfield_debug.yaml and pasted it into playfield.yaml. Wrong config settings. This right here is why I do not use any of those 3rd party editors as it butchers the yaml's. It could have been a copy paste error in your part, but the settings are all out of order.

    Give me another second to fix your playfield. I would advise you to not use EPD. Also we are on 9.5.0. Notice how the build number is in weird order comparing to Empyrion's example. These editors do not work efficiently. For optimized loading, put the things in the correct order where Unity finds it in order for faster load times. Sure it will work out of order (whacked) but will cause other problems down the road.

    Also in your prefabs it is better to name them with no space or use an underscore. Example: WeaponBase1 or Weapon_Base1. Spaces always tend to cause extra issues. The name field is how you properly name the base and spaces are totally fine there (not trying to confuse you).

    Note: Vagish isn't even in your sectors.yaml. Included playfield that isn't even used. I will end up having to go through everything since they don't have proper error logging, stating on which line the error occured. I see your sectors.yaml is butchered as well (due to an editor).

    Another Note: After going through numerous of your playfields and finding errors in almost all, it will be hard for me to pinpoint what is the root cause. I will tell you, you are running older yaml's in the newer version of Empyrion and that causes issues as playfields changed. I tried brother, but don't have the time to fix everything. I would suggest Empyrion to put in better error catchers (Exception Handling for loading playfields) in their Unity app.

    Got it ! your sectors.yaml is the root cause. Going through it now to find out which section is causing it to not load in multiplayer.
     
    #9
    Last edited: Mar 24, 2019
    ravien_ff likes this.
  10. shortybsd

    shortybsd Ensign

    Joined:
    Jul 21, 2017
    Messages:
    14
    Likes Received:
    7
    The fix, in sectors.yaml. Line #589 and #590. Delete line #590, modify line #589 to this:
    Code:
      Allow: []
    or delete the line entirely. Defining a list with no values is pointless and not needed. Anything with Allow: [] or Deny: [] can be deleted altogether.
    It is fixed. Funny how one character can totally wreck everything after. *cough* Eleon should convert over to XML rather than using yaml. :p With yaml, it is very temperamental as if you were to mismatch a single space while indentation, all of your code thereafter will stop working.

    For those here that don't have a clue where the subscribed scenario is, it is located under Steam\steamapps\workshop\content\383120\1637536675\

    For the ones that copied over the Steam\steamapps\workshop\content\383120\1637536675 and renamed the folder to Conquer Scenario then placed it under their dedicated server as in Content\Scenarios\Conquer Scenario.. make sure you edit the sectors.yaml file there, delete your save game for the server OR modify the saved game sectors.yaml file itself to reflect the above changes. Restart server, poof it works :)

    On a closing note, please use the examples provided by Eleon. Preferably ones that didn't use EPG. As you know EPG is detected as a tojan lol. Sure ... it is a false positive but could be re-programmed to not be detected as such. Use Notepad++ or some other editor, that way you don't turn a 150 line yaml into a 450+ line (over 3 times the amount of lines as original). Those editors do nothing but make the yaml format ugly as anything, hard to read and really not necessary. Also they add in improper yaml code and have very little error checking. After all, YAML is a human-readable data serialization language. Not a language to pro-long and stretch one line into 4 making it hard to read.
     
    #10
    Last edited: Mar 24, 2019
    TK85 and Mia like this.
  11. ravien_ff

    ravien_ff Rear Admiral

    Joined:
    Oct 22, 2017
    Messages:
    6,291
    Likes Received:
    11,948
    I once spent 2 hours troubleshooting my solarsystemconfig.yaml file for my scenario before I realized I forgot to include a sun. :mad:
     
    #11
    TK85 and Mia like this.
  12. shortybsd

    shortybsd Ensign

    Joined:
    Jul 21, 2017
    Messages:
    14
    Likes Received:
    7
    Technically this should be a different topic but wanted to throw out there what EPD does to break havoc on yaml's. Here is a before and after with ZERO modification to the file. This is to show you how that editor makes a 118 line file into a 371+ line by doing nothing but simply clicking save.

    I grabbed Default Akua-Omicron\Sectors\Sectors.yaml, made a copy of it then opened it in EPG. Simply clicked save and it wrote a bunch of non-sense in yaml format and also added in an extra carriage return. Blank lines are ignored in yaml so there is no reason at all for this. I do take into consideration there are many different types of ways to beautify yaml. However, making it unreadable where it spans across multiple lines is just absurd. Also adding in an extra carriage return there is no reason at all for this either. In Yaml when making a list, if it doesn't contain a value then it doesn't even need to be defined. Example Allow: [] that is total non-sense.

    Stock:
    stock_sectors.png
    After loading it in, making no changes. Yaml butchering session:
    butchered_sectors.png

    I rest my case on using broken editors.
     
    #12
    Last edited: Mar 24, 2019
  13. Mia

    Mia Commander

    Joined:
    Jun 7, 2016
    Messages:
    164
    Likes Received:
    66
    Sorry, it doesn't work, I don't know why. I might have done something wrong.

    Skärmklipp.PNG
     
    #13
  14. Mia

    Mia Commander

    Joined:
    Jun 7, 2016
    Messages:
    164
    Likes Received:
    66
    I have the same problem with scenario "Hard Survival" in it, I have not changed much I have only used SSG.
    In Conquer Scenario I have used SSG and then EPG.
     
    #14
  15. shortybsd

    shortybsd Ensign

    Joined:
    Jul 21, 2017
    Messages:
    14
    Likes Received:
    7
    Make sure you edit the correct file, if you already have a save then look under
    Code:
    steamapps\common\Empyrion - Galactic Survival\Saves\Games\YOURSAVEHERE
    same applies to a dedicated server. Unless you got the dedicated server via SteamCMD look under your dedicated server folder\Save\Scenario_Name\Sectors\Sectors.yaml.

    The file you edited was only for generation, for a new world (new save). On existing make sure you look under saves and edit it there. If it is a dedicated server, make sure to restart the server after the changes are made under saves\Games\And_Your_Game_Save_Name\Sectors\Sectors.yaml.
     
    #15
    Last edited: Mar 24, 2019
    Mia likes this.
  16. Mia

    Mia Commander

    Joined:
    Jun 7, 2016
    Messages:
    164
    Likes Received:
    66
    I do not understand, Galactic Survival Saves Games are just games that I have already played.
    I don't know what SteamCMD is.
    I have no server, the only thing I found was:
    C: Program Files (x86) Steam Steamapps Common Empyrion - Galactic Survival
    folders:
    EmpyrionAdminHelper
    EmpyrionDedicated_Data
    Magick.NET-Q16 HDRI x64.Native.dll
    steam_appid
    steamclient64.dll
    tier0_s64.dll
    vstdlib_s64.dll
    and in EmpyrionDedicated_Data
    folders:
    Managed
    Mono
    plugins
    Resources
     
    #16
  17. shortybsd

    shortybsd Ensign

    Joined:
    Jul 21, 2017
    Messages:
    14
    Likes Received:
    7
    That is also where your local co-op saves to! Edit the Sectors.yaml under the correct save in order to fix your game to properly load. After I fixed it, I tested in both single player and dedicated server. Works great. the one in the screenshot from earlier was your standard Scenario that it grabs the data from when creating a new world. If PDA info was there it would always load info from there even after new game creation. Making a new world would have worked just fine. Are you opening up a saved game and loading from there or creating a new game?

    Do you not have a "Saves" folder under Empyrion - Galactic Survival ?
    empyrionfolder.png
     
    #17
    Last edited: Mar 24, 2019
    Mia likes this.
  18. Mia

    Mia Commander

    Joined:
    Jun 7, 2016
    Messages:
    164
    Likes Received:
    66
    Yes I have Saves" folder under Empyrion - Galactic Survival :)
     
    #18
  19. Mia

    Mia Commander

    Joined:
    Jun 7, 2016
    Messages:
    164
    Likes Received:
    66
    The changes I had made in :

    C: Program Files (x86) Steam steamapps common Empyrion - Galactic Survival Content Scenarios Conquer 3__1637536675 Sectors
    is also in the Saves Games single game Sectors.

    But in CO-OP it has not uploaded even the sector that is in my scenario. https://www.dropbox.com/s/mr8ico4wa0b9g0f/sectors.yaml?dl=0
    the sector only has 143 lines

    Very odd
     
    #19
    Last edited: Mar 24, 2019
  20. Pantera

    Pantera Administrator Staff Member

    • Developer
    • Moderator
    Joined:
    Aug 15, 2016
    Messages:
    3,249
    Likes Received:
    5,708
    Use this attached sectors.yaml it works fine for me now with editing line 589 & leaving in 'Deny' also

    Code:
      Allow: []
      Deny: []
    
    @shortybsd thanks!
     

    Attached Files:

    #20
    Mia and shortybsd like this.

Share This Page