Yeah, I know... A thread about something other than complaining about this or that element being overpowered, or accusing someone of cheating, or speculating on what new bugs we can expect in 1.21 is totally out of place here. What the heck, tho... a change of pace might be nice.
:p
Let's attempt to ignore that BR is currently non-functional ATM and talk about the feature itself a bit.
I'm wondering how many people actually use the Battle Recorder system? I've had some great fun messing with files I've pulled down from the R2 server. Lots of potential there that doesn't seem to be capitalized on at all.
It would be very cool to see Dice return to the concept of BF2TV by going back to BR and filling out it's feature list. Failing in that, maybe some talented folks out there might be able to put something 3rd party together.
Some stuff I'd like to see:
- Index points
There's a solid reason that you can't rewind the BR playback. When you are watching a BR file it's actually using the game engine and all client/server communcation to recreate the battle. You simply can't reverse that data flow and expect to get accurate results without some massive number crunching. HOWEVER, you could make an index point that would save all current object properties referanced to the playback flow. This would give you a point to jump back too. For example, if there was a spectacular event that you want to get multiple camera angles on, you could make an index point just before it happens, recored your camera, jump back to that point, and do it again.
- Stock Camera Angles
It would be hella handy to be able to use all the camera modes that are avilible to you in-game. Including follow, fly-by, and first person.
- Jump to player via list
This would just be conveniant. You could use the Tab menu to bring up a full list of players and click 'em to jump to 'em.
- Render points:
Much like indexing, but these points would be strictly for referancing what should be rendered. You'd have a start point and a stop. Render out what's in between. This would cut down on render times and HUGE file sizes if you want to get uncompressed output. Should funtion for sound output as well as video.
Anyone else have thoughts?
I'm not sure what the feasability of writing a wrapper for BR playback with extended features would be. BattleLauncher makes a good tool for managing playback and takes lots of the comand line stuff out, but it's very limited and hasn't seem to have gotten any TLC for awhile now.
:p
Let's attempt to ignore that BR is currently non-functional ATM and talk about the feature itself a bit.
I'm wondering how many people actually use the Battle Recorder system? I've had some great fun messing with files I've pulled down from the R2 server. Lots of potential there that doesn't seem to be capitalized on at all.
It would be very cool to see Dice return to the concept of BF2TV by going back to BR and filling out it's feature list. Failing in that, maybe some talented folks out there might be able to put something 3rd party together.
Some stuff I'd like to see:
- Index points
There's a solid reason that you can't rewind the BR playback. When you are watching a BR file it's actually using the game engine and all client/server communcation to recreate the battle. You simply can't reverse that data flow and expect to get accurate results without some massive number crunching. HOWEVER, you could make an index point that would save all current object properties referanced to the playback flow. This would give you a point to jump back too. For example, if there was a spectacular event that you want to get multiple camera angles on, you could make an index point just before it happens, recored your camera, jump back to that point, and do it again.
- Stock Camera Angles
It would be hella handy to be able to use all the camera modes that are avilible to you in-game. Including follow, fly-by, and first person.
- Jump to player via list
This would just be conveniant. You could use the Tab menu to bring up a full list of players and click 'em to jump to 'em.
- Render points:
Much like indexing, but these points would be strictly for referancing what should be rendered. You'd have a start point and a stop. Render out what's in between. This would cut down on render times and HUGE file sizes if you want to get uncompressed output. Should funtion for sound output as well as video.
Anyone else have thoughts?
I'm not sure what the feasability of writing a wrapper for BR playback with extended features would be. BattleLauncher makes a good tool for managing playback and takes lots of the comand line stuff out, but it's very limited and hasn't seem to have gotten any TLC for awhile now.

Comment