As I was expecting, again.

There's no need for videos or anything else. Your folks at develop team now very well what we are talking about, as this micro-shutters have always been there in the PC version for a while already, because you decided not to follow the system other devs use in order to get this sorted out in the PC versions of their games; to create a shaders file in your Windows/GPU files that need to be installed prior playing the game in the SDD, so the micro-shutters caused by the poor communication between the engine and the GPU drivers anytime new situational stuff needs to be loaded dissapear, once every part of the map has been loaded at least once.

And the cause of this?, of course "consolization", as your PC version still isn't optimized for PC very well, right?, I mean on consoles this doesn't happen because the engine is straight up prepared to deal with this, perfectly optimized for that. What a coincidence uh?

One of the classic issues of FC on PC. When the game loads stuff like the area graphics/shaders/npc/enemies/general stuff you're gonna come across in an area, it produces a micro-shutter due to a poor shader implementation having trouble when communicating with gpu drivers, regardless amd or nvidia. Doesn't matter you are on ssd, happens the same.

The issue becomes even more noticeable when using a car due to obvious reason with the game having to load more situational stuff faster.

Is this problem present again in FC6?

I'll be honest. I was a fool when I thought New Dawn would not be the prototype for a rpg system that would dominate next big Far cry.

That is all.

The miploaddisable=1 and maxgpuframebuffer=1 don't remove the situational shuttering when the game loads stuff. It just easen it up a bit, and that's all. Being using it since FC4, but the issue still there.

And the micro-shutter when saving is another story folks, don't derail the topic please. The micro-shutter when saving has nothing to do with which is being discussed here, and it is already known that it is caused by constant access to your ssd anytime you grab an item. So kudos to the brilliant mind at Ubisoft who had such a great idea when he introduced it in FC5, and now even more kudos for you Ubi for not removing it in FC6.

Let's see if you folks get it. There's three kind of shutters with the FC games on PC since FC3 which haven't been fixed since:

a) High cpu load in one of the cores, causing overall in-game heavy shuttering for many (not me)

b) The infamous autosave micro-shutter when grabbing anything at any time. Was introduced in FC5 by some brilliant mind at Ubi dev team, and they didn't remove it in FC6. Good job Ubisoft!. In FC5 this can be fixed with the Resistance mod, but there will still be micro-shutters whn you grab story items, but not anymore with ammo, crafting stuff and money.

b) Poor communication between gpu drivers and Dunia engine when loading shaders, which causes the micro-shuttering when the game loads situational stuff (NPC, shaders; textures etc) as you advance through the map. This is even more noticable when you drive around, as the game has to load this stuff faster, obviously. This is the issue reported in this topic and the one I was talking about. Ubisoft manager changed the topic to overall shuttering in their clssic effort to hide this already shameful issue from FC3, but remember what was being talked here, please. Don't derail.

@ubi-borealis Keep ignoring the main issue with the drivers and Dunia for not preloading shaders in a dedicated file, causing the situational micro-shuttering that has been plaguing your bad PC port since FC3 everytime the game loads stuff as you avance through the map. That's the shutter this topic was about.

And the second in importance shuttering, the cpu related one due to much load in one single core, keep ignoring that one too!!

Keep doing it man!

And oh Christ you're gonna fix the auto-save shutter?, and how are you gonna do this man?, by not auto-saving everytime we grab an item like the Resistance mod did for FC5 because you were that lazy?, what a fix!!, genius!!!

Seriously now this is a joke. We're losing our precious time here as you obviously don't seem to acknowledge the true issue this topic was about before you changed the topic tittle.

And RPG elements are there to make the game more interesting (which they do).

In your opinion

@ubi-thrupney "our internal teams actually working on these issue are specialists. We're not always in a position to report on exactly what their findings are, but I'm confident they'll have come to correct conclusions with the available data."
______________________________________________________________

Given your curriculum on your PC ports since the days of FC3, everything seems to point exactly in the opposite direction on your confidence about getting things fixed.

The situational micro shutter when the game loads stuff as you advance through the map is an eight years old issue already that you never fixed in the past FC entries for PC, so sharing your confidence on your team of "specialists" being able to get this sorted out at long last pretty much seems to me like some masochist act of faith, faith which is pretty much misplaced given their chances to fix this issue up to zero in a scale of ten.

You know this cannot be fixed so long you don't add a shader cache file that needs to be preloaded only once before playing the game (or anytime you change your gpu drivers), which would mean updating Dunya to todays standards in order for your PC ports to function properly in comparison to its console counterpart, which hey what a miracle, never suffered from this issue. Why?, because shaders and everything are designed to communicate perfectly fine with the console gpus, but then when this has to happen with PC, the issue becomes real with gpu drivers communicating with the engine.

And then the other issue about terrible CPU work spread, forcing almost everything on one of the cores. You know what to do but still too lazy to get it sorted, right?, but hey keep asking us about handing you dumb stuff over, so you can concentrate on fixing nothing, as usual.

Lol, and what can one say about the fix for the auto-save micro-shutter you are rolling our on a forthcoming patch. All you're gonna do is, precisely, not to save anytime we grab stuff, rofl, like the Resistance mod for FC5 did way before. Yeah now that's some "specialists" you got over there right?, genius!

