>8:10
>"It's like Christmas morning"
>sniper holding Bushwacka

Wait a minute...
https://youtu.be/6cm2iFmASBc?t=13s

is it just me or did he slow down the framerate after rendering it in order to achieve slow motion

fuck that

TF2Center automatically uploads to logs.tf. It's up to the server to have Sizzling Stats enabled, because sizzlers require the STV demo to be uploaded, which requires FTP access, which requires a sourcemod plugin, not simple rcon like TF2Center uses.

When you sign into Sizzling Stats, you can see a history of all uploaded stats that have you in them. Top right, hover over your name and hit "Profile".

My old team leader went on a hacking spree one night after some UGC 6s scrims. Four of us were left in the server so we were doing some 2v2 KOTH rounds for fun, we all agreed to not go med or engie and one of the guys did and it pissed him off enough that he ragequit.

He was VAC banned the next morning. He talked to a UGC admin and they said that he could simply switch to an alt account and continue playing in the season, so long as he didn't use cheats in matches.

This was at a Gold level, and it frankly sickens me that they're so openly okay with it.

No 120 FOV fix? No transparent viewmodel fix?

Alright, we're still good.

I thought I was on to something when it came to getting it to work on DX8. I thought by simply generating a Du/dv map and adding a $dudvmap section to the material, I could enable it in DX8 mode.

Turns out the real reason it won't work in DX8 is because DX8 doesn't support motion blur. So, basically, the refract shader DOES work in DX8 (though possibly not as well), but because there's no motion blur, we can't apply the refract shader to the viewmodel.

It's never gunna be possible to get it running in DX8 mode with this method. Sorry guys.

i deleted this comment because it was so bad that it ruined the thread

Getting this too, thought it was just me. Sucks that there's no fix, it's pretty make or break.

EDIT: I've figured it out. It's not entirely the refract shader. Your image can be edited to decrease the effect.

The way you're gaining transparency is by throwing a refract shader over the entire viewport, although it ignores the HUD and alters the viewmodel. The refract shader is actually warping the entire image as a side effect. You've disabled the blur associated with the refract shader by setting $refractamount to 0, however the refract shader still warps the image a linear, pixel-driven amount. Because of this, the blur we're seeing is actually from the low resolution of the overlay. By increasing the resolution, we can't actually remove the blur, but we can exponentially make it less visible.

I resized the 256x256 image to 2048x2048. The blur effect is still there, but it's hardly visible.

Having some issues getting the 256px to even load right now, but I'll show screenshots in a second.

EDIT2: I have no idea what I did to break my game like this. The aliasing was REALLY bad when it was 256px. I increased it to 2048x2048 and used "mat_reloadmaterial REFRACTnormal_transparent" without even leaving the server, after turning sv_cheats on, and then the blur became really subtle, but still there.

I've since deleted the 2048px image and wiped both the vmt and vtf with the original ones from the archive, restarted tf2 a bunch of times, and no matter what I do I can't get the blur to be any worse than it was at 2048px.

I've configured it mostly the way they have, while eyeballing a couple of settings that felt off - for example, pure white was tinted green in my experience.

It feels alright on average, but the black levels are absolute shit. Black eQualizer is disabled in the OSD when using the Standard profile, like they used. The only modes that enable it are the gamer modes, but those have other options disabled that also make it look equally shitty. For example, the Movie preset enables eQualizer, but also disables things like blur reduction, enforces oversaturation, and a couple of other issues.

Movie forces oversaturation, Photo fucks up contrast and gamma, sRGB removes that contrast issue from Photo but makes the gamma ten times worse, Eco disables almost all controls and turns the brightness down, on top of having bad contrast, FPS1 is like the worst of Photo and sRGB, FPS2 is even worse oh my god my screen is almost entirely white, RTS is basically FPS2, and Gamer1, Gamer2, and Gamer3 are pretty much the same as FPS2 and RTS.

I don't know who the fuck designed these profiles.

I think in the second video he mentioned Ohio

there's a second one

https://www.youtube.com/watch?v=kIH2oEwxX2A

I've turned up the brightness beyond what they've suggested, and turned the contrast to what feels good. The colors from the profile are better than the out of the box colors, but they're still horrible, honestly. They piss me off all the time. I just don't have access to a colorimeter.

I've tweaked the OSD beyond what it told me, and while I'm okay with some colors, darkness has a tint to it and I can never get low blacks. That's actually a "feature" that I can't disable, meant to improve visiblity in games with low light. Why the fuck can't I disable it?

I use the 2420Z @ 144, I just use the color profile from here

I think the color is ass from this profile (for my own panel) but I haven't really been bothered to make it better. It's far better than the best I could get out of the box. Fuck I hate the contrast and low light settings it forces on you. But man, dat 144Hz.

It was alright. Not my cup of tea, and I felt it kind of droned on for a little long. It feels like lots of songs mashed together. Still alright though.

https://www.youtube.com/watch?v=0NNFOcPGXX4