This is BS. Motherboards don’t have much impact on performance(as they share the same chipset). It’s rather RAM/Infinity fabric, but not the motherboard.that resulted in problems especially with computers with lower quality motherboards.
This is BS. Motherboards don’t have much impact on performance(as they share the same chipset). It’s rather RAM/Infinity fabric, but not the motherboard.that resulted in problems especially with computers with lower quality motherboards.
This is BS. Motherboards don’t have much impact on performance(as they share the same chipset). It’s rather RAM/Infinity fabric, but not the motherboard.
It’s very hard to write a game that will efficiently utilize 8 cores. I think all rF2 physics + AI utilizes one core. AFAIK another one is used for graphics. Don’t know about sound - it’s often on another thread in other games.I don't know how much CPU or Cores rFactor can use. I know rF2 has a multicore support since a while but how many cores ?
Many gamers have a 8 core cpu today, this is a lot power
And yes, I was surprized how much the cpu change done with rF2..
Hi, I have the HP Reverb G2. And I have both the memories and the cpu tighter than the screws of a submarine. I've read that VR benefits a lot from the X3D cache of the ryzen 5800X3D, so I guess it will do much better with the upcoming 7000 series X3D. I'll keep an eye on the benchs when they come out.
The only stutter issues I had were related to MSI Afterburner, it seems that this app doesn't play very well with VR. It took a few weeks until I found out what caused them by this application.
This is not completely true, and definitely not that simple as suggested.This is BS. Motherboards don’t have much impact on performance(as they share the same chipset). It’s rather RAM/Infinity fabric, but not the motherboard.
Show me it when motherboards have the same chipset, same RAM speed etc.It makes a huge difference.
That's what I said.Show me it when motherboards have the same chipset, same RAM speed etc.
Expensive motherboards have more features, better VRMs so that you can overclock more.
To see correct sparks you have to turn on non-parallel projections in Pitool, notwithstanding similar option in the player.json. If sparks are critical for you I'd suggest turning on this option in both: player.json and Pitool. This way it is less costly for performance. I refused from sparks to optimize performance.Anyone with a Pimax here? I have some troubles in VR latetly. Until now i used a Samsung Odyssey Plus and was more or less fine and had no bugs. But now with the Pimax there were two bugs introduced. First i don't see any driver labels although i see them on the VR mirror and second the sparcs are complety bugged. They are 3-4 meters wide and the complety distract me while driving. Does anyone else have this issue?
I have pimax 8k plus, the tab works perfectly for me with the labels, I have the sparks disabled, when putting special effects the low will not be seenAnyone with a Pimax here? I have some troubles in VR latetly. Until now i used a Samsung Odyssey Plus and was more or less fine and had no bugs. But now with the Pimax there were two bugs introduced. First i don't see any driver labels although i see them on the VR mirror and second the sparcs are complety bugged. They are 3-4 meters wide and the complety distract me while driving. Does anyone else have this issue?
To see correct sparks you have to turn on non-parallel projections in Pitool, notwithstanding similar option in the player.json. If sparks are critical for you I'd suggest turning on this option in both: player.json and Pitool. This way it is less costly for performance. I refused from sparks to optimize performance.
doneMaybe you and @juanchioooo can hop also into my bug report and confirm this issue."