Mouse 1

[tes]

Hello, my name is Tim, I'm from Berlin and because I grew up in East Germany, I don't speak English very well.
I'm sorry about that.
I've been playing Dark Project since 1999 and I'm very grateful that TDM exists.
I just played A Night in Altham.
Yesterday the mouse 1 button (Attack) stopped responding. The mouse wheel still worked, but I couldn't call up a weapon to use it.
I changed the mouse button mapping, quit the game, restarted it at save points, but the mouse 1 button would not relay the command.
I reinstalled the game using the existing installation.
After that, the saves were lost as I had downloaded a newer version of TDM and all save points were gone.
I started the mission again with the new version and realised that, for example, when I drew the bow, I could see the arrow but not the bow.
So I deleted the game completely and reinstalled everything.
I invested a lot of time in the mission and completed all but one of the missions, including the optional ones.
All the missions I had played before worked perfectly. Input via mouse 1 works with all other PC applications.
If I play the mission again, do I have to expect the error again?

Many thanks for any answers.

The PC's operating system and driver configuration are up-to-date:

Operating system name Microsoft Windows 10 Home
Version 10.0.19045 Build 19045
System manufacturer ASUS
System model All Series
System type x64-based PC
System SKU All
Processor Intel(R) Core(TM) i5-4460 CPU @ 3.20GHz, 3201 MHz, 4 core(s), 4 logical processor(s)
BIOS version/date American Megatrends Inc. 2106, 27/11/2014
SMBIOS version 2.7
Version of the embedded controller 255.255
BIOS mode UEFI
BaseBoard manufacturer ASUSTeK COMPUTER INC.
BaseBoard product H81M-PLUS
BaseBoard version Rev X.0x
Platform role Desktop
Secure boot state On
PCR7 configuration binding not possible
Windows directory C:\Windows
System directory C:\Windows\system32
Start device \Device\HarddiskVolume1
Locale Germany
Hardware abstraction level Version = "10.0.19041.3636"
Installed physical memory (RAM) 8.00 GB
Total physical memory 7.93 GB
Available physical memory 4.05 GB
Total virtual memory 17.4 GB
Available virtual memory 11.9 GB
Size of the swap file 9.50 GB
Hyper-V - VM monitor mode extensions Yes
Hyper-V - SLAT extensions (Second Level Address Translation) Yes
Hyper-V - Virtualisation enabled in firmware No
Hyper-V - Data Execution Prevention Yes

Graphics NVIDIA GeForce GT 610

PNP- Gerätekennung PCI\VEN_10DE&DEV_104A&SUBSYS_847B1043&REV_A1\4&3834D97&0&0008
Adapter type GeForce GT 610, NVIDIA compatible
Adapter description NVIDIA GeForce GT 610
Adapter RAM 1.00 GB (1,073,741,824 bytes)
Installed drivers C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_c1a085cc86772d3f\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_c1a085cc86772d3f\nvldumdx. dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_c1a085cc86772d3f\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_c1a085cc86772d3f\nvldumdx.dll
Driver version 23.21.13.9135
INF file oem38.inf (section Section002)
Colour levels Not available
Farbtabelleneinträge 4294967296
Resolution 1920 x 1080 x 60 Hz
Bits/pixel 32
Memory address 0xF6000000-0xF6FFFFFF
Memory address 0xE8000000-0xEFFFFFFF
Memory address 0xF0000000-0xF1FFFFFF
I/O port 0x0000E000-0x0000E07F
IRQ channel IRQ 16
I/O port 0x000003B0-0x000003BB
I/O port 0x000003C0-0x000003DF
Memory address 0xA0000-0xBFFFF
Driver C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\NV_DISPI.INF_AMD64_C1A085CC86772D3F\NVLDDMKM.SYS (23.21.13.9135, 16.73 MB (17,544,792 bytes), 15.11.2023 16:42)

Translated with DeepL.com (free version)

[nbohr1more]

Please post your darkmod.cfg

and the output of:

condump mouse_issue.txt

( open the console via CTRL+ALT+TILDE )

https://wiki.thedarkmod.com/index.php?title=Reporting_Problem

[tes]

Thank you very much for your answer.
The data I am sending is from a new installation, I have adjusted the settings.
The bugs described are not present in the new installation.
The text input for the console is not accepted by the console:
"added to the dump for full lines in the console fix for long file paths being broken up in the output"
Sorry for that.

Darkmod-cfg.txt

[tes]

Thank you very much for your answer.
The data I am sending is from a new installation, I have adjusted the settings.
The bugs described are not present in the new installation.
The text input for the console is not accepted by the console:
"added to the dump for full lines in the console fix for long file paths being broken up in the output"
Sorry for that.

[nbohr1more]

Thanks!

I don't see config problems so I think this issue is mission specific.

I advise discussing with the mission author @joebarnin