Rack 2 works fairly well, although my laptop is throwaway, but I have problems with some downloads: NYSTHI 2.0.6 and Valley 2.0.0.
It tells me download complete, close Rack and reopen it to see the new modules, but when I reopen Rack I don’t see them, and I find them to download again.
Does it happen to you too?
I apologize if I post in the wrong section or if someone with the same problem as me has anticipated me.
Your side might be good, how’s the server you’re trying to download from doing? This was happening with a few plugins for me, I came back and tried again a few hours later and they went through fine.
Rack v2 has a 10 sec max download time when updating plugins, so if a plugin doesn’t finish in that amount of time, the update cancels. This is affecting a lot of the larger plugins. I contacted VCV support about it, and hopefully it gets fixed soon (either with a longer timeout, or by removing the limit altogether)
Ah! Yeah, I just watched this happen several times with Substation, NYSTHI, and Valley, all of which I would dearly like to have now in V2
For anyone wondering if this is happening to them, you’ll see the percentage counting up, then it will either flash up much faster or just reset to the version number, there won’t be a check-mark, and the next plugin (if there is one) will start downloading.
Even after the timeout is redefined to be less hair-trigger (like e.g. 30 seconds since the last packet was received, not 10 seconds to do the whole thing) it would probably be good to color the failed plugins in red with a tooltip, or something. Right now it’s not even clear from the interface that something has gone wrong.
For me, are the “ohmerprems” and “valley” module, which does not install, I noticed, unlike the others, when downloading the “* .vcvplugin” is zero bytes when it is created, so no ‘’ installation when restarting the application.
Oh, that is super interesting. I’d say “mystery solved”. It is pretty bad to give no error message. Is there at least something in the log when this happens?
I don’t know about no time out… In my experience most front end proxy servers will time out after a minute or two. Don’t know why really, but it seems “normal” to me now… 10 seconds, however, is crazy short.
I tend to agree, although really until this release it’s not really happened much before, and Andrew is pretty ruthless with not added non-essential features (probably one of the reasons he can so something as amazing as VCV).
I know at work someone would probably make me work for a week on something like that