Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

19 Good

About AstralWanderer

  • Rank
    (3) Conjurer

Profile Information

  • Location
    North West, United Kingdom


  • Pillars of Eternity Backer Badge
  1. Did you receive the collector's edition box and non-disc contents? (map, manual, etc). These were shipped in March 2015 (according to KS updates) while the discs were shipped later (from Paradox in June 2015 according to my emails). There have been several updates since the discs were released however, so you would also need to download the appropriate patch to take them from 1.04 to 3.03. If you already have an up-to-date copy then there's probably not much point in having the DVD.
  2. Apologies for necro-ing a thread, but none of the replies given actually addressed the original poster's question. Pillars of Eternity *will* run on Windows XP and can be completed without problems - the only requirement is a modification to the boot.ini file as noted in this support article (specifically to add the /3GB switch and I would recommend the /userva=2900 switch also to minimise the downsides of /3GB - most important for software that uses PAE to access memory above 4GB).
  3. I'd cast my vote for the original PoE title screen also. It better reflects the majority of the game and having to look at a snow-covered landscape on every launch gives me unnecessary chills.
  4. Been reviewing a previous thread on this, which does offer some workarounds. There seem to be two problems combining here - the first is that basic load/save operations are far slower than they should be (I have to wait 20-30 seconds for area transitions and that's with an SSD RAID array capable of 700MB/s sequential read/write) which seems to be a Unity3D "feature" (other games like Dreamfall Chapters exhibit a similar problem with long load/save times). With Pillars, this seems to be worsened with two copies being made of each savegame file (one with a .savegame suffix and the other with
  5. Presumably the 23/26°C readings are for the internal case temperature rather than from CoreTemp/MSI Afterburner? (which read the embedded CPU/GPU temperature sensors). 3°C doesn't seem like a large difference but if it is case temperature, then it could mean a larger (10-20°C) temperature change on the CPU/GPU. Thanks for the update, and please let everyone know if it has fixed your issue.
  6. This is something that should be seriously considered. What graphics settings people use should be their own choice, and while Obsidian should feel free to offer advice ("Your system specification will likely result in a poor experience with this setting") they should not arbitrarily restrict resolution settings - not least since it then fails to account for future developments (i.e. what happens 10+ years later when Mac notebooks are available with GPUs powerful enough for Retina+ displays?).
  7. Intermittent errors can be amongst the hardest to resolve. The most likely causes would be either be overheating (leading to memory corruption and CPU errors) which Prime95 should have identified and faulty memory which MemTest86 should have spotted. You could try monitoring temperatures using the likes of CoreTemp (your system would need the 64-bit version) for the CPU and MSI Afterburner for your GPU. Anything in excess of 80°C should be a cause for concern and addressed by checking your system is clean of dust and has sufficient airflow.
  8. Crowded areas are likely to increase the load on the CPU rather than GPU. PoE in my experience will max one core out while using 50% of a second, so setting affinity (and thereby limiting it to one core) is more likely to make things worse. With a Core i7-920 (clocked at 3.4GHz) and SLIed 580GTXes, I see similar FPS rates as yourself - 35-40 in crowded parts of Copperlane, 60 in quieter locations. However plenty of others have reported worse results in the Why does this game run poorly? so it's probably a fair statement that this game is severely lacking in performance. Hopefully Obsidian
  9. Almost certainly not - your GTX 560 Ti should be ample for PoE and the problems you have reported seem to be intermittent data corruption issues. If Prime95 ran OK and MemTest86 gave no errors, then try checking your disk for errors by opening a command prompt window and typing chkdsk c: - if errors are reported ("Windows found problems with the file system") then rerun chkdsk with the /f parameter to fix them (chkdsk c: /f) but this will likely require a system restart. Also use Crystal DiskInfo to check the SMART (Self-Monitoring Analysis and Reporting Technology) status of your disk - it'
  10. For Prime95, leave it run. If it encounters an error, it will report it and stop that thread - any errors reported almost certainly mean a hardware problem. Review the included stress.txt file for more information. With Process Explorer, do an online search on any processes you don't recognise or which come from unknown companies.
  11. If a save that previously worked now crashes (and does so repeatedly) then you almost certainly have something on your system that is modifying the savegame files. If a save that previously worked crashes *sometimes* then odds are that something else is causing problems with PoE itself. Have a careful look at what else you have running on your system using Task Manager - better yet install either Process Hacker or Process Explorer and use these to check that all the processes running on your system are legitimate. Assuming these check out, then the next most likely cause is memory issues
  12. Welcome to the forums Campa147, Looks like you've hit the 2GB per-process limit in 32-bit Windows. See Obsidian's blog entry for how to work around this, raising the per-process limit to 3GB. There may be negative consequences for other software that uses PAE (Physical Address Extension) or large amounts of kernel memory, so if you do find other programs crashing afterwards, try experimenting with altering this setting.
  13. Your latest output_log.txt reports the same "corrupted ZIP" error before crashing as previously. So it seems most likely that the first crash after starting with a new character caused a corruption in your savegame file. Pillars does seem to scan savegame files on startup so an invalid one can cause a crash on the intro screen. My suggestion would be to go to your savegames folder - create a subfolder in that (called "Backup" say) and to move the most recent savegame to that. Then try restarting PoE. If problems continue, move the next most recent savegame to Backup and continue until you re
  14. While saved games should be compatible across versions as celliott has noted, it seems very unlikely that you would be able to install a Steam version of the expansion over the GOG version of the base game, without considerable effort. The Steam installer will expect the game to be in a different location and while it is possible to import a game into Steam, there's no guarantee that subsequent updates would work as intended. A similar issue applies in reverse - the GOG installer creates specific registry entries which are checked for by updates and expansions. So the GOG version of PoE's ex
  15. PoE is far more demanding of CPU/GPU than a game of its type should be, but is no more likely to cause overheating than any other demanding game or application. Computers should be designed with cooling effective enough to withstand extended periods of 100% utilisation, but there are situations where this doesn't apply (cost-cutting on a "big name" brand, excessive overclocking on a home/store-built system or dust/dirt reducing the effectiveness of heatsinks and fans on an older system). The best approach therefore is to keep a regular check on temperatures - there are several programs t
  • Create New...