My game compiles shaders on every launch, is this normal?

[VerminatorX]

Can I do something so it wont do it every time?

[palto_cosis]

is normal in that kind of game

[Emotional]

no, they screw up somehow with the last update.

[Dr.Shadowds 🐉]

Yes.

1st time takes awhile because it building it. Then every other time it's just loading your built shaders.

[ninjaguyDan]

Originally posted by Dr.Shadowds 🐉:

Yes.

1st time takes awhile because it building it. Then every other time it's just loading your built shaders.

No. That's how it should work. That's how it worked for me in the beginning. But, like OP, since the S1 update I now have to build them each time I start the game.

And when I do, it pushes my CPU temps to 92 C, which is certainly damaging my processor if it has to do it every time.

[IndianaJones]

Originally posted by VerminatorX:

Can I do something so it wont do it every time?

Mine does too, and no it's not normal.

The precompile shaders should be done once to avoid compiling them on the fly during gameplay, which cause game to stutter.
Shaders could be also recompiled upon GPU driver update or major GPU settings changes.

I do not think the game compiles the whole shaders though, it kinda verifies them or just wrongly compiles some part of it every game launch.

IMHO should be fixed ASAP, along with GPU crashes.

[VerminatorX]

Originally posted by ninjaguyDan:

And when I do, it pushes my CPU temps to 92 C, which is certainly damaging my processor if it has to do it every time.

That's exactly my concern. It does not take long for me, but my CPU usage and temperature spike dangerously during this compiling.

[Dr.Shadowds 🐉]

Originally posted by ninjaguyDan:

Originally posted by Dr.Shadowds 🐉:

Yes.

1st time takes awhile because it building it. Then every other time it's just loading your built shaders.

No. That's how it should work. That's how it worked for me in the beginning. But, like OP, since the S1 update I now have to build them each time I start the game.

And when I do, it pushes my CPU temps to 92 C, which is certainly damaging my processor if it has to do it every time.

For me takes 2-3 seconds on the screen while usage goes up I agree it's concerning. Now I don't go 92C, it only went up to 70 ~ 73c which I have Ryzen R9 7900 that air cool btw.

I was in open beta, and whatever they been doing from then to the main release, they've done something to be like this, even microstutter issues wasn't there as it was before, not sure why they change things to how they compiles shaders, or what with their odd microstutters that wasn't there before.

All I know for currently in my case Microstutters is mostly resolved when change windows setting of Control Flow Guard from on default to off default. Since this game built on UE5 I'm not really shocked of some kind of problems. So overall I do think they need to make changes, and correct things.

[Luckiernut]

Yeap, normal

[MisterSmellies]

You can blame unreal engine

[Peek]

> And when I do, it pushes my CPU temps to 92 C, which is certainly damaging my processor if it has to do it every time.

TO be fair, your comp should never really reach that temperature in the first place. It's standard practice to use burnin software (e.g. passmark) after you've built a computer to test that its cooling solution is adequate at keeping the temperature sufficiently low even under full load.

If you're CPU is actually reaching such dangerously high temperatures consistently and across all cores, you should consider lowering its frequency or improving its cooling

[Peek]

Originally posted by VerminatorX:

Originally posted by ninjaguyDan:

And when I do, it pushes my CPU temps to 92 C, which is certainly damaging my processor if it has to do it every time.

That's exactly my concern. It does not take long for me, but my CPU usage and temperature spike dangerously during this compiling.

To be fair, your comp should never really reach that temperature in the first place. It's standard practice to use burnin software (e.g. passmark) after you've built a computer to test that its cooling solution is adequate at keeping the temperature sufficiently low even under full load.

If you're CPU is actually reaching such dangerously high temperatures consistently and across all cores, you should consider lowering its frequency or improving its cooling

[Chaosolous]

Normal for this game, not normal in general.

[Octarius]

No, it's not normal. I had one long shader loading after installing game for the first time and now got express one before every launch. I had your problem but with Horizon: Forbidden West and it seems it's Radeon issue. With Nvidia card you need to increase shader GB limit in Nvidia panel to make it go away.

[Squirtle®]

Originally posted by Octarius:

No, it's not normal. I had one long shader loading after installing game for the first time and now got express one before every launch. I had your problem but with Horizon: Forbidden West and it seems it's Radeon issue. With Nvidia card you need to increase shader GB limit in Nvidia panel to make it go away.

What should we set or shader GB limit to (Nvidia)?

[Xilo The Odd]

Originally posted by ninjaguyDan:

Originally posted by Dr.Shadowds 🐉:

Yes.

1st time takes awhile because it building it. Then every other time it's just loading your built shaders.

No. That's how it should work. That's how it worked for me in the beginning. But, like OP, since the S1 update I now have to build them each time I start the game.

And when I do, it pushes my CPU temps to 92 C, which is certainly damaging my processor if it has to do it every time.

i'd get a better cooling solution for your CPU then, mine doesnt get that hot doing this.

but i'm also not over volting it and pushing it so that all cores run its boost clock speeds. i can certainly make it that hot. but i can also certainly make it less hot just by tuning it.