![]() If I could find when those messages were printed, I could find the cool frags! Thus, the first Cut by Pattern feature was born: Cut by Chat. ![]() I then realized that the chat message is a marker for cool frags. Whenever I had made a cool frag, I was using the same exact chat message every time because I had a chat bind for said message, so all I did was press a key. I was definitely not going to watch them, so I had to find another way. Those others demos were not renamed (time-stamp, type of frags) nor sorted. When I started work on my first fragmovie, I had a bunch of properly sorted and named demos with cool frags but I realized I had a lot more cool frags scattered among a huge amount of demo files. UDT_viewer requires Direct3D 11 on Windows and GLFW 3 on Linux. If you have Windows 8 or later, then you should have it pre-installed with the OS unless you changed system settings. NET Framework 4.0 Client Profile at a minimum to run. not in Program Files nor Program Files (x86)). It is therefore recommended to put all the binaries in a new folder with read and write access (i.e. The command-line tools have no third-party dependencies.įor Windows users: UDT_GUI, UDT_cutter and UDT_viewer need to be able to read and write to config files right next to them. No installation is required for any of the binaries. Read/write demos can be analyzed, modified and cut. GUI application for demo analysis, information display, cutting by time or various patterns, time-shifting, merging, conversions, etcĪ 2D demo viewer for Q3 and QL that can generate heat maps Shared library that does the actual cutting and analysis workĬommand-line application for cutting demos by time, chat patterns ( Cut by Chat) or matches ( Cut by Match)Ĭommand-line application for splitting demos with at least one map change into individual demos with no map changesĬommand-line application for shifting the non-first-person players back in time (a sort of anti-lag)Ĭommand-line application for merging multiple demos into oneĬommand-line application for exporting analysis data to JSON files (one per demo file)Ĭommand-line application for exporting a sorted list of all flag captures from the demo recorder to a single JSON fileĬommand-line application for converting demos to a different protocol version A 2D demo viewer for Q3 and QL, UDT_viewer, written in C++.Supported OSes: Windows only (requires the. A GUI application, UDT_GUI, written in C#.A set of command-line tools, written in C++.A shared library, UDT_DLL, with a C89 compatible interface, written in C++.The project is currently comprised of 4 parts: Viewing Q3 and QL demos with the 2D demo viewer (top-down view)Īlternatively, you can browse this folder where you can also find older releases.Converting demos: convert demos to a different protocol version.Merging demos: given multiple demos from the same match recorded by different players, create a new demo with more complete information.Time-shifting demos: shifting the non-first-person players back in time (a sort of anti-lag).Searching for patterns: given rules defined by the user, find matching events and display the results with the option to apply cuts later.Cutting by patterns: given rules defined by the user, find matching events and cut demos around the times of said events.Splitting demos: given a demo with multiple gamestates (happens on map change/reload), create a new demo file per gamestate.Cutting by time: creating a new demo file that is a time sub-range of the original demo file for easier processing or demo viewing.Extracting and displaying information or saving it to a JSON file (examples: map name, player names and teams, game mode, team stats, player stats, etc).UDT is a set of tools for analyzing, cutting, converting, modifying and viewing Quake 3, Quake Live and Return to Castle Wolfenstein demo files.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |