Twitch was having some problems yesterday. Try again today maybe.

http://dolphin-emu.org/

Use the new site.

I'm making one of these. Works on Windows so far, doing a Linux test in a bit.

Edit: Works on Linux.

You won't be able to play on any vac secured servers (aka every server ever) though, so it's not very useful right now.

I was not implying that Valve is responsible for it, I am saying that they are the only ones that can do anything about it since Orange is long gone.

I don't know what goes into getting a plugin signed or what is required by Valve. Maybe they compile the source for you, I don't know.

The only thing we have here is a patched binary which differs by 2 bytes. If they can do something with that, perfect. Otherwise, I guess we are out of luck.

Edit: This won't work anyways since the client interface for calling functions has changed.

All that's required is the hl2sdk, well just bits of it. For the bare minimum, you need just a few specific headers which is enough information to create the plugin object.

As for making a useful plugin, that requires much more work.

Edit: There is a sample plugin project for visual studio inside the sdk if you were wondering. Also, there is information on the Valve Developer Wiki on how to modify and compile it.

My patch is the equivalent of a recompilation with the fix; I didn't need the source code to fix the plugin. So if all Valve needs is the binary, you can take the fame and send it to them:

<link>

I was able to successfully patch and load the plugin binary, but that is only with -insecure in the launch options. Modifying the binary must have affected how the game sees it as a signed or unsigned plugin.

All I did to patch the plugin was hex edit "VFileSystem019" to "VFileSystem020" since the latest update changed the interface version number. It's up to Valve then to fix this one since Orange has pretty much stopped supporting this plugin by taking his site down.

I can whip up something simple... if you'll test it, that is.

I wouldn't set a goal right away, you should just get a feel for what you are doing then decide how fast you want it running.

Remember, with your chip, you have to increase a base clock which affects other components. This means that you need to lower the multipliers of your memory, HT bus, NB, and anything else that uses the base frequency in order to keep them close to default values while you increase the cpu frequency.

It might be a bit tough for you if you haven't overclocked before. The chip you have has a locked cpu multiplier, so if you do overclock it, you will be doing so by incrementing a base frequency which also affects other components in your system.

Do some googling and read up about how the non black edition chips work with respect to overclocking. If you do learn enough to overclock your cpu, I'd say not to go too far above the recommended voltage for your chip, or keep it as a limit if you want to be safe. Wikipedia says the range for your chip is 0.975 - 1.425 V.

edit: low temperatures are good too. < 70 load i guess

Those are pretty old. Did you give the most recent WHQL driver a try? 310.70

http://www.nvidia.com/object/win8-win7-winvista-64bit-310.70-driver.html

edit: those are beta, not whql, whoops. try them anyways i guess

What was the original driver version that you tried?

Yeah, that can be done.

I'd rather stick with the .command syntax to be sure that there will never be any command conflicts between our plugins, but we'll see.