Known Issues as of 22-8-2017 (Patch 1.03 Community Test Branch)

  • We are currently investigating a freeze which requires you to restart the game when loading into maps using Windowed and Borderless Windowed display modes.
  • When equipping the M1917 the weapon is already cocked; the cocking animation plays but the weapon does not appear to change
  • On Territory mode Song Be after capturing an objective NLF players will sometimes get a notification that they are in enemy territory.
  • Helicopter pilots’ names sometimes will not display on the spawn list. The helicopter will still be available as a valid spawn locations, however.
  • Names using Cyrillic characters will have those characters replaced with # symbols




Known Issues Fixed Since 1.02

  • Squad leaders in roles without pistols who are made SL automatically when joining a match do not receive a pistol as intended on deployment. This can be avoided by manually selecting the squad menu on the squad deployment screen.They will, however, still receive binoculars.
  • We are currently investigating a community-reported issue where sometimes equipping a claymore prevents switching to other weapons until a claymore is planted. If you have any reliable steps for reproduction of this issue, please report them using the steps detailed below.
  • There are issues when planting tripwire traps - sometimes the marker will appear white, and the spot will appear valid but the trap may fail to plant. This does not occur in all instances, and if you do encounter this issue, please report it using the steps underneath this list.




There are bugs that we do need your assistance in finding proper reproduction steps for. If you experience the below bugs, please be as detailed as possible with your report.

HOW TO ACCURATELY REPORT A GAME CRASH OR BUG

Crashes

  • All crash logs and dump files will be generated to the following directory:




C:\Users\”your user name”\Documents\My Games\Rising Storm 2 Beta\ROGame\Logs [/color] .Please send in the latest .log file and the latest .dmp file.

  • Please report what you were doing right before the crash occurred, as detailed as possible.




Bugs

When reporting a bug, it is imperative to provide the following in your report.

Graphical Issues

  • Please submit a DXDIAG file. You can locate this file by following the below instructions:
  • To start the diagnostic, click on Start \ Run and type in “dxdiag” and click OK. If this is the first time you're running this diagnostic, Windows will ask you for permission to check for WHQL Digital Signatures. Click Yes to this.




http://media.tripwirecdn.com/forum/dx1.jpg


You will then be presented with the DirectX Diagnostic Tool. The default tab will be System, where it lists the general information about your system and most importantly what version of DirectX you currently have installed.


At the bottom of this window you will see ‘Save All Information’. Click this button and save the file to your desktop. This is the file you will want to send in with your report.

http://media.tripwirecdn.com/forum/dx2.jpg

  • Please provide a screenshot of the graphical issue you are experiencing.
  • Please provide a screenshot (or written details) of the graphical settings you have chosen, from the options menu
  • Many graphical issues can be a symptom of outdated video card drivers. Please make sure you have the latest video card drivers installed before reporting a graphical issue.




Performance Issues

  • Please submit a DXDIAG[/color] file. Please see the above instructions on how to send in your DXDIAG file.
  • Please provide a screenshot (or written details) of the graphical settings you have chosen, from the options menu[/color]
  • Please detail if you are experiencing framerate issues, hitching issues, latency issues etc. Be as detailed as possible in your report




Sound Issues

  • Please submit a DXDIAG file. Please see the above instructions on how to send in your DXDIAG file.
  • If the sound issue is weapon related, please list what weapon you were using and specifics about the bug
  • If the sound issue is environment related, please list the location where the sound issue occurred and the nature of the issue.
  • If the sound issue is ‘character foley’ related (cloth, footsteps, gear rattle etc.), please list the specific issue and what was occurring

Many sound issues can be a symptom of outdated sound card drivers. Please make sure you have the latest sound card drivers installed before reporting a sound issue. Visit your soundcard or motherboard manufacturer for the latest sound card drivers.


UI (User Interface) Issues

  • Please provide a screenshot (or written details) of the UI issue you are reporting.
  • Please also notate what resolution you are running the game in. You will find this setting in the game options.