Documentation > Getting Started > All on One

All on One PC, separated processes

When to choose this setup

When you want to use player in a production setting.

This is how the player is intended to be used.

Prerequisites

• We strongly recommend against custom firewall software such as Norton, Symantec, McAffee or similar in conjunction with VZX Pro Player. Windows has a built-in firewall which does the job quite well.
• The programs need to be able to communicate over IPv4 on 127.0.0.0/8.

Find the Program Executables

Go to the installation directory where the EXE files are installed * You can do this in Steam by going to the options cog * Click on "Local Files" * Click "Browse..." * Make a note of this directory.

Starting Player Manager

• Make sure Steam is running, Player needs Steam to validate DLC ownership.
• Start "vzx_pro_player_manager.exe"
• You will now get at least one question from the Windows Firewall.
• This is because the managers are designed to listen on the local network (LAN)
• If you know you only are to run everything on the local PC, press the "Cancel" button
• Should you change your mind, you need to go into Windows Firewall Settings and enable all vzx_pro* programs

Note!

Player Manager in itself does not need Steam but Player Manager and Player will always run on the same PC so Steam must be active and logged in on that machine.

Starting Audio Server Manager

• Start "vzx_pro_audio_server_manager.exe"
• You will now get at least one question from the Windows Firewall.
• This is because the managers are designed to listen on the local network (LAN)
• If you know you only are to run everything on the local PC, press the "Cancel" button
• Should you change your mind, you need to go into Windows Firewall Settings and enable all vzx_pro* programs

Note!

Audio Server Manager and Audio Server do not need Steam on the PC they are running on.

Starting Controller

• Start "vzx_pro_controller.exe"

Note!

Controller does not need Steam on the PC it's running on.

Next Steps

Continue with the "Getting Started" in the Controller Documentation