How do I do this? - Look in this folder: \Users\<current user>\Documents\Project CARS\
Depending on the HMD you're using...
Oculus Rift, edit: oculussettings.xml
HTC Vive, edit: openvrsettings.xml
Look for a line called
HTML Code:
"<prop name="ResScale" data="1" />"
Change the number after 'data=' to whatever you want to set your super sampling to. Higher numbers will increase the resolution, while lowering the number will decrease the resolution. We recommend starting with a value around 1.5 and experimenting with it from there. How much you can push this will depend on your GPU.
Have fun

Dopo il rilascio dell'ultimo aggiornamento di alcuni giorni fa, al quale peraltro il team di sviluppo sta ancora lavorando per risolvere alcuni fastidiosi problemi tecnici riscontrati da quasi tutti gli utenti, Sector 3 ci aggiorna nuovamente con alcuni screenshots per mostrarci cosa aspettarci nel futuro del suo RaceRoom Racing Experience. Oltre alle migliorie delle quali vi abbiamo già parlato, ecco le prime previews della KTM X-Bow RR ed Audi TT RS VLN (di imminente rilascio), Formula RR 3 (una Formula 3 di fantasia), Formula RR US (IndyCar), varie GT3 aggiornate (BMW M3, Audi R8 e McLaren 650s), Volvo Polestart TC1 WTCC (che sarà nel WTCC 2016 pack il prossimo anno), senza dimenticare la pista di Silverstone, che dovrebbe arrivare già in dicembre.

This update contains:

• Gameplay: Added collisions between cars (Race mode)
• Gameplay: Added slipstream (Race mode)
• Gameplay: Added virtual mirror in HUD
• Gameplay: Huge improvement to AI behavior
• Gameplay: Procedural generation of AI profiles
• Gameplay: Semaphore on starting line
• Gameplay: Standings on position billboard
• Gameplay: Improved rules for race regularity and disqualification
• Graphics: Car mirrors are now working
• Graphics: Lighting management in night conditions
• Graphics: Rendering pipeline ready and compliant for VR (WIP)
• Graphics: Fixed bad illumination in some special cases
• Procedural engine: Improved walls/fences distribution
• Procedural engine: Improved track assets distribution
• Procedural engine: Added new asset: Kerbs models/type
• Procedural engine: Added new asset: Mega structures
• Procedural engine: Added new asset: Track/buildings on starting straight
• Procedural engine: Added new asset: Generic vehicles
• Procedural engine: Added new asset: Track/recovery vehicles
• Procedural engine: Added new asset: Marshall characters/stands
• Procedural engine: Added new asset: Cameramen characters/platforms
• Performances: Pre-generated track shaders during scene loading (which caused a lot of hiccups)
• Performances: Scenes transition is now seamless
• Performances: Smoother frame rendering
• Performances: Slightly optimized texture generation and memory occupation
• Performances: Reduced performance impact of dynamic reflections
• Performances: Fixed subtle crash in updating dynamic reflections on some configurations
• Performances: Slightly reduced CPU workload during rendering
• Performances: Fixed SMAA executed before tone mapping in post processing chain
• General: Bugfix and general polishing
  

This update will be released to the public in a few days, but before doing this we need your help.
We'd really appreciate if you can help us in testing this HUGE update and report any issues or problems on our communication channels (as stated below).

To download the update, you can access the BETA branch from Steam following these steps:
1) Right click on Racecraft on your Steam library to open the context menu
2) Click on the "Properties" entry
3) Open the "Betas" tab (if you don't see it, restart Steam and repeat steps 1 to 3)
4) Enter the code "proceduralbeta" (lowercase, it's case sensitive) in the "Enter beta access code to unlock private betas" and click on "Check Code"
5) If the message "Access code correct, private beta 'beta' is now available" appears, the Beta should be available
6) Select BETA from the dropdown menu above (if you don't see BETA, restart Steam)
7) The update will be downloaded automatically if you have automatic updates on
8) When you want to go back to the official version, select NONE from the dropdown menu

Reply ONLY to this thread if you experience issues or bugs and send the crash reports through the Crash Report game utility. Always indicate the following details when reporting a bug/issue/crash on the thread:

• Your Steam ID
• Windows OS version
• Hardware specs
  

IMPORTANT NOTE
We know there are some game crashes and unfortunately some people can't play, but several times these issues stem from outdated graphics drivers or operating system, so we highly recommend to check if your OS is updated and if you have the latest graphics drivers installed.

Known issues

• During Early Access, saved tracks and all related elements (ghosts, other options) will be wiped frequently because of technical upgrades to the procedural engine and other parts of the game. We apologize for any inconvenience this may cause.
• The game stutters during the first couple of generated tracks: this happens because it's generating and caching shaders
• If you have more than one control device connected to your system, disconnect the one you're not using to avoid crashes or calibration issues
  

Thanks for your support and good testing!
Racecraft DevTeam

