Is it possible to have a 10 second camera or something so we can capture those special moments (or destructive moments)? It would be cool when you're bored. You'd be like ,'Oh yer i remember that stupid Revenent (no offence).'

You may also be able to share it. That would be cool.

Oh what, like it screen-grabs a bunch of times for the 10 seconds?...

That'd be kinda neat.

Or you could write up a dump bind.

Like

/alias 10secdump "dump, wait 1, dump, wait 1, dump, wait 1, dump, wait 1, dump, wait 1, dump, wait 1, dump, wait 1, dump, wait 1, dump, wait 1, dump"
/bind f11 10secdump

I haven't written binds in a while. Are non-integer values for dumps valid yet? If so, you could increase the speed of the dump.

CP: /wait now has .01s resolution, so you could get 100 images per second. in theory.

Of course, if you have multiple waits in a single alias, they're all evaluated at the same time. So what you wrote wouldn't work. You'd have to have 100 different aliases, each written like this:

/alias dumpN "dump; wait .01 dumpN+1"

oooh... I thought waits were whole seconds only... thanks Miharu.

But, you could do:

/alias 10secdump "dump; wait 1 dump; wait 2 dump; wait 3 dump; wait 4 dump... etc. etc."

and: DumpN+1? Pseudo-code, or can we now do assignments? Though... no possible way that'd work that way, so pseudo-code.

EDIT: And use Quicktime (or whatever) to string the dumps together and you have a 10 (up to 100 theoretically) FPS movie. Neat. Just do it like this: /alias dumper "dump; wait .1 dumper" and then I guess you have to logout to stop your movie. But it'd record til then... use .04 for TV FPS (I believe TV recording is done at 25 FPS anyways). Assuming the client can do that many dumps that quickly.

np. I thought I mentioned it when I was trying to help make a toggle out of the spam bind you had going for [GRU], though.

Edit: yes, pseudocode.

actually, you could probably grab my auto-jettison bind off of the bind list, increase the speed of the recursion, and change jettison to dump, now that I think about it.

alias autoddump "dump; wait .05; autodumploop"
alias autodump_off "alias autodumploop none; autodumploop; bind F11 autodump_on"
alias autodump_on "alias autodumploop 'autodump'; autodumploop; bind F11 autodump_off"
alias autodumploop "dump; wait .05; autodumploop"
bind F11 autodump_on

I set the camera to 20 frames per second, but you can just change the value in the the autodump alias to anything. The bind is designed to rewrite the looping part of the code when you activate the bind anyway, so you only need to change that one value. Also, the bind has the ability to be stopped by pressing the activating button (in this case, F11) after it has been stopped, so that should be useful when you don't want to destroy your hard disk space.

As for standard FPSs, film is run at 24 frames per second (not enough of a difference between 24 and 25 fps for vendetta to recognize), PAL (standard tv for most or all of Europe) is 25 frames per second (wait .04), NTSC (USA, Japan, etc...) is 29.97 frames per second (wait .03).

FRAPS for windows, Snapz Pro for OSX, no idea for Linux. Video recording software. Not a permanent fix but a way around.

cp, that's impractical. dumping a screen takes almost 1 second on mac. so it's really not an option. (i was wondering why this took so long...?)

dont know if the devs can comment on this but...

it's my understanding that the vo server basically sends out ship movement information to whoever is in sector and that each client is responsible for rendering this, including dammage etc.

if the 20 second camera (or whatever buffer length we opt for this) record this information, we could in theory have a playback of that information (say, in a pda section so not to confuse playback and actual game play).

the playback though might require a bit of work depending on how the rendering is done.

devs?