mastercomsCould someone show me what prec_show_stv_status / prec_stv_status displays?
https://i.imgur.com/BeP7GlI.png
with score screenshot
also looking at your previous comment - i think you might've misunderstood what i meant by status, prec_screens 1 takes status of the server not stv, which is required by etf2l (see here https://etf2l.org/wp-content/uploads/screenshots/2023/08/64e0ff000dbd4.jpg)
[quote=mastercoms]Could someone show me what prec_show_stv_status / prec_stv_status displays?[/quote]
[img]https://i.imgur.com/BeP7GlI.png[/img]
with score screenshot
also looking at your previous comment - i think you might've misunderstood what i meant by status, prec_screens 1 takes status of the server not stv, which is required by etf2l (see here https://etf2l.org/wp-content/uploads/screenshots/2023/08/64e0ff000dbd4.jpg)
Ah alright, how does it integrate the status into the screenshot? Similar to the SourceTV status listed above?
Ah alright, how does it integrate the status into the screenshot? Similar to the SourceTV status listed above?
mastercomsAh alright, how does it integrate the status into the screenshot? Similar to the SourceTV status listed above?
it opens console and does basically clear;status;screenshot after your first death
here in action https://www.twitch.tv/videos/1906564345?t=0h24m43s
[quote=mastercoms]Ah alright, how does it integrate the status into the screenshot? Similar to the SourceTV status listed above?[/quote]
it opens console and does basically clear;status;screenshot after your first death
here in action https://www.twitch.tv/videos/1906564345?t=0h24m43s
One issue with P-REC is that if you crash/timeout and rejoin the server in an ongoing match the plugin won't automatically start recording again, you need to do a manual recording. Not sure if that's also the case with the built-in demo tool.
One issue with P-REC is that if you crash/timeout and rejoin the server in an ongoing match the plugin won't automatically start recording again, you need to do a manual recording. Not sure if that's also the case with the built-in demo tool.
disgusting necro
One thing that I always liked about p-rec is the ability the customize your bookmark.
any text you add after your bookmark bind will be shown in the killstreaks.txt file, so if I use this bind: bind "alt" "prec_mark Soldier" in my soldier.cfg, in the killstreaks.txt file it will be shown as
https://i.imgur.com/S2sC6SZ.png
So it's easy to go through your demos if you look for specific classes for example.
disgusting necro
One thing that I always liked about p-rec is the ability the customize your bookmark.
any text you add after your bookmark bind will be shown in the killstreaks.txt file, so if I use this bind: bind "alt" "prec_mark Soldier" in my soldier.cfg, in the killstreaks.txt file it will be shown as
[img]https://i.imgur.com/S2sC6SZ.png[/img]
So it's easy to go through your demos if you look for specific classes for example.
geduprec_screens 1
This, the automated status and end of game scoreboard screenshots for ETF2L match reporting has saved my team's ass countless times.
And as Phnx pointed out the prec_mark (as well as ds_mark actually) supports custom text.
However adding prec_tag "Medic" to class configs allows you to have that added to your demo filenames too for filtering & sorting, which DS does not support.
[quote=gedu]prec_screens 1[/quote]
This, the automated [b]status[/b] and end of game scoreboard screenshots for ETF2L match reporting has saved my team's ass countless times.
And as Phnx pointed out the prec_mark (as well as ds_mark actually) supports custom text.
However adding [i]prec_tag "Medic"[/i] to class configs allows you to have that added to your demo filenames too for filtering & sorting, which DS does not support.
somehow this time thru a friend the author listened to my screams and he published P-REC source: https://github.com/olegKoshmeliuk/Pov-Record
that means we can get it to work ourselves with 64-bit tf2 and make it work with ready up mvm mode so it could work on pickups too or have other problems resolved
edit: Orange also added an MIT license meaning we can already do the work and he offered support if someone takes the challenge of making things work/bugfixing/rewriting as long as his name is kept as the original author
somehow this time thru a friend the author listened to my screams and he published P-REC source: https://github.com/olegKoshmeliuk/Pov-Record
that means we can get it to work ourselves with 64-bit tf2 and make it work with ready up mvm mode so it could work on pickups too or have other problems resolved
edit: Orange also added an MIT license meaning we can already do the work and he offered support if someone takes the challenge of making things work/bugfixing/rewriting as long as his name is kept as the original author
[quote=supra]https://github.com/olegKoshmeliuk/Pov-Record[/quote]
Beautiful, thank you.
P-REC won't work after the switch to 64 bits, the Valve developer who originally signed it doesn't work there anymore, and the current developers are not keen on signing it again (something something security something anti-cheat).
I've summarized the (important) issues from this thread: https://github.com/ValveSoftware/Source-1-Games/issues/5457
If you feel that something crucial is missing, please let it be known.
Somewhere in the thread, I've seen someone mention that they didn't want killstreaks to be recorded, you can put `ds_min_streak 999` in your config.
E: For what it's worth, there's a willingness from the developers to assist the migration off P-REC, so it's not like I'm screaming into the void
P-REC won't work after the switch to 64 bits, the Valve developer who originally signed it doesn't work there anymore, and the current developers are not keen on signing it again (something something security something anti-cheat).
I've summarized the (important) issues from this thread: https://github.com/ValveSoftware/Source-1-Games/issues/5457
If you feel that something crucial is missing, please let it be known.
Somewhere in the thread, I've seen someone mention that they didn't want killstreaks to be recorded, you can put `ds_min_streak 999` in your config.
E: For what it's worth, there's a willingness from the developers to assist the migration off P-REC, so it's not like I'm screaming into the void
twiikuuSomewhere in the thread, I've seen someone mention that they didn't want killstreaks to be recorded, you can put `ds_min_streak 999` in your config.
I don't think the problem is the recording of killstreaks, but recording them in pregame or casual.
[quote=twiikuu]
Somewhere in the thread, I've seen someone mention that they didn't want killstreaks to be recorded, you can put `ds_min_streak 999` in your config.
[/quote]
I don't think the problem is the recording of killstreaks, but recording them in pregame or casual.
twiikuuP-REC won't work after the switch to 64 bits, the Valve developer who originally signed it doesn't work there anymore, and the current developers are not keen on signing it again (something something security something anti-cheat).
I've summarized the (important) issues from this thread: https://github.com/ValveSoftware/Source-1-Games/issues/5457
If you feel that something crucial is missing, please let it be known.
Somewhere in the thread, I've seen someone mention that they didn't want killstreaks to be recorded, you can put `ds_min_streak 999` in your config.
E: For what it's worth, there's a willingness from the developers to assist the migration off P-REC, so it's not like I'm screaming into the void
I've submitted a fix nearly a year ago for casual games being recorded, and have also implemented some of the features suggested in this thread over time, but have not prepared full feature parity with P-REC yet before I send it to Valve. The complete list of features I've decided on have been: better filenames, not recording pre or post game, SourceTV status, and better killstreak logging.
[quote=twiikuu]P-REC won't work after the switch to 64 bits, the Valve developer who originally signed it doesn't work there anymore, and the current developers are not keen on signing it again (something something security something anti-cheat).
I've summarized the (important) issues from this thread: https://github.com/ValveSoftware/Source-1-Games/issues/5457
If you feel that something crucial is missing, please let it be known.
Somewhere in the thread, I've seen someone mention that they didn't want killstreaks to be recorded, you can put `ds_min_streak 999` in your config.
E: For what it's worth, there's a willingness from the developers to assist the migration off P-REC, so it's not like I'm screaming into the void[/quote]
I've submitted a fix nearly a year ago for casual games being recorded, and have also implemented some of the features suggested in this thread over time, but have not prepared full feature parity with P-REC yet before I send it to Valve. The complete list of features I've decided on have been: better filenames, not recording pre or post game, SourceTV status, and better killstreak logging.
mastercomstwiikuuP-REC won't work after the switch to 64 bits, the Valve developer who originally signed it doesn't work there anymore, and the current developers are not keen on signing it again (something something security something anti-cheat).
I've summarized the (important) issues from this thread: https://github.com/ValveSoftware/Source-1-Games/issues/5457
If you feel that something crucial is missing, please let it be known.
Somewhere in the thread, I've seen someone mention that they didn't want killstreaks to be recorded, you can put `ds_min_streak 999` in your config.
E: For what it's worth, there's a willingness from the developers to assist the migration off P-REC, so it's not like I'm screaming into the void
I've submitted a fix nearly a year ago for casual games being recorded, and have also implemented some of the features suggested in this thread over time, but have not prepared full feature parity with P-REC yet before I send it to Valve. The complete list of features I've decided on have been: better filenames, not recording pre or post game, SourceTV status, and better killstreak logging.
any news about this?
[quote=mastercoms][quote=twiikuu]P-REC won't work after the switch to 64 bits, the Valve developer who originally signed it doesn't work there anymore, and the current developers are not keen on signing it again (something something security something anti-cheat).
I've summarized the (important) issues from this thread: https://github.com/ValveSoftware/Source-1-Games/issues/5457
If you feel that something crucial is missing, please let it be known.
Somewhere in the thread, I've seen someone mention that they didn't want killstreaks to be recorded, you can put `ds_min_streak 999` in your config.
E: For what it's worth, there's a willingness from the developers to assist the migration off P-REC, so it's not like I'm screaming into the void[/quote]
I've submitted a fix nearly a year ago for casual games being recorded, and have also implemented some of the features suggested in this thread over time, but have not prepared full feature parity with P-REC yet before I send it to Valve. The complete list of features I've decided on have been: better filenames, not recording pre or post game, SourceTV status, and better killstreak logging.[/quote]
any news about this?
The 64 bit update had to be released early seemingly, so I don't doubt this will come later
The 64 bit update had to be released early seemingly, so I don't doubt this will come later
mastercomsThe 64 bit update had to be released early seemingly, so I don't doubt this will come later
now that the big summer update is here, could you try reaching out to your contacts again?
[quote=mastercoms]The 64 bit update had to be released early seemingly, so I don't doubt this will come later[/quote]
now that the big summer update is here, could you try reaching out to your contacts again?
i found a new issue with ds_screens 1, half the time, the screenshot at the end of the game is without scoreboard, just normal pov screenshot
i found a new issue with ds_screens 1, half the time, the screenshot at the end of the game is without scoreboard, just normal pov screenshot
Another small bug - I can't get TF2 to generate "_events.txt" for killstreak logging when the demo output folder is /tf/. The individual json files for each demo are still created, but not the txt file. It's a bit annoying because I like to use the console autocomplete to find demos. (Making the autocomplete work within subfolders would also be a nice fix but I have no idea how hard that would be.)
For clarity, the commands I'm using:
ds_dir ""
demos are saved to /tf/, txt file is not present
ds_dir "demos"
txt file is correctly generated inside /demos along with the demo files. Also works with any other custom folder name.
Another small bug - I can't get TF2 to generate "_events.txt" for killstreak logging when the demo output folder is /tf/. The individual json files for each demo are still created, but not the txt file. It's a bit annoying because I like to use the console autocomplete to find demos. (Making the autocomplete work within subfolders would also be a nice fix but I have no idea how hard that would be.)
For clarity, the commands I'm using:
ds_dir ""
demos are saved to /tf/, txt file is not present
ds_dir "demos"
txt file is correctly generated inside /demos along with the demo files. Also works with any other custom folder name.
kindredI like to use the console autocomplete to find demos.
Add "-insert_search_path tf/demos" to your launch options (without the quotes). Or you could record to "ds_dir custom/demos".
You can then play demos as if they were directly in tf/.
[quote=kindred]I like to use the console autocomplete to find demos.[/quote]
Add "-insert_search_path tf/demos" to your launch options (without the quotes). Or you could record to "ds_dir custom/demos".
You can then play demos as if they were directly in tf/.