Automobilista 2 Server Manager and Project Cars 2 Server Manager have a great selection of features to enhance your sim racing experience, this page aims to briefly explain each of the current features.
This page expects that you already have your Manager up and running successfully, if you don't please refer to the Installation Instructions.
The AMS2 server and PCars2 server and Manager are very similar but not identical, when something applies to only a certain game/manager the name of that game/manager will be used, otherwise we will refer to simply the "Game" or "Manager" if it applies to both.
The server options page includes a set of options for the Manager and the Game server. You definitely need to access this page when first setting up the manager, read through the options and their descriptions and set the values. Most of the options explain what they do and how best to use them in the description beneath the input.
At the absolute minimum you need to set the "Name" of your server, the "Steam Port", "Host Port" and "Query Port".
If your router supports UPnP then switch that setting on, this means the ports you configured will be forwarded automatically by the Manager with your router's UPnP service.
If your router doesn't support UPnP then switch that setting off. Then you will need to access your router settings in your browser (usually at 192.168.1.1, although it can vary for different routers) and manually forward the ports that you configured. If you're not sure about how to forward ports there are plenty of guides online, for example:
If you can't port forward ACSM ports check if your ISP is using CGNAT IPv4 addresses, this is getting more and more common and makes hosting an AC server impossible, as it does not support IPv6. If your ISP is using CGNAT then you'll need to contact them and ask for a public IPv4 address, depending on the provider they may charge for this.
The HTTP API can be used to monitor the current state of your Game server whilst it is running as well as carry out some admin functions (such as modifying settings for the next session).
If you are hosting locally (and accessing your Manager through 127.0.0.1 in your browser) then the default HTTP API setup will be functional, and you can access it at 127.0.0.1:9000 in your browser whilst the Game server is running. In other setups you may need to change the "HTTPAPI Interface" value, and you will need to change it if you want the HTTP API to be accessible over the internet.
The default admin login information for the HTTP API is user: admin password: adminpassword, but we recommend that you change these in the "HTTPAPI Users" input.
At this time the HTTP API isn't available to customers of Emperor Servers, although this feature is planned for the future.
The Lua API allows the server to be extended by in-server scripting in Lua. We do not recommend changing any of the default options here unless you really know what you're doing!
Disabling the Lua API or removing any of the default "Lua API Addons" or "Lua Allowed Libraries" will prevent the Manager results pages from working!
Discord notifications (via webhooks) can be configured to automatically send messages to your Discord server on certain server events (preset scheduled, championship event started etc.).
The styling of the Manager can be tweaked to your liking, there is a base option for the theme that allows you to switch between light or dark mode (or auto based on browser preference).
You can also control the styling of the Manager in much more detail by using Custom CSS, which allows you to customise the Manager by injecting your own CSS. You can read more about this on the AC Manager Theme Wiki page (This guide is referencing our AC Server Manager, but the system works in the same way for ACCSM).
Quick events are designed to give you the shortest possible route to starting an event on your server, they have very minimal options but are the quickest way to getting your server online in the lobby.
We recommend using quick events to run your first event just to make sure that everything is working properly.
Presets are saved configuration files for AMS2/PCars2 events, you can make as many presets as you like, and can start, edit or use them as a template later on. Presets have a lot more options than quick events, and can also be scheduled to start at a specific date/time.
Championships are a collection of presets with points tracking, each preset is treated as a championship event and can be configured and scheduled like a normal preset. The main difference here is that as each event is completed the championship keeps track of the drivers results, and builds a points table across the championship.
Championships have a few advanced features that can be configured:
Any event that is successfully completed will generate a results file, which contains the finishing leaderboard of the session, data about every lap completed by each driver (including lap time, sector times, lap validity and more) including AI drivers.
Accounts allow you to access your Manager, and provide access to other people with customisable levels of access via the "Group" system. There are currently four available groups:
By default your Manager will be "closed", meaning that in order to access any pages at all a user will need to log in to an account first. If you want users to be able to access the manager with "Read" group permissions without logging in you can click the "Make Open" button on the accounts page.
The calendar displays a list of all events currently scheduled by the Manager to start in the future, either in a list or graphic format (the default view can be set on the Server Options page).
The server logs page displays logs from the Game server and logs from the Manager itself, in two separate sections. In general, you should use the logs page to help resolve any issues that you are having. Most issues that can occur with the server or manager will show a message in one of the logs.
You can also use the "Download" button above each log to download it to your computer, if you contact us asking for support we may well ask for a copy of these logs to help us debug the issue.