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
Windows could recognize the problem as it was asking whether I wanted to close TLD or wait for it to respond.
I had thought GT-1030 graphics card was giving me a problem (the GPU core runs at 100% in TLD) but your post says that I may have stumbled across a new problem.
Way too many effects added to the flames...even my Ryzen 7 / GTX 1070 EX OC struggles when starting more than 4 fires next to each other.
Have just had to end task on TLD.exe twice.
No spike on graphics or CPU usage in Task Manager, so it doesn't seem to be a hardware problem.
Number of fires burning doesn't seem to matter, it seems to be the number of fires that I have lit consecutively. So, probably not do do with the visual effects.
Game seems to hang when the fires change state from being lit>burning>embers>burned out.
Hanging issue appears to worsen with each fire lit until program stops responding.
I agree with Dr Khees, the failure seems to be due to my fire-chaining, and not the number of total current fires.
For example, all three crashes have been on or around my third or fourth chained fire (lighting with the torch). For clarity, this will be on the last fire in the series before the crash occurs (for me always during the lighting evolution). For example, my most recent crash started with me chaining fires from FM's forge and west to the cave in the corner of the map. It was around either the 2nd or 3rd fire (maybe fourth) inside the cave when the game froze while lighting it.
I've got almost 1,000 hours in and this is just now becoming an issue, which as mentioned above is probably due to the engine change.
Do you guys think it's a coding/logic issue? I am glad to find this post because I was afraid that it was my laptop, now after all of your posts I don't think that it is. Also, I'm just starting to get powerful in my current run and I'm getting a lot more opportunities to chain fires. (Which is probably why I'm just seeing this).
Too many 'details' rendered for the assigned buffer.
So far so good. I use campfires rather than drop tinder plugs or cattail heads because campfires are permanent. I had a ton of cattail heads that Lost and Found gathered up for me in Forlorn Muskeg to help me not lose all my weak ice markers. Sigh.
this one specifically too,
as soon as the stutter begins, or as we now know, 4 - 5 fires. Exit interior and reenter, or the opposite if you're outside.
This refreshes everything and fixes it and resets our crashy stuttery ''timer'' of 4 - 5 fires.
This is all what works as of now
It doesn't seem like a huge deal in game but in Interloper it really is. I haven't even played my survival run anymore after having it crash like this.
You can use a snow shelter.
Building snow shelters isn't a good solution to chaining torches, or resetting the stutter, because it's resource and time intensive, at least compared with the small amount of time and effort in starting a fire to chain a torch.
I'm trying to use these torches to head to BR, and I just know that before I even get to that map, or midway through it on my way to the maintenance shed, the weather's going to get very bad and I'll wish I had a torch (granted I have matches, but this glitch is totally ruining my normal interloper methods).