Jump to content

Dragoonlordz

Members
  • Content Count

    148
  • Joined

  • Last visited

Community Reputation

70 Excellent

About Dragoonlordz

  • Rank
    Exorcist of the Obsidian Order

Badges

  • Pillars of Eternity Backer Badge
  • Deadfire Backer Badge
  • Deadfire Fig Backer
  1. Limiting the framerate/fps to between 30-60 and making sure vsync is set correctly i.e. either set to on in Nvidia control panel for example and off in game or off in the control panel and on in game should help reduce heat a lot. Leaving the framerate uncapped in Unity engine games causes massive usage and temp build ups and has been an issue with the Unity engine in a lot of Unity based games. I don't know why the engine has this problem in so many games but it does, if you google Unity engine/games and overheating/framerate you will find a lot of examples of this and a lot of examples of people solving it by capping the framerate to reduce excessive heat buildup.
  2. Try running it from the main game .exe file located in Program Files (x86)\Steam\steamapps\common\Pillars of Eternity II folder rather than via steam or the steam created shortcut and make sure set to run as admin. See if that helps.
  3. Shutting down when playing does sound like overheating issue with GPU, CPU or PSU...even though you say it is not those it does sound like that sort of problem. If was just driver issue or corrupt files etc it would more likely stutter, freeze, crash to desktop or blue screen rather than shut the computer down completely. Unity games have long had a problem with GPU usage, wherein sometimes you have to manually limit the framerate to reduce the GPU load else can overheat plus also have to make sure Vsync is working correctly. Set the framerate to 60 for example and will notice a decrease in temps or set to 30 and will notice a substantial drop in temperatures. Now I could be wrong but I'm just saying from my experience does sound like an overheating issue and also based on my experience with Unity games it could be because the framerate is not being set to a capped amount, uncapped leads to excessive load on the GPU which is a issue Unity engine games have long been known to have.
  4. Crashed again, not sure if related to previous crash because one occurred on land in city and other while out at sea when tried to enter my own ship. Here's the error/log files the game created. 2018-05-12_090932.zip
  5. As title says, it came up with message after telling me to send you these error files it made when crashed. 2018-05-11_115730.zip
  6. Thanks. I found a temporary solution that also seems like might be working so far without achievements being affected but if my current method causes unforeseen problems later on that I haven't come across yet then I'll try your debug/console commands. The solution I am currently using basically involved changing some text in the "21_cv_player_awakens.conversationbundle" file in the "C:\Program Files (x86)\Steam\steamapps\common\Pillars of Eternity II\PillarsOfEternityII_Data\exported\design\conversations\21_prologue" folder then when started new game with PoE1 import this change created the right background for him including right necklace. Here is the changed file if someone who has same problem as me wants to download and replace the file on theirs (make backup before replace though to be on safe side).
  7. Does anyone know of a console/debug command to fix the wrong import flag having being set by the game when import the savegame from PoE1 in which got the following ending: In PoE2 when import a savegame with that ending the game gives him this backstory instead: This is putting me off playing the game because I spent 200+ hours and multiple playthrough's to find the perfect (personal preference) import ahead of time and PoE2 is not recognizing my choices from that import and setting wrong/inaccurate flags. I am also concerned that if this one is being set wrongly by PoE2 then just how many more examples will crop up in a playthrough...but I am not willing to find out until this one is fixed either by patch or console/debug command. I should add I do not care about achievements so I don't care if using a debug command turns those off.
  8. Well I have completed the game now and didn't get anymore shut downs after I did what I said in post 51 above. I did have few crashes to desktop though which resulted in a application has stopped responding type popup message window but since I have finished the game now I guess I don't need to worry about it happening anymore.
  9. I haven't had a shut down since did what I said above your post but doesn't mean won't happen again. It has however been 2 days of playing without shutting down so perhaps you can try what I did aka if using Precision then uninstall that one and install Afterburner instead, run a windows update and also uninstall all your audio drivers and refresh your device manager list so it will find them again and reinstall them. My audio installed is RealTek HD Audio and NVidia HD Audio type drivers, it's on-motherboard audio rather than sound card. It's worth a try even if doesn't work, just in case does. I am hoping mine is permanently fixed but that may be wishful thinking.
  10. I ran a windows update, ran a memory test (which came back fine), uninstalled Precision and installed Afterburner plus reinstalled my audio drivers and it seems the crashing to desktop has stopped. I do not know if the shut downs will stop though. I will continue to monitor my CPU and GPU temps but both as have said many times are running perfectly cool and certainly not overheating, will try playing for a long period of time see if shuts down again. I haven't had the crash to desktop or the shut down for over a day now so maybe both are fixed though that might be wishful thinking on the shut down aspect but the things I did above did certainly fix the crash to desktop issue.
  11. My drivers for audio are most recent ones which even though 2011 there are no newer ones, it is onboard sound not a sound card. It is the same drivers I have been using from the offset and it worked fine since the game came out with no crashes to desktop on those same drivers until now (the shut downs have been happening on and off seemingly at random for past week or so and I checked my GPU and CPU and they seemed fine). So I doubt that's causing it because it would of happened prior to now I think. I really do not think overheating is the issue with shut downs either, like I said I have been monitoring my CPU and GPU temps and they are not very high. I haven't checked my memory but will run diagnostic on that just incase. Yes I am using EVGA precision application to manage my GPU fans and framerate limiter, I could try MSI Afterburner see if that still has same issues I guess. I'll try disabling sound and run Afterburner instead of EVGA Precision see if that helps.
  12. Now it has started crashing every 30 seconds for some reason...attached is the error logs, crash reports etc. Going to delete the game, reinstall it and hope that fixes the newest problem though doubt will fix the shut downs. Between the system shut downs and now these constant crashes it has become completely unplayable. At least with others like Wasteland 2, Shadowrun Returns or Divinity Original Sin they were playable and never had these sort of problems with those (Original Sin crashed couple times until it got patched but never shut down my system), I hope Tides of Numenera which also backed doesn't have these sort of problems when comes out. EDIT: Nope, reinstalled and still can't play it. Crashes after few seconds once loaded game and even if start new game still crashes after couple seconds...this game is extremely broken. It is the most I have paid to back a project on KS and yet it is the only one that will not work between the shut downs and constant crashing to desktop. I am going to stop playing it until it is fixed now, it's just wasting my time trying at the moment. Pillars of Eternity.zip
  13. It is not a CPU overheat or OC issue. Not on mine. My CPU is neither OC'd or overheating. In fact my CPU is the coolest component in my system generally and never goes above 45 degrees on the most taxing of games, most of the time it stays around 21-34 degrees and in PoE it never gets very hot either. My HDD's run hotter than my CPU 99% of the time with the HDD's generally at around 40-43 degrees and my CPU is less than that. I had it happen again yesterday after having a couple days of playing fine despite not only my CPU and GPU temperatures being cool but also I was limiting the framerate to 60 which is another solution someone else suggested a while back, the system shut down while playing and I was keeping an eye on temps shortly before. The CPU was around 35 degrees and the GPU was only around 41-42 degrees before it shut down...after it shuts down and I turn the system back on a weird thing happened in which my CPU fan no longer turns on until reset the system a couple times. I am not sure why that could be but this is the only game out of over 200 games I have on PC (most very much higher requirements then PoE yet all run fine) and not a single one of those other 200+ games shut downs my PC at all. It has to be a coding issue because I would get the same thing happening on other games if was a hardware issue yet no others do this. I am not the ony one having this issue and plenty of us have supplied Obsidian what they asked for but still no possible solutions or suggestions by them about the issue since page one where they asked for the files from us. Are they still looking into it or have they made any progress on the issue? Here's a new log file from the latest shut down occurence (you should already have my dxdiag file from previous page of this thread so guessing don't need another copy of that) plus most recent save game from prior to latest shut down. output_log.txt
×
×
  • Create New...