The standard and professional toolkit versions are now combined into a single toolkit providing access to all activeMARK features rather than deciding which toolkit to run for each project.
Basic mode supports the majority of packaging projects in a fast and simple three step process. Advanced mode exposes many of activeMARK's customization features such as configurable security settings, individual fileset protection rules and custom branded product trial pages.
ActiveMARK v6 allows users to switch between Basic and Advanced modes at any time, while retaining all data and settings. This allows most users to package titles using the Basic mode and switch to the Advanced mode via a single mouse click when they need access to an advanced feature. Once they have used the feature, they may switch back to Basic mode to finish the project.
| Basic Mode | Advanced Mode |
 |  |
ActiveMARK basic mode is configured with the most common settings allowing most titles to be successfully packaged, tested and registered in less than 15 minutes. Configuring with additional custom settings does not add much more time to the overall process.
The ActiveMARK v6 Graphical User Interface exposes numerous advanced features as easily selectable options. Features such as Content Individualization, File Shuffling, Entry and Exit Behaviors, Hook Libraries and more may now be easily selected in the Toolkit. No more manually adding advanced options by adding lines to the .amproject file.
| Advanced Compatibility Settings |
 |
Enable you product with our automated file update and patch management feature and your consumers will never need to worry about finding or installing the latest updates. The auto update feature is packaged as part of your base product enabling it to periodically checks the Trymedia servers for updates in a non intrusive and polite manor. Updates / Patches are protected with activeMARK and then associated with the original product. If you use the activeMARK integrated NSIS installer, we can automatically generate the update delta file from a newer version for you.
Whether you're offering an expansion pack with a new game engine or a set of Add-On data files, activeMARK can not only secure them, but associate them to the parent product to ensure a valid license of the base product.
ACB Intertwines the ActiveMARK code with the game code at both a functional and structural level, preventing removal of the DRM security without removing crucial parts of the game code. Does not require source code, all DRM security is added to the game binary.
Security overhead can be adjusted as appropriate by the products overall file size. Casual games with small overall file sizes, often less than 10 MB, can adjust the security settings to normal mode which only adds about 500 KB of overhead when using the standard ActiveMARK product pages.
ActiveMARK now supports telephone activation for your shrinkwrap CD / DVD distributed products through our Interactive Voice Response system (IVR). Consumers who purchase your product on a CD / DVD through traditional retail outlets and do not have an Internet connection may activate their products by calling our phone activation line. This allows ActiveMARK to easily support your product for both online and retail distribution.
ActiveMARK v6 provides a convenient method to allow your protected product to be signed during the activeMARK packaging process. Simply point to your certificate and private key file locations and ActiveMARK will produce the final packaged product signed and ready to go. NOTE- This requires the developer to have the .NET SDK running on their system.
For those that don't wish to create custom html in game pages, we offer a few different design templates that can be selected for your product end user experience pages. Select the template and preview how your product will be presented to consumers directly from the ActiveMARK packing toolkit.
ActiveMARK v6 now supports SOAP based uploads over secure SSL port 443 connections with full resume capability. This ensures the highest level of access as if a developer/packager can connect to a secure https website they can connect to our packaging central servers.
|
|
|
