Release Build: SimracewayGame_66.exe
Release Date: 05/09/12
Overview
- Garage: added “queued” label to download-queued cars view
- Quick race: improved messaging when track is not installed
- HUD improvements & minor fixes
{ 0 comments }
From the category archives:
by JimN on May 9, 2012
Release Build: SimracewayGame_66.exe
Release Date: 05/09/12
Overview
{ 0 comments }
by JimN on April 25, 2012
Release Build: SimracewayGame_65.exe
Release Date: 04/25/12
Overview
{ 0 comments }
by JimN on April 13, 2012
A planned update to the racing servers in both US and UK locations is requiring a momentary disruption in service. This is in support of the new release and will require a simple restart of the game to start the updates. As always we are enhancing systems to provide you with the best experience possible, many thanks!
{ 0 comments }
by JimN on April 13, 2012
Release Build: SimracewayGame_64.exe
Release Date: 04/13/12
Overview
Fixed Issues
{ 0 comments }
by JimN on March 29, 2012
Release Build: SimracewayGame_63.exe
Release Date: 03/28/12
Overview
{ 0 comments }
by JimN on March 15, 2012
Patch Release Build: SimracewayGame_62.exe
Release Date: 03/15/12
{ 0 comments }
by JimN on March 14, 2012
Release Build: SimracewayGame_61.exe
Release Date: 03/14/12
Overview
{ 0 comments }
by JimN on March 6, 2012
Release Build: SimracewayGame_59.exe
Release Date: 03/06/12
Fixed Issues
{ 0 comments }
by JimN on February 28, 2012
A patch release went live and users who updated may be repeatedly prompted to update in error. We have currently taken this patch offline and will have a fix to replace this as soon as possible. While we recommend waiting for the fix patch to update the game on its own, the option to reinstall SimracewayGame_57.exe will return your game to that particular state. We will be posting more information once the new patch is up.
{ 0 comments }
by JimN on February 14, 2012
Our issues have been resolved and the UK servers are being brought back online. This was an unscheduled outage and we apologize for any inconvenience that this may have caused. The problem has been identified and we are taking steps to prevent this from happening in the future.
{ 0 comments }