Mugello WIP: bugs

Sergey Moskovkin wrote:Hey guys, thank you very much for ability to take a part in your test race at Mugello track

Here is some feedback from me:









Also track seems to be heavy for video card - even my GT9800 had some troubles to get good FPS (until I turned off supersampling in nVidia panel).

Is the short version of Mugello ready to use? Cause I can't complete a lap there now. I can do it now

M Carey wrote:Noticed the same stuff. Had fairly low FPS as well (Min 13, Max 122, Avg 84) so couldn’t race online but it’s good to see your scratch build has the same lovely flow as other versions of Mugello

Sergey Moskovkin wrote:Lets see...

My PC configuration:

Hardware:
Inter Core2Duo E8400 3.00Ghz
4Gb System RAM
Gainward 9800GT Green Edition 1Gb RAM (this is a bit underclocked version: graphics clock is set to 550Mhz against stock nVidia 600Mhz)
Monitor: SyncMaster P2350
Resolution: 1920x1080@50Hz

Software:
Windows 7 Home Premium x86
nVidia drivers version 197.45
netKar PRO 1.1 Final

FPS problem:

I have low FPS only when I use Antialiacing Transparency set to Supersampling (it's off by default in nVidia control panel), so a lot of objects eats a lot of performance with such settings. After I've turned it off - all back to normal and I've got solid 50FPS (at least alone, cause that race was my first one on this track and I couldn't fight in front or middle of traffic). In NKP I have all graphix settings to Max and vSync is on.



So, you clearly can see that FPS wasn't a big problem in my case, but I really don't know what could be wrong with ATI (M Carey case). Anyway seems to be a version with textures in normal resolution (less then HD at least) may be a good idea


Thank you for your time guys

Sergey Moskovkin wrote:Thank you for replies guys


@Albert McSaltens

Such resolution isn't a big problem for 9800GT, because it has four times more power then 9500GT. I have no problem with iRacing at 1920x1080@50Hz at all - it eats a lot of performance.

And at the moment I don't have programs which require to address more then 3.25Gb, so 64 bit a bit useless for me


@laurent resende

Yeah, vSync eats some, but I just hate tearing and that's why I use 50Hz instead of 60Hz. As I described above my problem was Supersampling option. Now it's gone - I even can record a movie by Fraps

Albert McSaltens wrote:
well but if you use 32 bit you have 3,25 but you use of those 3,25gb one for graphics, so you end up with 2,25 gb for windows resources and programs. if im not wrong using 64bit then you would have more memory for programs.
.but i could be wrong because im not sure if the graphics card uses his own ram and let the system ram intact someone could explain that?

Sergey Moskovkin wrote:

Albert McSaltens wrote:
well but if you use 32 bit you have 3,25 but you use of those 3,25gb one for graphics, so you end up with 2,25 gb for windows resources and programs. if im not wrong using 64bit then you would have more memory for programs.
.but i could be wrong because im not sure if the graphics card uses his own ram and let the system ram intact someone could explain that?

As far as I know graphix card and other stuff uses exactly the rest of my 4Gb RAM - 0.75Gb, which I can't use with x86 system.

Sergey Moskovkin wrote:Here are FPS results (min - average - max):

Mugello Full

vSync OFF - Supersampling OFF
All - Solid 126

vSync ON - Supersampling OFF
All - Solid 50

vSync OFF - Supersampling ON
Open Wheels: 56 - 70 - 88
Abath 500: 37 - 44 - 55

vSync ON - Supersampling ON
Open Wheels: 37 - 44 - 55
Abath 500: 25 - 33 - 50


Aviano Full

vSync OFF - Supersampling OFF
All - Solid 126

vSync ON - Supersampling OFF
All - Solid 50

vSync OFF - Supersampling ON
Open Wheels: Solid 126
Abath 500: 65 - 70 - 78

vSync ON - Supersampling ON
All: Solid 50

René Lorig wrote:That is at T1: Some Textures wrong, and lightning "bug" (nearly everywhere on the track)