demagogue on 17/2/2021 at 02:38
I just started this game back up last night after a long hiatus, after I got enough HD space for it again. First thing is I have to figure out how to fix the damn jiggling trees bug, as it kills immersion. I remember I changed one parameter that fixed it last time, just trying to find which one it was now as everybody has a million different remedy ideas in the threads on it.
At some point, I'd like to script a kind of show in MP for it, using something like Red5, the setup for open roleplaying, and modeling some scenes & props in. But I want to get through the campaign first. I do like how it builds up characters and how it's a slower burn than a GTA game.
EvaUnit02 on 20/2/2021 at 12:17
Quote Posted by demagogue
I just started this game back up last night after a long hiatus, after I got enough HD space for it again. First thing is I have to figure out how to fix the damn jiggling trees bug, as it kills immersion. I remember I changed one parameter that fixed it last time, just trying to find which one it was now as everybody has a million different remedy ideas in the threads on it.
Is this it?
(
https://www.reddit.com/r/reddeadredemption/comments/dsngkq/flickeringtwitching_trees/f8r68j1/)
(
https://archive.vn/8TXpL)
Quote:
you should be able to go to documents, Red dead Redemption 2, settings, single click system.xml until you see it is highlighted, right click on system.xml and pick open with notepad or something similar. Head down to <asyncComputeEnabled value="false" /> and change the "true" function to "false" It should now look like this; <asyncComputeEnabled value="true" /> once this is done BE SURE TO HIT "File" AND "SAVE"
now restart the game.
---
This fixed the issue for me, however, don't change it while the game is running as the comment might suggest. Close the game, open the file, make the change, save the file, then run the game.
demagogue on 20/2/2021 at 17:05
Yes, that's the issue, and I'd already found that instruction and did it.
I did a list of things, and I think one of them might have already fixed it (although I don't think it was the one that you linked to).
But it takes a little wind to get the problem, so I'll probably confirm whether I did or not on my next play through.