Assetto Corsa

Has anyone else had a weird thing happen,ie when racing the ai if you quit before the end of the race I've twice been recorded lap times much quicker than I've actually done?
Both instances happened a fair time ago,so hope maybe it's been fixed during various updates.
What reminded me was just now doing a few laps using a new g27 wheel,happened to do 3 laps round mugello beating my previous ghost,not quick as I'm adjusting to wheel,but I did a 1.50,on my records for that car and track it shows my best lap as a 1.46.7
Remembered ages ago game gave me that wrong time after quitting against ai,my view is if that's happened to me,then it must also have happened to many others from the thousands playing,I've not dl'd any lap time apps,and hope full game will wipe boards and have inbuilt leaderboards,otherwise a risk of leaderboards full of fake times.
 
Recently got a G27, I nearly broke my wrists and arms with the force feedback. fun times! :D

I had to turn down the force to 35% so its enough for me to feel the grip but not wrenching the wheel out of my hands......

Drifting with the wheel is so much easier :D
 
When you use the Pg Dwn key to reduce the HDR intensity, is there a way to save the setting as when I load the game again it forgets everything?

There is some .ini file with default exposure setting for each track, but I cant remember where it is or where I read about it. If I come across it again, I'll post here.
I'll try your LOD -1 settings in inspector tonight as well, thanks for sharing. although from both of you screenshots it seems like negative lod has brought in blurring - look at the dials, they were more crisp in your first pic.

Has anyone else had a weird thing happen,ie when racing the ai if you quit before the end of the race I've twice been recorded lap times much quicker than I've actually done?

I suggest you post this in bugs section on Ac forums, sounds like a bug to me. http://www.assettocorsa.net/forum/index.php?forums/gui-huds-apps-bugs-issues.18/
 
Recently got a G27, I nearly broke my wrists and arms with the force feedback. fun times! :D

Then you have it set way way to high..



BTW the X8 SGSSAA set in the inspector tried it last night my god it does make the game look lovley. But killed my frames i was down to 40fps with a full grid. KNocked it down to 4xSGSSAA gave me better performance but no where near the 70+ I aim for.

What GPU is needed to run this with that kinda AA involved. Im using 4x AA in game.

basic spec 1920x1200 580gtx 2500k 8 gig of ram. Is my GPU letting me down ?
 
Yeah, SSAA does kill frames, I've suggested it to Josh86 since he has gtx780 ;) 580 is probably not enough, unless sub 60fps is acceptable. I run 4x SGSS myself.
 
Sub 70 isn't enough for me. I prefer frames 90+ on racing games. My settings give me between 70 and my 91 fps cap on full grids.

Ill leave it as it is thanks though, does look a million times better maybe one for replays.
 
There is some .ini file with default exposure setting for each track, but I cant remember where it is or where I read about it. If I come across it again, I'll post here.
I'll try your LOD -1 settings in inspector tonight as well, thanks for sharing. although from both of you screenshots it seems like negative lod has brought in blurring - look at the dials, they were more crisp in your first pic.



I suggest you post this in bugs section on Ac forums, sounds like a bug to me. http://www.assettocorsa.net/forum/index.php?forums/gui-huds-apps-bugs-issues.18/

FXAA blurs and darkens the image somewhat, I think that is what caused the dials to look less crisp. The previous LOD may have made the dials look more shimmery. I'll take some screenshots showing various options tonight, so prepare for this thread to get bombared with pics :p :eek:
 
Sub 70 isn't enough for me. I prefer frames 90+ on racing games. My settings give me between 70 and my 91 fps cap on full grids.

Ill leave it as it is thanks though, does look a million times better maybe one for replays.

The game still isn't consistent yet imo. I still get drops down to 45FPS under certain scenarios and I notice it does stutter at those frame rates. I measured CPU utilization with 25 cars on track and it was around 59% across all cores, but this was using Windows System Performance utility.

You can see my system specs and game options here:
PC Specs:
i5 3570K 4.5Ghz | SLI GTX 670 1280Ghz | 16Gb Samsung Green 2133Ghz | 256Gb Samsung 830; 2TB Hitatchi Deskstar | Asus Sabertooth Z77 | Corsair 650D; Noppoo Choc Mini/G700s; Audio Technica ATH-AD900X; Asus STX; Sinus Live Bass Shakers; Sony DA2400ES | Monitor- S27A750D | Wheel - TH500RS; TH8RS | Windows 8.1

