Unfortunately, Win 7 become a "very outdated" OS.
"Note: Cyberpunk 2077 is a DirectX 12 game. DirectX 12 works on Windows 7 thanks to porting tools and features may be limited. Also, please mind that Microsoft ended official Windows 7 support in January 2020."
Cyberpunk 2077 - PC | Technical Support — CD PROJEKT RED
Welcome to CD PROJEKT RED Technical Support! Here you will find help regarding our games and services, as well as answers to frequently asked questions.
support.cdprojektred.com
I tried playing 1.23 version on Windows 7 and I didn't have crashes or any other issues, but I can confirm that 1.3 is unplayable (on Win 7).
I'm not picking on you but please note what was written:Unfortunately, Win 7 become a "very outdated" OS.
"Note: Cyberpunk 2077 is a DirectX 12 game. DirectX 12 works on Windows 7 thanks to porting tools and features may be limited. Also, please mind that Microsoft ended official Windows 7 support in January 2020."
And it's not likely to get betterCyberpunk 2077 - PC | Technical Support — CD PROJEKT RED
Welcome to CD PROJEKT RED Technical Support! Here you will find help regarding our games and services, as well as answers to frequently asked questions.
"Note: Cyberpunk 2077 is a DirectX 12 game. DirectX 12 works on Windows 7 thanks to porting tools and features may be limited. "
Now does it say that it will crash and at times be unplayable? It says "features many be limited". That is the key difference. [...] And here's the real kicker. Myself and others sent all this info to them about DX12 way back in December/january. They have a bug in their porting tool that is causing the crashes. We know all about Win 7 and DX12. World of Warcraft and others created wrappers (what they call porting tools) to get WOW to work. But just like the game itself there is a bug in their wrapper. It appears when looking in mirrors either in game or during cut scenes.
And just because MS ended their support for Win 7 doesn't let CDPR get off the hook. They said and continue to say that it will run under Win 7. Just go look at the required specs.
Cyberpunk 2077 System Requirements — Cyberpunk 2077 | Technical Support — CD PROJEKT RED
Welcome to CD PROJEKT RED Technical Support! Here you will find help regarding our games and services, as well as answers to frequently asked questions.
support.cdprojektred.com
So they say it works under Win 7. therefore they should fix their "tool" that mimics DX12 under Win 7.
Last edited by a moderator:
You can report it. If no one does, it doesn't help and maybe they will fix it
Personally, I can't blame a game developer for not dwelling on an OS too much, when the developer of that OS (Microsoft in this case) doesn't care anymore about it at all. So for me, unfortunately, Win 7 has to be put in the same category as Win 98/2000/ME/XP/Vista, completely outdated and abandoned OS
Last edited by a moderator:
in my opinion, CDPR really needs to update the system requirements for Cyberpunk 2077, regardless of weither this can be fixed or not. Windows 7 and 3GB of VRAM is not going to be enough for the next gen patch.Personally, I can't blame a game developer for not dwelling on an OS too much, when the developer of that OS (Microsoft in this case) doesn't care anymore about it at all. So for me, unfortunately, Win 7 has to be put in the same category as Win 98/2000/ME/XP/Vista, completely outdated and abandoned OS
It's a very little change, but the iconic weapon at Fingers is no longer on the bed, but on the table
I have reported it. But here's the difference that for some reason you don't recognize. CDPR does not say that the game will work on Win 98/2000/ME/XP/Vista. But they do say it will work on Win 7. That is the difference.You can report it. If no one does, it doesn't help and maybe they will fix it
Personally, I can't blame a game developer for not dwelling on an OS too much, when the developer of that OS (Microsoft in this case) doesn't care anymore about it at all. So for me, unfortunately, Win 7 has to be put in the same category as Win 98/2000/ME/XP/Vista, completely outdated and abandoned OS
And that is going to be a problem for them. They sold the game under the current specs. That means if they make changes and it no longer works we should get a refund.
I wonder, you set all graphic settings on "minimum" (the lowest ones) ?
Because if I look the requirement, Win 7 could run the game only if you select the lowest settings available.
(If I understand the requirements, even on recent high end PC, if you are on Win 7, you couldn't run the game with high settings...)
Even the front door ? In front of the security gates ? You have a screenshot ?
I and others have done everything. We have isolated it to the DX12 wrapper they use. The crashes happen when you see a reflection of V. This can be in a mirror, cut scene or other ways. The settings don't matter as the game can run perfectly on high and the second V's reflection is shown it does a hard crash. And if you set everything to minimum it will still hard crash. All of this and much more has been given to tech support. Shit we can probably fix it if they would let us but they won't give us the wrapper code.I wonder, you set all graphic settings on "minimum" (the lowest ones) ?
Because if I look the requirement, Win 7 could run the game only if you select the lowest settings available.
(If I understand the requirements, even on recent high end PC, if you are on Win 7, you couldn't run the game with high settings...)
That is what is most frustrating. The issue is known, the problem identified and a general solution is also known.
BTW one last interesting tidbit. Notice they don't list Win 8? But they do list Win 7.
It is 100% true that the game will work on Windows 7 -- provided the player has their DirectX 12 installation through Win7 completely installed and configured.I'm not picking on you but please note what was written:
"Note: Cyberpunk 2077 is a DirectX 12 game. DirectX 12 works on Windows 7 thanks to porting tools and features may be limited. "
Now does it say that it will crash and at times be unplayable? It says "features many be limited". That is the key difference. [...] And here's the real kicker. Myself and others sent all this info to them about DX12 way back in December/january. They have a bug in their porting tool that is causing the crashes. We know all about Win 7 and DX12. World of Warcraft and others created wrappers (what they call porting tools) to get WOW to work. But just like the game itself there is a bug in their wrapper. It appears when looking in mirrors either in game or during cut scenes.
And just because MS ended their support for Win 7 doesn't let CDPR get off the hook. They said and continue to say that it will run under Win 7. Just go look at the required specs.
Cyberpunk 2077 System Requirements — Cyberpunk 2077 | Technical Support — CD PROJEKT RED
Welcome to CD PROJEKT RED Technical Support! Here you will find help regarding our games and services, as well as answers to frequently asked questions.
So they say it works under Win 7. therefore they should fix their "tool" that mimics DX12 under Win 7.
Next onion layer:
It's not CDPR's responsibility, nor is it possible for the studio to affect in any way, the way a player has their PC configured...or what state their Win7 installation is in.
Next onion layer:
Microsoft has completely ceased any and all support for Windows 7 across the board. That includes additional support for DirectX 12. This does not negate the fact that the game will run correctly if DX12 is correctly installed on Win7 -- it means that if a player has a problem, there's no longer any way to troubleshoot it with Microsoft, and Microsoft is not going to add any future support for things like new drivers, new GPUs, new peripherals, etc.
So...if a player has Windows 7, and they have a problem with the game, and it's not being caused by the game's code...they're kind of up the creek. They'll have to individually figure out what's wrong with their DirectX 12 installation and fix it on their own. This will likely mean a complete reinstallation of Windows 7, as DX12 is only available through Windows Update -- there are no standalone installation packages like there are for DX9-11. If something is wrong, that's the only way to "update/repair" your DX12 installation.
Lastly, especially newer hardware is very, very, extremely likely to have issues with DX12 on Win7, as they will have been released after Microsoft officially cut its support for Win7.
So, what this means in the end is:
Cyberpunk 2077 supports DX12 running under Windows 7. However, this automatically means the user is running the game on an unsupported operating system. As long as you have your Win7 installation in perfect order, it should work just fine, though features may be truncated, as there's no way to make them functional using DX12 on Win7. Or the player's hardware has a conflict. Or the drivers are not fully compatible. Or...whatever else. In that case, nothing can be done other than say, "Please reinstall Windows 7." Troubleshooting future issues on the studio end is going to be problematic if Microsoft no longer supports its own OS.
TL; DR :
If using Win7, you're largely on your own solving any issues with CP2077 that may crop up. You can contact the team, and I'm sure there will be issues that can be solved or worked around -- but that support is going to be limited because of Microsoft's decision to abandon support for Windows 7.
_______________
And once again, a reminder that my thoughts are my own. I'm not speaking for CDPR, and I'm not making an official response about Tech Support. I am identifying the reality of the situation, and letting people know what lay of the land looks like in that regard.
A probable hitbox problem, so I think I could be very difficult to fix (except if you allow player to loot items through other object (but it will break other things...)
This is wrong because DX12 is not available on Win 7 for the user to add. ONLY a game company can add it. See this link as validation.
How to install the latest version of DirectX | Microsoft Support
Describes how to obtain the latest version of DirectX to enable games and multimedia applications on your system.
support.microsoft.com
Once again DX12 can not be installed. Instead the game developer has to create a "wrapper" program for it to work. See this link for validation and proof.
Porting DirectX 12 games to Windows 7 - DirectX Developer Blog
We publish binaries and documents to allow game developers to run their DirectX 12 games on Windows 7.
devblogs.microsoft.com
Microsoft has even said they worked with a number of game developers. So it is the game developer that is responsible for DX12 on a Win 7 platform. See this article that shows a number of game developers doing this.
Microsoft finally ports DirectX 12 to Windows 7, but only for certain games
Too little, too late?
www.pcgamer.com
That not just for Win 7 but for everything. Graphic card manufactures do this all the time with updated drivers. Plus the statement is inaccurate in that is not how it actually works on a computer. All the OS does is pass various calls back and forth between the game and the hardware. And since DX12 is NOT part of Win 7 that means the game company is the one responsible for changes.
What is actually means is Cyberpunk is SUPPOSED to mimic DX12 for Win 7 platforms since there is no such thing as DX 12 ON Win 7. The wrapper takes any new DX12 function calls and converts those to DX11 or changes them so performance isn't as good. But the statement of DX 12 running under Win 7 is false, inaccurate and simply not correct.
No because just like consoles CDPR made a statement that the game would work under Win 7. Even to this day they STILL say this. And like consoles it was a false and misleading statement. The difference is Sony had the power to force CDPR to fix their bugs and issues. In this case CDPR so far has ignored their responsibility to fix their program.
You're misunderstanding the way this works. DX12 does not work well on Windows 7. Some parts of it don't work at all on Windows 7, as they rely on functionality that was only present from Windows 8 onward. Microsoft, based on heavy demand, decided to "take a crack" at seeing how much DX12 functionality they could shoehorn into Win7. It was quickly discovered: not much...and what is there is likely to be both limited and quirky. But hey, at least that much works.
Several Windows Updates were then released that introduced DX12 files and functionality to Windows 7, then did a little bit of work on bug-fixing the basic functionality that had originally been introduced. In other words, it's like this:
If DX12 on Win8-10 includes A through Z, then DX12 on Win7 includes A-C, E-M, Q, S, and W. The other parts aren't available because Windows 7 doesn't support them.
It was then that Microsoft said to devs: "Here's what we can build in for you. But don't come asking us for help if something doesn't work out, and don't ask us to put any more stuff in there. We're also not going to build in any support specifically for this or that game. Work is done. This is what you get. Work with that."
This is very different from working with DirectX as it would be under normal, fully supported versions. There, as a studio, I can call in to Microsoft and say, "Hey, I'm having trouble getting this audio file to play at the right moment," or, "Sorry, but can I ask for this function to be added to the DirectX functionality so that I can create the visual effect I want?" This is largely what results in ongoing updates and new versions of DirectX. In the case of DX12 on Win7, Microsoft was saying, "Nope! Can't help you. You're on your own, studio! Good luck with the existing SDK!"
Yes: for Windows 8, 8.1, and 10. The same was also true for Windows 7 while it was still supported. But that support is now ended. If you don't believe me, try contacting Microsoft and seeing what sort of help they're willing to offer you working through an issue where CP2077 is crashing at launch...or failing to display graphics properly...or playing distorted audio...on Windows 7. The answer will be: "Sorry, support for Windows 7 is discontinued. Here's a link to online articles that may help."
You're right! It is! But we're talking about this particular issue concerning DX12 on Windows 7.
For this particular issue (modern gen hardware trying to run on a legacy OS version), the difference is that there will likley be no fixes forthcoming. Support for Windows 7 (including support for DX12 issues on Windows 7) is done. Any problems that exist are likely never to be resolved. So people that might be in this situation are banging their heads against a wall if they continue trying to get such hardware working with the game under Windows 7.
The same is not true for people using that same hardware on Win8-10. Those issues very likely will be resolved through future game updates, driver versions, DX12 updates, etc.
If you're arguing semantics, I'm not sure why. There is support for DX12 on Win7. It's terribly limited and very unfriendly to use. No one ever said that native DX12 runs under Windows 7. In fact, I specifically outline how there is no, actual, full version of DX12 on Win7. I go to some length to identify how problematic DX12 on Win7 can be.
What I said was:
Again:
This requires the player to have the files released by Microsoft (available only through Windows Update, which introduce limited DX12 support on WIndows 7) installed completely, correctly, and for the rest of their configuration (hardware and software) to be 100% compatible with it, or they're going to hit errors. If those errors are encountered, there is very little chance those errors will be successfully resolved in the future.
But why someone may ask?
Because Microsoft no longer supports even the wonky support for DX12 under Win7 that was introduced. Studios cannot contact them to make any needed changes to DX12 as it pertains to Win7, and that means that certain issues may simply have no solution. So, for any studio, that mostly means I either need to leave the bugs in the game...or completely disable whatever function is causing that bug. Hence, the game's options may be limited because of the nature of DX12 on Win7. What I'm clarifying is: there's not likely going to be any fixes down the road for these things.
If you're having an issue like this, the options are to reinstall Windows 7 (which will reinstall what support there is for DX12 from scratch), then keep your fingers crossed...or upgrade to Windows 10 (which can still be done for free).
That's because the game will work fine on Windows 7. But it requires, just as this is a concern for all players, on any version of Windows, using whatever hardware they have, to ensure that their system is configured properly.
That basically means:
1.) Best-case scenario: I own a PC built while Windows 7 was still supported. I downgrade my drivers and such to ensure that they're Windows 7 native. I ensure my Windows 7 installation is fully up to date. The game will work fine.
2.) Meh-case scenario: I own a PC that has most parts that were supported under Windows 7. Others may not be, but I can still get things configured on my own. The game will run fine, but may require me to disable certain things or put up with minor bugs because my system isn't 100% compatible with the software I'm trying to run.
3.) Worst-case scenario: I own a PC with lots of modern parts that are simply not fully compatible with Windows 7. DX12 support for Win7 can't communicate properly with my hardware and software. The game is not going to work. My system is not properly configured for Windows 7.
You do not understand this at all. DX12 does NOT come with Win 7. There is and NEVER was any DX12 for Win 7. There is only a "wrapper" which converts the DX12 to DX11 calls. I can not nunderstand why this concept alludes you. Microsoft never "took a crack" at it. Instead they provided their code to game developers so THEY could take a crack at it.
I provided a link that PROVES this.
dewvblogs.Microsoft.com said and I quote"
"We provide binaries and documents to allow game developers to run their Directx 12 games on Windows 7."
I don't know how much clearer that can be. It refutes what you are saying.
Support doesn't come from Microsoft because Microsoft never CREATED the DX12 wrapper code to begin with. The game companies are the ones that support it because they created it.
And here's the funny thing. If CDPR would publish this DX12 wrapper code the community would have a fix for it in days.
Once again you miss the central point. THERE IS NO DX12 RUNNING ON Win 7. Never was and never will be. The wrapper, or as CDPR calls it "porting tools" takes their code and when a DX12 function is called they convert it to DX11. Once you accept this FACT you will see where you were wrong in your comments.
Again Microsoft does NOT have any DX12 files for Win 7. Never had and never will. The game companies convert it in their "wrapper" or porting tools.
Look I understand you don't like me calling out CDPR for THEIR failure [...]. But this is the same as for the older consoles. Which BTW PROVES my point.
So what does that even mean? If by fine you mean crashes to the desktop (Cyberpunk has flatlined) then it's working fine. If by fine you mean never looking into any mirrror else you crash then it's working fine. If by fine you mean not being able to proceed beyond a cutscene because it always crashes there then I guess it's fine.
Also if by fine you mean EVERYONE on on a Win 7 PC has these exact same crashes then I guess that's fine.
Last edited by a moderator:
Call it "a version"...call it "a wrapper"...call it "hooking the calls"...call it whatever you wish.
Fact: Microsoft introduced limited support for DirectX 12 on Windows 7.
Fact: It doesn't work all that well.
Fact: It is only available through Windows Updates.
Fact: There's no further support for it. Not for users, not for studios, not for anyone. It's done.
These are the only facts that matter in the situation concerning CP2077.
Conclusion: If I have CP2077 on Windows 7 and have a DirectX issue -- I'm largely on my own, and my options are going to be very limited.
This is inaccurate or incorrect on every level. If you don't believe it, that's fine. You can believe whatever you wish. Can't help you.
What it means is:
If I bought or built a computer before 2014, I'll have hardware and software that will work perfectly with CP2077 on Windows 7. I may need to roll back drivers and such, but the game will work with my hardware, firmware, drivers, etc. in the end.
If I bought or built a computer, for example, in 2020, there's a good chance that my hardware, firmware, drivers etc. will not be fully compatible with DX12 on Windows 7. There will be insufficient legacy support for these things on Windows 7.
_______________
Now, let's talk about your claim that EVERYONE on Win7 having the same issue would be "fine". Nope -- people have all sorts of different issues. Mine was that after the Day 0 patch hit, I would get an occasional CTD. Mostly, I could use the character creator for hours on end with no issue. Then, at some point during the prologue, the game would crash again. Normally, it would be a few seconds after the start. Sometimes, I'd be able to play for a minute or two.
Cause? DX12 calls that were creating conflicts with my GPU and crashing the game.
Reason? I had manually disabled Windows Update, as I totally don't need all of their security updates on my system. Not running a bank; I don't use my PC in airports; etc.. Thus, critical updates for DX12 functionality on Windows 7 had been missed. I tracked it down to 6. I was able to manually install two, but the other 4 required too many prior updates for me to figure it out, and my personal management of the updates had made it far too messy for me to be bothered sorting it all out myself. (Didn't care enough.)
Solution? 2 options:
1.) Drive wipe and reinstall Windows 7, hoping that allowing for a full installation of Windows Updates got the files I needed and worked. But it could mean that I'd still have fiddling to do finding the best drivers, etc., as it had been many moons since Nvidia had released any Win7 drivers for my 980 ti.
2.) Finally bite the bullet and upgrade to Windows 10. Which I did and am very please with the OS overall. Honestly, it's the most game-friendly OS I've seen since WinXP. Beautiful performance, very friendly with legacy games, extremely robust. Problem solved.
Conclusion: If you want to fight with your system to get it configured correctly for Windows 7, knock yourself out. It can be done. There are thousands of gameplay videos running on Windows 7 all over the net. If there was a problem with the game, it wouldn't work for anyone. EVERYONE would have the same issue...
...and if EVERYONE had the same issue...
...that would be great! It would mean that there was something in CDPR's code that was causing it, and it would likely be quick to track down and fix. As is always the case when something works on these 3 PCs, but that one has a weird glitch, and this one crashes...that's a matter of the player's PC having an issue.
No, studios do not have total and complete control over DX12 functionality on Windows 7. No, they cannot rewrite the "wrapper" the way they want. That would not only be impossible, because core parts of the SDK are still encrypted, but it would be illegal as studios do not have the right to modify licensed IP. All studios must work within the existing "wrapper" as it is. If something cannot be made to work, that's it. If players encounter weird issues, there's not much to be done.
Or, believe whatever you want.
The building doesn't have doors to enter in it. But it impossible to go up as the lifter is locked, the staff only door is also locked like the door on the left.