| Account Details | |
|---|---|
| SteamID64 | 76561198075543642 |
| SteamID3 | [U:1:115277914] |
| SteamID32 | STEAM_0:0:57638957 |
| Country | Finland |
| Signed Up | February 20, 2014 |
| Last Posted | July 29, 2022 at 2:11 PM |
| Posts | 19 (0 per day) |
| Game Settings | |
|---|---|
| In-game Sensitivity | |
| Windows Sensitivity | |
| Raw Input | |
DPI |
|
Resolution |
|
Refresh Rate |
|
| Hardware Peripherals | |
|---|---|
| Mouse | |
| Keyboard | |
| Mousepad | |
| Headphones | |
| Monitor | |
i got this stuff going on https://www.teamfortress.tv/59603/airshot-ticks-from-stv
if you get too much demos to go through i can add stuff like user interfaces/filters to quickly go over submitted stuff
i can add more data to medic airshots etc. like how high in the air target was to quickly go over submitted stuff
sorry for my english
JMaxchillLooking at https://etf2l.org/matches/83439/, which has SteamID screenshot properly submitted and parsed, the console shows it GETs the API requests for Zoey and deli69 properly, but for the other 10 players it returns either `status: {code: 500, message: "Internal Server Error"}` or `status: {message: "Internal Server Error", code: 500}`.
This is with version 0.1 on up-to-date Chrome. It's also giving the issue "Audit usage of navigator.userAgent, navigator.appVersion, and navigator.platform" for common.js:1, and telling me my browser is managed by my organisation, but I suspect those aren't the problems.
Out of curiosity did this userscript work before for you? I coded it to use only "force cache", so all new network requests are fetched from local cache. So it might be that errors from api got cached. Best way to clean cache just from one site is to have dev tools open on etf2l match page and click reload button with mouse2 and select: "Empty Cache and Hard Reload"
It seems like this userscripts shortcoming is to issue too many network request at same time and also cache them, even if they are errors. I'm looking into fixing it.
If you want you can pm me for new test version on tf.tv or add me on steam to reduce bumping this topic. Or wait new version on github
JMaxchillThe ETF2L match page script seems to be broken for me, tampermonkey is showing it as installed and running but it's not displaying its interface
What browser are you using? Are there errors or something relevant on browsers developer tools when you are on ETF2l match page. Please link match page where this userscript is not working for reference.
I retested it now with Chrome, Opera, Firefox and Edge and it seemed to work. Its bit on rough state so when match page does not contain status screenshot (aka ETF2l doesn't have player information) interface is missing. This usually happens on new match pages.
carterholy fuck? this is actually insane. if this is yours great fucking work
My work is gui/webapp and small wrapper around Icewinds https://github.com/demostf/demo.js tf2 demo parser.
Basically that repo has cleaner uhtml/uce partial rewite/port of my React app: https://i.imgur.com/b3BRSZB.png
and that React app was rewite of my Discord bot that rendered preview clips from airshots. Picture from that bot: https://i.imgur.com/8LkAFd2.png Just some boring data visualisation, but on interesting subject.
Guide:
Download 6v6 .stv from Demos.tf.
Drag and drop it here: https://mazatf2.github.io/DemoUI2.5
Wait. Scroll down to last table.
https://i.imgur.com/Wz6Dnna.png
Open demo and go to 4733 tick.
https://i.imgur.com/qGUhRnq.png
See Permzilla blasting while ubered from testing demo.
Full screenshot: https://i.imgur.com/0MAgvOw.png
Features:
Events:
- Player died from airshot while blasting
- Attacker got airshot kill while blasting
- ÜberCharge activated while blasting
- Airshot healing arrow
- Blast jump while ubered
- Blast jump while kritzed
Visual timeline for rounds (ticks for starts, ends and pauses, first kills and mid captures)
Relevant sourcecode.
https://github.com/mazatf2/DemoUI2.5/blob/aefe70ae2f5ecad84e2037db1e1d8fca69798627/gui-src/overlay-manager/src/page/events.js
https://github.com/mazatf2/DemoUI2.5/blob/aefe70ae2f5ecad84e2037db1e1d8fca69798627/gui-src/overlay-manager/src/demotool/demotool.worker.ts
Rest code on same repo. Licence MIT
If demo contains pauses player doesn't handle them. For example this https://demos.tf/384366 stops at 62 325 tick (whole demo contains 136 815 ticks). Player doesn't show rest of the match after pause.
Overview of demo. Pause in 3rd round.https://i.imgur.com/IRjxeK2.jpg
It seems 'setPause' packet contains pause data. It fires when pause starts and ends. So it can be used to get right tick after pause ends.
Messy reference code how it can be used for tick offsets after pause ends: https://github.com/mazatf2/DemoUI2.5/blob/4a3bc844eb8d9782f09c8cadc2a3e2bea095e066/gui-src/overlay-manager/src/demotool/demotool.worker.ts#L294
I haven't tested if DT_SceneEntitys props: 'm_bPaused', 'm_flForceClientTime', 'm_bIsPlayingBack' work for older demos (<2018). For 2018-2020 demos that I tested with demo.js and it seems they aren't preset.
Purpose: Search logs or demos uploaded to logs.tf or demos.tf.
For TF2 historians and frag movie makers.
3 separate scripts:
https://i.imgur.com/1rWavL4.png
Github: https://github.com/mazatf2/tf2-comp-userscripts
More gifs: https://github.com/mazatf2/tf2-comp-userscripts/tree/master/docs
dipp_This might be a long shot, but do you think you can include demos in the logs? ...
I created userscript that searches demos uploaded to demos.tf
Screenshots: https://imgur.com/a/FK1dS3R
https://www.teamfortress.tv/56783/search-and-link-demos-and-logs-userscripts
It works best on logs / demos that are 10 min - 2 years old. There is some expected delay on logs.tf/demos.tf apis. At the moment demos.tf api seems little buggy for old demos.
tl:dr Antialiasing is controlled by mat_antialias and mat_aaquality.
Q: Why mat_antialias is set to 0 by default?
A:
pazerBecause the values of these cvars are loaded as part of the material system config that is stored in the registry. They arent loaded and stored like normal cvars.
Q:
stephwhats the harm in setting it to 0 anyway?
A:
pazerDon't set these to 0. The minimum value of these cvars is 1, and setting them to 0 will just cause a material system reload = breaking mumble overlay/increasing game startup time. Think about it: mat_antialias controls the number of samples taken per pixel on your screen. If you took 0 samples per pixel, your screen would be entirely black :Pmat_antialias 0 mat_forceaniso 0
Reading directly from the game's code, the same hardcoded minimum exists for mat_forceaniso:
pConfig->m_nForceAnisotropicLevel = max( mat_forceaniso.GetInt(), 1 );
Antialiasing off
mat_aaquality 0
mat_antialias 1
MSAA x2
mat_aaquality 0
mat_antialias 2
CSAA x8
mat_aaquality 2
mat_antialias 4
Run "good" benchmark and compare it to others. (if you don't have any, try Passmark PerformanceTest, it has good score database) = To see if little unstable overclock is causing performance loss.
Reinstall OS to spare harddrive and copy stuff over and try to stream with it = To see if old OS causes it.
mitchcliff123PootisPootisPootisPootistheres no vdf or dll filemitchcliff123how do you install this?https://github.com/PazerOP/CastingEssentials/releases
extract to =>
E:\steamapps\common\Team Fortress 2\tf\addons
E:\steamapps\common\Team Fortress 2\tf\addons\CastingEssentials.dll
E:\steamapps\common\Team Fortress 2\tf\addons\CastingEssentials.vdf
mitchcliff123how do you install this?
https://github.com/PazerOP/CastingEssentials/releases
extract to =>
E:\steamapps\common\Team Fortress 2\tf\addons
E:\steamapps\common\Team Fortress 2\tf\addons\CastingEssentials.dll
E:\steamapps\common\Team Fortress 2\tf\addons\CastingEssentials.vdf
https://i.imgur.com/HJuQbuk.png
Overclock cpu for better frames.
On soldier I'm always rocket jumping around. Quick flick required for jumping makes my fps to unstable, because I need to look at ground for rocket jump which makes my fps to rise from normal. Turning around after that to look forwards while on mid air lowers my fps back to normal again. TF2 is prone to have input lag spikes when fps changes too much.
Because of this I'm running dx8 with fps configs to get rid of fps fluctuations.