Just can't get any consistency going on this combo... I've built my race set on hards so going to softs is nqr for qual. PB is a 2.04 so still plenty of time to find. Tyres especially the fronts  cool after about 5 laps or so so need to push harder and harder which causes the errors to appear and then lap times go out the door. Need to find that consistency and go at 95% for the races.

I'm about to upgrade my pc, and bought a Samsung 250GB 840 EVO cheap, looking forward to a fresh windows install since Z97 is UEFI only and MBR disks aren't even supported to boot off, so yeah can't image the current 120gb SSD Will have to figure out the whole steam thing again also.

But yeh having all your my documents and downloads, videos library etc off the ssd helps with space. All of that is on a 1TB WD Green HDD. My Windows install is just over 22GB and Program Files are a bit over 33GB, that's nearly 60GB for just windows and the main programs.

I moved my AC game from a hdd to my ssd lol dunno if it did anything for loading times though, still takes forever.

All the settings are stored under "Documents/Assetto Corsa" so make sure to back that up. Copy your "assettocorsa" folder to where you want it then follow Dick's instructions, the way I did it was bit different and I think Dick's way is better.

Was a good nights racing, I couldn't believe how much grip the track had, felt the quickest in a long time.

I think I qualed around 8th for the first race but was way off pace on mediums. Then I played with my set too much, lost my HUD and lost my mojo. 2nd qual and race was just meh and the 3rd race was a disaster, ended up retiring.

Thanks to everyone that put up with dodging me on track. See you at Silverstone.

Some very cool updates there, I think server side settings need to addressed so everyone is using the same settings etc before flat spots are a concern.

Make sure sleep time=1 is in your server config, I just ran into the same problem and the server would try to use 100% cpu and ping was 500+ms.

Thanks heaps for the great write up dave, I have managed to configure a server with this quite easily now just going to test it out. 

I have tested my server but getting very high ping rates for some reason from 180 to 550 each time I refresh the server list.

Make sure you have chosen Sydney and not the default Oregon region in AWS Console. The region sets the actual location of the server affecting pings dramatically.

Hi guys, made a quick (took me a while actually lol) video to explain how to setup your AC server on Amazon Web Services for free! I might be tempted to do a lunix version if there's any interest and Kunos fixes the high cpu use on it in an update.

Sorry about lack of audio, had a screaming 2yo in the background + TV so didn't want to record anything. Here is the process involved in 10 steps, and the video can be found on youtube here....



1. Go to aws.amazon.com and create an account if you don't already have one. You will need a valid credit card for any charges and a phone/mobile phone to verify you're real.

2. Once the account is created login to the Management Console with your email address and password you supplied when creating your account.

3. When logged in, change the region in the top right to Asia Pacific (Sydney), if you want to you can also change the Start Page to EC2.

4. Click on EC2 under "Compute & Networking" then under Create Instance click Launch Instance.

5. Tick Free tier only to see the corresponding AMIs and then scroll down and select Windows Server 2003 R2 Base 64-bit or a flavour of your choice. The instance type should automatically be selected as t2.micro, if this is not available make sure you have chosen a 64bit OS.

6. Leave the default settings for the instance details, if you wish you can tick Protect against accidental termination. Storage also leave it as default. Set the tags to whatever you like.

7. The Security Group is basically a firewall. Here you need to allow yourself to access the Remote Desktop of the server, choose "MyIP" under Source and your IP address will automatically be prefilled. If you have a dynamic IP address or wish to access the server remotely from other locations, add them manually. Create rules for the TCP and UDP traffic that is required for the Assetto Corsa server to function. These are TCP 8081, 8082, 9600 and UDP 9600.

8. Just before launching the instance you must create a key pair to access the server securely. Use a key you've made previously or create a new one, give it a name and save it to your computer.

9. Once the instance is launched you must wait around 5 minutes before you can access the server's Public IP username and Administrator password. Once you have these copied down you can access your server through Remote Desktop. Setup a few items on RD for ease of use.. I like to set an easy to use resolution and map some local drives that hold the Assetto Corsa files.

10. Connect to the server and copy over the server files from your local machine that you downloaded from Steam Tools. Turn off the windows firewall, configure the server and then run the acserver executable file to launch the server.