ASNA Visual RPG Classic: FAQs

AVR 4.x was created with what is now a very old C++ compiler. In order to extend AVR Classic life as much as we can we have since ported the old AVR 4.x project to a much newer C++ compiler. This newer compiler enables us to pledge support for AVR 5.x with Windows 10. AVR 4.x is not supported on any 64-bit Windows platforms. Other than Windows 10 support, functionally AVR 5.x is the same as AVR 4.x. 

We released AVR 5.0 in 2012. At that time, we replaced an 18 year-old C++ compiler with a new one. Time flies and we have since replaced that second C++ compiler with one about eight years newer. While AVR 5.0 is currently supported, we strongly recommend using AVR 5.1. 

We don’t support using multiple versions of AVR Classic (or .NET) for either development or runtime  on the same PC. 

No. Support for AVR 4.0 ended several years ago and support for AVR 4.0 ended with the arrival of AVR 5.1. We strongly encourage AVR 4.x customers to upgrade to AVR 5.1.

Third-party COM controls present a challenging issue. Our testing shows that many do work, at least in a runtime environment, on Windows 10/11. However, we’ve also experienced intermittent problems, even when running the same code on similar Windows 10/11 PCs.

One of the problems is that most of the companies who originally offered these controls are now out of business and there simply isn’t any support available for the controls. Mabry and Graphics Server are simply gone. Sheridan was bought by Component Source and they still sell the popular Sheridan Active Threed controls, but look at the caveat towards the bottom of their Web page that says:

“Please note that this product is no longer supported by the publisher, so it is no longer eligible for product support or maintenance.”

Translation: Component Source will gladly sell you deprecated copies of the Sheridan controls—but don’t call for support!

The behavior of third-party controls is completely out of our hands, so when controls have issues with Windows 10/11 there isn’t anything we can do about that. Customers using third-party controls will need to test their apps vigilantly.

Your existing 4.x should compile with AVR 5.x just fine. Simply open the 4.x project in 5.x and recompile. Do note that upon opening the 4.x project, as in past versions, the 4.x project is converted to a 5.x project—and there is no going back on this process. Be sure to make a backup of your 4.x project to project yourself against unseen issues. Remember also that you may encounter issues that third-party controls may impose. If a third-party control doesn’t work in 5.0 you’ll need to find an alternative.

No, we aren’t pranking you! We would never do that. We have seen many 4.x installations work fine on a given Windows 10/11 PC but then fail, for no apparently, on another similarly-configured Windows 10/11 PC. We no longer provide fixes or enhancements to the AVR 4.x family, and do not test it on Windows 10/11. As for it working on Windows 10/11 for you, it may. But it also may not. And it may not at very inconvenient times.

AVR 5.1 is not recommended for use with Windows Surface devices. For building apps Windows Surface devices we recommend using AVR for .NET. None of the AVR family runs natively on Apple or Android devices.