DICE Team@EA_Atic any updates yet. has this been brought up with dice. we need more transparency than this as its ruining our experience.
@EA_Atic You actually asked us to record videos and show you the issue and then all we get is silence, absolutely zero transparency.
This is really unfair, we paid our hard earned money for this game.
We deserve at least some kind of update like "the team is aware of this" just to know that our efforts were not in vain.
I don't know what is the reason @EA_Atic you are not updating us, whether it's not wanting to commit to anything or not wanting to acknowledge a major issue with the game, but try to think of it from our perspective as customers who paid and are passionate about the game (I even bought some cosmetics in hopes the game won't be abandoned).
This is just unfair...
Well this isuse is caused by render thread hitching during PSO/Shader compilation.
@NightHawkk1997 unfortnely no I dont, I mean I can block the game from acessing the cache folder, but Im not sure if it stops the entire engine from compiling, also It doesnt makes the stuttering stop so I guess it still compiling, just not writing in the folder.
Only Dice can fix this. It´s an engine issue. Would be great if they compile most PSO stuff on app startup and not during runtime/gaming. Doing this during runtime isnt recommend.
"Avoid runtime PSO compilations as they most likely will lead to stalls
Can you please respond and help us. This is totally unfair
I think he means that only DICE is able to fix it, since its an engine level problem and needs to be fixed in the game's source code.
@NightHawkk1997 Yes I agree, although Im not sure about the shader caching being the problem, I get @Flakstar explanation but this doesnt explains why it also happens on console, maybe consoles also have this caching problem? Idk, but I really wish DICE could take a look at this game breaking issue, its been a while since Im tagging Devs on Twitter with this and no awser so far
Well I believe its something in the netcode, client or even server side, but well I gave up on playing the game and you should do the same, come back when a new update arrives and see if they fixed it, Im doing this.
Its sad cause I really think the game is on a considerably better state than before, but if most of the playerbase dont bother with a problem like the one we are experiencing, the DEVS wont lose ressources trying to fix it, I mean how can we blame them anyways since EA has probably droped the investiment in the game already, and I bet is thinking on the next tittle.
@NightHawkk1997 I know, it may be a simple fix, but it took them a considerably ammount of time just to implement a scoreboard in the game, so I believe this version of Frostbite is really hard to work with, or it could also be that the dev team is not experienced enougth yet, either way we lose ☹️
Yes I do, I can even spot the problem on livestreams, ist something in the game not our connections or hardwares
@Jonas2QTXBox newgen should use DX12 too. Since the hardware is the same in every console, you could ship/provide the needed files with game download/installation. No idea how EA/Dice handles it. Got not much clue about consoles.
Servers and MM are another issue. With the last updates they finally made sure to lower the count of OOR players on EU servers, which already helped alot. Now they have to sort out VPN user from MM. Pretty often the 2042 servers still perform like BFV breakthrough servers on weekend mornings, where i was one of a few with a latency below 140ms.
Oh I see thanks for the explanation, maybe PS5 uses some similar API to, wich would even make devs life easier.
Well I olay on SA servers and ALAT is usually arround 30/40 ms, so its good, but even then the TN lag occours so Idk if its related.
