SEADS Version 3.22 is now available!
Mo_Steel
Changes In Version 3.22:
* Added conversion options to the Demo Browser menu.
--> H x W - Pretty self-explanatory, lets you define the game
window size.
--> Tick - Lets you choose a starting tick; default is 1 (this
will override any other Demo Edits you have for the selected demo.)
--> FPS - Lets you define the host_framerate value to record at
(and inversely the host_timescale value; I've read varying info on
timescale, so if anyone has a better grasp on it please chime in).
--> Disable HUD Elements - Should disable all HUD displays (chat,
crosshair, hp, etc.)
--> Disable Viewmodel - Sets r_drawviewmodel to 0 (this can
persist after recording; add "r_drawviewmodel 1" without quotes to
your autoexec if you use this a lot).
--> Disable Voice Chatter - Sets voice_enable to 0.
--> Enable Depth Overlay - Sets r_depthoverlay to 1. Mostly useful
for creating depth of field effects in post production.
* Demo Browser functions (view, record, recycle, rescan, etc.) have
all been moved up into the menu bar.
* Demo Browser functions can also now be selected by right-clicking on
a demo in the Demo Browser list.
* The Demo Browser now recycles empty folders in the "saved_demos"
subdirectory when it scans for games.
* Removed "saved_demo" from the naming programming (mostly superfluous
with map name, time, and demo numbers for differentiation).
* Added an option to the Demo Browser configuration tab: Highlight /
Delete Demos Without Markers.
* Added a button to the General Configuration tab to open the Demo
Browser.
* SEADS will now make a backup of "config.cfg" on fresh install or
after checking for new Source Games for keybind / settings backup
purposes.
* Minor cosmetic changes for the Configuration menu and the Demo
Browser.
[b]Bug Fixes:[/b]
* Fixed the Save Recorded Demos button not working properly.
* Fixed an issue with DoD:S Demos not being saved.
* Modified the application manifest to request highest available
rights from the system. Hopefully this will resolve some user issues
with insufficient rights for file operations.
-------------
One thing I've noticed with the addition of scanning for markers in
the Demo Browser is an increase in memory footprint from ~10,000 to
~250,000 that persists until the system is idle or other programs need
the memory. I'm looking into improving and resolving this, or if I'm
unable to resolve it making marker scanning an option that can be
disabled to maintain a smaller footprint. In the meantime, closing
the entire program (by right-clicking the tray icon and selecting
Exit) and opening it again will clear it out manually if desired.
As always, feedback, suggestions, and encountered bugs or problems are
welcome.
~Mo