Jump to content

Ekital

Members
  • Content Count

    39
  • Joined

  • Last visited

Community Reputation

14 Good

About Ekital

  • Rank
    (1) Prestidigitator
  1. Wrong directory, If It's the steam version it will most likely be in C:\Program Files (x86)\Steam\steamapps\common\Pillars of Eternity\PillarsOfEternity_Data\Mono As for the GOG version it will most likely be in C:\Program Files (x86)\GOG\Pillars of Eternity\PillarsOfEternity_Data\Mono Just look inside the main game directory.
  2. What Im saying is this, if you're not attempting to solve the issue then there's no point in ranting about it. If you can figure out whats wrong with it then you can post the solution or hey if you're looking for a solution how about attempting all the solutions first and providing some relevant data about your specific crash . A game isn't going to be patched if people don't give detailed information to the developers. Every system is different especially on Windows where so many libraries are externalized and non-standardized. Also, a large problem with PoE is that it unfortunately inherits all the issues with Unity. Hence why so many of these crashes are caused by the same issue (.NET or Fonts).These problems are apparent and easy to fix for yourself if you actually attempt it instead of just crying over it.
  3. I'll refute your points. Unity has issue for sure but there are several games far more impressive and demanding using less resources than PE. Despite Unity's flaws PE's demands are excessive. "These days" many people don't give 2 sh17s about computers in general. Not all gamers are equal in their quest for "heavy iron" or quad digit frame rate supremicy. Just because you deem everyone should have something doesn't make it so and it's got nothing to do with the reality PE should not require such things even if it is common. Obviously the game should run on my machines spec, but it doesn't. I.e. it's a bug and you point it out as a technical issue is a reduntant pointless statement. As for me being inept, doubtful. I've been an OEM for 15+ years and was probably building machine since before you were born. That being the least of my technical resume. As for bringing Linux into it makes a lot of sense as the problem seems to only affect the Windows builds. It also illusrtates that is a lesser machine running Linux can load/run the game better there is more bloat or issues with the various libraries or systems being called on Windows builds under certain circumstances. If I wanted to rant you'd know it. It's a question being posed about the numerous launch bugs. From saves not being cross platform compatabile (which affects Steam sync) to lockups, crashes, stat glitches and more. I love people like you, you assume everything about the person because you feel superior to others. A 4GB stick costs 30 dollars, so please stop sticking words into my mouth. I never said people need to build amazing rigs, I was stating that 4GB has been a minimum for a few years now. Now take this stupid ****ing discussion elsewhere if you aren't having a problem with crashing because this is what this thread is for.
  4. Actually those tricks and the way the models are built are the reason the game is demanding. It's because Unity is simply not well optimized in general.However Im going to refute some of your "points", First of all there's no reason people shouldn't have 4GB of RAM these days. Second of all it will run on those specs you named, you're just simply having a technical problem but you're too inept to solve it so you're blaming the game. Third of all why bring Linux into this? It has no correlation to the discussion. Also this is a technical support thread not a rant section so take that bs elsewhere.
  5. @kyubi Umm no, Fallback handler could not load library C:/Program Files (x86)/Steam/steamapps/common/Pillars of Eternity/PillarsOfEternity_Data/Mono/libc Fallback handler could not load library C:/Program Files (x86)/Steam/steamapps/common/Pillars of Eternity/PillarsOfEternity_Data/Mono/.\libc Fallback handler could not load library C:/Program Files (x86)/Steam/steamapps/common/Pillars of Eternity/PillarsOfEternity_Data/Mono/libc System.TypeInitializationException: An exception was thrown by the type initializer for Mono.CSharp.CSharpCodeCompiler ---> System.IO.FileNotFoundException: Windows mono path not found: C:\Program Files (x86)\Steam\steamapps\mono\mono\mini\mono.exe at Mono.CSharp.CSharpCodeCompiler..cctor () [0x00000] in <filename unknown>:0 will show up in everyone's output log. It has to do with MT and Cross compatibility for different operating systems. "GetThreadContext failed" is definitely a Unity error try attempting this fix: https://stratics.com/community/threads/if-you-get-constant-getthreadcontext-failed-crashes-this-should-fix-it.300386/ You can find mono.dll inside the Pillars of Eternity\PillarsOfEternity_Data\Mono folder. If you're using Avast, Kaspersky or NOD32 as your anti-virus then it's most likely the AV causing the crash. =========================== @Meika, The minimum RAM requirement for Pillars of Eternity is 4GB. 2GB is not enough to run the game properly and it is what causes the gilded vale/other ingame crashes. Unfortunately there is no good fix for this especially for a 32-bit system which is naturally restricted to only using 2GB. At your present moment you have somewhere in the region of ~1-1.5GB of useable memory, which is basically just enough to get the game running but not enough to handle the game under higher stress aka towns etc. With your current setup there is no way you'll get past the Gilded Vale. I suggest upgrading your RAM and unfortunately switching to 64-bit. You can try adding more memory up to 4GB and using the RAM workaround that obsidian has posted however that is not really recommended. =========================== More info: The .Net Framework/Mono fix will only work if you notice the following line in your error.log (Not the output log): mono.dll caused an Access Violation (0xc0000005) in module mono.dll at 0023:101071b5.
  6. @Gaunilo I've never used a MAC so I can't really help you there but as far as I can see there is a problem with the game pathing towards one of the required .dll's. A developer would need to check this out. @kyubi http://answers.unity3d.com/questions/24574/fatal-error-in-gc-getthreadcontext-failed-.html Seems to be an anti-virus problem. ------------------ Most of the problems stand from the following issues: 1.) [Win]The C++ Redistributables (vcredist) aren't installed if you need them they can be found here: x86 x64 2.) [Win/Lin] Missing .Net Framework (You can grab this one from Windows update) [Most likely the reason for mono errors.] For Linux simply download the Mono package. I doubt you'll have a problem running this on Linux anyway..3.) [Win/Linux] Attempting to play using a 32bit system, yes it's possible but you have to do a memory workaround and even then it's not really good. 4.) [All OS] Having 2GB or less of free memory 5.) Corrupt Download or Corrupt Fonts
  7. There is really no good way to patch this. This is a Unity problem itself which has been pointed out to the developers of Unity. The fix was already given. Post your error and output log so that the devs can figure out the reason.
  8. It will be inside of an error folder inside the main PoE folder, it will be a dated folder and it should contain both error.log and the output log. However it will only show up if the game crashed, if you never got it to run then it might be a problem. Example: You can find the output log however in the data folder
  9. I think I may have the same problem as you but I am not sure. How do you install (repair) vcredlist. When I check the redistributable folder of PoE i see it is already there. Post your error.log and output log just in case as it could not be related.
  10. Hmmm.. heating is an issue even for desktops. Didn't notice this until I looked at the temps now. Both with and without msaa, I'm running in the low to mid 70s which is definitely not normal.. GPU: CPU:
  11. @K3V Hmm,this is a bit more weird considering mono is a C# compiler so it's not actually PoE itself causing the crash. Please post the output log it should be very helpful in this case. In the mean time try the following: -Install the vcredist inside the redistributable folder of PoE. -Install all windows updates, especially anything related to the .NET framework
  12. Seems like you have some sort of shader problem. -Are you running any over-clocking software? -Are your gfx card drivers updated? -Have you verified your game cache?
  13. There could be a multitude of reasons for that BSOD: -One or more of your processor cores could be faulty. -One of your drivers is not meant for W8. -Caused by overclocking software. This problem is most likely a unique one to you unfortunetly.
×
×
  • Create New...