Sound-FmodEx-AudioDevice Thread created: FMOD (WASAPI) feeder thread (2480) Using speaker mode: FMOD_SPEAKERMODE_STEREO Record config is set to autodetect using record driver 0 Ɉ=0 FmodEx-AudioDevice: Now running on driver: Speakers (Sound BlasterX G6)ġ.Ğxternal Mic (Sound BlasterX D>=>2 ("5E=>38O Intel® Smart Sound 4 O D>=>2) Starting to initialize Windows Audio Session API output!Ģ. Initialize FMOD with dynamic memory callbacks Initializing CryPhysics done, MemUsage=152Kb Initializing CryFont done, MemUsage=12Kb Windows Error Reporting is enabled setting exception handler Microsoft Basic Render Driver (vendor = 0x1414, device = 0x008c) Intel® UHD Graphics (vendor = 0x8086, device = 0x9a60) NVIDIA GeForce RTX 3080 Laptop GPU (vendor = 0x10de, device = 0x249c) Japanese keyboard and 5+ button mouse installed Current display mode is 3840x2160x32, (Unknown graphics card) PageFile usage: 41MB, Working Set: 38MB, Peak PageFile usage: 42MB, 65238MB physical memory installed, 47968MB available, 134217727MB virtual memory installed, 26 percent of memory in use Local time is 23:11:54 07/23/21, system running for 395 minutes * Installation of KB940105 hotfix required: no! (either not needed or already installed) Number of available logical processors: 16ĬPU: Intel 11th Gen Intel® Core™ i9-11980HK 2.60GHz Using STLport C++ Standard Library implementationĮxecutable Command Line: Bin64\MWOClient.exe I`ve prioritized the use of the GPU over the intergrated oneīackupNameAttachment=" Build(0) 23 Jul 21 (23 11 52)" - used by backup systemĮxecutable: C:\Program Files (x86)\Piranha Games\MechWarrior Online\Bin64\MWOClient.exe I`ve made the Atributes.xml like it is stated here: Very good! I'll add this info to the OP, since I have been notified that the link there is dead by now. You may need to restart your system for the changes to take effect. Game crash in Intel 10th & 11th Gen CPU's. If you still have issues please contact support via Please try starting Post Scriptum again, you may need to restart your system for the changes to take effect. Enter the following into the Variable value box: ~0x20000000 Enter the following into the Variable name box: OPENSSL_ia32cap Create a new "System Variable" (NOT USER VARIABLE) Open "Control Panel" by searching for it in Windows search bar, by pressing the Windows button or key. Until we have a permanent fix, we have a workaround that should let the users affected play the game. Any game that currently uses this version will have issues, this includes Unreal Engine 4.21 which is what Post Scriptum runs on. This issue is related to a bug in OpenSSL 1.2. Some players using Intel 10th and 11th Gen CPU's have been running into issues with the game crashing upon launch. The above command-line options for only MWO or other steam launched game while the below would be for any games overall which might be affected and have not updated, even at this time. Or the sticky post in Steam below from Post Scriptum, including link and copy/paste of said information. I think that it would work as well in Steam variant, by adding to command-line options this:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |