Jump to content

Remij

Hermits
  • Content Count

    39,397
  • Joined

  • Last visited

  • Days Won

    147

Everything posted by Remij

  1. Yea.. like Horizon ZD wont come to PC... the PSNow version.. THERE'S your PC version of the game™
  2. Indeed... simply because you idiots said it wouldn't happen
  3. Gonna be fun to smack you down along with Jehurey DynamiteCop knows all too well about betting against me.. Jehurey should by now but he's clearly too stupid I expect more from you though Madmal
  4. I said Steam would support the controller... they now do. Devs can do what they want. Dualsense.... is NOT exclusive to PS5 anymore bitchboy
  5. I said the controller would be fully supported... and it is. Haptics work... I'm literally playing Dirt 5 right now with haptic rumble. Developers are now free to support the controller... like I said they would... and they will.
  6. No you didn't "No.. it won't be fully supported on PC" It already is I said it would be... and it is. Any game can literally utilize the functions of the controller... and like I said some devs WILL make use of it. I bet you're feeling the haptics in your ass cheeks right about now by how hard I'm drilling you
  7. It's all I'm going to have to post any time Jehurey thinks to speak as if he's technically inclined. That image will forever be a reminder that he's fucking retarded
  8. You can add it to the same list as Horizon ZD wont come to PC, and Steam wont support the DualSense list
  9. And I'm also going to post this picture every single time and laugh at how you thought this was due to difference in hardware power and not a bug
  10. Yes.. I DO You aren't shutting SHIT down. I know A LOT more about Dirt 5 today than I did 1 month ago... you fucking clown. And I don't need to know anymore Series X information to know that this is a bug that will be fixed.... There was no PS5 version when DF did their first preview. Now there is.. and now I know there's a difference between them... and I know for a fact that it's a bug. I know the performance impact of that seeing is FUCK ALL... and my knowledge of hardware gives me the ability to tell you to your punk bitch ass little fa
  11. Yes, I do know better know. I know exactly how little the setting impacts performance. I know that dropping any other number of settings improves performance without the completely obvious visual cost. I know now how the the game adaptively adjusts each setting individually, as well as has 3 different rendering resolutions... an output res, temporal res, and back buffer res... I know a lot more now. I know the PS5 is not more powerful than Series X.. and I know that besides being a bug, there's no legitimate reason why the developer would OPT to choose that. And I can test it a
  12. No.. I'm saying at the time of the old DF vids I didn't know any better.. now I do
  13. There was no PS5 version to compare it to... and idiots weren't going on about supposed superiority of PS5 back than either.. I'm simply clearing up and explaining what the likely culprit is. DUDE... I CAN LITERALLY TEST THESE THINGS... Geometry has extremely negligible performance impact on the game... ESPECIALLY DURING the race intro... where you see the headlight and you aren't controlling the game... LOL as if they couldn't stand to have the FPS drop 5 more for that brief moment...
  14. Because it's all related to a bug... guaranteed. And no.. I'm not trying to say those things aren't as significant as car geometry.... I'm literally testing what performance impact each of the settings has... and I've already said that other settings are FAR MORE significant than Geometry... which is why the fact that it gets dropped... is so strange. Specifically when other... more taxing things... can be dropped. This will be patched.. 100%
  15. Nope... doesn't make sense in a game which can adaptively adjust every single setting independently from each other as well as resolution and temporal resolution ALL seperately. Why would the game drop Geometry instead of dropping resolution Jehurey? It's a fucking BUG
  16. No. That's fucking stupid of you to even think... LMAO. The fact is that EACH SETTING can have a dynamic value based on load independent from all the others.... Every setting can independently adjust on the fly.. LOL There's absolutely NO reason for Series X to be adjusting the Geometry setting because it barely changes framerate regardless. I already showed from Ultra Low to Ultra High is 4fps. There's OTHER settings which affect framerate far more... so dropping the geometry instead of any other number of settings is almost useless. It's 100% a bug that will be
  17. Jesus christ... I'm posting the proof right in front of you... in this game there is little to NO performance benefit from Geometry and Tessellation settings on their lowest from their highest.. I love how I can LITERALLY test this shit... and you're like... durrrrrr
  18. Mike Ybarra (former Xbox guy who has no issues talking shit about MS) lmao, you guys are jumping the gun on all this shit. It absolutely is a failure of MS though that this shit is happening at all for launch.
  19. Oh... and you thought a game developer was going to tell MS that their Tools were garbage in the interview they conducted with said developer?
  20. 10/10 AMD build breh I've got a 5950X coming as well. Gonna hold off for the 3080TI or Super w/e it is.
  21. LOL you don't even know what you're talking about... There ARE settings which affect performance....... but Geometry and Tessellation aren't them And LOL as I said.. even the next lowest setting... Low... makes the visuals look FAR better.. This is Low... Ultra low... lmao... There's absolutely NO reason for Series X to be using Ultra Low. I'm certain the issue is that this game, since on consoles it adjusts all settings dynamically on the fly (which you can also set it to do on the PC) gets bugged a
  22. Ok Void.. let me take the screenshots at the same time that they do in that comparison pic 2fps difference Yea... the Geometry and Tessellation settings aren't a bug
×
×
  • Create New...