Counter Strike Psp Iso Download
Arnau Cyr
I'm using an Intel Arc A750 LE and after upgrading from the 4887 WHQL driver to 4952, 4953, and 4972, I've noticed that there are occasional texture flickering issues in Counter-Strike 2 (CS2) using DX11. I've used DDU in safe mode for all upgrades and I've cleared the DirectX Shader Cache. The GPU is not overclocked.
It seems to happen most at round starts, showing of scoreboard, and when bringing up the chat wheel. It looks like a bit of (mostly) white static noise across the display. It goes away within a second or so, but it is distracting. It probably happens 5-10 times during a 10 minute gaming session.
I've given the new 31.0.101.5074 driver some more thorough testing with MSAA enabled in Counter-Strike 2 and my conclusion is that the issue has been fully addressed. The issue appears to have been introduced as a regression in driver 4900 or 4952.
Thank you for providing us with all the necessary information. We understand that it may take some time to capture the video demonstrating the issue you are facing. We would like to assure you that we are willing to wait until you share the video with us. Also, please let us know if you encounter any difficulties while recording the video.
I've tried to capture a video of the issue with the Intel Arc Control software, but even though the flickering is visible on the monitor, it isn't captured in the output even with the highest capturing resolution, frame rate, and bitrate. So, instead I captured it with my phone camera (most visible around the 4-5s mark):
This is driver 4972 on an Arc A750 LE using DX11 (DDU'ed, etc). The issue seems to be affected by the anti-aliasing settings. The video above is with MSAA x8, but I've seen the issue with MSAA x2 too. If I use CMAA2 instead, the problem appears to go away. Attached is the SSU report from the system after updating to driver 4972 and reproducing the issue. The issues seems to be a regression since driver 4887 (WHQL) does not exhibit the same behavior.
I've tried with Vulkan too (specifying -vulkan as a launch option), but there is a whole new level of texture glitches on Vulkan both with MSAA x8 and CMAA2. Others have reported the same thing, so I does not appear that using Vulkan is a good choice for Counter-Strike 2 just yet.
Thank you for taking the time to record the video and capture an image that shows the graphical error. We appreciate your efforts in providing us with the necessary information to understand the issue you have described. We will be conducting a thorough internal review of this issue reviewing the information you shared. We will keep you updated as soon as we have more details.
Thank you very much for providing us with the information. We appreciate your effort in testing the game with different settings. The more details we have, the better we can investigate this matter. We want to inform you that we are still investigating this issue, and although we don't have an update yet, rest assured that we are working on it.
We would like to inform you that we are still investigating this issue internally. Although there isn't a current update on this, we are actively addressing the issue and will do so as soon as we can.
Do let me know if you find the reported issue reproducible or not. If the engineering team has a hard time reproducing the issue, I'd be happy to help out any way I can. Reproducing an issue is usually the most significant part of solving an issue.
Are there any updates on the reproducibility of the reported issue? I see a number of reports of poor MSAA performance on the Community Issue Tracker, but is unclear if those are related to the anti-aliasing induced flickering I reported back in November.
Thank you for getting back to us on your thread. We want to let you know that we're still investigating the problem internally, but we don't have any updates to share at this time. We understand that other users have reported similar issues with MSAA, but we need to look at each issue to determine the root cause. It's possible that even if two users are experiencing the same symptom, but different applications, the underlying cause may be different. That's why we need to investigate and confirm the root cause of each issue before we can implement a fix.
I've done a quick round of testing on the new 31.0.101.5074 driver and it appears as if the problem has been addressed, not just on MSAA x4 as noted in the release notes, but also on MSAA x2 and x8. I will start using MSAA anti-aliasing in Counter-Strike 2 from now on and make notes of any issues I discover. Give me a few days and I should be able to confirm if the issue is really gone.
We appreciate your efforts in testing the new driver version. We are glad to know that it seems that the issue has been addressed, but you would like to play the game using g MSAA anti-aliasing in Counter-Strike 2 taking note of any problems you may discover. We will wait for you to test the game. Please do not hesitate to let us know if your original issue persists. If you encounter a different problem, we recommend that you submit a new thread. Reporting one issue per thread will help us keep the topics organized. We will wait for your response after testing the game.
We have received your feedback regarding the MSAA problem in Counter-Strike 2 and we are pleased to inform you that the issue has been resolved. As a result, we will be closing this thread. If you require additional assistance, please create a new question, as this thread will no longer be monitored.
Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.
It seems at the moment no other community member is looking to report crashes on CSGO2 so following our previous recommendation, it would be better to check with Valve or to wait for them to continue patching the game and improving its stability, however, in case any other issues come up and you have the steps to reproduce the problem we will be more than willing to continue testing this game. We know this is a very popular title and will be happy to help.
If the same issue still happens after the above steps we might need to test this problem from our side, in that case, we would like to get the in-game graphics settings you are using so we can test in the same conditions, if possible to share a screenshot it would be better.
Along with the in-game graphics settings, we would like to know the exact steps to reproduce the problem, From what I see in your post this happens when getting into the different game modes but should the issue happen right after loading the game mode or during regular gameplay.
Yes, I did update the motherboard bios and did a clean install of the gpu drivers with DDU. However I noticed that the game started running smoother without these glitches when loading into games prior to me updating my bios and drivers. This issue was then probably addressed in a game update by Valve.
Then again now I have started to come across inconsistent game performance since updating my bios and reinstalling drivers in the form of random game crashes. I have updated my drivers since my original post to the .4885 driver version, but I am still experiencing game crashes.
Here I have attached screenshots of my in-game settings that I have encountered these issues with. As I previously tried to explain, this behaviour seems very inconsistent, and I could therefore not replicate a game crash.
I speculate it has something to do with molotov grenades being extinguished by smoke grenades, as it seems to occur during this kind of situation in-game. Though I could not recreate this on my own in a private match, but I did observe a sizeable drop in FPS during this action (from around 220 to around 140).
Hope this will help.
Just to make sure from what I understand from your previous posts, the main, original issue which was a partially frozen screen is not happening anymore but now there are random crashes that seem related to Molotov Grenades, Is this a good summarization of the situation?
Also, there has been a new driver update version 31.0.101.4887. Please let's retest with the new version and check if the same issue still happens. If possible as previously advised continue to use Display Driver Uninstaller before updating to the new version.
Thank you for clarifying and confirming the issue still happens after testing driver 4887. Let us take a look at this issue and check if we might be able to reproduce it. We will let you know once we have more information.
We wanted to give you an update on this issue and a couple of recommendations as well. We have been testing this game in multiple multiplayer matches and tried also with the Molotov Grenades, however, we have not been able to reproduce any crashing behavior so far and the game has been working fine without issue.
Please let's try updating to our latest driver version 31.0.101.4900 using the DDU method we shared in previous posts, and make sure to update the game to the latest version since Valve has released a few updates since our last post. In case the issue continues to happen after updating the game, we would advise that you uninstall completely, redownload, and reinstall the game to make sure the issue is not caused by a corrupted game file.
I wanted to check if you had the chance to retest the game with our latest driver or if you have reinstalled the game on your system. Please let us know if the issue is still happening. Check a video of the tests we have done so far in the following link =ZMwpcxx7WJc, however, as informed in our latest post we have not been successful in reproducing this issue.
7fc3f7cf58