My 2013 laptop with its Intel graphics card may have crashed a few times while I was doing intense quest work on Telos, but nothing that restarting the game and reloading a save didn't fix. Telos citadel was easily my least favorite place to be, but now it looks waaaaay better than it used to.
Note: if you can't find your 'swkotor.ini' file by following the steps above, try following this path instead: Library > Application Support > Knights of the Old Republic. Your 'swkotor.ini' file might be hiding in there if you're playing on Mac via Steam. Once you've found it, pick up with the bullet point in the list above that starts with the words 'Right click'.
Kotor 2 Graphics Overhaull
Download File: https://ssurll.com/2vzNGB
3) Click the Update button next to the graphics driver to automatically download the correct version of that driver, then you can manually install it (you can do this with the FREE version).
3. Double-click on the name of your graphics card. A smaller window will pop-up that contains the graphics card properties. There are 5 tabs at the top, click on the second one that says Driver.
4. The Driver tab will show the name of your graphics card at the top and a bunch of information about the currently installed driver. There are 5 wide buttons on the bottom-left with descriptions to the right of them. Click on the second button, Update Driver.
I was facing the same issue and tried all the solutions in this post and many other ones I found on the internet (some involving tweaks in the registry) too but none worked for me and I was really frustrated because this problem started occurring in a new laptop I bought less than a week ago and this was my first computer with an AMD processor. Luckily I came up with a solution which is a combination of some of the solutions I found from all over the internet. So just some background info, I am running an HP Pavillion 15 laptop with an AMD Ryzen 7 5700U processor with AMD Radeon graphics on Windows 11 Home 22H2 (dev channel). The problem that I think is happening is that Windows 11 update is incorrectly choosing the AMD drivers for my hardware, therefore the update installs a driver not compatible with my AMD hardware. Now let's get to the solution
Hi everyone, I'm new to the forum and I signed up to look for a solution to the following problem:I bought the amd rx 6700 xt graphics card.I connect it, install the latest drivers (adrenaline version 21.4.1) but halfway through the installation I hear that the card "detaches" (sound of device removed), the screen goes black and there is no video signal (the HDMI symbol appears on the screen).This is usually normal in video card installations, but I waited half an hour and the screen remains black and no video signal.The really weird thing is that I have been testing and testing for days, reinstalling windows 10, all motherboard drivers, etc., and SOMETIMES the video card works.I managed to get it working several hours after a few windows reboots, other times after reinstalling the drivers, other times by disabling and re-enabling the video card in safe mode.But every time I turn off the PC and come back a few hours later or the next day, the video card no longer works.Currently I am able to turn on the pc, I arrive at the windows loading screen but, just before the password entry screen, the screen goes black and there is no video signal.
I had the same issue today after updating the graphics driver recently my computer booted then my monitor when into power save mode after the bios, I entered safe mode uninstalled all AMD stuff and then installed the last driver 21.3.2 and its all working again something is up with the latest driver I think.
I am having a similar Issue every day After I turn on my PC I get the bios post screen then the screen goes blank. If I boot into safemode or start the computer with the onboard graphics of the mobo I can see that the driver no longer works or is recognised by the AMD software, I uninstall it and re-install it and I am good until I shut down and turn it back on the next day. Really annoying and worrying.
System was running for more than 3/4 of a year very good with Windows 10 Th1 and Th2. Particulaly, there were never any graphic issues on the Desktop, e.g. corrupted graphics or such. However, from time to time (very occasionally, maybe once a month) the display hung for
I have tried different graphics drivers (Lenovo, Intel, Intel beta) but all of them showed this behavior. This occured on both wired and battery operation and was independent on battery saving options (I played around with all of them). I even set BIOS back to defaults but it did not help.
When the PC was slow and the graphics corrupted, uninstalling the Intel driver helped. So when Windows removed the Intel software and activated its built-in standard VGA driver, the PC was fast again (of course screen resolution was low and the graphic animations not perfectly smooth). After reboot, Windows automatically installed the Intel driver again and again, after the "trigger" (e.g. AIMP) everything started again.
Then there was a comulative update to Win 10 1607, KB3176495 build no. 14393.51. After installing this update, the graphics was already corrupted after reboot. (No trigger required any more). And the graphics issues were even worse. In the start menu, all colors fainted (got darker), the text became black, and other things. After KB3176495, the PC did not get so extremly slow any more, but it still got noticeably slower whatsoever and moreover the graphic corruption was much much more serious! Again, I have tried different graphics drivers and also different graphics setting, but no success.
What makes me suspicious is that there is not a problem at all with 1511 and reproduceable buggy in 1607 with any driver I could find. Microsoft must have changed something in a way it messed up this graphics feature.
When I first installed 1607 beginning of August I also had other graphics problems with the start menu (with or without AIMP). Those are now gone, but I still feel like this is a general issue and nothing related to AIMP only (although I have not found another program so far which triggers this bug). 2ff7e9595c
Comments