- Dec 26, 2017
- 5
- 0
Hey folks, I'm stuck at a roadblock and hoping someone here is able to help...
I'm able to run the game and do small mods here and there, but I cannot run the game for longer than 15 mins before my computer overheats and shuts off. Never had this issue with any fully developed game running max graphics. So I've monitored RAM and CPU like a hawk, and while the RAM does very slowly increase, it never gets close to 75% max and CPU never over 30%. I've scoured this thread for any info, and while I believe the mention of a memory leak could be the issue, I cannot understand the "fix" that was explained.
And yes, I have cooling pads and have even gone overboard with large desktop fans, and while it does help, it only adds about 2 more minutes of game play before the computer shuts off.
Currently, the latest release I can run without issues is v0.1.7 (I don't have v0.1.8) but it seems this issue starts at v0.1.9 and any release after that point. So perhaps there's something to say within that, I'm not sure.
I would love any help someone can provide as I would love to start supporting Fek for this project, but if I can't get this to run longer than 15 minutes, I don't see a point.
UPDATE (Dec-26 10PM EST): Doing more tests, seems more clear that it is not a graphics issue as the overheating still occurs on the loading screen (where it asks you click any button to continue). Let it sit there, nothing else running other than a task manager window to monitor RAM and CPU; 15 minutes goes by and computer shuts off due to overheating. So I'm thinking it might be something in the main coding that's causing this? I'm not sure. I did manage to run v0.1.7 for 6 hours with no issues today, but tried v0.1.9 and no luck.
UPDATE (Dec-27 8PM EST): Attempted v0.2.3 by moving main exe w/ folder and unity.dll to desktop (instead of in a folder on the desktop). Computer operated on the edge of wanting to shut off, but lasted over an hour of continued play and shut down the game normally. Boot it back up a few hours later, and its back to only running for 5-10 minute periods. Nothing changed that I know of between the two time frames, and frustrations are continuing to mount. Observation however, seems that the more UID objects created, the quicker my computer wants to shut off, so I'm almost back to thinking it's a hardware issue... almost.
UPDATE (Dec-30 8PM EST): Downloaded a temperature monitor to see where my heating issue was coming from. And with that, I have been switching between v0.1.7 and v0.1.9 to find any differences between the two that would cause the overheating. So, first and foremost, the heating was not coming from my CPU, but rather from my GPU. Also have noticed that the GPU loading between v0.1.7 (~20% loading) and v0.1.9 (~20-40% loading) was greater but not as much as I was expecting, however the temp difference was very large, obviously. v0.1.7 operates normally around 56*C and v0.1.9 upwards to 75-80*C before shutting down at sustained temps of 85*C after ~15 min of use. So a few things jumped out about the build differences between the two, and the most notable dealt with the graphics settings (obviously). But more specifically, a settings called "IK Quality." No idea what it is, but I played with all the graphic settings, turned everything down/off and that helped a little. Turned on a few things, no change, until I get to the IK Quality setting. Turn that up just a little and so far, it seems to be the culprit. Have loaded v0.2.3 with the IK Quality set to min and so far things have been looking promising. Monitoring the temps for that show my GPU holding around 75*C. Still higher than v0.1.7 but it seems to not go above the 80*C threshold, which is good. However, in having this setting turned down, I believe it deals with the character motion/animation interactions as the sex interaction is rather glitchy/jumpy causing bad experiences from test subjects. I will continue to monitor this activity and hope there might be something better involved. But for now, I'm confident to say that the IK Quality is the reason for my misfortune.
UPDATE (Jan-2 1PM EST): Been running v0.2.3 the past couple of days for several hours at a time. Temps are still slowly increasing to dangerous levels but have yet to reach an actual shutdown. Still not great, but at least I can say for sure that the issue has been patched on my end for now. And if anyone is wondering my hardware specs:
-CPU: Intel i7 3610Q 2.3 GHz (8 Core)
-RAM: 8GB
-GPU: Nvidia GeForce GT 630M 2GB
I'm able to run the game and do small mods here and there, but I cannot run the game for longer than 15 mins before my computer overheats and shuts off. Never had this issue with any fully developed game running max graphics. So I've monitored RAM and CPU like a hawk, and while the RAM does very slowly increase, it never gets close to 75% max and CPU never over 30%. I've scoured this thread for any info, and while I believe the mention of a memory leak could be the issue, I cannot understand the "fix" that was explained.
And yes, I have cooling pads and have even gone overboard with large desktop fans, and while it does help, it only adds about 2 more minutes of game play before the computer shuts off.
Currently, the latest release I can run without issues is v0.1.7 (I don't have v0.1.8) but it seems this issue starts at v0.1.9 and any release after that point. So perhaps there's something to say within that, I'm not sure.
I would love any help someone can provide as I would love to start supporting Fek for this project, but if I can't get this to run longer than 15 minutes, I don't see a point.
UPDATE (Dec-26 10PM EST): Doing more tests, seems more clear that it is not a graphics issue as the overheating still occurs on the loading screen (where it asks you click any button to continue). Let it sit there, nothing else running other than a task manager window to monitor RAM and CPU; 15 minutes goes by and computer shuts off due to overheating. So I'm thinking it might be something in the main coding that's causing this? I'm not sure. I did manage to run v0.1.7 for 6 hours with no issues today, but tried v0.1.9 and no luck.
UPDATE (Dec-27 8PM EST): Attempted v0.2.3 by moving main exe w/ folder and unity.dll to desktop (instead of in a folder on the desktop). Computer operated on the edge of wanting to shut off, but lasted over an hour of continued play and shut down the game normally. Boot it back up a few hours later, and its back to only running for 5-10 minute periods. Nothing changed that I know of between the two time frames, and frustrations are continuing to mount. Observation however, seems that the more UID objects created, the quicker my computer wants to shut off, so I'm almost back to thinking it's a hardware issue... almost.
UPDATE (Dec-30 8PM EST): Downloaded a temperature monitor to see where my heating issue was coming from. And with that, I have been switching between v0.1.7 and v0.1.9 to find any differences between the two that would cause the overheating. So, first and foremost, the heating was not coming from my CPU, but rather from my GPU. Also have noticed that the GPU loading between v0.1.7 (~20% loading) and v0.1.9 (~20-40% loading) was greater but not as much as I was expecting, however the temp difference was very large, obviously. v0.1.7 operates normally around 56*C and v0.1.9 upwards to 75-80*C before shutting down at sustained temps of 85*C after ~15 min of use. So a few things jumped out about the build differences between the two, and the most notable dealt with the graphics settings (obviously). But more specifically, a settings called "IK Quality." No idea what it is, but I played with all the graphic settings, turned everything down/off and that helped a little. Turned on a few things, no change, until I get to the IK Quality setting. Turn that up just a little and so far, it seems to be the culprit. Have loaded v0.2.3 with the IK Quality set to min and so far things have been looking promising. Monitoring the temps for that show my GPU holding around 75*C. Still higher than v0.1.7 but it seems to not go above the 80*C threshold, which is good. However, in having this setting turned down, I believe it deals with the character motion/animation interactions as the sex interaction is rather glitchy/jumpy causing bad experiences from test subjects. I will continue to monitor this activity and hope there might be something better involved. But for now, I'm confident to say that the IK Quality is the reason for my misfortune.
UPDATE (Jan-2 1PM EST): Been running v0.2.3 the past couple of days for several hours at a time. Temps are still slowly increasing to dangerous levels but have yet to reach an actual shutdown. Still not great, but at least I can say for sure that the issue has been patched on my end for now. And if anyone is wondering my hardware specs:
-CPU: Intel i7 3610Q 2.3 GHz (8 Core)
-RAM: 8GB
-GPU: Nvidia GeForce GT 630M 2GB
Last edited:
