Echo Units in Echo VR or Lone Echo can access this database anytime for additional information on troubleshooting, banning, reporting bugs, and more.


· Reports and Banning

· Network

· Finding Logs and dxdiag

· Performance

· Miscellaneous

· Echo VR High Quality Capture Mode

· Submitting a RAD Support Ticket and Reporting Bugs

Reports and Banning

Where should player reports be sent?

All player reports should be sent to report@echo.games and https://support.oculus.com/report-user/ .

Where should ban inquiries/appeals be sent?

Contact accountadmin@echo.games via email.

How do I know if I’ve been banned?

When logging in to Echo VR, you will receive a message letting you know your access has been restricted by Ready At Dawn. Contact our Echo Games Account Admin Team via email at accountadmin@echo.games to find out if your account has been banned, and for what reason.

Who processes reports, and when?

Our Account Admin Team tries to review and respond to emails/ban appeals during working hours Monday — Friday 8am to 5pm PST. However if a report is sent on Saturday for example, our Team will respond on Monday when they’re back in the office.

What happens when a player is reported?

An investigation is conducted by our Team to determine if a player violated the Code of Conduct for Echo Games and/or Oculus. If we find evidence of a violation, a ban will be automatically placed on the headset of the player. Bans are based on violations of the Code of Conduct, how many times a violation has occurred, the severity of the violation, and if the Reporter provided evidence of the violation.

Where can I find the Code of Conduct?

The Code of Conduct can be found on a poster in-game in the Brawler’s Den of the Echo VR Lobby, or online here: https://support.oculus.com/1694069410806625/.

How long is a player banned for?

The only way to find out how long you’ve been banned for is by contacting our Account Admin Team.

Players are banned based on the severity of the violation, and how many times they’ve broken the Code of Conduct. Not all bans are permanent. Temporary 24-hour bans for example often serve as warnings to players who have committed minor violations. Longer bans are given for moderate violations, with severe violations resulting in permanent bans.

Bans begin after our team completes their investigation. Once you contact our team, they will let you know how long your ban will last, and what your violations were.

How do I find out why I’ve been banned?

Send an email with your display name and when you noticed the ban to accountadmin@echo.games . Our Team will then respond to your email (during Monday — Friday 8am to 5pm PDT) explaining why your account was banned, what the violation was, and how long your account will be banned. If you don’t contact our Account Admin Team, you won’t know why you were banned or for how long.

Who will know why I’m banned?

The Account Admin Team, and you. Unless you publicly share this information, our Team keeps the reason for bans confidential to protect your privacy once you come back to the Echo VR community.

I share a headset, can I still be banned?

Yes. You are responsible for the actions of all accounts associated with your headset. If a friend, roommate, sibling, etc . continuously violate the Code of Conduct, or commit a severe violation, a permanent ban will be issued.

How do I appeal a ban?

To appeal a ban, send an email to our Team at accountadmin@echo.games. Let them know your display name and that you are wanting to appeal your ban. Our Team will review your file, and then contact you to let you know if your appeal was successful or not. If you are permanently banned and your appeal is denied, our team will contact you if there are changes to the status of your account/ban.

Finding Logs and DxDiag


The default location .log files are within the logs folder, located here: C:\Program Files\Oculus\Software\Software\ready-at-dawn-echo-arena\_local

.logs can also be found in the “Program Files (x86)” location, subdirectory: C:\Program Files (x86)\Oculus\Software\Software\ready-at-dawn-echo-arena\_local

If you installed your game to another hard drive, then that part of the directory may be different.

If you’re having trouble finding your logs:

· Open up your File Explorer

· Select your Local Disk

· Find and click on Program Files

· Find and click Oculus

· Find and click Software

· Find and click Software

· Find and click ready-at-dawn-echo-arena

· Find and click _local -Find and click r14logs

· Select the time log that your bug/problem happened

  1. Copy and paste it to your computer.
  2. Attach the file to your Support Form or to your message in the Support Channel of the community Echo Games Discord.


To create a copy of your DxDiag:

  1. Press the Windows key + R
  2. Type ‘dxdiag’ and press Ok or hit the Enter key
  3. Click Save All Information
  4. Under ‘Save as Type’ make sure Text File (*.txt) is selected, and save the file
  5. Click the Exit button
  6. Attach your saved DxDiag file to your Support Form. If using the Support Channel of the community Echo Games Discord, please private message your dxdiag after a Developer contacts you (RAD_Wing, RAD_Wyvern, RAD_DavidN, etc).

