Hi there,

after installing Crysis Gog-Version at my rig, I got the error hat CryInput.dll and XInput.dll could not loaded, because of an possible DirectX-issue.

Unfortuneately Tech-Chat-Bot wont give me an ticket but all other possible solvings of this problem are not working. I tried a lot, what I found at the www.

Please see attached screenshot and dxdiag.

Thank you very much!

dxdiag (partially):
------------------
System Information
------------------
Time of this report: 11/21/2022, 11:04:55
Machine name: PC
Machine Id: {}
Operating System: Windows 10 Pro 64-bit (10.0, Build 19044) (19041.vb_release.191206-1406)
Language: German (Regional Setting: German)
System Manufacturer: To Be Filled By O.E.M.
System Model: To Be Filled By O.E.M.
BIOS: BIOS Date: 11/21/17 11:44:52 Ver: 05.0000D (type: BIOS)
Processor: AMD Ryzen Threadripper 1900X 8-Core Processor (16 CPUs), ~3.8GHz
Memory: 32768MB RAM
Available OS Memory: 32650MB RAM
Page File: 8845MB used, 32507MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 12
DX Setup Parameters: Not found
User DPI Setting: 96 DPI (100 percent)
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
Miracast: Available, with HDCP
Microsoft Graphics Hybrid: Not Supported
DirectX Database Version: 1.0.8
DxDiag Version: 10.00.19041.0928 64bit Unicode

------------
DxDiag Notes
------------
Display Tab 1: No problems found.
Sound Tab 1: No problems found.
Sound Tab 2: No problems found.
Sound Tab 3: No problems found.
Sound Tab 4: No problems found.
Input Tab: No problems found.

--------------------
DirectX Debug Levels
--------------------
Direct3D: 0/4 (retail)
DirectDraw: 0/4 (retail)
DirectInput: 0/5 (retail)
DirectMusic: 0/5 (retail)
DirectPlay: 0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow: 0/6 (retail)

