!IMPORTANT! New test patch for gamepad/dll issues - Printable Version +- Frictional Games Forum (read-only) (https://www.frictionalgames.com/forum) +-- Forum: Technical Support (https://www.frictionalgames.com/forum/forum-57.html) +--- Forum: Technical Support - Amnesia: A Machine for Pigs (https://www.frictionalgames.com/forum/forum-52.html) +--- Thread: !IMPORTANT! New test patch for gamepad/dll issues (/thread-23014.html) |
RE: !IMPORTANT! New test patch for gamepad/dll issues - CalinTM - 09-12-2013 This patch doesn't update automatically by steam ? RE: !IMPORTANT! New test patch for gamepad/dll issues - fuckyoufrictional - 09-12-2013 Doesn't work for me it come an error that says: EXCEPTION_ACCESS_VIOLATION in module <UNKNOWN> I spend my money in you're game guys if I can't play at least give me my money back or better SOLVE MY PROBLEM know I'm a very angry customer by now I TRY ALL YOU'RE ''FIXES'' please do something guys. -.- RE: !IMPORTANT! New test patch for gamepad/dll issues - plutomaniac - 09-12-2013 Guys when a crash occurs please remember to attach the HPL.log file as well. RE: !IMPORTANT! New test patch for gamepad/dll issues - fuckyoufrictional - 09-12-2013 WE SPEND MONEY ON THEY'RE GAME WE HAVE THE RIGHT TO GET ANGRY ! RE: !IMPORTANT! New test patch for gamepad/dll issues - someone972 - 09-12-2013 Perhaps, but you aren't going to get much help unless you post the log file from Documents\Amnesia\Pig\HPL.log. We need information in order to diagnose crashes. RE: !IMPORTANT! New test patch for gamepad/dll issues - someone972 - 09-12-2013 I finally figured out why the sound fails sometimes. When the sound updater is being created the SDL_CreateThread function is called before SDL_CreateMutex. The updater thread starts running before the mutex is created, so the call to SDL_LockMutex is passed a NULL pointer. This is where it gets tricky: sometimes the mutex is finished being created before SDL_UnlockMutex is called in the updater. This makes the next call to SDL_LockMutex in the updater block, stopping sound from playing. When the mutex has not yet been created by the time SDL_UnlockMutex is called it has no issues. TLDR: Essentially the SDL_CreateMutex call needs to be moved ahead of the SDL_CreateThread call when creating the sound updater if my debugging is correct. EDIT2: Scratch EDIT1, I just had missed a few instructions when moving stuff around. I moved the CreateMutex call above the CreateThread call by moving and fixing up the hex bytecode. I've tried the executable thoroughly and it no longer has the no sound/hanging issue anymore, both with hardware and software. Will this fix be incorporated into the next patch? RE: !IMPORTANT! New test patch for gamepad/dll issues - eskrow - 09-13-2013 --------------------------- aamfp_sdl2.exe - System Error --------------------------- The program can't start because MSVCP100.dll is missing from your computer. Try reinstalling the program to fix this problem. People are saying to delete MSVCP100.dll from the game folder, but it's not in there?!? RE: !IMPORTANT! New test patch for gamepad/dll issues - jens - 09-13-2013 Try downloading this http://www.microsoft.com/en-us/download/details.aspx?id=8328 or this http://www.microsoft.com/en-us/download/details.aspx?id=14632 RE: !IMPORTANT! New test patch for gamepad/dll issues - larz1234 - 09-13-2013 (09-11-2013, 09:08 PM)nebej Wrote: http://thedarkswarm.com/downloads/public/sdl2_test_patch.zip The test patch does not work for me. I still cannot play because of the OpenAl error I keep getting when I try to launch the game. I have tried everything I can find to get it working but nothing is helping. The new launcher included in the test patch does not help at all. Is there a new patch in the works for crash at startup? RE: !IMPORTANT! New test patch for gamepad/dll issues - Alienguardian - 09-14-2013 Hi, the test patch also does not work for me, and the game crashes a fraction of a second after the Steam loading window comes up. I'm also unable to find an HPL.log file for the game anywhere on my computer; all I can find is "launcher.log" . Any suggestions? I'm running a 32-bit Windows XP system with a Nvidia GeForce 6600 GT graphics card. |