April 18, 2013 - TF2 Team
An update to Team Fortress 2 has been released. The update will be applied automatically when you restart Team Fortress 2. The major changes include:
Added a new ConVar cl_first_person_uses_world_model to allow this mode to be used outside of VR mode
Disabled plug-ins that would allow users to connect to secure game servers even when -insecure is specified on the command line
Continued use of such plug-ins will risk your Steam account getting VAC banned
Added support for unloading the displayed URL when the user closes the info panel
Added ConVar sv_motd_unload_on_dismissal to allow server ops to control the default behavior of their MOTD
Fixed a client crash related to doing a changelevel while firing the Minigun
Fixed a bug where you could come out of a teleporter facing the wrong way in VR mode
Fixed a bug with custom fonts not loading for third party HUDs on Linux.
Improved performance and stability for the Linux version
Also, Steampipe for TF2 is pushed back to the 30th.
April 18, 2013 - TF2 Team
An update to Team Fortress 2 has been released. The update will be applied automatically when you restart Team Fortress 2. The major changes include:
Added a new ConVar cl_first_person_uses_world_model to allow this mode to be used outside of VR mode
[b]Disabled plug-ins that would allow users to connect to secure game servers even when -insecure is specified on the command line
Continued use of such plug-ins will risk your Steam account getting VAC banned[/b]
Added support for unloading the displayed URL when the user closes the info panel
Added ConVar sv_motd_unload_on_dismissal to allow server ops to control the default behavior of their MOTD
Fixed a client crash related to doing a changelevel while firing the Minigun
Fixed a bug where you could come out of a teleporter facing the wrong way in VR mode
Fixed a bug with custom fonts not loading for third party HUDs on Linux.
Improved performance and stability for the Linux version
Also, Steampipe for TF2 is pushed back to the 30th.
90% of etf2l gonna be m a d
90% of etf2l gonna be m a d
P-REC is unaffected, right? I'm pretty sure it's certified.
P-REC is unaffected, right? I'm pretty sure it's certified.
brah secure game servers
does this mean just the ones that are vac protected? like that little shield in the browser?
[quote=brah]
[b] secure game servers[/b][/quote]
does this mean just the ones that are vac protected? like that little shield in the browser?
Added ConVar sv_motd_unload_on_dismissal to allow server ops to control the default behavior of their MOTD
i don't like the sound of this at all
hookyP-REC is unaffected, right? I'm pretty sure it's certified.
no it is not affected, p-rec is a signed plugin and does not need -insecure.
[quote]Added ConVar sv_motd_unload_on_dismissal to allow server ops to control the default behavior of their MOTD[/quote]
i don't like the sound of this at all
[quote=hooky]P-REC is unaffected, right? I'm pretty sure it's certified.[/quote]
no it is not affected, p-rec is a signed plugin and does not need -insecure.
kacebrah secure game servers
does this mean just the ones that are vac protected? like that little shield in the browser?
Yes
PREC is unaffected.
"sv_motd_unload_on_dismissal" = "0"
game
- If enabled, the MOTD contents will be unloaded when the player closes the MOTD.
[quote=kace][quote=brah]
[b] secure game servers[/b][/quote]
does this mean just the ones that are vac protected? like that little shield in the browser?[/quote]
Yes
PREC is unaffected.
"sv_motd_unload_on_dismissal" = "0"
game
- If enabled, the MOTD contents will be unloaded when the player closes the MOTD.
OpenPlugin_down
And p-rec shouldn't be affected since it doesn't require you to use -insecure.
OpenPlugin_down
And p-rec shouldn't be affected since it doesn't require you to use -insecure.
Does this make moose's statement more valid?
STAY TUNED!
Does this make moose's statement more valid?
STAY TUNED!
FogDoes this make moose's statement more valid?
STAY TUNED!
copying what i wrote in the other thread:
how is it a warning shot? who else was vac banned for using this plugin?
moose was NOT vac banned for openplugin. either he modified it or ran it wrong somehow, or there is something he is not telling us.
nobody else has been banned for openplugin so it wasn't that.
[quote=Fog]Does this make moose's statement more valid?
STAY TUNED![/quote]
copying what i wrote in the other thread:
[quote]how is it a warning shot? who else was vac banned for using this plugin?
moose was NOT vac banned for openplugin. either he modified it or ran it wrong somehow, or there is something he is not telling us.[/quote]
nobody else has been banned for openplugin so it wasn't that.
FogDoes this make moose's statement more valid?
STAY TUNED!
Why would they ban someone and then patch it straight away afterwards without touching anyone else
[quote=Fog]Does this make moose's statement more valid?
STAY TUNED![/quote]
Why would they ban someone and then patch it straight away afterwards without touching anyone else
DroidsterWhy would they ban someone and then patch it straight away afterwards without touching anyone else
I've heard of that happening before, especially in motorsports.
[quote=Droidster]
Why would they ban someone and then patch it straight away afterwards without touching anyone else[/quote]
I've heard of that happening before, especially in motorsports.
Yep i got banned for this shit.
Yep i got banned for this shit.
Can we bring the moose autism to a full-stop already, he wasn't banned for open plug-in. The likelihood of him being the only person to be banned for it and then it getting patched out a week later is actually 0.
Can we bring the moose autism to a full-stop already, he wasn't banned for open plug-in. The likelihood of him being the only person to be banned for it and then it getting patched out a week later is actually 0.
People can still use Eyefinity and other stuff to increase FOV I guess
People can still use Eyefinity and other stuff to increase FOV I guess
Well, to change the subject. cl_first_person_uses_world_model is quite fun to play with.
Well, to change the subject. cl_first_person_uses_world_model is quite fun to play with.
cl_first_person_uses_world_model
Does this do what I think it does.
(getting accurate flame representation on your screen)
cl_first_person_uses_world_model
Does this do what I think it does.
(getting accurate flame representation on your screen)
bunnyYep i got banned for this shit.
no
[quote=bunny]Yep i got banned for this shit.[/quote]
[b]no[/b]
LKincheloeWell, to change the subject. cl_first_person_uses_world_model is quite fun to play with.
heh
https://dl.dropboxusercontent.com/u/84556731/2013-04-18_00005.jpg
[quote=LKincheloe]Well, to change the subject. cl_first_person_uses_world_model is quite fun to play with.[/quote]
heh
[img]https://dl.dropboxusercontent.com/u/84556731/2013-04-18_00005.jpg[/img]
rip 120 fov, ah well.
Is there a way I can still get transparent viewmodels without OpenPlugin ?
rip 120 fov, ah well.
Is there a way I can still get transparent viewmodels without OpenPlugin ?
So, because I'm a technical noob, what about other plugins that require -insecure? Specifically Blue's spectator outline plugin, which I'm guessing should still be ok since you only connect to STVs with it. I have to cast and don't particularly want to risk anything without knowing for sure...
So, because I'm a technical noob, what about other plugins that require -insecure? Specifically Blue's spectator outline plugin, which I'm guessing should still be ok since you only connect to STVs with it. I have to cast and don't particularly want to risk anything without knowing for sure...
Wouldn't be surprised if Moose's claims lead more than a few people to inquire with valve about OpenPlugin's VAC status, effectively forcing them to make a decision.
Wouldn't be surprised if Moose's claims lead more than a few people to inquire with valve about OpenPlugin's VAC status, effectively forcing them to make a decision.
sourcetvs are not VAC secure and you can connect to them with whatever plugins you want running. blue's spec plug-in does not include the little feature of letting you connect to VAC secure servers so it is safe
sourcetvs are not VAC secure and you can connect to them with whatever plugins you want running. blue's spec plug-in does not include the little feature of letting you connect to VAC secure servers so it is safe
HueyLewisSo, because I'm a technical noob, what about other plugins that require -insecure? Specifically Blue's spectator outline plugin, which I'm guessing should still be ok since you only connect to STVs with it. I have to cast and don't particularly want to risk anything without knowing for sure...
stv servers are not vac secure so this does not affect bluee's plugin afaik.
[quote=HueyLewis]So, because I'm a technical noob, what about other plugins that require -insecure? Specifically Blue's spectator outline plugin, which I'm guessing should still be ok since you only connect to STVs with it. I have to cast and don't particularly want to risk anything without knowing for sure...[/quote]
stv servers are not vac secure so this does not affect bluee's plugin afaik.
stvs aren't vac secured afaik , should be fine
edit: ninjad, fuck
stvs aren't vac secured afaik , should be fine
edit: ninjad, fuck
hookyP-REC is unaffected, right? I'm pretty sure it's certified.
it is certified, valve has to send a .dll file compatible with the current version of tf2 for p-rec to work
[quote=hooky]P-REC is unaffected, right? I'm pretty sure it's certified.[/quote]
it is certified, valve has to send a .dll file compatible with the current version of tf2 for p-rec to work