Project Reality Forums

Thanks for replying. So clearing the shader cache fixed it? Does it happens again after that?

Not sure 100% but it seems to happen less if I clear my shaders every time I close pr. Hasn't obviously happened when I do so since the couple times I've tried it. I haven't tried reinstalling or deleting my profile since it seems to have not happened yet, and if I've cleared the shader cache each time I close pr,or if it crashes, it seems to not pop up from what I can tell if it hasn't popped up before I cleared it.Basically if it happens, then if I clear shaders, usually rebooting or it doesn't go away, then if it's fine when I'm playing,and I clear them each time I close the game, or the game crashes before booting the game or rebooting my computer, it stays away for now, and most likely clearing the cache and rebooting will probably clear it again if it happens as it did before. So I might of found a way to avoid it. Or make it a possible mostly preventable inconvenience. Before I only would clear the shader cache when I reboot(full shutdown) my computer ( I usually clear it anyway since sometimes,especially sometimes in fh2 the shaders get corrupted occasionally if they aren't cleared every so often),so I never tried always clearing it after closing or crashing the game since it takes longer to get back if you just got crashed from a squad position,or just played and it was working. I might see if deleting my profile,or if that doesn't work reinstalling bf2 fixes it completely if this doesn't work or it happens again. But for now I will try this method unless it starts happening again. On an afterthought it could also be the pr download for all I know if deleting the profile wouldn't fix it, so I might try downloading the installer (although it would be the full one instead of 9.57 then the 2 patches to 9.66 then 9.73) again before reinstalling bf2 if the profile being replaced wouldn't fix it. Although I think it was happening before I downloaded the 9.57 full installer, so maybe,maybe not.On ANOTHER afterthought(lol) again, it might of started around the time,before or after, I got the .957 version of pr, so I might of underestimated how long that version was the latest, or when the problem started since I checked when I downloaded (the date on the files properties) the file. Which was 10/15/10 (.957 full install) if your curious. The other two patches 7/15/11 (.966) and 9/4/11 (.973) respectively.

Just a final comment. Since I started clearing the shader cache every time I close pr, it seems to almost never occur. One time when it did, closing the game and clearing fixed it without rebooting. Basically, it seems that clearing the cache fixes the problem as long as I do it usually, and it works normally. So from the problem starting to getting rid of it was like this; Usually I clear the shaders every time I reboot, it would leave. Pr would work normally after starting it,shaders were loaded, and all was fine. After I closed pr, In the past I only cleared the shaders if there was a problem with the graphics or before,or after if I forgot, I rebooted the pc. So I start the game with the same shaders that were cached when it ran before. The problem would randomly start after that or after closing and starting pr a seemingly random number of times. If the problem started as it normally did,when I'd run pr a few times over hours or a few days without clearing the cache before starting pr,and the problem usually starting,then only going away after clearing the cache and rebooting my pc, it wouldn't usually go away if I cleared the cache after the problem started until I rebooted since I hadn't cleared it before it occurred once again (it probably gets loaded into memory). But if I clear the cache when I reboot my pc(or working normally would probably work),and before starting and after (or just before, but less likely to forget that way)closing pr, it seems to not happen or only happen occasionally, as compared to starting randomly as it often did before, and clearing the cache is quicker and less frustrating than rebooting completely after just a few hours, or bearing with it. I haven't tried reinstalling or deleting the profile since this seems to negate the problem (at least for now).