Needs attention READ BEFORE REPORTING - Bug Report Template, Requirements, Known issues & Troubleshooting

Discussion in 'Bugs' started by Hummel-o-War, Jan 15, 2019.

Thread Status:
Not open for further replies.
  1. Hummel-o-War

    Hummel-o-War Administrator
    Staff Member Community Manager

    • Developer
    Joined:
    Jun 15, 2015
    Messages:
    10,808
    Likes Received:
    17,072
    HOW TO REPORT A BUG?

    1. Read through the READ FIRST Paragraph if you are unsure which information are required: https://empyriononline.com/threads/...-requirements-known-issues.47118/#post-290340

    2. Check the Bug Forum if your issues is ALREADY added!!!

    https://empyriononline.com/forums/bugs.34/

    2.a Also check the known issues list below:
    https://empyriononline.com/threads/...-requirements-known-issues.47118/#post-290341

    2.B Check here if you have any problems getting the game to launch, crahses & general trouble shooting tips
    https://empyriononline.com/threads/...-requirements-known-issues.47082/#post-296904

    2.C Check here for info on how to record video with OBS studio

    https://empyriononline.com/threads/...own-issues-troubleshooting.47082/#post-390329

    3. IF yes, please contribute your findings to an existing thread by USING THE REPORTING TEMPLATE from below.

    4. IF your issue is not yet listed, please create a
    NEW THREAD in this forum by USING THE REPORTING TEMPLATE from below.

    IMPORTANT: Please only report ONE BUG per THREAD. Do NOT add SEVERAL bugs per thread as this will make your report hard to track! Thanks!


    5. When creating a NEW THREAD you need to select the Prefix "NEW" from the dropdown next to the headline

    6. GIVE A DESCRIPTIVE AND ON-THE-SPOT headline (thread title) so your issue is regognized by QA and by OTHER PLAYERS that might run into the same issue.

    Please note that our moderators will move and merge threads that do not follow these rules

    =====================================
    =====================================
    =====================================


    REPORT TEMPLATE

    Post your bugs here using the following template:

    Mode: (Creative, Survival, Freedom mode)
    Mode: (Singleplayer, Dedicated Server, Peer2Peer Coop)

    SERVER NAME: (If the issue happened on a public server, please add the name here)
    SEED-ID: (Please always add the SEED-ID for SingleplayerSurvival games; Open the console. The Seed is noted somewhere to the "playfield loaded" dialogue)

    If applicable:
    MODIFIED PLAYFIELDS: Yes/No/DontKnow (<- YES if new planets or non-default playfields are used. Use DontKnow if you are not aware if anything has been changed)

    Reproducibility: (Always, Sometimes, Unable)
    Severity: (Trivial, Minor, Major, Crash)

    Type: (Global / O2Rooms / Temperature,Radiation / Player Armor,Boosters / Repair / Teleport,Portals / Instances / Triggers,Sensors / AIVessels / Gamestart / ... )

    Summary: (1-liner = can be the same as the thread headline)

    Description: (short description: 1-2 sentences)

    Steps to Reproduce: (steps to reproduce the issue. This is ESSENTIAL for a bugfix!)

    Screenshots, Crash Logs, any other Relevant Information or Download links: ( Note: for more complex reproduction usecases that require quite some "setup", please create a savegame and upload it to a service & also attach a copy of your client log (& crashes log if a crash occurred):

    How to attach a save game to a report:
    Go to:
    For SP or Co-op:
    SteamLibrary\steamapps\Common\Empyrion - Galactic Survival\Saves\Games

    For MP:
    SteamLibrary\steamapps\Common\Empyrion - Dedicated Server\Saves\Games
    1. Right click on the save folder & place your mouse cursor over 'Send to' create a compressed copy of it (or use winzip or 7zip)
    2. Drag & drop a copy in your reply box or use the upload a file option on the forum.
    3. If the folder is too large use a file hosting site like mediafire, dropbox or google drive & add a share link to it

    How to attach logs to a report:
    1. Client log location:
      Right click on Empyrion in your steam library > Properties > Local files > Browse local files > Logs - then make a copy of the folder which is named by the build number currently released & compress it.

    2. Crashes folder location:
      C:\Users\<YourUserName>\AppData\LocalLow\Eleon Game Studios\Empyrion - Galactic Survival - & also make a copy of that & compress it.

    3. Create a dxdiag file & attach it with the previous files
    In Windows 7:
    • Click on the "Start" Button.
    • In the Search Box type dxdiag and press <Enter>. The DirectX Diagnostic Tool pop-up window should appear.
    • Click on “Save all Information.”
    • Save the information to your Desktop, keep the file name as is.
    In Windows 8, Windows 10:
    • Press the [Windows]+[R] keys on your keyboard to bring up the Run command.
    • In the "Run" command box, type in dxdiag and press <Enter>. The DirectX Diagnostic Tool pop-up window should appear.
    • Click on "Save all Information." Save the information to your Desktop, keep the file name as is.
    Now all of these have been copied & compressed attach them to your report by dragging them into the reply box or using the upload a file option.

    Thanks in advance for saving us time to address your issue! :)

    =====================================


    A blank template can be found here click on the spoiler to expand it:

    Mode:
    Mode:

    SERVER NAME:
    SEED-ID:


    If applicable:
    MODIFIED PLAYFIELDS:

    Reproducibility:
    Severity:

    Type:

    Summary:


    Description:

    Steps to Reproduce:

    Screenshots, Crash Logs, any other Relevant Information or Download links:
     
    #1
    Ephoie, TK85 and Tyrax Lightning like this.
  2. Hummel-o-War

    Hummel-o-War Administrator
    Staff Member Community Manager

    • Developer
    Joined:
    Jun 15, 2015
    Messages:
    10,808
    Likes Received:
    17,072
    READ FIRST: For a proper testing procedure and bug reporting, we recommend the following preparations and workflows:
    1. Go to your steam library and VERIFY your game files!
      Steam > Library > Right-click Empyrion in the list > Properties > Local Files > Verify Locale Data

    2. Make sure you are NOT using a custom config!
      There are currently multiple files that can be "modded".
      These are all found in: Empyrion - Galactic Survival\Content\Configuration

      When running into an issue, it would be HIGHLY RECOMMENDED to check if you are using a customized version of any file in the configuration folder.


      If you are using a custom file:
      Please move the customzied file/s out of the folder (Rename, remove, move)
      Verify the game files via STEAM (this will restore the default files if you do not have them ready)
      :
      1. Right click on Empyrion in your steam library & select properties
      2. Click on the local files tab & choose the 'Verify integrity of local game files' option
      3. Then recheck for the error with only stock files in the Configuration folder.
    3. Avoid resuming any pre-Release Candidate savegame!
      There is a chance that changes we made do not translate to older savegames. Especially for bugs concerning terrain, loot and other playfield configs.
      Best practice: if you run into an issue with a savegame that was started BEFORE a RC has been released, please re-test the issue in a fresh new RC savegame again!


    4. Additional Routine: Delete the GAME CACHE when trying to reproduce a bug!
      The game cache saves some presets and may be source of a false positive reports or even be part of the problem. To make sure we have all the infos, please check the following folder when trying to reproduce a but and make a note in your report if the bug still happens AFTER clearing the cache: ..\Empyrion - Galactic Survival\Saves\Cache
    ----

    'Continue or Quit' (CoQ) Error

    When you get a so called 'CoQ' (Continue or Quit) error in SINGLEPLAYER, please do the following:
    1. Note the build number in the top right (the last 4 digits) for example B2785 then exit the game (click QUIT or ALT+F4)
    2. Right click on Empyrion in your steam library > Properties > Local files > Browse local files > Logs
    3. Look for the folder name that matches the build number from step 1 or look for the folder named by the highest number and open it
    4. Right click on the client log from when this happened & place your mouse cursor over 'Send to' create a compressed copy of it
    5. Open your Email, attach the compressed copy of the log & write what happened BEFORE the CoQ and send to:

    [email protected]

    The QA team will pick up your issue and decode or ask back more info.

    2) IF YOU RAN A COOP SERVER need to:
    - send in the Client.logs for all players that were affected
    - send in the COOP server and COOP-client logs

    The COOP Client logs are in the SAME folder on the PC which started the session.

    Look for
    a) logs that start with 'Client_AsPf_'
    b) log that starts with 'Dedicated_'

    Send in both COOP Client and Server logs to the same Email address

    3) IF you are running a DEDICATED SERVER,
    go the the /LOGS folder, zip the whole thing (in case you do not know what are the latest files) + ADD an info on which playfield and WHEN (time stamp) the issue happened...and send it to the same Email address as well.

    -----

    GLOBAL ADVICE ON REPORTING!!

    1. If you haven an issue with a Base or Vessel with temperature, radiation, colliders, can-not-dock, o2 or plants not growing or anything that happens without anything else in the game world is directly affected, please ADD THE BLUEPRINT or the SAVEGAME and add an info if SP or MP! If you want to add your savegame, please upload your savegame to a cloud host (like dropbox, google,..) and add a LINK to your report

    2. If you having issues with something missing from your planet, spawned in the wrong place or anything that keeps being broken after resuming a savegame PLEASE UPLOAD the savegame to a cloud host (like dropbox, google etc) and add a LINK in your bug report

    3. If you CRASHED with a message "Continue or Quit" on a SP or MP game, PLEASE FOLLOW 'Continue or Quit' instructions as written above

    4. If you CRASHED back to desktop (empyion.exe does not work anymore) do the same as in (3.).

    5. If you game FREEZES (locked up), please make a note that this is a FREEZE (not a "Crash"). Add the same files as in 3. and maybe add a dxdiag as well.

    THANKS A LOT FOR YOUR SUPPORT! :)
     
    #2
    TK85, Ephoie and Tyrax Lightning like this.
  3. Hummel-o-War

    Hummel-o-War Administrator
    Staff Member Community Manager

    • Developer
    Joined:
    Jun 15, 2015
    Messages:
    10,808
    Likes Received:
    17,072
    KNOWN ISSUES EXP

    A12:

    https://empyriononline.com/forums/known-issues.93/

    https://empyriononline.com/forums/tracking-filed.91/


    Waypoints:

    • [7349] The "Remove" button in the "Add a map marker" window isn't working
    • [7346] Shared markers when copied to another players private list no longer persist after server restart
    • [7296] Waypoint of a vessel remains after playfield change
    • [7292] Waypoints placed on a planet seen from a close by moon "detach" from where they should be
    General:
    • [7254] Fixed scenarios cannot change starter planet size
    • [7253] Troop transports triggered by killing a Drone guarding POI's or damaging the POI doesn't deploy troops
    • [7173] LCD Projector & screen background color will not turn off when the screen is turned off
    • [7245] Sort list for the player inventory when in a portable constructor doesn't update
    • [7156] Projectile Turrets hit themselves when being fired
    • [SP] Devices not being turned of when teleporting away to another playfield
    • Space defense AI vessels when spawned in can be seen to not attack player vessels
    • Local Co-op & MP (standalone server) creative mode not working
    • Creative mode Orbit start & traveling to orbit from a planet triggers a CoQ <- Click on continue to get passed it the scenario isn't updated to the new system just yet.
    • SSG doesn't work as of A12

    ====

    Previous issues:

    A11:

    General:
    • [7269] Vessel thruster sounds from other players cannot be heard
    • [7178] Avatar animation glitch after switching from 1PV to 3PV camera
    • [7177] Shields can continue to recharge whilst being damaged when the end of a turrets barrel is being fired on
    • [7176] Different amounts of damage dealt to shields depending on where explosive blocks are placed on the structure
    • CoQ spam when T4 CPU blocks are downgraded to T3
    • [7065] [MP/Co-op] No sound from doors or ramps which are setup to be controlled by motion sensors
    • [7028] Player suit light remains after removing armour
    • [7012] Pipes L does not mirror correct anymore
    • [7007] Block shape 'Notched C low' when mirrored doesn't get orientated correctly
    • [6970] Using drill (flatten) on ground below an auto miner will completely erase the miner and all contents.
    • [6926] [MP] Terrain engine CoQ after leaving a planet
    • [6919] Solar battery amount can be carried over to other save games
    • [6540] Windows can be seen clearly through fog
    • [6287] Signal logic can force the covered thrusters to turn on
    • [6434] MainDroneBase Space POIs don't use DSL
    • [4384] Camera view becomes glitched when players Personal drone is destroyed
    • [6361] Sometimes when drilling rocks/ore rocks in water nothing is dropped from them for the player to pick up
    • [6450] Respawning on a floating POI will always spawn you on top of where you died
    • [5923] Weapon color changes after entering & exiting a cockpit
    • [5985] After rotating a base to spawn, Home/End causes base to move side to side
    • [5295] CV mining drills 'Failed setting triangles' messages
    • [5952] Mirroring Lights does not copy over the settings of lights
    • [6258] Compass heading showing incorrect when exiting & reentering a cockpit until the vessel is moved again
    • [6271] HV thrusters cannot be entirely turned on or off via switches or signals
    • [5835] RepairStation can always be used when the power button is OFF
    • [4930] Autominers do not deplete Voxel Deposits
    • [1887] Large Blueprints (max size) are broken in 2 parts or do not spawn completely.
    • [3913] AI vessel RespawnDelay Timer not working
    • [2838] Symbol + and double+ are off about 1px in some directions
    • [3503] HV/SV still produce "Smoke" when grounded and all thrusters and hover engines are off
    • [4748] Turret zoom level applied to 3rd person vessel view after exiting turret.
    • [3957] Symbols orientation is not mirrored correctly.
    • [4872] Player falling through the world when getting of a motorbike on uneven/mined terrain
    • [4789] Waypoints are not finding the quickest route through polar region
    • [5434] Docked vessels that have the waypoint option enabled take the name of the vessel they are docked to
    • [6064] Invisible Sun in space when viewed through any transparent object
    • [6165] Windowed mode 'always shown on top'
    • [6141] Cannot exit ATM with F
    • [3814] When you have the 'Show on HUD' option enabled on a device after removing that device the marker isn't removed also
    • [3498] Possible to fly through AI freighters, Carriers etc with player vessels (MP also has a issue with drones spawning & teleporting around player vessels)
    • [4342] Environmental effects affecting avatar when in 3rd person or using the personal drone.
    • [3695] Weather effects are visible when moving up & down in elevator blocks or jumping inside CV's & BA's & moving downward underwater.
    • [5835] RepairStation can always be used when the power button is OFF
    • [6831] [MP] 3PV camera distance is reset when rejoining a server
    ----
    Vessel Controller:
    • [6837] Structure hull blocks micro stutter when moving
    • Holding SHIFT-W does not turn off boost even if boost is empty
    • Issue with 'spiked' shapes on vessels & drag algorithm changing the max speed
    ----
    Logistics:
    • Trader don't use the connected container or toolbar
    • [7017] Logistics 'connected' overlay stays on screen when changing from a connected container to the repair station
    • [5562] F4 structure convenience caching gets stuck when several structures are close by
    • [5963] A large item or stack when swapped with a smaller one will leave the inventory overfull
    • [5971] Container-Slots get increased when re-accessing dead corpses
    • [6061] [MP] Container controller volume info is not updated after removing & placing a new one until another CE is added.
    • [6135] Second pane for logistics dialog persists an entry from previous source when you pick a new one
    • [6267] Items on the virtual toolbar do not contribute to the mass of the connected container.
    ----
    UI:
    • [6570] 'Drill mode:' UI element disappears from HUD when connected to a container after opening & closing of CP
    • [6291] With the weight & mass check disabled the pentaxid tank when 'overfilled' shows a higher percentage than it should
    • [6414] Constructor item list - invalid scroll position
    ----
    Terrain:
    • [7010] Terrain placeables can become unplaceable on terrain around structures
    • [6463] When removing terrain from under a BA that has been placed on raised terrain SI doesn't collapse
    • [3696] When a base has terrain inside of it standing on the terrain results in the outside weather damaging the avatar.
    ----
    Game pad/Controller issues:
    • [7126] [Game pad] D-Pad Down + A doesn't take all
    • [7275] After entering a lock code some actions for the controller stop working
    ----
    Local Co-op:

    [7227] We are aware of an issue for Co-op mode if the host sets a password for the server anyone joining can be met with a CoQ/InternalError.
    For the time being with this issue please remove the password from the dedicated.yaml in the save game folder:

    1) Make sure the co-op server is not running & open the dedicated.yaml in the save game folder

    2) Look for Srv_Password: & remove anything after Srv_Password: like this for example
    ServerConfig:
    Srv_Name: Local co-op
    Srv_Password:

    3) Save the file then start up the co-op game again. If you are prompted from this point for a password leave the dialogue box blank & click ok.

    Passwords for co-op aren't completely necessary the only players who can see or join your Co-op game are on your steam friends list.

    ----

    Should be fixed now, but please observe:
    • Currently not possible to save "Rotation Sensitivity" adjustments sliders in a blueprint


    More A12 fixes can be seen in here "Fixed in NEXT update": https://empyriononline.com/forums/tracking-filed.91/
    Or "Fixed" https://empyriononline.com/forums/fixed.90/
     
    #3
    TK85, Xzanron, Ephoie and 4 others like this.
Thread Status:
Not open for further replies.

Share This Page