![]() ![]() Loading patch_ui_mp.ff from disc, not from the update drive Using picmip 0 on most textures, 0 on normal maps, and 0 on specular maps Using video memory size to cap used texture memory at 496 MB. PROFILES: setting server info to 0.0.0.0:0ĭirectX reports 512 MB of video memory and 635 MB of available texture memory. becasue if it was a registry issue then cod waw should have played without errors with the fresh windows 7 install.See if you can make sense of this it's the last part of the error log that pops up in the WaW console when I get the unhandled exception message. and when someone engages voice chat that is when I'm getting the unhandled exception caught error.ĭoes anyone else notice the same thing? If I'm right then it must have to do with my physical setup. so I'm thinking that my issue is related to voice chat. and on the ones with voice chat I can play for a short period then unexpectedly the error shows itself. One thing I think I've noticed is that I can play on servers without voice chat. then it started with the unhandled exception caught error not to long after. I had a work trip and when I returned 4 days later.bam, it worked again. then out of the blue the sound goes out again. ![]() like the day after it came out, was it november? well anyway, when I patched and had the sound issue I changed my setting to the 24bit 48000 settings and then sound was ok. The odd thing is that I played the game with out a hitch for over 3 months. and I still got the unhandled exception caught error. I installed on my other hard drive windows 7 beta and then only codwaw. ![]() 4gig ram and a power color 4830 video card(amd). I'm running an asus motherboard M3A78-EM with a triple core amd processor 8450,maybe. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |