rFactor 2 Build 930 Now Available

Status
Not open for further replies.
I am really sorry to fully agree with you, even if you and I, will receive a lot of flak from fanboys you are right.

Nothing wrong in agreeing... Voicing issues is the way forward, right?
I love ISI to bits for what they've provided me with since F1 2000. But I'd be a FEWL to ignore this elephant in that corner :) I mean I can live with half-baked features... But slow-downs during racing is a game-killer.
 
I understand that fixing some issues can be dificult, and that the cost of putting up a new version is high even to fix a small point.

But meanwhile why doesn't ISI put a warning in the download page of the demo to new potencial buyers (about fonts in Windows, about anti-aliasing not working in game, and the necessity of setting it from the video card settings, and of the rare, but real case of CPU spikes that will be sorted in a new version).

That would avoid burning away new clients and show respect for customers since day one.

Cheers

Lol. The demo is there exactly for testing the game before you buy it. If there was no demo (as for 95% of games today) it would be a different story. The ingame AA works perfectly as intended. Some older ISI tracks use sharpening of textures (there is player file setting to reduce this), which makes some white lines a bit edgy. This is fixed on newer tracks (Silverstone 1.35), it was not something related to AA anyhow but to track design.

I had reports of issues from old non-i5/i7 Quad core users last autumn as well (build 860 I think), CPU usage went to 100% with many AI. So it's not first time older CPU's has issues, and probably not last.
 
Lol. The demo is there exactly for testing the game before you buy it. If there was no demo (as for 95% of games today) it would be a different story. The ingame AA works perfectly as intended. Some older ISI tracks use sharpening of textures (there is player file setting to reduce this), which makes some white lines a bit edgy. This is fixed on newer tracks (Silverstone 1.35), it was not something related to AA anyhow but to track design.

I had reports of issues from old non-i5/i7 Quad core users last autumn as well (build 860 I think), CPU usage went to 100% with many AI. So it's not first time older CPU's has issues, and probably not last.

40-50 racers online on every race in VEC. NP - apart from 930.
 
VEC updates to new rF2 build about once a year I believe. Screenshot from Intel Q6600 user taken from FSR league Suzuka race 4.10.2014 (build 860), showing this maxed CPU bar issue.
 
MarcG, StoneC You are both very strange people. I have spent some time considering if I should go through everything single thing you have said to me in recent posts and slap it down, I have decided not to waste my time.

The CPU is quad core not dual core as you keep on saying. Quad core 3.0ghz, its no beast but it run 910 and all previous builds with its eyes shut. I have had none of the problems you say was never even possible in the first place with such CPU, you are both simply wrong about everything. The devs acknoweldged it was an issue with the build and have been very good about it, one dev made this post quite some time ago http://isiforums.net/f/showthread.p...-bar-maxed-out?p=346439&viewfull=1#post346439 I was testing the problem way back when 930 was new, with a guy running dual core 2.4 his game was running fine but my quad 3.0 was not, I do not need you to come here spouting stuff in inch high red letters desperately trying to blame problems on ANYTHING except the build. You know nothing.

Unlike you I have spent a lot (a LOT as it is not easy to reproduce) of time trying to get to the bottom of things before I opened my mouth. It seems to happen when certain tyre contact conditions become true. You boys just preen around here attacking anybody who says something you do not like which I find deplorable. Virtually every single thing you have said is totally wrong.

And this is extraordinary. At the same time as these rabid posts are coming in, I receive an unsolicited abusive PM from MarcG attacking me further! I have reported you, and I hope you get banned. Certainly, the absurdity of your behaviour grossly outweighs anything Spinelli is guilty of, he is a good guy who seems to have some typing fetish. You are acting like a crazed animal.

I have run into you two before. I made a post one day here http://isiforums.net/f/showthread.p...-Now-Available?p=332670&viewfull=1#post332670 simply saying I did not think putting builds out on sunday morning was great, the upsides are minimal, the downsides are significant. And its you two laughing it up, making me out to be some kind of baffoon saying something outrageous! I remember when you MarcG, you just could not stand not having the last word or something, and come up with this desperate straw clutch - something to do with the race rejoin - as justification for it. I recall last year SCES waiting for that it never come, it never worked for a long long time and it was silly of you use that as an argument. You just have to attack people all the time, shouting everybody down around you whilst they respect your opinions no matter how misguided they are. MarcG, I cannot say it directly as I will get banned, but you know what you are.

I hope this is not a stupid question but could the CPU spiking cause the CPU to suddenly shut down or cause the CPU to overheat? It's a new Intel 4790k, not overclocking too
 
