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
0 
Report this post
Regarding your questions:
- Default map size
- AMD Ryzen 5 7600 / 32GB RAM, 3090ti (it's not my pc)
I also run a tool called process lasso which helps cpu intensive software run smoothly, so this really shouldn't be an issue (although there might be some weird things happening because of it...).
I've been playing without celsius since the bug surfaced, it rendered the game unplayable unfortunately. The slow updates might also be something to do with the mod FrameRateControl?
What is probably happening is that an earlier function of Celsius (which should only be terrain temperature and terrain replacement) is crashing and can't run the cell temperature simulation that should run after those two. Since there's 400 mods in that modlist I can't narrow down at all what's causing it though.
What happened to me earlier when I updated Celsius was that PerformanceFish was acting up and causing my save game to crash when loading. I basically fixed it by uninstalling and reinstalling completely, since PF had some sort of cache I couldn't clear. The same modlist works after that. No idea what PF was doing
In addition - I also see the "[Celsius] Skipped update of temperatures because previous was still running." message in the dev log.
As I mentioned in my previous post, I'm seeing the "infinite heat" issue with a sunlamp. The lamp is off, but the square has gotten to about 1500F (apologies to the 99.9% of the rest of the world that doesn't use F) and stays there without any fluctuation. All surrounding squares are normal temps. Some cloth on the same square as the lamp spontaneously combusts and the temp continues to increase with the fire until a pawn extinguishes the fire. At that point, the temp on that square immediately drops down to about 480F, which I'm guessing is the temp the fire would have been on any normal square.
However, the temp never drops from that, even though all surrounding squares (which did increase with the fire) cool off over time. As soon as the sunlamp turns on, the temp starts increasing again.
It seems as though the heat at these squares isn't dissipating properly and just... lingers.
[Celsius] Skipped update of temperatures because previous was still running.
Before it started I noticed the gyseirs heating up to over 1k°C, and eventually the temperature refused to change at all. Like on the whole map. (I tried to up the temperature with dev mode, which doesn't work. Explosions cause a small spike of a few degrees C in the cell in which the explosion was... and yeah that stays at that temperature permanently.)
Also, before it stopped, got this error constantly:
Could not register region Region(id=1426, mapIndex=0, center=(270, 0, 102), links=1, cells=92) in link (span=(root=(272, 0, 96), dir=North + length=1) hash=281474977104144, regions=924, 1360): > 2 regions on link!
The coordinates always seem to be deep water tiles that were about to freeze. Seems like deep water and moving water tiles are the only ones that aren't frozen on the map.
Maybe Map Designer or Map Reroll screwed something up? Like celsius tries to freeze them, but they're not how they're supposed to be so it goes "Wtf??"
Also same, After turning Debug Log on, this pops up:
[Celsius] Updated temperatures for Map-0-PlayerHome 491 times at 0.0 ms per update.
So... it's running? or more like skipping?
I have no idea what's the cause. I have so many mods, trying to narrow it down would be a pain!
It might be because of a timing error with another mod?
Or maybe because I changed the map after the game started & edited it with dev tools and now Celsius gets confused? Or Celsius gets bitey with one of the map mods I have?
Whatever it is, Changing to Water freezes works like a charm. Doesn't cause any problems so yay for that~
I have the same register region error. I don´t see the problem the game has, on this specific tile is nothing special.
It mentioned earlier as error several plants from regrowth aswell as biomes, I guess the destruction due to freezing is causing problems?
In any case it is very quickly utterly gamebreaking, it slows the game to few fps and leads after a moment even to a unity crash.
Sometimes it istantly kills out fps, in testing it mentioned the position where a fleece spider from biomes-caverns was located. Killing it restored fps but did not stop any register region errors.
The bed part was mentioned in an error log before, it was mentioned in combination with biomes-caverns as far as I remember. Error log gets filled very quickly, so hard to track everything.
It seems that once you start getting the "Skipped update" messages, then temperatures have stopped updating properly.
Geyser has now 42k°C.. Killing everything in the vicinity.
I also have Pathfinding Framework and Biomes running. Might be an issue with them, but Celsius kept acting that way after removing both mods.
This issue only started after the 1.5 update.