Medium9 wrote: ↑

Fri Mar 22, 2024 3:57 pm

Whoops, uploaded wrong log. Sorry!! The one here is from when I recreated the issue right now.

This also does not have a crash in it. It simply shows it running normally.

Thanks for the report however there is no crash in the log file. It simply shows normal operation and then you closing the game by clicking the "X".

This was fixed in 1.1.97 so it will simply swap without needing any extra logic.

Are all of these errors on the same laptop from the same manufacturer? I'm wondering if I could buy that laptop and reproduce this myself to figure out why it's broken with Radeon mobile graphics.

Based off the crash I doubt you will find steps to reproduce. My suspicion is you had a random bit flip and or your RAM is going bad. Are you having any other issues with other games/programs? What does running https://www.memtest.org/ show?

Do you have any way to reproduce this crash? Looking at the log, I've seen this crash in the crash reports before but it has nothing to do with research. It also makes zero sense that it should ever crash where it crashed unless something has corrupted memory (either bad code we wrote by mistake or ...

Those are all distribution problems with demand exceeding supply, produce as much as you need and you have no issues. This is the same answer as it was 6+ years ago. It's such an incredibly simple solution - I have no idea why people insist on making fluid splitters when the root issue is "You...

Thanks for the report. This is now fixed for 2.0.

Did anything ever happen with this? Given the other people reporting the same issue and they seemed to get it working?

This is fixed in 2.0

Thanks for the report. This looks like it's the same as here viewtopic.php?f=30&t=111580 which will be fixed for the next release.

Thanks for the report however looking at the blueprint-storage.dat file it seems to be corrupt. Without knowing how to get a working blueprint-storage file into this corrupt state all I can do is speculate that some hardware issue on your end has broken it. Do you know how to get a working blueprint...

Thanks for the report. This is now fixed for the next release.

Thanks for the report however due to the lack of other users reporting issues around this my inclination is to blame your hardware and or software (drivers) as being possibly broken/failing.

Are you able to reproduce this on any other computer?

Thanks for the report. This appears to be working correctly in the latest 1.1.104. Can you confirm if it's still happening for you?

Thanks for the report. This issue is solved in 2.0 due to other changes there.

Thanks for the report. We're specifically doing away with the secondary-bounding-box logic in 2.0 at some point so this will resolve itself. The new rails in 2.0 do not use the logic and once we have allowed a sufficient amount of time for saves to be migrated to 2.0 we will be removing the feature ...

Can the benchmark feature be used to detect bit flips in conjunction with heavy mode? If between saving and loading to do the comparison the original or loaded version have bits flipped, yes. But it will be quite slow to do. I am aware that prime95 or memtest64 are better tools for that. I just wan...

Is there anything I need to do? I loaded it, zoomed out fully, and waited 10 minutes and no crash.

Thanks for the report. This will now give a standard modding error for the next release.