Furthermore, and to continue to discourage your PC customers in your usual ways, (you continue to treat us all as pirates, remember?), you keep ignoring this issue instalment after instalment, treating us as idiots with your absurd requests of "provide us with this and with that", when your team of "specialists" know very well what the issue is about.

And then you don't even remove Denuvo one year after release or when the game gets bypassed, protection that contributes to the overal instability of the game regardless what you and many bots around say otherwise (look at the ultimate case with this with Resident Evil 8, where it got absolutely out of control), let alone won't remove such intrusive drm even when one of the two situations aforementioned complies. That's how you like to treat legal PC customers. Your disrespect towards us is absolute.

I'm afraid that our confidence on you, support team, and your "specialists" borderlines on none-existent for the time being, at least concerning PC support. It's been so many years already, and we know perfectly well what you're about when it comes to PC versions of your games.

Yeah Ubi I think you still aren't woke enough in your effort of "equality" and gender representation in your games.

I think Catillo's army, which is 80% females still isn't realistic enough, so what about going full 100% female enemies in your next Far Cry game?

I don't like "X" thing.

Please Ubisoft remove it because I don't like/offend/scares me.

This is already utopian, and I say this because at first I thought the OP dude was trolling, but now I see he/she/it being serious about it. So remove this because I don't like it.

@_OP: Go ask for censorship elswhere. We currently have enough with woke and political correctness defiling the series, and not just this one franchise.

@dv20katana Download the "Resistance" mod. Among the trillion things it allows you to either add or change, one of them is that enemies will still spawn in all liberated regions.

Combine that playing in infamous difficulty mode + reset enemy cult outposts, and FC5 literally lasts forever, or until you truly get tired of the game.

I DO hate rpg stuff in a game like this.

Having to shoot a dude three times with a goddamn 50 caliber sniper rifle (or a lesser one, it still should be one shot kill) really sours my mind.

And what the [censored] is with the absence of prone in a game like this. Do you really hate snipers that much Ubisoft, and just because of crybabies giving childish excuses not to add it?

And the woke stuff defiling everything else in the game story/characters wise omg. When is this dogmatic laughable plague gonna end?

Ubisoft always listening to those they shouldn't have to. [censored] that already!

Far Cry 2 and 5. Still the best.

@robertemerald you ok bro?, you sound triggered much

okay

uh okay okay

@alexawaken Far Cry 2 indeed s the best instalment to the franchise yet, even after all this time ([censored] FC3), but I think they reached paramount with FC5 regardless it is still a modern FC.

FC6 feels like a goodbye anyway so don't worry. Next instalment should be different enough and, with a bit of luck on a new engine like Unreal, and again with a bit of luck, we can [censored] go prone on a [censored] shooter Ubi?

BTW, FC2 engine is the one used until today with FC6. They didn't use another one. All they've been doing is degrading physics and upgrading graphics basically.

That's why we need FC5-alike infamous difficulty mode asap.

@heyscot Game is full of females, specially in our side. No problem if just one dies, and one of worst and most vomitive ones might I say

@azullfr And infamous mode is needed too. That is even more important than new game+

@ubi-gizmo "they resolved your issue by updating their SATA Drives"

hahhah++ oh well..

Btw yes. I saw my topic, first seeing its original name "situational shutter due to poor communication between gpu drivers and Dunia engine loading shaders", changed for a more streamlined "Fps drops / shuttering", in a clear attempt of you folks trying to avoid which is still, after 8 years, the main issue with FC on PC since FC3 (doesn't happen on consoles, what a coincidence uh), for now being butchered into separated shuttering "might-causes" that have nothing to do with the original topic, which pointed you directly to the main issue.

But now I see that, not only this one, the main issue that gave name to the original thread doesn't appear in any of that list (just lol), but you have also avoided to include in that laughable list that which is the second main problem for the shuttering after the gpu drivers/shader communication with Dunia (because you don't want to [censored] create a [censored] shader file cache, hence the shuttering issue), being this the high cpu load on one single core, while the rest have a poor work spread.

So you omitted the two main causes for the shuttering, being:

"Situational micro-shuttering due to poor communication between gpu drivers and Dunya, due to the absence of a shader cache file, everytime the game loads stuff"

"Very noticeable shuttering due to high cpu load on one single core, while the rest have poor workspread"

See?, you omitted, precisely, the two issues that truly matter. Where are these in that list now?

You're mocking us.

@ubi-gizmo yeah well I had already opened a topic about the situational shutter that happens since FC on PC on every friggin' port of yours, about the poor communicatin between gpu drivers and the shaders, and also about the high single threaded cpu optimization which leads to bad shutter as well, and your help was borderline comical, beginning by the very change of the topic name, and finishing on the most ridiculous pieces of advise to the users there. Anything but fixing the true issue you know about for already a decade.

This is ridiculous. You know your PC port has always been poorly optimized (because these issues don't happen on console version), yet you try to confuse and straight lie everyone by pointing them to totally irrelevant stuff.

Your good behaviour and also aparent intentions isn't the only thing we need.