Skip to content

beatmania IIDX 31 EPOLIS

Please make sure you downloaded your data from an appropriate source.
This guide is unable to troubleshoot any problems related to bad or poorly managed data.

About data

The full game should be around 100gb while updates are only around 2-5gb in size.

Standard (LDJ) / Lightning (TDJ)

Please keep the following in mind as you're going through this guide.

IIDX's codename is LDJ. For IIDX 31 Epolis this would be either:

  • LDJ-010 (TDJ, Lightning cab, 120 FPS)
  • LDJ-012 (LDJ, Standard cab, 60 FPS)

The main difference between 010 and 012 is the game's main .dll file, bm2dx.dll.

This changes which features the game offers, and which conditions the game expects to run under.

  • TDJ expects a 120hz compatible monitor for its main screen, and a second 60hz touchscreen compatible monitor called a subscreen. The second monitor isn't mandatory, we can get around that using spice2x.
  • LDJ expects 60hz monitor for its main screen, and no subscreen.

We'll be using the terms TDJ for Lightning, and LDJ for Standard throughout the guide.

If you're coming from IIDX 30 Resident

You'll want to update your data from LDJ-003 to LDJ-010 or LDJ-012 FIRST then follow this guide as normal.

Preparing data

After downloading and extracting your data, we need to make sure your files aren't set to Read-only.

  • Right click the folder containing your data, then click on Properties.
  • In the General tab go down to Attributes, untick Read-only and click Apply.
  • A popup will appear, select Apply changes to this folder, subfolder and files and press OK.
  • Finally, click OK again to exit out of properties.

You should end up with a file structure with a few folders only, as follows.

If your data doesn't look like this

If you're missing the modules folder and instead have bunch of .dll files next to your folders:

  • Create a modules folder.
  • Move all .dll files inside of it so you end up with a structure as shown above.

If extra files are present next to your folders, such as executables, scripts, etc.. remove them.
This also means your data was tampered with and we strongly recommend getting new data from somewhere else.

If you don't need to update your data, you can skip over to the Installing Spice2x section.

Updating data

Please make sure you're using the right update for your current data.

As we've seen in the About data section, the main difference between LDJ and TDJ is the bm2dx.dll file.
When updating from a previous version to the next, our current .dll will be overwritten.

Knowing that, patches re-uploaded by the community tend to be named LDJ-DATECODE-to-LDJ-010/012-DATECODE.
Note: If updating from IIDX 30 Resident, it will be LDJ-003-DATECODE-to-LDJ-010/012-DATECODE.

For example LDJ-2024032500-to-LDJ-010-2024050700.

  • 2024032500 being your current data's version, no matter if it's using a TDJ or LDJ .dll file.
  • 2024050700 being the version you would arrive at.
  • 010 meaning you would end up with a TDJ (Lightning Cab) bm2dx.dll file.
  • Extract your patch's files to your existing data in a way that matches its file structure. Agree to overwrite files if necessary.
  • Open prop\ea3-config.xml in a text editor and find the following lines near the top.
    <soft>
        <model __type="str">LDJ</model>
        <dest __type="str">J</dest>
        <spec __type="str">E</spec>
        <rev __type="str">A</rev>
        <ext __type="str">2024050700</ext>
    </soft>

On the line with <spec __type="str"> the letter needs to match your data type:

  • E for Standard (LDJ-012, LDJ, 60hz)
  • D for Lightning (LDJ-010, TDJ, 120hz)

Replace the letter accordingly if necessary.

On the line with <ext __type="str"> the datecode needs to match your new version.

  • If that's already the case then great! Don't touch anything.
  • If it instead corresponds to our pre-patch datecode, replace it with the new one.

Now save the file.

Installing Spice2x

If you already have Spice2x installed, make sure it is up to date!

  • Head over to spice2x.github.io and download the latest release.
  • Extract the spice64.exe and spicecfg.exe files from the archive to your game's directory.

Configuring Spice2x

Open spicecfg.exe, each following sub-section corresponds to a tab at the top.

Buttons

Click on Bind then press the key you want associated with the action.

With your controller and/or keyboard plugged in, configure your keys for:

  • Maintenance: Service, Test
  • P1 Game buttons: 1 to 7, Start, EFFECT, VEFX
  • P1 Keypad: Keypad Insert Card

Only if you're using LDJ:

  • P1 Keypad: 1 to 9

Only if you're playing using a keyboard:

  • Turntable: TT+, TT- and optionally TT+/- which alternates between TT+ and TT- on each press.

Analogs (controller/cab only)

With a controller rather than binding buttons to TT+ and TT-, you need to:

  • For Turntable P1, click Bind.
  • In Device, pick your controller.
  • In Control, pick whichever one corresponds to the turntable.
  • Turn your turntable ensuring that the Preview turns along with it.
  • Click Close, leaving the rest of the settings alone.

