Failed to load plugin "../tf/addons/PREC"

I have same issue, that was in my console. I've tried replacing and am currently verifying the integrity of the game cache to see if that helps. Any word on this would be nifty.

if somebody fixs it i will love them x4

Here's the etf2l thread to watch: http://etf2l.org/forum/general/topic-6647/

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.

Well, yeah, signing is basically a hash of the file. If you modified the binary so that it had hacks in it, recognizing it as a signed plugin still would be pretty bad. Every change needs a new signing.

You'll have to wait until the author gets the program resigned if you want to run it secure.

EDIT: Also, I doubt valve will fix it, since it's not their code/project. It's on orange, not them. If he released the source code and someone else compiles it, they would probably sign it, but this isn't their responsibility. At best they'll create their own P-Rec into the game. But a standalone plugin? Nope.

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>

Did you remove the signing on the file (I'm assuming you modded a previously signed binary)? I'd expect that they'd want you to cut that off for them so they can apply the new signing. I'm unsure if they actually look at the source for the program and just pray the person has good intentions, and if they'll accept someone else moding someone else's program without permission.

I know the fix just has to do with an updated setting (config plaintext for the TF2 system). However, programming practices probably won't budge for this. Go ahead and try to get them to verify it, they might. I stopped using P-REC way back and just came by to inform you programming practices as to why they aren't exactly the ones responsible and might not signing a fixed P-REC. Though they're generally nice enough so they might.

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.

Well thanks for the temp fix <3 don't think running -insecure is too big of a deal

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.

oh derp :(

nvm didn't work

Here's what he said when I contacted him:

So if Valve needs the source code (most likely, to verify there's no cheating in it like aimbots) PREC is pretty much dead, and we need to wait for an replacement.

pretty douchebaggery of him to not release the source code if he dont intend to support the plugin. If he releaased the source code, im pretty sure other people can pick it up and have the plugin fixed quicckly rather than coding from scratch which takes longer time. For prec its pretty much esssential on etf2l for taking screenshots and record demo to provide it to the admins if they get requested so.
And judging by that conversation suyo, it seems that orange is just making claims that "casual" can make it but doesnt signify if casual intends to make a replacement.

I never realized how much I took PRec for granted until now. :<

So he's going to make the plugin, how long it takes for it to be signed by Valve, if ever, IDK.

I emailed Valve about this (and the broken demos thing), but I don't know if they are able to fix P-REC.

He doesn't really owe the community anything. Yes it's annoying as fuck that someone will have to recode it because he doesn't want to release the source, but it's not his responsibility to work for free for the community.

The thing is the author already done this for free for the community by offering free download and not charging for money. IF he got the codes already what is the point of keeping it on his computer and let it stay there untouched for years. All he can do is just upload the codes and publish it.

There are really no loss for him by releasing the codes since he stopped supporting prec years ago.

He could and it's pretty assholish, but in the end he doesn't have to or need to. People are pretty possessive of their creations (see half the HUD makers and map makers).

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

Edit: Works on Linux.

Orange said he's sending in the files to be signed. http://etf2l.org/forum/customise/topic-6647/page-42/?recent=425792#post-425788

At least we have a backup if he ever leaves. But to be fair, it's been less than a week since the update and since he's not active he probably just trolled and intended to update.

What does that mean exactly?

^ Plugins like P-REC wont work on secure mode without Valve's signing. Original P-REC plugin was signed by Valve and thus worked on all servers. Apparently Orange modified P-REC to work with the newest update, so he needs to send the new files to Valve for signing.

However, I don't have a clue how this signing works

Signing is adding something to the end of the .dll you download that the hl2.exe (TF2 program) checks when it's loaded. It's a hash/checksum created by a special key that valve has so that the TF2 program can reverse check if it matches the one the generated. A checksum/hash is created by getting all the bits from the .dll file and putting it through a special algorithm that will generate a X length bit sequence to the end of the file (256 or 512bit most likely if they use sha2 as the hash). and It's a security feature that basically says Valve officially inspected and approved of the file. It helps prevent plugins that are malicious from working on VAC servers (you could make hacks with plugins that wouldn't be VAC banned if it wasn't for the disabling on secure servers since it's loaded by the game and considered valid).