Well, thats one way to get PC owners to consider an Xbox One X
Game will probably run better on the original Xbone than on slightly old i7's.
Well, thats one way to get PC owners to consider an Xbox One X
Of the whole thing, that's your problem? That I used one word wrong (use instead of max)?
Here:
Of the whole thing, that's your problem? That I used one word wrong (use instead of max)?
Here:
Of the whole thing, that's your problem? That I used one word wrong (use instead of max)?
Here:
Menus are stuttery on Xbox as well. Gameplay runs smoothly though.So heavy stutter in menus is because of this? Or another poor optimization issue?
so this is why it runs like crap on PC? wtf
That's a relief!Thats...odd.
Menus are stuttery on Xbox as well. Gameplay runs smoothly though.
Of the whole thing, that's your problem? That I used one word wrong (use instead of max)?
Here:
Of the whole thing, that's your problem? That I used one word wrong (use instead of max)?
Here:
Of the whole thing, that's your problem? That I used one word wrong (use instead of max)?
Here:
YesI've never heard of multithreading causing input lag. Is this legit?
Just a bit of insight, there is actually some advantage to eliminating as much context switching as possible from a programming perspective, and it can reduce latencies in certain scenarios. Node.js is the new hotness and is entirely single-threaded.
That said, i don't know if it this excuse has any legitimacy. The xbox version being 60fps would have me learn towards no..
Well that's a great attitude to have.As long as I get constant 60 FPS I don't see the problem.
Note to that those with stutter : how can you be sure this is the issue ?
It's absurd. Seems more like an excuse than an actual reason to do this to the port. Got to make the Xbox One X's 2.3GHz Jaguar look good.It's weird, since Turn 10 would have had to multithread the snot out of Forzatech to get it running as well as it is on the Xbone. Them continuing to think that you should them undo all that work for a PC version is completely baffling, especially after Horizon 3 PC's less-than-warm reception on launch for this exact same issue.
Technically there may be latency benefits to what they're doing.Just a bit of insight, there is actually some advantage to eliminating as much context switching as possible from a programming perspective, and it can reduce latencies in certain scenarios. Node.js is the new hotness and is entirely single-threaded.
That said, i don't know if it this excuse has any legitimacy. The xbox version being 60fps would have me learn towards no..
Now I need to know the source of the video
I've never heard of multithreading causing input lag. Is this legit?
Here:
As long as I get constant 60 FPS I don't see the problem.
LolWell, thats one way to get PC owners to consider an Xbox One X
Of the whole thing, that's your problem? That I used one word wrong (use instead of max)?
Here:
Of the whole thing, that's your problem? That I used one word wrong (use instead of max)?
Here:
It doesn't suck, but theres random stutters especially in the menus
It could definitely run better, but in game it ran perfect for me tbf
Unless it runs like shite, I don't see an issue with this
I guess the rest of the cores will be used for 4K gaming on the One X version
Of the whole thing, that's your problem? That I used one word wrong (use instead of max)?
Here:
it freezes for some people for a few secondsThe guy said that it's normal for one core to run at near 100%. Not that the game only uses a single core. And yes, his latency excuse could be valid. Thread interference is a real thing when trying to access shared resources between multiple threads etc.
I've only seen the stuttering on the menus. Do people have it happening during gameplay? Just saying I've ran the demo on slightly older hardware that I didn't think would make the cut, but it ran perfect. So, uh yeah.
intel g4560 here i come!