---------------
Display Devices
---------------
Card name: Radeon RX Vega
Manufacturer: Advanced Micro Devices, Inc.
Chip type: AMD Radeon Graphics Processor (0x687F)
DAC type: Internal DAC(400MHz)
Device Type: Full Device (POST)
Device Key: Enum\PCI\VEN_1002&DEV_687F&SUBSYS_E37F1DA2&REV_C1
Device Status: 0180200A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER]
Device Problem Code: No Problem
Driver Problem Code: Unknown
Display Memory: 24444 MB
Dedicated Memory: 8119 MB
Shared Memory: 16324 MB
Current Mode: 2560 x 1080 (32 bit) (60Hz)
HDR Support: Not Supported
Display Topology: Internal
Display Color Space: DXGI_COLOR_SPACE_RGB_FULL_G22_NONE_P709
Color Primaries: Red(0.660156,0.331055), Green(0.305664,0.609375), Blue(0.149414,0.061523), White Point(0.313477,0.329102)
Display Luminance: Min Luminance = 0.500000, Max Luminance = 270.000000, MaxFullFrameLuminance = 270.000000
Monitor Name: Generic PnP Monitor
Monitor Model: LG ULTRAWIDE
Monitor Id: GSM59F1
Native Mode: 2560 x 1080(p) (60.000Hz)
Output Type: HDMI
Monitor Capabilities: HDR Not Supported
Display Pixel Format: DISPLAYCONFIG_PIXELFORMAT_32BPP
Advanced Color: Not Supported
Driver Name: C:\Windows\System32\DriverStore\FileRepository\u0374383.inf_amd64_12cfd68385ecddd5\B374323\aticfx64.dll,C:\Win dows\System32\DriverStore\FileRepository\u0374383.inf_amd64_12cfd68385ecddd5\B374323\aticfx64.dll,C:\Windows\S ystem32\DriverStore\FileRepository\u0374383.inf_amd64_12cfd68385ecddd5\B374323\aticfx64.dll,C:\Windows\System3 2\DriverStore\FileRepository\u0374383.inf_amd64_12cfd68385ecddd5\B374323\amdxc64.dll
Driver File Version: 30.00.14011.3017 (English)
Driver Version: 30.0.14011.3017
DDI Version: 12
Feature Levels: 12_1,12_0,11_1,11_0,10_1,10_0,9_3,9_2,9_1
Driver Model: WDDM 2.7
Hardware Scheduling: Supported:False Enabled:False
Graphics Preemption: Primitive
Compute Preemption: DMA
Miracast: Not Supported by Graphics driver
Detachable GPU: No
Hybrid Graphics GPU: Not Supported
Power P-states: Not Supported
Virtualization: Paravirtualization
Block List: DISABLE_HWSCH
Catalog Attributes: Universal:False Declarative:True
Driver Attributes: Final Retail
Driver Date/Size: 01.12.2021 01:00:00, 1819744 bytes
WHQL Logo'd: Yes
WHQL Date Stamp: Unknown
Device Identifier: {D7B71EE2-2B3F-11CF-DB75-C4F56EC2D335}
Vendor ID: 0x1002
Device ID: 0x687F
SubSys ID: 0xE37F1DA2
Revision ID: 0x00C1
Driver Strong Name: oem31.inf:cb0ae41418d44bb9:ati2mtag_R7500:30.0.14011.3017:PCI\VEN_1002&DEV_687F&REV_C1
Rank Of Driver: 00CF2000
Video Accel: Unknown
DXVA2 Modes: DXVA2_ModeMPEG2_VLD DXVA2_ModeMPEG2_IDCT DXVA2_ModeH264_VLD_NoFGT {4245F676-2BBC-4166-A0BB-54E7B849C380} {6719B6FB-5CAD-4ACB-B00A-F3BFDEC38727} {9901CCD3-CA12-4B7E-867A-E2223D9255C3} DXVA2_ModeHEVC_VLD_Main {EA72396A-67EC-4781-BEDE-56F498F04EF2} {C152CA8F-738C-461B-AD89-FC292CF8F162} {514A356C-7027-4AFF-8A60-AFD2C1F672F1} DXVA2_ModeH264_VLD_Stereo_Progressive_NoFGT DXVA2_ModeH264_VLD_Stereo_NoFGT DXVA2_ModeVC1_VLD {CA15D19A-2B48-43D6-979E-7A6E9C802FF8} {7C74ADC6-E2BA-4ADE-86DE-30BEABB40CC1} DXVA2_ModeMPEG4pt2_VLD_AdvSimple_NoGMC {D1C20509-AE7B-4E72-AE3B-49F88D58992F} {84AD67F6-4C21-419A-9F0B-24F0578906C1} {725AD240-786C-471E-AD3C-38F739936517} {95664FF5-9E03-4C74-BB4F-9178D6035E58} DXVA2_ModeHEVC_VLD_Main10 {65D1FA41-58AF-453A-9CAB-5D981156DA9F} {2DB154B6-DBB2-4079-A3FF-60D7A898A6AB} {C74A3FD0-D713-4581-A02E-8EDFB112ACE3} {603A4756-A864-4F91-BB62-2C935B7A1391} {C58B9A06-7E89-11E1-BB00-70B34824019B}
Deinterlace Caps: n/a
D3D9 Overlay: Not Supported
DXVA-HD: Not Supported
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled
MPO MaxPlanes: 1
MPO Caps: Not Supported
MPO Stretch: Not Supported
MPO Media Hints: Not Supported
MPO Formats: Not Supported
PanelFitter Caps: Not Supported
PanelFitter Stretch: Not Supported

You can probably help others help you if you tell us what you've tried already. At this point I only know that you have DirectX12 installed. That's about it.

https://www.warofrightsforum.com/showthread.php?5832-ERROR-CryInput-dll-could-not-be-loaded&s=21a8db447558ba8c748e60691949e635&p=88736&viewfull=1#post88736

As one of the people said on that forum, the problem is pretty common because it's an error the CryEngine throws for a few different reasons. The biggy is an issue with DirectX 12 itself. Or it could be something as simple as what kind of mouse you have connected.

... just a quick check: you do have a standard mouse connected when you run the game, right? A few people complained of this problem over the years and found out it can be triggered by having only a controller connected at the time (others had a mouse, but it was a Kensington trackball).