Skip to content

GITADORA Arena Model

bicarus edited this page Aug 31, 2026 · 117 revisions

Caution

GW Delta is a new version and not a slight upgrade over GW; it requires a whole new cabinet I/O. Do not reuse prop XML files or DLLs from older Gitadora versions. If you do that, game will crash, boot with missing features, or end up with corrupt NVRAM. You may also get banned from EA servers for sending invalid requests.

Getting it to boot

Network error (5-2000-0000)

You'll need the Allow 192.168.x.x ip range patch otherwise the game will fail to boot with a network error.

IP address error (5-1506-0000)

You shouldn't see this anymore as of the latest beta. If you still do, disable all network adapters except one that you are using.

Monitor error

While you can continue past it, but it likely means you configured something incorrectly. Read graphics options below.

Graphics options

Fullscreen

Option A) fullscreen with a single 4K@60Hz monitor with subscreen overlay

This should work by default; spice will scan for number of monitors connected to the PC, and if you don't have four monitors, it will default to this mode.

The monitor MUST support 4K@60Hz. Any smaller than that, the game will start with a black screen, and when it does occasionally render (alt+tab) you'll see a monitor error.

Option B) fullscreen with 2 monitors (4K@60Hz main monitor + touch monitor)

You can set -gdlayout to 2 boot into full screen with a 4K primary monitor and a secondary touch screen, omitting the side monitors. Make sure -graphics-force-single-adapter is disabled.

Your touch monitor must support 800x1280 in portrait (16:10 monitor, not 16:9!!!). You need to rotate the monitor before launching the game.

New in PR 900: -gdasublayout can be used to display the subscreen on a touch monitor in landscape orientation. It can also display the left / right monitors (live2d animations) on the sub monitor. It can be combined with -forceressub.

Once in the game, go into test menu and perform touch calibration to fix your touches not lining up.

Option C) fullscreen with 4 monitors (AC configuration)

Requires the following, which is the same as what an arcade cab uses:

  • HDMI -> main gameplay monitor @ 4K (and it must be 4K otherwise things will not render properly)
  • DP port 0 -> LEFT monitor @ 1080p portrait
  • DP port 1 -> RIGHT monitor @ 1080p portrait
  • DP port 2 -> SMALL monitor (subscreen / touch screen) @ 800x1280 portrait (16:10 monitor, not 16:9!!!)

The port number depends on your GPU so you'll need to experiment.

If the requirements are not met, the game will show monitor error on boot, but you can continue past it. You can probably plug in dummy DP cables for the monitors you don't have?

Make sure -graphics-force-single-adapter is disabled.

Windowed

You don't need a 4K monitor for this one; 1080p is enough (even smaller if you adjust the window size)

You can use scaling options in spicecfg - such as Window Border Style and Window Size options to make the window borderless fullscreen. F11 menu does work but some of the options can't be changed while the game is running as resizing tends to lock up the game.

Option A) borderless fullscreen with 1/2/4 windows

  1. Enable windowed mode
  2. Set Window Border Style to borderless
  3. Select number of monitors using GITADORA Arena Layout option
  4. Choose monitors using GitaDora Windowed Xyz Monitor option

Option B) windowed with 1/2/4 windows

  1. Enable windowed mode
  2. Set GitaDora Arena Layout option to 1/2/4

For 1 window, use the subscreen overlay to access the touch screen with your mouse.

What doesn't work

Force Full Screen Resolution (-forceres) doesn't work. Even if it did, the game would render things assuming 4K anyway.

Audio

By default, the game tries ASIO (with 7.1 channel) on Xonar driver, but falls back to WASAPI Exclusive @ 48kHz.

How it works on the cab

On a real cabinet, things are wired up like this:

  • ASIO: Xonar AE Front port - top speakers for BGM
  • ASIO: Xonar AE Rear port - center speakers for SE
  • ASIO: Xonar AE Center port - center woofer (BGM, SE)
  • ASIO: Xonar AE Side port - bottom speakers (SE)
  • WASAPI Exclusive: Realtek onboard audio green port - headphones

The game specifically looks for ASIO driver with XONAR in it, and an audio endpoint with name Realtek in it.

Using ASIO

If you have a Xonar then the game will attempt to use it. Make sure it's in Speakers mode, not Headphones, and set the Playback Configuration to 7.1. The sample rate and bit width shouldn't matter.

If you want to use another ASIO driver, use GitaDora Arena ASIO Driver option. Check the log to ensure that the game didn't fail to open ASIO and silently failed over to WASAPI.

If you only have stereo channels (2 channels), try using the -2ch option. This routes the center (mono) channel to your front speakers so you can hear keysounds.

Using WASAPI

If you don't have a 7.1 surround system, you won't hear any sound effects (drum / guitar key sounds). In this case, you should turn on -2ch option which downmixes everything to stereo. If you need to adjust the volume ratio between BGM vs. sound effects, go to the test menu and adjust volume level. Avoid using 2-channel patches if possible as they often result in buzzing noise.

If you need shared WASAPI, use the -wasapishared option or use a patch.

Touch

If touch doesn't work, this is usually caused by bad prop files in NVRAM (bad touch calibration data).

Option A) delete NVRAM folder to reset calibration, or

Option B) go to Test Menu, navigate to I/O Check - Touch Panel Check by pressing test / service buttons, and press test + service to perform calibration

Clone this wiki locally