VRS Introduces TacPack®/Superbug™ v1.7!
Upgrades Available for TacPack P3D v1-5 Licenses
TacPack® and Superbug™ support is now available for Prepar3D® v6 covering v6.0.26.30799 through v6.0.34.31011 (HF4).
While the TacPack v1.7 update is primarily focused on obtaining support for P3D v6, other changes include TPM performance and visual upgrades as well as the removal of the legacy requirement for DX9c dependencies.
TacPack and Superbug v1.7 is now available for anyone currently running P3D v4 through v5. v1.7 supports all 64-bit versions of P3D including v6. If you are currenrtly running v4 or v5 TacPack licenses, you may upgrade to a v6 license at up to 50% off the new license price regardless of maintenance status on the previous license. Any existing maintenance remaining on the previous license will be carried over to the new license.
Customers who wish to continue using TacPack for P3D 4/5 may still obtain the 1.7 update from the Customer Portal as usual, provided your maintenance is in good standing. If not, maintenance renewals may be purcahsed from the customer portal under license details.
For additional details, please see the Announcements topic in our support forums. If you have any questions related to upgrading or new purchases, please create a topic under an appropriate support sub-forum.
Introducing SuperScript!
For TacPack-Powered VRS F/A-18E Superbug
VRS SuperScript is a comprehensive set of Lua modules for FSUIPC (payware versions) for interfacing hardware with the VRS TacPack-Powered F/A-18E Superbug. This suite is designed to assist everyone from desktop simulator enthusiasts with HOTAS setups, to full cockpit builders who wish to build complex hardware systems including physical switches, knobs, levers and lights. Command the aircraft using real hardware instead of mouse clicking the virtual cockpit!
SuperScript requires
FSUIPC (payware),
TacPack & Superbug for P3D/FSX. Please read
system specs carefully before purchase.
Install Team R2r Root Certificate New
How to Install the New Team R2R Root Certificate Safely Audio software enthusiasts and producers often encounter releases from the reverse-engineering group Team R2R. Many of their modern software modifications require a custom root certificate to validate emulated licenses.
Which (Windows 10/11 or macOS version) are you currently using?
A security warning may pop up asking if you want to install a certificate from a source claiming to represent "Team R2R." Click .
Installing any third-party root certificate grants that certificate authority total permission to validate software and web traffic on your machine. install team r2r root certificate new
Expand the section and change "When using this certificate" to Always Trust . Close the window and authenticate again to save changes. Verifying the Installation To ensure the certificate is running correctly:
How to Install the New Team R2R Root Certificate: A Complete Guide
If you understand the risks and need to install the certificate, follow these steps. Step 1: Open the Certificate Manager Press to open the Run dialog box. Type certmgr.msc into the text field. Click OK or press Enter. Step 2: Locate the Trusted Root Certification Authorities Look at the left sidebar of the Certificate Manager window. How to Install the New Team R2R Root
: Select Local Machine (this requires administrative privileges). Select the Certificate Store : Choose Place all certificates in the following store .
The old R2R root certificate reached its expiration date.
: Ensuring that the R2R components, like the Silk Emulator for Cubase 12, are seen as authentic by Windows. A security warning may pop up asking if
How to Install the New Team R2R Root Certificate: A Step-by-Step Guide Introduction
Installing a third-party root certificate grants that certificate authority the power to validate any website or software on your machine. If a malicious actor compromises that certificate, they could theoretically intercept your secure internet traffic (a Man-in-the-Middle attack).
Most R2R releases are optimized for Windows systems. Follow these exact steps to ensure the certificate installs into the correct system store. Step 1: Locate and Extract the Certificate File
: Find the file named R2R.crt , Team_R2R_Root_Certificate.der , or similar inside the release folder.
