FAQ
Echo Units in Echo VR or Lone Echo can access this database anytime for additional information on troubleshooting, banning, reporting bugs, and more.
Highlights
Click on a link to jump to the section.
· How to record video on Quest for Code of Conduct Reports
· Echo VR High Quality Capture Mode
· Echo VR Error Messages and Meanings
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/ .
What should be included in my report?
Please provide our team with the username of players you believe are violating the Code of Conduct, along with a description of what happened, and any evidence you have (video, screenshots, audio, etc.).
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. Please note: Severe violations could result in a permanent ban without a warning or another ban being applied beforehand.
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. Repeatedly filing appeals after our team has responded to you and rejected your appeal with not help your case.
How do I appeal a Social Lobby ban by a Community Moderator?
Social Lobbies are a unique way for players to connect with other like-minded individuals in-game to socialize with. Social Lobbies are moderated by Community Moderators who have each established their own list of community rules as well as to the Echo VR Code of Conduct. Community Moderators have the ability to kick or ban players from Social Lobbies in the event a player violates their rules. If you are kicked or banned from a Social Lobby, you will need to contact the Community Moderators to appeal it.
How to record video on Quest for Code of Conduct Reports
How do I record videos using my Quest headset?
1. Press the Oculus Home Button.
2. Select the “Sharing” section of the menu.
3. Select “Record Video” to start recording.
4. To stop recording, repeat steps 1 & 3.
How do I get recorded videos from my Oculus headset onto my PC?
1. Start by making sure “Developer Mode” is off in your Settings.
2. Plug your Quest into your PC using a USB-C to USB cable/Oculus Link cable.
3. Go to “Devices and Drivers” on your PC.
4. Click on your Quest.
5. Go to Oculus > Videoshots.
Finding Logs
Q: How to I find my logs for Echo VR / Lone Echo?
Logs
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
OR
· Open your Oculus app
· Go to your Library
· Find your game (Echo VR, Lone Echo, etc)
· Click the three dots to the right
· Select Details
· Hover over Location with your mouse, and copy the Location
· Open the Location on your computer
· Find and click _local
· Find and click r14logs
· Select the time log that your bug/problem happened
Reporting Bugs
**UPDATE 3/2: We’re currently working on making a new support system that will be easier to access. Until then, the Support Form has temporarily been disabled.
There are two ways to report Echo VR bugs:
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. Logs can be shared with our Developers via private message after they’ve contacted you in the Support Channel.
Network
Q: Help! I’m having difficulty connecting to a game or staying connected.
Q: I’m getting a Login Authentication error for Echo VR.
A: Your router could be blocking the ports Echo VR requires to connect online. Try some of the steps below:
· 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 using an alternate DNS, like Google or Cloudflare.
· Try forwarding your ports https://portforward.com/ (listed below):
Ports
Login (TCP):
347125
34712
Matchmaking (TCP):
42148
General (UDP):
2000
2100
2200
2300
2400
6792
Note: If you require further assistance, contact your ISP; they will be able to walk you through this.
Q: Echo VR keeps disconnecting
A: You might be experiencing network disconnect from your Quest to your router. We’ve got a list of things to try to stabilize the connection:
1. Keep your headset on a 2.4Ghz WiFi signal. If you want to use your 5Ghz signal, make sure you’re within approximately 8 feet/ 2.5 meters of your router and make sure that no other devices are connected
2. Monitor network usage at home — is someone streaming or downloading? How many devices are connected? Try to reduce those while you play!
3. If your PC is connected via ethernet, are you still experiencing network issues? You might need to troubleshoot your router or check the speed of your connection.
Performance
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/
Q: Help! I’m experiencing frequent crashes in Echo VR/Lone Echo.
A: If you are encountering frequent crashes please ensure that you are not overclocking. If you are overclocking, try resetting your GPU/CPU to normal and reproducing the issue.
If you’re still experiencing frequent crashes in Lone Echo or Echo VR after removing overclocking, please contact our Devs (see the Submitting a RAD Support Ticket and Reporting Bugs section on this page) and we’ll be happy to help you as best as we can!
Miscellaneous
Lone Echo or Echo VR won’t download/ or update
If you have issues downloading Lone Echo or Echo VR, or downloading a game update, there are some quick troubleshooting steps to try:
· Disable your antivirus.
· Restart your PC / headset
· 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.
Lone Echo Progression/ Save Point Issues
Having issues progressing in Lone Echo (stuck at the Depleted Dig Site or unable to socket a battery?), or encountering crashes or black screens? Use one of our replacement save files found here.
**Spoiler Alert: Please only read as far down as you need to, as there may be hints to certain plot developments**
If you’re still having issues, please contact our Devs (see the Submitting a RAD Support Ticket and Reporting Bugs section on this page) and we’ll be happy to help you resolve your issue.
Q: Why does my Rift S mic sound high-pitched in Echo VR?
A: Do you have a high-pitch voice mod enabled in your social settings? You can change this in the Settings menu.
If you don’t have a voice mod enabled, are you using an external microphone? If you’re using an external mic, if it has to be outputting at 48khz. If not, your voice will sound high-pitched. You can adjust this in your microphone settings in your PC’s Sound Properties settings.
Q: My controllers stopped working/don’t appear in Echo VR / Lone Echo.
A: Are your batteries drained? If not, re-insert your batteries. This will return functionality.
Q: Will I lose game progress in Echo VR if I reset my headset?
A: No. Our cloud servers store your information, so you will not lose your progress.
Customizations
Q: Can I have my customizations transferred from one account to another?
A: No. Our team doesn’t transfer customizations to different accounts.
Echo Pass
Q: Can I refund a customization or Echo Points?
A: Per Oculus policy In-App purchases are non-refundable. For questions, issues, or concerns about a purchase or transaction, please contact Oculus Support here.
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.
Disclaimer:
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.
Instructions:
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
Troubleshooting
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:
- 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.
- To ensure we see your feedback or respond to your issue, please share your feedback and report your bugs to our team here: https://www.surveymonkey.com/r/9HD9MDK
By using this form our team is able to see what issue you’re having (meaning it isn’t lost in spam or buried by other convos) and we’re able to quantify feedback for quality of live fixes (similar to our feature request channel).
Echo VR Error Messages and Meanings
Message: Echo VR service is unavailable, invalid login request/login timeout, kicked from server, login authentication failed…
These are all network related issues.
Either your headset cannot connect because your network connectivity has dropped, or servers are down. Please restart your router and headset/pc before seeking further help.
For errors stating “authentication failed” or “certificate failed”, something is preventing Echo VR from connecting to your network: either anti-virus software, a firewall, or blocked ports.
QUEST (standalone):
- Try forwarding the ports Echo VR uses.
RIFT/PC/LINK:
- Disable or add Echo VR to your firewall/antivirus program’s ‘trusted apps’ list. (Windows Firewall, Windows Defender, Norton, etc).
- Try forwarding the ports Echo VR uses.
PC FORWARDING:
WORKAROUND:
If these tips don’t resolve the issue, you can circumvent this entirely by connecting to a VPN (PC) or mobile hotspot (Quest). This may result in increased latency or mobile data usage.
Message: Echo VR Failed to find a compatible server…
Is your Oculus OS and Echo VR version up-to-date? Restart your router and restart your Quest/headset/beta restart your Oculus app on PC (settings > beta >restart)
Message: Echo VR Server join failed: Server is locked
The match has reached the last few minutes of the game clock, preventing late-joins from changing match balance.
Message: Echo VR Server join failed: Server is full…
The Lobby or game has reached the maximum amount of players.
Antivirus blocking Echo VR
Q: Why can’t I play past the tutorial? A message appears saying I have antivirus blocking me from playing Echo VR.
A: A program on your computer (anti-virus/firewall/anti-malware, etc) is blocking Echo VR from connecting to the internet, as a safety precaution. You will have to:
1. Identify the firewall/anti-virus/anti-malware program your PC is using
2. disable that program/authorize Echo VR as a trusted program. If you don’t know which antivirus programs you’re running, you can check to see if any other security programs you have running, by using the tasklist command:
· Type *tasklist * into a command prompt to output a list of all the currently running processes. You’ll be able to see what anti-virus programs are running on that list. This might require the assistance of someone tech-savvy.
Contact Information for Issues Outside of Echo VR
VRML
· For VRML issues, please contact the VRML Admins or Moderators. You can do this by opening a ticket in Discord or contacting them via their website.
Oculus hardware/software issues
· Please contact Oculus Support for all Oculus hardware and/or software issues here: https://support.oculus.com/
Oculus feedback:
· Please share all feedback you have with Oculus here: https://oculus.uservoice.com/
Known Issues
ARENA
- Announcer VO does not play for the catapult or end of game timers in private Arena if a goal is scored in the last 15 seconds.
- Post-match terminal buttons are disabled if there are only spectators during a private match.
- Players may see distortion, blue orbs/circles, sparkling lights, boosts/gunfire, etc while Transitioning.
- Audio position may become reversed on the original Oculus Rift (CV1).
- Friends Tab does not refresh the player status once they are shown as “Online”.
- The rewards tablet may display the player’s Arena level and experience at the end of a Combat match.
- On Rift, players cannot be invited to a party from their Lobby social tab if they are not on your friends list.
- Grabs may occasionally fail to stop or add momentum in AI Teammates VS AI matches.
COMBAT
- Phase shifted players may have their full-screen FX disabled if they are being healed by a teammates’ repair matrix that ends before their phase shift does.
- Some Meteor projectile VFX maybe be missing after a player dies.
- After joining a private Echo Combat Match and muting all players in 2D Spectator, players cannot be unmuted.
- The title may occasionally become stuck on a black screen as a 2D spectator in Combat matches.
MENU/TRANSITION SCREEN
MENU/TRANSITION SCREEN MESSAGES:
- “Login Authentication Failed”
- “No Network Connection Detected”
- “Server Join Failed: Bad Request”
- “Server Join Failed: Timeout”
- “Disconnected from Server Due to Timeout”
The application has disconnected from the network.
· “Certificate Validation Failed”
The ports required for the Echo VR app to connect to servers are blocked on your network, most likely by security software.
CRITICAL
- Some PC users regularly experience a crash associated with NVIDIA GPU cards.
- Vive users may experience repeated crashes. Please note: Echo VR does not officially support Vive.
- Changing Anti-Aliasing settings causes a performance drop, which may lead to a crash.
GENERAL
- Players might have issues using their emotes in Echo VR due to tracking. Please make sure you are tapping the side of your head/headset and not the corner/front.
- User’s thumbs will stop moving during play.
- Transition screens when exiting games of both Arena and Combat may appear black.
- Some players may suddenly be missing their customizations (event decals, emotes, patterns, etc.).
- Tutorials do not pause when the headset is put into standby with the power button.
- Punch gloves stop working in the Brawler Room/Arena.
- Attaching darts to props can cause lag.
- User loses the ability to spawn the personal disc in the Arena Training Area when partially exiting the training area.
- Combat weapon holsters and un-holsters inconsistently while approaching towards the Combat’s exit to the Viewing Area on the Floor 2 of the Lobby.
- On rare occasions, players will hear a loud, rumbling noise around some of the walls while in the Skirmish Area.
- Intro tutorial is not marked as completed if the player completes it while they have no network connection.
- Equipping a bracer too quickly after removing a bracer may cause the newly equipped bracer to temporarily lack visibility.
NETWORK CONNECTION
- Latency may result in players’ punches not stunning opponents.
- Players with low bandwidth speeds may experience time outs when trying to connect to a Lobby or match.
- Users’ voice may sound distorted/crackly due to packet loss/bandwidth issues.
Matchmaking
- Uneven number of players in public matches.
- Parties may be split in Public matches. This is done to balance teams in matches, and prevent pub stomping.
COMPATIBILITY & PERFORMANCE
- Players using 430.39 drivers or older may experience a bug causing high CPU usage. Please upgrade to at least 430.53.
AUDIO
- Player’s mic may stop working after navigating to the Oculus dashboard or losing tracking.
- Rift S users may rarely have their audio crackle/become unclear.
ARM COMPUTER AND PARTIES
- Players will not be able to join a party (and will get immediately kicked out).
- Parties may be split in Public matches. This is done to balance teams in matches, and prevent pub stomping.
- The Friends List doesn’t refresh player status when they go offline, and instead will show friends as “online” even after they’ve logged out.
- The Friend’s List on the Arm Computer may not display all Oculus friends.
RIFT S
- Players may experience tracking issues or blackouts if their USB port doesn’t provide power/enough power. View this thread for more info[ [https://bit.ly/2KaEo2P]|https://bit.ly/2KaEo2P].
- Rift S users may rarely have their audio crackle/become unclear.
- Rift S users may hear a mechanical sound coming from their headset. This sound might make it difficult to have other player’s hear your VOIP, or for you to hear their VOIP. Unplugging your headset and plugging it back in will fix this issue.
QUEST 1 & 2
- Players will see a black screen in the Arena, where they are only able to see glowing tunnels and other players’ heads.
- Max volume on Quest can result in crackling/zapping VOIP due to Quest mic feedback.
This FAQ will be updated occasionally. Last update: 8/4/2021
