Why then did they said it would work under Windows 7. Per you the solution everyone on a Playstation should do is just buy a PC.
Because it will work under Windows 7. However, getting my system 100% up to spec with the rickety way DX12 was implemented into Win7 is
my responsibility. In my case, it would have required a complete drive wipe and reinstallation of Windows 7 and all updates.
I wasn't going to do that, as this is not the first time I've had to forego some feature or driver option because I didn't have Windows 10, yet. Thus, I opted to finally make the switch to Win10, instead. And...problem solved. (Understand, I have been outrageously stubborn about these things over time. But if I'm going to intentionally be stubborn, I can't complain when banging my head against the wall results in a headache. I need to just pop some Tylenol and continue banging. I've also managed to get through many a wall with nothing but my head.)
So, it is possible to get it working if you're determined. It may simply take a lot of work since support for Win7 is now completely and utterly discontinued. To me, it wasn't worth it to reinstall the Win7 if there was a chance I might miss a step and have to do it again. And since a reinstallation of the OS was necessary either way to get it running, I went with the path of least resistance. It was time.
It 100% is related to DirectX 12. The program makes a call that is not supported. Now Microsoft never actually created a DX12 file for Win 7. However, they allowed game companies to write their own "wrapper" Blizzard did this and created a wrapper for WOW. CDPR was the responsible party to create the needed wrapper and include in in their installation. Otherwise they should never have said it was Win 7 compatible.
I would not write or complain if they simply said Win 10 required. Of course I wouldn't have bought the game. Right now this just adds to their credibility problem.
I'm leery of updating to Win 10 because of some very bad experiences by others I know. I don't want to do a clean install as I'll lose to much that I have on this PC. When things go wrong you have to wipe everything and do a fresh install. There is no undoing the update process. I'm not against Win 10 as I use it for work. It's the getting there that I'm really worried about.
Exactly. Cyberpunk may be a bit more complicated under the hood than other titles that have utilized DX12 on Win7 (of which there are actually very few). If players want to tackle it, then they'll have to deal with whatever problems crop up on that end, send in tickets to Support, etc. It's the same for all such games, but I'd imagine, based on what I was seeing from my own experience on Win7, that it's probably not worth the struggle. Not when there's a much easier and totally free solution standing right out in the open.
But, to each their own. If you're determined to stick with Win7, then I bet you'll wind up with a playable game in the end. Might be quite a hike, though, depending on what sort of issues you're encountering.
Incorrect. System requirements mean the game should work without CRASHES. The game is NOT running on Win 7. It crashes unless you do some crazy shit. Now CDPR also did not come up with this fix. Myself and another person figured it out. If we didn't try all kinds of stuff there wouldn't be a workaround. You clearly have no concept or idea of the problem. I get 50-60 FPS EXCEPT during a few cut-scenes and when looking into a mirror.
Crashes have nothing to do system requirements unless you're under the minimum or so far over the maximum that the architecture no longer applies. The vast majority of stability issues across all titles are a result of the PC not being correctly configured for gaming. A "bug" in a game is universal -- every single person on the face of the planet will see exactly the same thing in exactly the same spot for exactly the same reasons. That's a
bug. As I stated, I completed my ~50 hour playthrough of the game with only 2 crashes, and neither one occurred twice. That proves the game is actually in stable shape, even if it's extremely particular about what it will and won't play nicely with. (Witcher 3 is much the same way.)
PC players will always need to tweak their system to solve issues with whatever title if they pop up. Just because I'm seeing an issue doesn't mean that everyone else is as well. Just because I'm not experiencing an issue doesn't mean there isn't one for other players. If I'm playing on a system built of non-standardized hardware and software, and I'm experiencing weirdness, it's up to me to figure out what on my system may be causing the issue. Figuring out if it's a system problem or a game problem is really simple. A quick Google search will return one of two things:
- Direct hits with players experiencing the same issue across PC, Xbox, Playstation, Switch, etc. This is likely a bug.
- Random and scattered issues that apply to only pockets of players on only certain platforms. This is likely system config.
Many people believe that if there's a problem with a game, it's automatically the studio's responsibility to fix their issue. This is mistaken. No studio is responsible for providing perfection.
Most problems that appear are on the user's end. It's then a very good idea for studios to try to address those problems if they can. Many "fixes" that are included in games are not implemented because there's anything wrong with the game -- they're attempts to add tweaks and workarounds because some random driver or widely-used 3rd-party app is conflicting with a game function. Just because a studio takes the time to address such things does not mean that it was the studio's responsibility nor that they were in any way required to make such a change. It's often the shortest distance between two points, so there's no reason not to hop in and help.
End result is:
If I'm intending to game on PC, then learning my machine and getting into the nitty-gritty will be needed regularly. That's both to fix issues that result from system config, and to help identify actual bugs which can later be patched. This is how it was in the 1980s. This is the way it stayed over the decades. This is the way it will remain in the future. Not liking it doesn't change it.
Windows 7 DirectX support is finicky. That's the reality. Support for Windows 7 is completely discontinued. That's the reality. Fixing any DirectX issues on Windows 7 is the user's responsibility. That's the reality.
Like I said, you can get it working, but it will likely involve the following:
- A complete drive wipe and reinstallation of Windows 7 to ensure all applicable Windows Updates introducing DriectX 12 fucntionality are applied in the correct order.
- A roll-back to driver versions that will be compatible with DX12 on Win7. Newer driver versions will probably have issues.
- Deactivation or uninstallation of any software that may conflict with DX12 on Win7.
- Special permissions being activated on the Win7 game that you wish to run in DX12 mode.
- Specifically modified .DLL files to replace standard GPU driver or audio files to be compatible with certain hardware running in DX12 mode on Win7. Depends on your CPU / GPU combo and driver versions.
I'm 100% confident I could get it working, but I'd be expecting weeks of trial and error since there's no way to contact Microsoft for support anymore. Thus, I opted to just Win10 it.
forums.cdprojektred.com
support.cdprojektred.com