Overlay

Modifying buttons in this section is not required but you are free to change what you want.

Click on Bind then press the key you want associated with the action.

Lights (controller/cab only)

Your controller might support having its lights controlled by the game through spice2x.

If it does, here's how you may link different actions to your lights:

  • Click Bind.
  • In Device, pick your controller.
  • In Light Control, select the corresponding light.
  • Click Close.
  • Repeat for your other lights.

Cards

Covered in the Connecting to a network section.

Patches

Go through the Spice2x Patching page to import patches.

Ever since EPOLIS final (2024-08-26), patches have a description built-in to them.

To view it, hover-over the (?) or (!) to the left of each patch's name.

To prevent issues, avoid patching things you don't need or understand.

API

Leave everything at default unless you know what you're doing.

Options

If you don't know what an option does, hover over the question mark at the very left.

Be very careful changing options you don't understand as it may cause issues.

Required

Category Option Parameter Setting
Game Options IIDX Disable Cameras -iidxdisablecams ON
Network EA Service URL -url Covered in Connecting to a network

Required For TDJ

Category Option Parameter Setting
Game Options IIDX TDJ Mode -iidxtdj ON

If you only have a single 120hz monitor, and not another 60hz touchscreen:

Category Option Parameter Setting
Graphics (common) Only Use One Monitor -graphics-force-single-adapter ON

Highly Recommended for NVIDIA users ONLY

Category Option Parameter Setting
Graphics (common) NVIDIA profile optimization -nvprofile ON

Advanced & Development

Leave everything at default unless you know what you're doing.

Connecting to a network

Please choose one of the two solutions, not both!

Remote (Online Network)

Open spicecfg.exe and head to the Options tab.

In the Network category, set the following settings:

  • EA Service URL to the URL provided by your network.
  • PCBID to the PCBID provided by your network.

Next you need a card number.
If you don't already have one, generate one in the Cards tab.
To keep your card number safe, create a new .txt file with ONLY it inside.

Once that's done, head to the Cards tab, for Player 1 click Open... and point to your text file.

Local e-amuse Emulator (Asphyxia)

This is covered in the Asphyxia CORE page.

Pre-launch requirements

These steps are required, otherwise your game won't run.

VCRedist & DirectX

Audio

  • Open spicecfg.exe.
  • At the very top, click on Shortcuts then Audio Playback Devices.
  • In the popup window, right click on your default audio device, and click on Properties.
  • Go to the Advanced tab.
  • Check both boxes under Exclusive Mode.
  • Open the Default Format dropdown.
  • Pick the 24 bit, 44100 Hz (CD Quality) option and click Apply then OK. 24 bit, 48000 Hz is also acceptable as spice2x will handle it.

Standard / Lightning / Language settings

Read through the Extra Information page and edit your prop\ea3-config.xml file if necessary.

First launch

If you have any issues running the game, refer to the Troubleshooting page.

BACKUP DATA

If you've followed all instructions correctly, you're now finally ready to launch the game!

First plug your controller if you have one and run spice64.exe, press Yes when it asks for elevated privileges.

If it's your first time running the game, you'll immediately be greeted with this screen.

CLOCK ERROR

Press your Test key to initialize the backup data, a message will pop up stating it's been initialized.

Next, you'll get another error.

Let the game run for a bit until the monitor check is complete and you should be taken to the service menu.

Instructions on how to navigate the menu are shown at the bottom of the screen.

  • Press 1 and 2 to go up and down.
  • Press 6 to select/execute.

Start by going up to CLOCK.

Here, simply select SAVE AND EXIT and the clock will be set.

You'll be back in the service menu.

NETWORK OPTIONS

Go to NETWORK OPTIONS then SHOP NAME SETTING.

We will need to set a shop name.

  • Name your shop to whatever you'd like. Instructions on how to navigate are at the bottom of the screen.
  • Go to EXIT then SAVE AND EXIT.

Select GAME MODE.

You're all done! The game should load up properly now.

Carding in

Before carding in, you have the option of changing the game's language by pressing your EFFECT key.

For LDJ (Standard)

LDJ should accept keypad number binds:

  • Press your Keypad Insert Card button.
  • Enter your code using your keypad binds.
For TDJ (Lightning)

TDJ will ignore keypad number binds, you need to:

  • Press your Keypad Insert Card button.
  • Press your Toggle Sub Screen overlay button (PgUp by default) to bring up the sub screen.
  • Enter your code by clicking on the subscreen's keypad.
  • If your code is accepted, you may now close the overlay.

(optional) Installing Omnimix

Check out the Data Mods and Omnimix guide.

Troubleshooting

Have any other issue?

Check out the Troubleshooting and Error Codes pages.

For any more game-specific information, check out Extra Information.