#Frequently Asked Questions

Here you can find answers to some of the most frequently asked questions. If you can't find your question here, feel free to ask for more help on the Official Quaver Discord Server.

#General

#What is Quaver?

Quaver is a community-driven and open source competitive rhythm game. It is inspired by a variety of classic vertical scrolling rhythm games and plans to expand on them by being focused on real-time competitive play.

#How is Quaver different from other games?

The game is fully open-source, which allows anyone to help and improve the game. Furthermore, we are aiming to provide a new VSRG experience by bringing competitive concepts, such as competitive matchmaking.

#What platforms is Quaver released on?

Quaver is released on Windows, Mac and Linux.

#Gameplay

#What game modes does Quaver support?

Quaver currently supports 4 keys (4K) and 7 keys (7K). 7K maps with additional scratch lane (7K+1) are also supported, while scores on them remain unranked.

#Where can I get more maps?

You can download more maps using the in-game downloader or from the Quaver website.

#Can I import maps from other games?

Yes, Quaver currently supports .osz, .sm and .mcz files. To import them, drag the files into the game's window.

#I have a lot of maps in an external game, can I import them all at once?

It is possible to import all of your maps from other games at once. In Quaver, navigate to Options > Miscellaneous, enable "Load Songs From Other Installed Games", and click "Detect Songs From Other Installed Games."

#Can I import my skin from another game?

The game doesn't support skin conversions out of the box, however you can download a .osk skin converter here along with a tutorial.

#I found a bug, where can I report it?

Any bug reports should be posted on our GitHub issues. Feel free to post anything you find, but please check if the issue has already been reported to avoid duplication.

#I have a feature request, where can I post it?

Similar to bug reports, feature requests belong on our GitHub issues. Simply choose “Feature Request” when creating a new issue!

#Can I change my username?

Changing your username is a donator-only feature. If you are a donator, you can change your username once every 30 days.

#How do I reduce the hitsound audio latency on Linux?

The audio latency should work well out of the box. It's possible to tweak the variables if unusual circumstances arise.

If you experience the audio latency increasing over play-time, open /etc/pulse/default.pa, find a line that says:

load-module module-udev-detect

and change it to:

load-module module-udev-detect fixed_latency_range=yes

Then reboot the system. Note, that this may cause severe audio glitches in certain applications (opening Discord in Firefox currently causes this, although the responsible component has already had a fix deployed).

You can also adjust the latency Quaver requests from the system. In quaver.cfg, find the following settings:

DevicePeriod = 2
DeviceBufferLengthMultiplier = 4

These control the period (2 ms by default, how often the system polls Quaver for new audio) and the buffer length (4 by default, how large the audio buffer is, as a multiple of the period). Decreasing period will decrease the audio latency while increasing the CPU load, and decreasing the buffer length multiplier will decrease the audio latency while potentially introducing audio "crackling" and other artifacts. Increasing these values will lead to more latency while decreasing the CPU load and audio glitch probability respectively.

#How do I use the Wayland VSync?

To use Wayland VSync, you need to be running Linux with a Wayland compositor, such as present in the newer versions of GNOME and KDE (make sure you're not using the "Xorg" mode), or a standalone one, such as Weston or sway.

Turn on the "Prefer Wayland" option in Video/Linux and restart Quaver. Now turn on Wayland VSync. You can ensure that it works using the FPS counter. Your FPS should become equal to your monitor refresh rate, while UPS should become higher.

For the lowest latency (below 1 frame) when running sway, set up max_render_time on the output and on the Quaver window. See man 5 sway for instructions.

#Interface

#How do song select search filters work?

We currently have following search filters:

All filters can use the = (equals) and != (not equals) operator, number comparisons can additionally use >= > <= <.

To negate the condition, prepend a : before the term (e.g. !d>10 searches for difficulty <= 10)

For strings, you can use = and : for contains, != for not contains.

To include spaces for escape semantics, surround your string by a double/single quote (e.g. "hello world" matches the space too)

For lists of strings, you could use the OR combinator (/) or the AND combinator (,) to join the strings. For example, c:piano/emi returns maps whose creator contains either piano or emi (or both), while c:piano,emi returns maps whose creator must contain both piano and emi.

For the Game and Status parameter, if its values are listed without using key-value pair (i.e. the searching of unranked or etterna but not unr, g=unranked, etc.), it will be interpreted as if you are searching for status=unranked or game=etterna. To avoid this, wrap the term in quotes (e.g. "etterna"). This is called a singleton enum.

You use a filter by typing a flag, an operator and an argument into the search bar, all without spaces. An example would be difficulty>30. Any string from the short to the long flags will be matched, diff>30 would be a valid filter.

If the term is without keys and is not a singleton enum, it will be treated as a regular keyword and display all mapsets that contain that keyword in the metadata (artist, title, mapper, tags).

All top level terms in the search have to be met for a mapset to be shown (AND).

#Troubleshooting

#The game doesn’t launch

Make sure Steam is running, as Steam is required in order to run Quaver.

#Linux, offline or local build

Running an offline, or a published stand-alone build (e.g. from dotnet publish -c Release -r linux-x64) needs to be done through the Steam runtime. Run this command from the Quaver repository folder:

~/.steam/bin/steam-runtime/run.sh Quaver/bin/Release/netcoreapp2.1/linux-x64/publish/Quaver

Running a regular, non-stand-alone build (e.g. from dotnet build -p Quaver -c Debug) requires the correct library path. This can be done using the Steam runtime launch script and Quaver’s own launch script:

~/.steam/bin/steam-runtime/run.sh Quaver/bin/Debug/netcoreapp2.1/quaver.sh

#I'm getting "Content File Locked" while trying to download Quaver on Steam

This seems to be an issue related to Steam.

A few things that might help fix this problem can be, running Steam as administrator, restarting your computer, and verifying the integrity of Quaver's game files.

If none of these work for you, you might find the answer in one of these forum threads:

• Thread One (SteamCommunity)
• Thread Two (Reddit)

#The game launched with a resolution bigger than my monitor's, thus making it unplayable

If your game launched with this issue, close Quaver and navigate to the game's steam local files.

Open the quaver.cfg file and look for the configuration options WindowHeight, WindowWidth, and WindowFullScreen. Proceed to set your desired window resolution. The next step is optional, it'd be a good idea to set WindowFullScreen to False until you start the client back up to avoid further problems.

#My antivirus detected Quaver as malicious software

This is due to the fact, that the game files are not digitally signed for their authenticity as this requires purchasing and maintaining costs for a Digital Certificate.

To avoid Quaver being picked up by your antivirus, add Quaver.exe or the local files directory to your antivirus's whitelist.