Tremulous Forum
General => Feedback => Topic started by: Odin on April 10, 2007, 10:25:58 pm
-
Would it be possible to implement a system where the game automatically saves a screenshot when you get a kill? Possibly not taking screenshots for kills for 3 seconds to prevent it from taking a screenshot if you get multikills/etc.
Sometimes the best moments in Trem are the kills, and you never get to get a screenshot of it.
-
What would be important about the screenshot A corpse and obituary message?
-
MD the tyrant up the ass, luci the mara in the face, blast the goon, etc.
Nuder the rant with a psaw >_< etc
-
It would take it the instant you get the kill, so your enemy would only be on the first frame of the death animation.
-
I'd really like that! Make it so you can choose the format it saves in, preferrably a crappy jpg or something.
-
i make to mutch kills to fast wil probly rape my fps and then shove it up my ass and wil end up geting lag killed
-
i make to mutch kills to fast wil probly rape my fps and then shove it up my ass and wil end up geting lag killed
Eh?
-
What about the issue of your screenshot folder becoming obscenely bloated after a couple of matches?
A screenshot bind might be more useful?
-
Record the match and work out your kills afterwards.
-
// print message on the local console
void trap_Print( const char *fmt );
-
What about the issue of your screenshot folder becoming obscenely bloated after a couple of matches?
A screenshot bind might be more useful?
Uh, the screenshots would go in another directory.
-
yeees. Thats why I said the screenshot folder. Think about it. In a long game you may get as many as 100 kills.
Say you play 5 games one day.
Thats 500 screenshots.
In a week you have thousands of screenshots.
Good luck looking through them all for something useful
-
That'd be awesome. I myself have over 300 screenshots in my screenshots folder. How would that be bad?
-
yeees. Thats why I said the screenshot folder. Think about it. In a long game you may get as many as 100 kills.
Say you play 5 games one day.
Thats 500 screenshots.
In a week you have thousands of screenshots.
Good luck looking through them all for something useful
You can easily delete them after each game if you don't like them, you can even delete them ingame if you're in windowed mode, you can alt+tab to the screenshot folder.
That's common sense.
-
yeees. Thats why I said the screenshot folder. Think about it. In a long game you may get as many as 100 kills.
Say you play 5 games one day.
Thats 500 screenshots.
In a week you have thousands of screenshots.
Good luck looking through them all for something useful
You can easily delete them after each game if you don't like them, you can even delete them ingame if you're in windowed mode, you can alt+tab to the screenshot folder.
That's common sense.
Yep, let me just stand in your base for a little Mr. Tyrant while I delete this screen shot of me owning your friends...
-
Right now i'm scrimming with PC$.
-
Well I just dont think its a sensible option. I know some people are running tremulous on lower end systems, and automatically taking thousands of screenshots in a quick way to fill up their hard drives.
Still I suppose as an option it wouldnt be the end of the world. I still think you'd be better off just using a handy screenshot bind though. I mean doing administrative work after every tremulous game? Just plain silly if you ask me
-
The only reasonable place to put a bind for a killscreenshot would be on the mouse (I'm using all of my three buttons allready) or around the WASD keys, that's Q, E, X, F, R, C, tab, shift, 1, 2, 3 (I use all of those), and C. Z isn't very convienient since you have to move a finger off one of the movement keys.
-
If you want to implement this, it'd be as simple as leaving it off by default, requiring "cg_killScreenshot 1" in console to turn it on/off. You could even bind a toggle for it.
I like the idea, some of the most interesting moments would be caught: sawkills are always a rush, and some l33t MD action would be captured pretty well.
-
Why look at pictures when you can watch demo's?
-
Why look at pictures when you can watch demo's?
Because you can't post them on the internet?
That's like asking "why take pictures when you can record video instead?"
-
He's just saying what everyone else is saying.
"Demo it and then you can get any screenshot you want after by taking it while playing the demo."
We do not want to fucking do that. We want to take a screenshot ingame as it happens.
Get
-
That
-
Through
-
Your
-
Thick
-
Heads
-
And
-
Shut
-
The
-
FUCK
-
Up
-
Please.
-
Get
-
That
-
Through
-
Your
-
Thick
-
Heads
-
And
-
Shut
-
The
-
FUCK
-
Up
-
Please.
Some kind of code?
But actually ppl, this is a pretty simple concept that even my rats understand. demos are all fine and good, but pictures are another category.
Geez!
-
i make to mutch kills to fast wil probly rape my fps and then shove it up my ass and wil end up geting lag killed
Eh?
+1, I dont understand if your fighting pictures or trying to shove silicon up your ass.
-
sounds good...
i guess...
yeah...
I guess it'd be good. But not when you are shooting from far away and you don't see the enemy dying
-
If there's some way to disable it, fine. I really don't want a ton of screenshots on my PC requiring me to manually delete them, or, in the offchance I actually want to keep a screenshot for whatever reason, to sort through them all.
-
We were both on S3. I was out in a battlesuit with my luci, and down the hallway I see an advanced goon. The goon sized me up and slowly crawled towards me.. then lunged! However, while he was preparing the pounce I was charging my luci... he pounced smack into it! I did not expect the first shot to hit so I was already charging a second. With no target to shoot at, I simply shot it back at the dead corpse... only to happen to kill an advanced mara and a dretch! It was pretty sweet... wish I caught it :-P
-
We were both on S3. I was out in a battlesuit with my luci, and down the hallway I see an advanced goon. The goon sized me up and slowly crawled towards me.. then lunged! However, while he was preparing the pounce I was charging my luci... he pounced smack into it! I did not expect the first shot to hit so I was already charging a second. With no target to shoot at, I simply shot it back at the dead corpse... only to happen to kill an advanced mara and a dretch! It was pretty sweet... wish I caught it :-P
Yes, considering that only the Mara and Dretch would be seen.
This only demonstrates a flaw that should be fairly obvious, the beauty of the kill isn't in the first death frame. The beauty of the kill, and pretty much only the thing worth capturing, is the actual execution of the kill. Looking at one screen is insufficient to see how the kill was carried out, and what really makes it remarkable. Maybe if this used short demo clips instead of screenshots to film the battle I would find it interesting, but with screenshots I can't find any situation in which I would use it. I want to see the dodging, close calls, tricky maneuvers, etc.
-
// print message on the local console
void trap_Print( const char *fmt );
// print message on the local console
void trap_Print( const char *fmt );
if(trap_Print("Player1 killed player2.")){
trap_Print(\screenshot);
}
Not sure if that will work. ;p
-
Not sure if that will work. ;p
I doubt it, but I'll look into it.
The screenshot function is R_ScreenShotJPEG, but I can't access that from anywhere in cgame where CG_Obituary is handled. I'll look into it a bit more, but it's not going to be easy without learning some new tricks, I suspect.
-
I think that kill screenshots are a pretty cool idea. Maybe you could set something up so that evry week or so, it deletes unlooked at pictures.
-
i dont. sometimes i dont look at my screenshots for a month or so before browsing them. it doesnt mean i dont want them.
-
How about if you can tell the console to take a screenshot every time so-and-so player and you are involved in the same chat event. "PlayerOne lasgunned Sow&Sew." Screenshot. "Sow&Sew pounced PlayerOne." Screenshot. With a toggle for the ones where you lose, so people can turn it off. Then every time you pwn Sow&Sew or he pwns you, you have recorded the event. For posting, er, I mean posterity.