Not a bug Custom scenario problems with warping on dedicated servers [07374]

Discussion in 'Archive (Read Only)' started by ravien_ff, Jun 13, 2020.

  1. ravien_ff

    ravien_ff Rear Admiral

    Joined:
    Oct 22, 2017
    Messages:
    8,389
    Likes Received:
    15,716
    @Taelyn™ @Pantera I did some testing and hopefully the below steps combined with other people's reports will help you reproduce the issues. I believe this is what has been talked about in Discord lately.

    Mode: Survival
    Mode: Dedicated Server

    SERVER NAME: Privately hosted server on a dedicated PC.
    SEED-ID: 366678537

    If applicable:
    MODIFIED PLAYFIELDS: Yes

    Reproducibility: Always
    Severity: Major (game breaking)

    Type: Warping/teleporting

    Summary: In a custom scenario, warping is sometimes broken.

    Description:
    All tests done using the A12 test version of Project Eden installed on a private dedicated server PC using a new save game as of tonight and using EAH.
    Workshop link to scenario used: https://steamcommunity.com/sharedfiles/filedetails/?id=1849584208

    This scenario uses a combination of fixed sectors and a custom galaxy config.
    It also uses a combination of space_dynamic.yaml and playfield.yaml files for some of the fixed space playfields.

    Warps to fixed sectors will often fail, using up Pentaxid but not moving the ship.
    Using the sectors command to teleport to a fixed sector will often do nothing at all.
    Using the "sd debug" command to remotely view fixed sectors solar systems will often cause a CoQ error when you select any planet inside the viewed solar system.
    Everything works fine in singleplayer.



    Steps to Reproduce:
    Here are the exact steps I took to reproduce this issue, though I don't know which steps are actually required or how consistently the problems will appear.

    Start a new dedicated server using the current experimental branch and the Project Eden A12 scenario linked above.
    Use seed: 366678537
    Select Tallodar as your starting planet (Temperate2).
    Activate god mode.

    Try to use the following console commands to teleport to some of the fixed sectors in the scenario:
    sector 'Object 82'
    sector 'Core 1'
    sector 'Core 1 System'
    sector 'Core 8'

    Those commands failed.

    Console command: sector 'Rogue System' did teleport me to the Rogue System.
    From there I was able to spawn a CV and use it to warp okay to Object 82.
    I then used the sector command to teleport to a nearby randomly generated star.
    Then I was able to use command sector 'Object 82' to teleport back to that sector.

    I then used the sector command to teleport to a star that was near the Core 8 System (Iblotryu)
    20200612195700_1.jpg


    I tried to initiate a warp using a CV but it did nothing. The sector 'Core 8' or sector 'Core 8 System' commands did not work either.

    I then activated the sd debug command and was able to open up the Core 8 system by double clicking on it but when I selected the Core 8 planet itself I got a CoQ error.
    Then using sd debug to view the planet of the Rogue System would give a CoQ error too, as well as the planets of the Delta system.
    20200612200257_1.jpg 20200612200308_1.jpg 20200612200311_1.jpg


    So to summarize:
    Start a new dedicated server using that seed and scenario.
    Attempt to warp to or teleport to any of the following fixed stars or sectors:

    Core 1
    Core 1 System
    Core 8
    Core 8 System
    Object 82
    Object 1
    Object 42

    The space playfields in these sectors use a fixed playfield.yaml, NOT a space_dynamic.yaml file.
    I am unsure if this is a contributing cause.

    I will PM logs to Pantera.



    Screenshots, Crash Logs, any other Relevant Information or Download links:
     
    #1
    krazzykid2006, Pach and Jaxyl like this.
  2. ravien_ff

    ravien_ff Rear Admiral

    Joined:
    Oct 22, 2017
    Messages:
    8,389
    Likes Received:
    15,716
    Also of note:
    Warping or teleporting to randomly generated star systems appeared fine in the testing I did.
     
    #2
    krazzykid2006 and Jaxyl like this.
  3. Taelyn

    Taelyn Administrator
    Staff Member Community Representative

    • Developer
    • Administrator
    • Moderator
    Joined:
    May 29, 2016
    Messages:
    4,881
    Likes Received:
    6,003
    Ty! Now iam able to reproduce it
     
    #3
    ravien_ff, Pach and krazzykid2006 like this.
  4. Taelyn

    Taelyn Administrator
    Staff Member Community Representative

    • Developer
    • Administrator
    • Moderator
    Joined:
    May 29, 2016
    Messages:
    4,881
    Likes Received:
    6,003
    Hey, So we did some checking and it has to do with the fact the Warp Target playfields have the wrong names.

    Correct those and everything works fine!

    Its a MUST that the WarpTargets are named AFTER the Star name

    We made an example with your 'Core 1 System'

    First Screenshot is what you did, Second is how it SHOULD be

    image_2020_06_13T16_56_27_649Z.png
    image_2020_06_13T16_57_22_458Z.png
     
    #4
    Germanicus, ravien_ff and Pach like this.
  5. ravien_ff

    ravien_ff Rear Admiral

    Joined:
    Oct 22, 2017
    Messages:
    8,389
    Likes Received:
    15,716
    Oh thank you! No wonder I did not catch that if it worked fine single player but not multiplayer. :D
     
    #5
    Taelyn, Pach and Germanicus like this.

Share This Page