- Joined
- Oct 17, 2021
- Messages
- 807 (0.61/day)
- Location
- People's Republic of Banania
Processor | Threadripper 3955WX |
---|---|
Motherboard | M12SWA-TF |
Cooling | Arctic Freezer 4U SP3 |
Memory | G.Skill Trident Z DDR4-3733 (2x8GB) |
Video Card(s) | 5700XT + 3x RX 590 |
Storage | A lot |
Display(s) | ViewSonic G225fB |
Case | Corsair 760T |
Audio Device(s) | Sound Blaster Z SE |
Power Supply | be quiet! DPP12 1500W |
Keyboard | IBM F122 |
Software | 10 LTSC |
The Tomb Raider game issue could've been related to the ridiculous DRM malware it's packed with, those tend to create weird errors and glitches most of the times if you dare mess with Windows settings or mod it in some way, sometimes you can't even start some games if you don't have an internet connection, that'd be the improved version of having the game disc on the drive at all times while you were playing.
But anyway, I said it could've been related to that because of the date, the thread is from 2016 and Crapuvo wasn'tremoved disabled until 2021 for that particular game, that thing can't be fully removed as it'd break important parts of the games, so what crackers often do is bypass it so the game file still works without having to call the DRM to start.
I've played that game, with the WS service disabled, and had no issues, but also had a dormant DRM. It's not a problem caused by indexing.
But anyway, I said it could've been related to that because of the date, the thread is from 2016 and Crapuvo wasn't
I've played that game, with the WS service disabled, and had no issues, but also had a dormant DRM. It's not a problem caused by indexing.