Submitting a RAD Support Ticket and Reporting Bugs

There are two ways to report Echo VR bugs and submit a Support Ticket for technical assistance:

1. Fill out the Support Form here with as much relevant information as possible. Please attach any videos, images, logs, or dxdiag you have as well.

2. If you are a member of the community Echo Games Discord, you can report your problem in either the Lone Echo or Echo VR support channels. Please attach any videos, images, or logs to your message there as well. Dxdiags can be shared with our Developers via private message after they’ve contacted you in the Support Channel.


Help! I’m having difficulty connecting to a game or staying connected.

· If you’re on Wi-Fi trying switching to a wired connection.

· If you’re using a powerline adapter try using a normal Ethernet connection

· Make sure nothing else is using your internet bandwidth. (Game downloads, Video Streaming, other Users on your LAN)

· Try disabling any firewalls/Antivirus that may be running

· Try forwarding your ports https://portforward.com/ (listed below)

· Try using an alternate DNS, like Google or Cloudflare.


Login (TCP):


Matchmaking (TCP):


General (UDP):






PC recommended specs:

· Intel i7–6000 equivalent or greater

· Nvidia GTX 980 equivalent or greater

·Latest graphics drivers are installed

· You are not running any other programs that can be competing for resources on your computer: Streaming apps, another game, multiple chrome tabs open

· Your PC is not thermal throttling itself (GPU or CPU)

· Enable the Auto Res setting in the graphic settings

· How to determine if you’re dropping frames (F9)

· How to determine if you’re controller is not being properly tracked (F10)

· Oculus Rift recommended/minimum specs can be found here

F9 Debug Overlay

While in-game Press F9 to bring up a performance overlay on your monitor. From here you will be able to view FPS, Frame Times, Dropped Frames, Average Ping, and Packet loss. This data can be used to find any bottlenecks you may be experiencing. If you need help assessing this information, you can always send our Devs a screenshot or video with this overlay on via the Support Form, or in the Support Channel of the community Echo Games Discord.

F10 Debug Overlay

While in-game press F10 to bring up the track debug overlay. This will help you determine if there are dead zones in you tracking. If you are experiencing erratic tracking issues, this may be due to USB bandwidth. Try removing any unused USB devices and alternatively moving a sensor or 2 to a USB 2.0 port if everything is plugged into USB 3.0. https://support.oculus.com/302306743483970/


Game/Update won’t download

If you have issues downloading Echo VR, or downloading a game update, there are some quick troubleshooting steps to try:

· Disable your antivirus.

· Restart your PC

· Try deleting the game from your library and then redownloading it.

· If none of the above steps work, please contact Oculus Support.

Logs are not in directory

If game logs are not being written to our specified folder, you will be able to write them to manually, by launching Echo VR or Lone Echo via command line with the follow argument “> stdout.txt 2> stderr.txt”. Two text files will be created in Win7 folder. If you need instructions doing this please see below.

1. In Windows Explorer navigate to the folder than contains the executable. (Echo VR — C:\Program Files\Oculus\Software\Software\ready-at-dawn-echo-arena\bin\win7) or (Lone Echo — C:\Program Files\Oculus\Software\Software\ready-at-dawn-lone-echo\bin\win7)

2. Type ‘cmd’ and press enter

3. Type “LoneEcho.exe > stdout.txt 2> stderr.txt” or “EchoVR.exe > stdout.txt 2> stderr.txt”

4. Send us stdout.txt and stderr.txt once you have reproduced the issue

Q: What’s the difference between a “key save” and an “autosave”?

A: A “key save” is one we do at sort of a major beat of the game progression, while “autosaves” are done more frequently, e.g. at the start of each tutorial, and when re-entering areas

Q: My audio suddenly is reversed when playing Echo Arena (what’s on my left is coming through my right headphone and vice versa). What can I do about this?

A: Oculus Customer Support is actively tracking this issue and is looking to gather more info. Please submit a support ticket to let them know about this issue (make sure to include any troubleshooting steps you’ve completed as well as if you have any extra hardware that doesn’t come with the Rift+Touch box such as USB extension cables).

Oculus support ticket submission link: https://tickets.oculus.com/hc/en-us/requests/new

Troubleshooting steps you can try in the meantime include:

· Re-syncing your headset through the Oculus app.