Graphic Settings:
http://i.imgur.com/8fWy90l.jpg & http://i.imgur.com/vwWbmFI.jpg & http://i.imgur.com/b31bydQ.png

I don't want to lose any eye candy but I can sacrifice 120hz gaming in favour of a steady 60FPS.
 
I've downloaded the new rFactor2 build today and was reminded that it has exactly the same issues with AA- ingame AA is there just for show (unless you combine with fxaa), SGSS through inspector is the only way. I wonder if its the same with pCars?
 
Finally got xfire working correctly without random flickering all the time by switching off HDR

fps gain is fantastic with both cards enabled:)
 
Damn you people just splashed out on a G27, then decided I needed a new KB so got a K90, then decided I needed a new PSU to run it all.

Should be spending a good amount of time on Sunday setting up the wheel.

Does anyone use a Sweetfx config for the game? Seem one about that looks ok.
 
Sorry about that :D G27 should last you many years of fun racing and drifting, good choice! You didnt really need the new PSU to run your G27 and keyboard though :p

I've downloaded the new rFactor2 build today and was reminded that it has exactly the same issues with AA- ingame AA is there just for show (unless you combine with fxaa), SGSS through inspector is the only way. I wonder if its the same with pCars?

I'll answer this myself: these issues with AA are due to the now popular "defered rendering" engines. PCars runs it as well.

(http://en.wikipedia.org/wiki/Deferred_shading) "due to separating the lighting stage from the geometric stage, hardware anti-aliasing does not produce correct results any more: although the first pass used when rendering the basic properties (diffuse, normal etc.) can use anti-aliasing, it's not until full lighting has been applied that anti-alias is needed. One of the usual techniques to overcome this limitation is using edge detection on the final image and then applying blur over the edges,[6] however recently more advanced post-process edge-smoothing techniques have been developed, such as MLAA[7] (used in Killzone 3 and Dragon Age 2, among others), FXAA[8] (used in Crysis 2, FEAR 3, Duke Nukem Forever), SRAA,[9] DLAA[10] (used in Star Wars: The Force Unleashed II), post MSAA (used in Crysis 2 as default anti-aliasing solution)."
 
Last edited:
The lighting needs looking at in the game. Different views will give you totally different sky colours. This is with HDR enabled and no changes to any config files or Exposure.

vyqhZoZl.png.jpg
SliFRZVl.png.jpg

With Sparse Grid Supersampling turned off it goes back to normal

pD0Ff0Hl.png.jpg

Also I don't even think it makes any difference eliminating the jaggies tbh.
 
Last edited:
The lighting needs looking at in the game. Different views will give you totally different sky colours. This is with HDR enabled and no changes to any config files or Exposure.

vyqhZoZl.png.jpg
SliFRZVl.png.jpg

With Sparse Grid Supersampling turned off it goes back to normal

pD0Ff0Hl.png.jpg

Also I don't even think it makes any difference eliminating the jaggies tbh.

:confused: So surely it's not the game if it's Inspector doing the SGSSAA ? With it turned off the game is correctly exposing the cockpit.

Look at the screenshot with it turned on, the cockpit is much lighter. I'd say that the exposure is being pushed up all round, it's not just the sky.
 
Last edited:
Yeh, I'll post it on the NVIDIA forums. Hopefully there is a fix alongside their new drivers.

Edit - I just find it odd that when you change view with Sparse Grid Supersampling enabled that the exposure levels go back to normal. So I wasn't sure if it was an issue with the game or driver. Either way I've posted it on GeForce forums.
 
Last edited:
im just using my crappy 10 year old 360 Modena Steering Wheel, Shifter and Pedals lmao. Obviously not a patch on a G27 with force feedback, but it'll paint until I win the lottery.
 
The lighting needs looking at in the game. Different views will give you totally different sky colours. This is with HDR enabled and no changes to any config files or Exposure.

vyqhZoZl.png.jpg
SliFRZVl.png.jpg

With Sparse Grid Supersampling turned off it goes back to normal

pD0Ff0Hl.png.jpg

Also I don't even think it makes any difference eliminating the jaggies tbh.

Why didn't I think of disabling HDR. :rolleyes: :D

HDR: Disabled
sgssaa: X4

tGA8VXIl.png.jpg

So there is something broken atm with how SGSSAA and HDR are used together.
 
Back
Top Bottom