Some liveries look really bad on Xbox
As the title says, some liveries look really low quality and pixelated, specifically on the halo. Has anyone got this issue? On series X. I’ve attached images of the triple crown and rb19 Miami liv...
Forum Discussion
@mariohomoh Playing on XSX on quality mode but it’s weird it’s only on some liveries
@chubsterdubster Not necessarily weird.
Your console has a finite amount of computing power for rendering the graphics, computing all the calculations the engine needs, and executing all the tasks the game asks.
To sort it out and offer a good compromise, considering that the resource consumption is always fluctuating, one trick devs use is the dynamic resolution feature.
On high demanding scenarios, e.g. race start with a full grid or when the car in front of you hit the barrier and the system needs to work out all the physics and debris and visual effects, the app will kick in a lower resolution for a few assets, requiring less power from the console.
So it's very likely that the game has a 4k, a 2k, a FHD, a 720 and perhaps even a 480p texture for most assets you see on screen. Cars, track and scenario objects, etc.
Looks like the game thinks it needs to ease off on the resource consumption at those moments you took a screenshot, so it had a lower res texture of that particular livery being rendered by your console.
Why? Was it indeed a very power hungry instance, with plenty tasks being run by the console on the background? If so, then maybe functioned correctly, and it needed that lower res texture to keep your framerate stable at 60fps.
But what if that was not the case, what if you were on time trial or on a session with most cars still in the garage and very few tasks running in the background for the console to deal with? What if your system still had plenty of juice to render the 4k version of that livery?
We don't know 🤷
And that's precisely why session report codes are needed, as well as a rundown of settings etc. So that the devs can check if the dynamic resolution feature was indeed working as intended, or it needs some tweaking. Perhaps it just so happens that that particular 1080/720/480 whatever version of that particular livery is just not that good, and the design team can redo it better, with less perceivable compression artifacts or the like?
🤷
Your console has a finite amount of computing power for rendering the graphics, computing all the calculations the engine needs, and executing all the tasks the game asks.
To sort it out and offer a good compromise, considering that the resource consumption is always fluctuating, one trick devs use is the dynamic resolution feature.
On high demanding scenarios, e.g. race start with a full grid or when the car in front of you hit the barrier and the system needs to work out all the physics and debris and visual effects, the app will kick in a lower resolution for a few assets, requiring less power from the console.
So it's very likely that the game has a 4k, a 2k, a FHD, a 720 and perhaps even a 480p texture for most assets you see on screen. Cars, track and scenario objects, etc.
Looks like the game thinks it needs to ease off on the resource consumption at those moments you took a screenshot, so it had a lower res texture of that particular livery being rendered by your console.
Why? Was it indeed a very power hungry instance, with plenty tasks being run by the console on the background? If so, then maybe functioned correctly, and it needed that lower res texture to keep your framerate stable at 60fps.
But what if that was not the case, what if you were on time trial or on a session with most cars still in the garage and very few tasks running in the background for the console to deal with? What if your system still had plenty of juice to render the 4k version of that livery?
We don't know 🤷
And that's precisely why session report codes are needed, as well as a rundown of settings etc. So that the devs can check if the dynamic resolution feature was indeed working as intended, or it needs some tweaking. Perhaps it just so happens that that particular 1080/720/480 whatever version of that particular livery is just not that good, and the design team can redo it better, with less perceivable compression artifacts or the like?
🤷
- @mariohomoh Right ok I get what you’re saying. Do you think I should put something on the technical problems page?
- @chubsterdubster That will definitely be helpful, pal!
When you click on the create a new thread button, a form will appear. Just fill it up the best you can, having in mind that it is a step-by-step guide for the devs to reproduce the problem and investigate. Some fields may not make complete sense, but most of them are actually pretty useful.
Heh, imagine if there's an issue with a texture not loading up correctly that only happens on My Team in the Hungaroring. Then people report it without many details, the devs load it up on a Time Trial session on whatever track, and it all looks ok? The issue would understandably fall in the "can't reproduce, let's wait" hypothetical bin.
Anyway, hope it gets sorted out. That triple crown livery is looks Good! 💞👑💞I would like to mention this issue once more.
FOM livery is very low quality on XBOX Series X 4K@60p.
@mariohomohHonestly it just looks more like a low pixel graphical design, created that will only look good if shrunk down. Then they had to blow it up to a larger size to fit the halo than originally intended, created the low rez effect. It's all mickey mouse in the quality department. Example take a look at the word "Gulf" on the halo of the new 800 Williams livery. The word looks slightly crooked and the "G" is partly cut off. These things have nothing to do with restraints of hardware power, give me a break! Your explanation is way over complicating the real issue!!
@Halpen4 Did I ever preclude other reasons for the low quality visuals? Does your "low pixel graphical design" hypothesis preclude mine?
Was the "new 800 Williams livery" even revealed when I made that post?
You can gave as many breaks as you want from me, pal. We're clearly not even on the same page, your animosity is misdirected 😉
@mariohomohNo animosity here, why would there be? I don't even know you. my reaction was simply to the fact your explanation was 6 paragraphs long. We both want the same thing at the end of the day. I only made my possible suggestion of the problem what I said, based on the fact I work in a digital printing facility. People do it all the time, when they look at an image on a computer screen, and it looks high quality... Until they want it used to put on a shirt or poster, and only then is the image suddenly all pixilated and awful. Never mind the fact I've had that Williams Gulf livery since the week before the Silverstone race, so like for 2 or 3 weeks. Seriously, I wasn't checking with when you commented and comparing the date of the 800 livery, but... That is pretty funny for you to say!!
By "animosity" I was referring to this part:
@Halpen4 wrote:These things have nothing to do with restraints of hardware power, give me a break! Your explanation is way over complicating the real issue!!
Didn't sound chill in my book.
Anyway, that's beside the point. By dynamic resolution and "hardware power" I was referring to this:
Specifically what Linus refers to when he goes on to talk about MIP Mapping at the 2:40 mark. Not exactly what the game is using, but you get the gist.
Dynamic resolution is a commonplace technique these days and Digital Foundry shows on their review:
If it was only a matter of a "low pixel graphical design" from the get go, shouldn't those textures look pixelated as shown by OP all the time?
That's not the case. My Red Bull decals on the halo looks like this (pic below), nowhere near as bad as OP's, and I'm on PS5:
And it's not like I have different texture files as him.
Hence my mentioning of the lower res versions of those textures not being up to par, or the dynamic res being too aggressive and kicking in even when the game can still hit its performance benchmarks.
So it's like the game prints the thumbnail version of the graphic because it thinks the performance will drop if it keeps the full res version on.
- @mariohomoh what you took personally as animosity was me stating a fact, that if the problem IS in fact as simple as I described it... Then I stand behind my statement! That's all, it would seem to me at this point you're reading into things a little too far. Either that man, or you have real thin skin to think I was coming at you with animosity! Geez, you should see me when I do use animosity then, lol... Lighten up! Oops... You'll probably take "lighten up" the wrong way too. It's not an insult, just a suggestion to relax!!
Featured Places