Last month I mentioned that the USF2000 was almost ready and some of you have been asking when it will be released. I am happy to announce that it will be released on Wednesday, November 23rd. This release features the 2016 car and teams, and we are happy to announce that we have also licensed the 2017 car. The 2017 chassis, which is very similar to the F4 car, will be released somewhere next year.We also wanted to take this opportunity to congratulate our fellow simracer Pablo López on being selected by our colleagues at iRacing to take part in the Mazda Road to 24 Shootout. Since that event took place at NOLA Motorsports Park we sent him an early build of the layout he would be driving to practice.

Community wise we updated our forums and, behind the scenes, also moved our beta forums to this new location. Over the next couple of weeks we will be moving more of the website, including the development blogs, some of which have already been moved.
Development has been focussing on the DX11 engine and laying down the groundwork for our new UI. There’s not much we can show here yet until we’re a bit further along, but we are very happy with the current progress. In the mean time we are getting closer to our next Steam-only build. Remember to take advantage of the free option to migrate to Steam if you have not done so yet. Apart from a lot of smaller fixes this build will also feature the work we’ve done with the Stock Car community and we hope this will make rFactor 2 an even more enjoyable simulation for oval racing. As soon as the new build is out, we will also update you on Fallston.
Another new feature we would like to announce is support for paid content. It will integrate nicely with our workshop, and modders will also be able to leverage it to sell their creations. Obviously we would like to use this feature to offer you a wide selection of high quality and high profile content. This does not mean that all future content we create will be paid though.
That’s all for the second monthly update. Happy Simracing!

Inoltre sono state già previste novità anche per l'immediato futuro:

• controllo della vettura nella pitlane
• dati a schermo aggiornati e migliorati
• sistema delle bandiere
• sistema ratings per il multiplayer
• supporto alla VR ed al triplo monitor
• circuito di Silverstone
• nuove vetture: monoposto Formula RaceRoom 3, Formula RaceRoom US (ovvero la Indycar 2016) e modelli GT3 (Audi R8 LMS 2015, BMW M6 GT3, McLaren 650S GT3, Volvo Polestar S60 WTCC)
  

Vi ricordiamo che fra 3 ore, alle ore 20 italiane, il team Sector3 presenterà in un apposito streaming live tramite Twitch, tutte le novità in arrivo con l'imminente update di RaceRoom Racing Experience. Fra gli aggiornamenti disponibili vi ricordiamo che troveremo maggior trazione e grip, fisica e dinamica dei veicoli perfezionate, nuovi dati a schermo, bandiere funzionanti e persino un primo approccio alla VR.
The wait is almost over! Tune in on Monday, 14.11.2016 at 8pm CET when Sector3 Studios will host a LIVE dev stream on twitch.tv to inform you about all the details of the upcoming patch and the future plans for RaceRoom!

MaxTM is a telemetry tool for GPB, MXB, WRS and KRP: it allows to display graphs of the telemetry data exposed by GPB/MXB/WRS/KRP. It has two main components:

• A GPB/MXB/WRS/KRP plugin: in charge to generate the telemetry data files.
• A viewer application: in charge of displaying graphically the telemetry files saved by the plugin.
  

DOWNLOAD v1.13: <<-- THIS if for GPB beta9, WRS beta9 and KRP beta15
DOWNLOAD v1.12: <<-- THIS if for MXB beta4

INSTALLATION

• Download the archive from the link above and extract it somewhere. Inside the main folder you should have 4 extra folders: one for the plugin(s), one for the viewer and 2 folders with sample data.
• Take the viewer folder (MaxTM_Viewer-vX.Y) and the 2 sample foders and put them somewhere (Desktop, Documents, wherever you have write rights). DON'T PUT THEM IN Program Files OR SIMILAR. The viewer is a portable app: it does not write anything in the registry, it requires no installation (in the Windows sense) and it won't ask you if you want to install a stupid toolbar.
• Now run the viewer application (MaxTM_Viewer.exe and check it starts without issues. If it complains for missing dlls, you may need to install Microsoft Visual C++ 2015 Redistributable Package (x86): once you press Download, select the x86 version "vcredist_x86.exe".
• If you want to generate telemetry data from GPB/MXB/WRS/KRP you have to install the plugin: in the plugin folder (MaxTM_Plugin-vX.Y) you have 4 .dlo files (one each for GPB/MXB/WRS/KRP) and a folder named MaXTM_data. Just copy the appropriate .dlo and the MaXTM_data to the GPB/MXB/WRS/KRP plugins folder.
• Restarting GPB/MXB/WRS/KRP and going to the track you should hear a heartbeat sound each time you start a run: this confirm that the telemetry logging is active.
• You can also press 'Z' to see is if logging is currently ON or OFF, and CTRL+Z to toggle it ON/OFF. You can change the key in the .ini file of the plugin (MaxTM.ini, in the GPB/MXB/WRS/KRP data folder).
• Telemetry log data will be saved (2 files per run) in folder MaxTM under GPB/MXB/WRS/KRP data directory (e.g. C:\Users\MaX\Documents\PiBoSo\GP Bikes)