Wednesday, July 23, AM. I had create a repository and points to the location of the driver files I also associate the component with the repository via the component's settings page.
Thursday, July 24, AM. Now the drive to solve all the problems already, horm also realized, but in the realization of horm ausu on each boot the system gave me two options 1 Delete the data reduction and processing system Start Menu 2 to continue to re-launch system How can we ask the kind so that the system will not achieve horm there after the selection menu?
My computer will not appear in other such cases, but the Asus notebooks on the realization of such a situation What is wrong? Let me describ my steps first, 1.
Import the. However, what you posted doesn't even make sense even for Half Life. The way drvmap. The way the file format for drvmap. So when you choose "Defualt" in the menu, you are chosing the "Defualt" driver, which I assume is a variable in the software with a path to your opengl Defualt is what is automatically selected for everyone.
As in zip, nada, zero. For that to work, you would have to go into your video modes, and select what I can only assume would be the second entry in the drop down box, which would be empty. That doesn't make any sense. At least then you know what you are choosing in the menu. It will say "OpenGL Driver". I am sure whoever orignally came up with this idea for Half Life, not Steam actually knew what they were doing, but it appears it's been passed around so much by people who are totally clueless that it's lost all meaning.
I can only guess that the reason it "worked" for you is that either A you never had it selected to begin with, and you got that message anyway as we all do sometimes not sure why it happens. Or B When you switched back to opengl it switched back to the "Defualt" driver. Go to your video settings and I bet you have "Defualt" selected. Again, I am talking about Half Life here, not Steam. Just to make this absolutely crystal clear, drvmap. So if that is what you are talking about as is indicated by your original post , this was all a figment of your imagination, or else it was something else you did that caused your FPS to increase.
So, now that we have this squared away, I emplore people to stop passing around snake oil fixes that don't do anything, and only confuse the issue. You are absolutly right that editing the file does absolutly nill. But I know i'm not just imagining that my frames have increased. However I've noticed that when i delete the drvmap. When I cs opens my frames will be fps just like when I first installed 1.
Furthermore, when I switch to software than back in opengl, cs goes back to normal using the systems gl drivers and i get constant again. And I don't mean to pass around fixes that don't work. But I'm definate that I did not do anything else that could have altered my frame rates.
Last edited by johnnyutah : Dec 10, at AM. Well, I'm willing to try anything once, so lets go over this. Obvously editing drvmap. Is there anything else you can think of? That didn't do anything for me. If you can reproduce both the poor framerates, and then good framerates after whatever "fix" you are doing, that is a lot more than anyone else has been able to do. Please let me know exactly what you do to make the frame rates become poor again, and then what you do to make them go back up.
Stab: I've messed around with that and I see no difference. Those settings are of course for truform. I have truform off in the video card settings. If I turn truform on in the video card settings those console commands will effect the truform.
I am curious, when you mess with the settings, do you see any difference other than the frame rate? For me, it was quite obvious when truform was on or not, because all models not map stuff, but players and stuff would get "marshmellowy". But i run the game with 4xAA and 8xAF x x models are too small and aiming more dificult, i didnt thing there was a difference but after a few hours there was.
Thread Tools. All times are GMT The time now is AM. Also tweaked I have exact same problems with breakup after minimising UT. Don't supose you can fix the flaw with UT under vista locking up after certain auth systems have done their work? Yep good assumption. Just worked out that this is actually very easy to fix - just create a custom profile for UT in the NVIDIA control panel and disable threaded optimisation.
Job Done! GJ Chris! Nice PDF. Fixed it for me with GT and Phenom Also had the problem with GT and Phenom , but that card died on me so can't test this fix. I switched to Direct3D8 on that one, which worked fine too. But if you really want OpenGL, this fix is the way to go!
0コメント