· Plugging into a different USB slot.

· If using a USB extension cable, try removing it to see if that solves the problem or if you have an extra, plug it in to see if it changes anything.

Q: How do the auto res and the SS settings work together? And how does it adjust over time?

A: The resolution setting in the menu specifies your maximum possible res, as a multiple of the headset’s base res (2688x1600 for the Rift). So if you set res to 1.5, your max res will be 4032x2400. If you have auto-res disabled, you’ll always run at your max res no matter what. If you enable auto-res, the engine may drop the res down to 70% of your current max res if the GPU is having trouble hitting 90fps. So in our example of using a res of 1.5, your res can vary between 2822x1680 and 4032x2400.

That “70%” is also configurable through the settings file, even though it’s not in the settings menu. It’s called “adaptiveresminscale”. So if you’re using supersampling, you can possibly set that lower (maybe 0.5) and that will let the engine drop the res lower to try to avoid dropped frames.

Q: How does the target frame rate setting tie into all this?

A: The target frame rate is basically the frame rate that auto-res will try to stay at (or higher). If it detects that the GPU is running lower than target it will start to lower the res until the GPU is running at target frame rate again. So setting the target frame rate higher will cause auto-res to kick in more often, and setting it lower will it less likely to adjust things. The default is 90, since the Rift runs at 90Hz. You could potentially set it to 45 if you wanted to always run with ASW enabled, but obviously you don’t want to do that for EA.

The “headroom” basically gives us a little bit of wiggle room on the target frame rate. So for instance with default settings the target frame rate is 90Hz, which means we’re allowing ourselves 11.1 milliseconds of GPU time per frame. The default headroom is 0.05 (5%), which means the actual target frame time will be 11.1 * 0.95, which is about 10.5ms. This leaves about 0.6ms for the Oculus compositor, which generally takes about that long to do its thing. So setting the headroom higher is similar to setting the target frame rate higher, in that it will cause auto-res to kick in more frequently. This might be a good idea if you use streaming apps or other things that are sharing the GPU with the game, since it will give those apps a bit of breathing room.

Echo VR High Quality Capture Mode

This mode renders a second native 16:9 image to your PC monitor with high quality render settings, while maintaining a ‘normal’ rendered view to the headset. This is especially useful for improved video recording quality with a custom camera field of view more favorable for 2D viewing.


This feature requires a higher end graphics card, as it is effectively rendering the game twice! If your GPU cannot maintain frame rate please try lowering the graphics quality and running the game normally before reporting performance problems. This capture mode is NOT designed to conform to recommended hardware specifications for the game, and is provided for use on an as-is basis.


Open a command prompt and navigate to [Program File Location]\Oculus\Software\Software\ready-at-dawn-echo-arena\bin\

In the command prompt type echovr.exe -capturevp2 and hit enter to launch the game in this special rendering mode.

Adjusting Capture Settings:

You can now edit config_mp.json, located in [OS]\Users\[USERNAME]\AppData\Local\rad\loneecho\ to adjust settings such as a graphics quality and camera FOV. The graphics settings will be applied to both the headset view, as well as the monitor output. The ‘graphics_capture’ block of properties will only be used when you run with the -capturevp2 command line, so it will leave your normal graphics settings intact, when running the game through directly through the Oculus application.

Aside from standard graphics performance settings, you can also alter the PC Field of View by adjusting the capturefov value (measured in horizontal degrees), and the brightness of the capture by adjusting the gamma value (ranges from -1 to 1). Gamma and fov can ONLY be adjusted by changing this JSON file, however normal graphics settings can also be changed through the in-game options menu.

Disabling Player Names and HUD Elements:

Pressing F8 while in game will toggle player names and helmet HUD elements from rendering


If you do not see the ‘graphics_capture’ settings in the JSON file, run the game and adjust a setting in the options menu (any setting should do it). This should be a one-time step to write out a settings file with the new options.

Submitting a RAD Support Ticket and Reporting Bugs

There are two ways to report Echo VR bugs and submit a Support Ticket for technical assistance:

1. Fill out the Support Form here with as much relevant information as possible. Please attach any videos, images, logs, or dxdiag you have as well.

2. If you are a member of the community Echo Games Discord, you can report your problem in either the Lone Echo or Echo VR support channels. Please attach any videos, images, logs, or dxdiag to your message there as well.

This FAQ will be updated as necessary. Last update: 6/6/2019