Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
If you run into a crash, please do this: restart the game right after the crash (to the main menu), then open the console (key ~ or `) and type "report" (without quot. marks). Add some small information about what happened (e.g "game crashed after removing flowers" etc) and send the report - this will automatically include the previous log file (which hopefully contains more information about the crash) ;)
Video: https://youtu.be/ItP_ESuR_8Q?si=KnRlY77ZTOQT9cJt
Update: A pain but apparently decreasing block draw distance by a lot made it feasible to remove the flowers, apparently the higher the flower count the more strain on the processor so long as you have a ton of area being processed at the same time on higher graphics settings. ROG apparently doesn't handle this well.
Is it a naturally generated meadow, or did you place the flowers there manually? Do you mind posting a screenshot of the flower meadow which caused the issues? Alternatively you could also send a report - move to the flower meadow first (so that the flowers in question are visible), then send the report ;)
One thing that could potentially cause issues could be the gravity setting... maybe you could try to turn that off and see if this makes any difference. To do that, go to the game settings -> misc -> scroll down and turn off "Enable Gravity for Objects" and "Enable Gravity for Plants" (i.e set both to "off"). Does it still crash?
Only in few cases crashes are actually related to the overall performance of the system. In most cases a crash is either caused by a bug in the game, or a driver issue (or any other native issue) - and this can happen even on high-end rigs of course.
The game doesn't have different LODs for the flower patches (because they're already quite low poly), so performance shouldn't be much different if you get closer to the plant (at least when it comes to the rendering performance).
Is the performance already getting worse if you get there, or only if you interact with them in any way (e.g remove them)?
I basically lowered the block draw distance practically to 1 Red51 and managed to resolve it but having it up to like 40 for some reason causes the processor drama if I attempted to remove it, even a smaller flower patch causes lag or a momentary freeze on the processor so... Maybe a new a stronger processor? Anyhow, I resolved it through painstaking lower of block draw distance in the settings. Strange, but it is what it is apparently. In any case it'll be something to look into, for the meantime I think I'll study it.
what the hell kind of potato are you trying to run it on that a flower is kicking your ass? lol :P
I run a modest system by all standards. Simple i5-12000 w/a RTX3070. I ran around looking for a nice big flower bed. Didn't see the slightest drop in FPS, though I think there was some issues with the frame lock in RW that I have enabled. It didn't want to undo itself, but I held 60 - 72 FPS (the sync rates of my monitor) without any issues.
Of course, you'll need a system to support them too, but you can incrementally do that; buy the card, then upgrade the system later. Won't be the best way to do it, but can be done.