Actually, I can safely say that git clone --recursive doesn't actually download the binaries submodule, unless it's just my Git installation being, well, should we say, a git? Anyway, it's alright, git clone, the download the binaries separately. You'll get the same result. As for running the server on Linux, it's pretty straight forward. My instructions come from running this on a Raspberry Pi, which as we know is an Arm-based system, but the same should apply on an x86 linux box or vps. Nevertheless, no matter how you get Mono and asp.net installed, you download and run the server in the same way. Mono and asp.net instructions Keep in mind that if you scroll down past the commands in each step, there is a procedure to download a script that will automate those commands. You'll see what I mean when you read this setup guide.
Ok, so assuming we have Mono and Asp.net installed and running, let's make the server directory.
mkdir tdvsrv
Now to download the files
wget https://github.com/munawarb/Three-D-Vel … Server.exe
wget https://github.com/munawarb/Three-D-Vel … Server.pdb
wget https://raw.githubusercontent.com/munaw … exe.config
Now to run the server. cd tdvsrv
chmod +x TDVServer.exe
./TDVServer.exe
The server is now running. I'm assuming you've forwarded ports 4444 and 4445 already, so I won't go into that as those instructions are router specific. Type the ip address of your router into your browser, and it's all you from there. I will say that if it asks you for tcp or udp, tcp worked for me. Ok, now that we have our server running, go ahead and run the game, and the connect to your ip address. If it places you in the hanger, you're good to go. The good thing is that we're running the server natively, no ExagEar desktop or any other emulation, so not only are we guaranteed the proper hardware support, but we also have the benefit of passing commands straight through and getting output via speech, whether you're running headless or running with speakup. Note that obviously if you connect to the server without letting people know that your server is, uh, online ? you'll be the only pilot in the air, and that can get a little boring, right? Flying around and shooting at nothing is a good way to test your server's connectivity, but once you've had enough, go ahead and crash that thing. Besides, you being the only one on the board is not a proper stress test for your own server. Sure, if you have two computers or two virtual machines you can always run a second instance of the game to simulate other folks on the server, but unless you have a separate keyboard or are extremely good at switching between virtual machines in realtime, that's still not good enough. Having ai on the server is not only a good idea if there's no one on the server at the moment, but it's also an excellent way for admins to stress test the server to see how much it can take, without having to worry about pissing other people off when they're on the receiving end of a slow connection should the server setup be faulty. Note that this generally doesn't apply to vps's, but if you're running the server through one of your own machines, unless it's an actual dedicated server or a really good machine with killer specs that you can leave unattended, do keep that in mind.