-
-
Monospace Online
-
- Posts: 624
- Joined: Fri May 07, 2021 4:38 am
Sun Nov 14, 2021 11:07 am
It is a good point. Personally I download VSTs myself to try and replicate bugs, but I don't think musikbear typically downloads them right away, instead troubleshooting for basic problems first. So asking a user to check for prerequisite software packages or dependencies to run the program, is very useful a tip. When a runtime library is missing, it is a very irritating problem from what I've found. In other forums, like the PaintDotNet forums, there are a surprising number of support tickets re: VCRUNTIME140.dll, where you need a very specific version of it to run the program in the first place.
I don't think any of us would've thought of runtime libraries when receiving a support ticket without testing the VST ourselves. Subsequently, the suggestion is a good one to keep in mind because that way, if we face any "weird" error boxes, then we could directly ask the user to check for software packages without having to download the VST ourselves.
That being said, I must mention this. From experience, very few VSTs actually need runtime libraries, and very few VST support tickets actually are caused by missing runtime libraries. Asking the support team to request user to verify they have libraries for each time they get a VST help request, imo, is a bit of an overkill. It's like asking the user what architecture (x32 or x64) their computer is, or where they downloaded LMMS from, in the off chance they're using a 32 bit computer or an unofficial download. And even requesting user to tell where they downloaded LMMS makes more sense than checking availability of runtime libraries probability-wise, and still we don't typically ask users where they download LMMS, because the probability they downloaded from a site that isn't lmms.io isn't high enough to warrant asking.