I hope this is not a stupid question but could the CPU spiking cause the CPU to suddenly shut down or cause the CPU to overheat? It's a new Intel 4790k, not overclocking too
If a CPU is overheating, the system conducting a shutdown automaticly. In some circumstances, e.g. you`re using a stock cpu fan, a permanent spiking could evoke an overheating.
 
I hope this is not a stupid question but could the CPU spiking cause the CPU to suddenly shut down or cause the CPU to overheat? It's a new Intel 4790k, not overclocking too

4770K and 4790K I believe will begin an aggressive thermal throttle at 90C. That will slow things down so your chip has an opportunity to cool down. Any load on your CPU will cause it to warm up but with decent water cooling and a mid range OC it should peak under load testing between 50-60C.

If your PC is suddenly shutting down under load that sounds like your PSU doesn't have enough juice or it is faulty. Under load the GPU and CPU will draw more power from your PSU, if it isn't up to it, the PSU may shut down. It may sit there and idle all day fine, watching movies, etc. but in that state your PC is hardly using any power or stressing components.
 
Your computer will automatically shut down immediately when your CPU hits a certain temp. I know this from not connecting a cpu heatsink properly. :p
 
Jamie while true I assume you aren't using a Haswell? The Haswell line has voltage regulation on the CPU die. The plus side is this allows it to sip power when not under load (watching a movie, watching youtube) but it turns into a power eating chip when in use.
Haswells can get pretty hot when OC'd however this example isn't OC'd. They also aggressively thermal throttle (much more so than previous Intel chips) so to get it to the point of shutdown would require some effort. It is still possible but less likely than previous gens.
Usage spikes will also create spikes in power consumption (true for CPUs and GPUs) but temps will remain more constant assuming those usage levels don't persist.
 
System Specs

CPU: i3-3240 @ 3.40GHZ
Ram: 16GB
Video: NVIDIA Geforce GTX 760

Up to build 910 I was able to run everything smoothly in 1920x1080, settings med to high, HDR on, with many AI (30 or 40) without issue, or online with the same number of cars.
After 930, it is stutter-land, running alone, offline, everything is unsmooth, stuttered, and things get worse if I add AI or if I go online with more cars.

I think that lowering settings is not acceptable, I just want my rf2 as I have acquired it and been racing it up to 910.
Also for us southamerican people is a crazy load of bucks of investment to get a new PC, is not like I could go out and get an i7 just like that.

At the moment I simply can't start the game anymore, it's frustrating.
 
Lol. The demo is there exactly for testing the game before you buy it. If there was no demo (as for 95% of games today) it would be a different story. The ingame AA works perfectly as intended. Some older ISI tracks use sharpening of textures (there is player file setting to reduce this), which makes some white lines a bit edgy. This is fixed on newer tracks (Silverstone 1.35), it was not something related to AA anyhow but to track design.

I had reports of issues from old non-i5/i7 Quad core users last autumn as well (build 860 I think), CPU usage went to 100% with many AI. So it's not first time older CPU's has issues, and probably not last.

It's the AF setting that is not working, not the AA settings.

If you force AF through your driver you will see that the "edgy" lines are back to normal.
 
VEC updates to new rF2 build about once a year I believe. Screenshot from Intel Q6600 user taken from FSR league Suzuka race 4.10.2014 (build 860), showing this maxed CPU bar issue.

We update when the build handles endurance racing properly. That means working driver swaps, server rejoins (which is what kept us on 798 for so long), doesn't have a bug causing CPU spikes randomly (which is why we are on 910) and doesn't have any night lighting problems. These requirements have been meet more than once a year though.

All these personal attacks about the CPU bug are ridiculous. It's been acknowledged by ISI. No need to personally attack people for not being superior enough to have the most current CPU. If ISI added new features which put too much load on the CPU then it may be reasonable to up the reqs. But this is simply a bug (as acknowledged but the lead developer). It would be nice to have a fix by now, I know we (VEC) would love to take advantage of the new lighting but we can't until this CPU bug is fixed. We have large fields and the odds are high that one out of 50 is going to experience this bug. From our testing with 930 we realized it wasn't worth the risk. When one of our guys hit this bug it caused bad warping which resulted in cars colliding and spin in g off the track. This isn't something you want in a 12 hour race.

The bottom line, it's a bug. A bad one.
 
AF sharpens textures facing at angle so it will actually produce more edges in theory, but yeah it's broken in 930. No matter what AF setting is, result is same blurrish picture as you get with no AF. The clamp fix is no longer needed if you adjust "Texture Sharpening" to 0 in player.JSON. On newer ISI tracks you won't even need to change this parameter.

We will soon have opening race in FSR with about 100 racers in total over the weekend. So far 0 reports on our forums on any of these CPU issues, we'll see how it goes (not saying that this bug isn't real).
 
AF sharpens textures facing at angle so it will actually produce more edges in theory, but yeah it's broken in 930. No matter what AF setting is, result is same blurrish picture as you get with no AF. The clamp fix is no longer needed if you adjust "Texture Sharpening" to 0 in player.JSON. On newer ISI tracks you won't even need to change this parameter.

Texture Sharpening is working fine,AF X16,track Silverstone v.1.35, driver GeForce 347.88 WHQL

1=+2.0(very blurry)
View attachment 16193

4=-2.0(very sharp)
View attachment 16194

:confused:
 
Texture Sharpening is working fine,AF X16,track Silverstone v.1.35, driver GeForce 347.88 WHQL

1=+2.0(very blurry)
View attachment 16193

4=-2.0(very sharp)
View attachment 16194

:confused:

Texture Sharpening at Auto is not working because AF is not working. If AF works, you don't have to play with Texture Sharpening. Just set it to Auto and forget it.

Try AFx16 versus no AF (bi or trilinear) and see what happens without using Texture Sharpening.
 
Texture Sharpening at Auto is not working because AF is not working. If AF works, you don't have to play with Texture Sharpening. Just set it to Auto and forget it.

Try AFx16 versus no AF (bi or trilinear) and see what happens without using Texture Sharpening.

Yes it seem not to work :(

0=Off
View attachment 16195

1=+2.0(very blurry)
View attachment 16196

4=-2.0(very sharp)
View attachment 16197

5=0.0(auto)
View attachment 16198

Bi-linear
View attachment 16199

Trilinear
View attachment 16200

:(
 
Status
Not open for further replies.
Back
Top