Debriefing > Bug Reports & Fixes
GoldenEye: Source is messing up my VRAM and even breaking my GPU.
Kratos:
--- Quote from: Proxie on October 29, 2012, 11:14:18 pm ---Put your video card back in the oven, it's still raw in the middle.
--- End quote ---
LOL oh man my stomach!
and cook us some bacon in the meantime!
Mangley:
Have you actually tried reseating your GPU? You'd be surprised how simply disconnecting and reconnecting stuff to your motherboard can remmedy faults.
BMS and GE:S push source to its limits and do things that it was never intended to do in the first place. In our case it's our use of high resolution normal maps combined with liberal use of dynamic lighting effects that seems to eat frames for breakfast. Even though source is a lightweight engine that can run on practically anything, Valve never pushed it as far as we did (at least the version modders are restricted to) and they never optimized or fixed things that weren't going to be utilized by them for any specific title. Even now, GE:S is still more graphically detailed than CS:GO is technically speaking, and we don't even have the luxury of dynamic world lighting maps.
Try turning off dynamic explosion lights in the options that tends to resolve most of the issues people have.
Yes! I am Invincible!:
Ok i ''think'' i fixed this. I monitored Black Mesa: Source VRAM usage and it used 480 MHz of ram. well i overclocked RAM to 1000 MHz and now there's no errors.....YET!
So the problem was that GE:S and BM:S used too much VRAM (normal RAM clock was 512 MHz)
and now it has some extra space and doesn't stuff itself full of shit.
haha, nice one Proxy xD, That's Funny
kraid:
Not sure if it's a good idea to overclock it that much when you allready had to fix it with baking.
killermonkey:
RAM usage is not measured in MHz. What you are talking about is the data delivery clock signal, basically how fast data is requested and delivered to/from the processor.
By overclocking by nearly 100% you can nearly guarantee to see errors down the road. But we shall see, it could be that your ram was ubderclocked for some reason and was causing the corruption issues (not common).
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version