Oh my, oh my... I feel like it's Christmas - I pretty much solved my problem :elefant:
I just tried running 12 instances of LFS - FPS was crap with that many, sure, but regarding the responsiveness of the computer (which was by far the most annoying and biggest issue), it felt like it was 90+% responsive.
I just marshaled the 8h IGTC race last Saturday (before I fixed the problem). Chatting on IRC on the side was painful with just 1 instance running - 2 felt like.. well, doesn't matter - just go watch my Youtube video and imagine having to chat with that kind of updates. Jikes!
Although I haven't been looking hard lately, I found it to be difficult to Google the issue - but I finally found something - so here it is - and I found it when I wasn't looking for it :hypnotize http://forums.nvidia.com/index ... iew=findpost&p=570733 (post #2. I can't seem to link directly to it).
Who would ever had though that?? Really? Now that I know exactly what the problem is, I also know that I actually saw the first symptom some 1-2 years ago, when I bought a new mouse. It lags badly whenever I render. So bad that I eventually made a .bat file to always start the 3D app with lowest priority - because if not, then once the render had started, I often had to wait for it to complete before being able to do anything with the PC - but the mouse lag is complete gone too. I just rendered 8.000.000 polys and PC was like.. gimme more. I need polys nom nom!
I've had major sound stuttering issues too (which actually were what I was trying to look for when I found that threat - I had completely given up on solving the "LFS issue"). I had them first time when I installed Vista some 10 months ago. then on Win 7 TC.. a little tiny bit on CP 64 - none at all on XP 32 and I just installed Win 7 final tonight.. stutter as hell, which made be go look for a solution again again.. but sound stuttering is completely gone now after the fix (LFS behaved as before too on Win 7 - so it's not a Win 7 thing!).
3 seemingly different issues, but they are all caused by the same thing.. and yaya "now I can see how they connect". So great to be hind sighted
...imma go dance now :monkey:
Oh btw - that app thingy you can test with - before solving the issue: Bars were about halfway up to yellow or even red occasionally. In idle mode. Holding down F5 on desktop = constant red bars.
After the fix: barely come up half way up to yellow line - with F5 or whatever. Epic win!
Edit: an important note - in the guide it's mentioned to set the PCI Frequency to more or less than 100. I fixed my issue by setting it to 90 - more than 100 didn't work for me.
Looks like very bright hotspots to me (judging by the placement of the different "pixels" - doesn't appear to be random).
See if there is anything called clamp or clip in the renderer options or framebuffer perhaps - I don't know Blender, so can't point to the exact location. But it should be somewhere.. I think.
If I'm right, then whats happening is that the hotspots (reflections of the lightsource or whatever it is) are so bright that the intensity differences to the neighboring pixels are too great for the anti aliasing to kick in. So, what you need is to tell the renderer to clamp/clip the values so they fall within a lower dynamic range. That way they are much more likely to be be antialiased properly and look better.
Ps. not seeing them in lower quality only means that the renderer isn't aiming for as great precision, and can therefor miss the areas that has these spots. Try moving the cam to the side and see if the spots shifts places as well (like reflections would behave) - if yes, then that's defo your problem.
there have been a number of hardware based rendering accelerators for 3D, and so far they have all failed - don't ask me why. CPU is just the way to go.
That's a cool render (FOX render too) - I love the floor. But you really need to tighten up the smoothings on the car which will improve overall shading, and use a different refl map/shape. the current one isn't really doing the trick IMO.