Solved New Update Safe to do? 1.20.77.8 to 1.22?

[3rdStoryline]

I've been creating a fairly complex scene, with many animations, many nodes that get turned off and on through-out, many many varying potions across a large area, with many assets that get toggled on and off during all of this. Basically an entire house, that is intractable, with scenes that start in different parts of the house. With people that are interactive.

I've been reluctant to update as I'm still at version 1.20.77.8, I'm afraid updating will mess up my complex scene in someway, in which It will take me hours to go through the entire thing after updating to fix issues.

Does anyone know if there has been any issues updating? causing scenes to have problems?

And is it safe to update with that big of a jump?

Normally I'd just copy an install, and update the copy and see everything is okay. But in this case, my vam folder is 400gbs. Most of which are not VAR files, as I don't really care for managing VaM with VAR's unless required. Normally I'll just unpack them, and put them where I know to find them, and not in a giant VAR list along the side that you gotta scroll through for an hr looking at tiny text. I digress. So doing a temp update is sorta out of the question..


My other concern is that some things may have changed, in a way where when I continue making the scene, that I'll have to spend half a day reassessing the program.

Any insight would be appreciated!

PS: There are features in the latest update that has caught my attention. It's why I'm now considering it.

 

[atani]

Considering you can have more than one VaM folder, but don't want to have another or even use VARs, then stay in 1.20.
You'll be stuck in time and won't be able to use new things that only work in 1.21/22, but that's up to you. There's no garantee about anything.

 

[3rdStoryline]

Considering you can have more than one VaM folder, but don't want to have another, then stay in 1.20.
You'll be stuck in time and won't be able to use some new things that only work in 1.21/22, but that's up to you. There's no garantee about anything.

So there are known issues with updating?

 

[atani]

Issues in what way?
Will old scenes play? Very likely. If they break it's probably more related to the plugins being updated, or resources removed from the Hub, hardly ever from VaM changing.

 

[3rdStoryline]

Issues in what way?
Will old scenes play? Very likely. If they break it's probably more related to the plugins being updated, or resources removed from the Hub, hardly ever from VaM changing.

Hmmm.. I see. Now that I think about it, I've been using the latest plugins that are meant for the latest version(or 1.21) of VaM and not the one I'm on. And yet they all seem to work flawlessly, even though many of them claimed to only use on version 1.21 or higher. So maybe VaM is more lenient then I originally thought. In which case updating might be fine to do.

Do we know if the recent changes in world scaling will negatively affect an old scene? Or was that purely for Camera perspectives and not the actual objects in space?

 

[atani]

Do we know if the recent changes in world scaling will negatively affect an old scene? Or was that purely for Camera perspectives and not the actual objects in space?

I don't know what world scaling does, so no idea.

 

[DJ]

You can make another Vam installation without moving all your vars to it. I'd suggest making a clean install (it's about 20GB) then move over your big custom scene and any dependencies. See how it runs before deciding whether to stick with 1.22.

I'd be very surprised if you have any issues, but no guarantees.

The other option would be to update you main installation to 1.22, and simply revert to 1.20 if there are any issues. You can do that in the "options" section of the updater.

 

[3rdStoryline]

You can make another Vam installation without moving all your vars to it. I'd suggest making a clean install (it's about 20GB) then move over your big custom scene and any dependencies. See how it runs before deciding whether to stick with 1.22.

I'd be very surprised if you have any issues, but no guarantees.

The other option would be to update you main installation to 1.22, and simply revert to 1.20 if there are any issues. You can do that in the "options" section of the updater.

So I decided to Robocopy the entire directory for safe keeping.. RIP400gbs. xD Anywho, update 1.22.0.0 broke many of my animations as many of them used reverse actions. As of 1.22.0.1 however, that was fixed. so everything that I've tried thus far in 1.22.0.1 has worked flawlessly. I actually have a few more FPS then before. So that's a plus xD.

Only thing I noticed (and isn't a colossal deal) is some of my duplicate Morphs I made don't like to load separately, and get thrown in together as the same thing on scene load. Meaning the morph is doubled, instead of being their two separate values. Though, I can just manually fix that by naming them differently. no big deal. I should of done that to begin with anyway xD (I have some duplicate morphs, cuz I found during animating, that I some times would want two that can be handled separately. It works well, if used correctly.)

Thanks for all your help guys!

PS: just for testing purposes after realizing 1.22.0.0 wasn't working out, I reverted the install back to 1.20.77.8, just to see if everything would work again, and to see how safe reverse updates were. And that ended up working out well. So for anyone else that is worried or uncertain, updating to a previous version works flawlessly as far as I can tell.

 

[Stevio]

Hey together, wtf is wrong with this bulshit update 1.22. iwas still using 1.20 until recently, and now after updating to 1.22, Addon package folder in the Virt a Mate folder is apparently no longer on my drive. it shows me an error alarm,I can't access it, copy it, etc. What the hell is this? I hope someone can help me here, please.

 

[atani]

Hey together, wtf is wrong with this bulshit update 1.22. iwas still using 1.20 until recently, and now after updating to 1.22, Addon package folder in the Virt a Mate folder is apparently no longer on my drive. it shows me an error alarm,I can't access it, copy it, etc. What the hell is this? I hope someone can help me here, please.

As you're a very long time user, you should know you need a new key for a major version change update: 1.20>1.22
A VAM update doesn't delete files. Go to your VAM folder and you'll see the AddonPackages folder and its contents are still there. You can't use any because you're in free mode in 1.22 until you get a updated key.

 

[Stevio]

As you're a very long time user, you should know you need a new key for a major version change update: 1.20>1.22
A VAM update doesn't delete files. Go to your VAM folder and you'll see the AddonPackages folder and its contents are still there. You can't use any because you're in free mode in 1.22 until you get a updated key.

thank you, but i got a creator key and used it, like all the times befor where it works, but now !?

 

[atani]

thank you, but i got a creator key and used it, like all the times befor where it works, but now !?

Do you have a creator key for 1.20 or 1.22? They're different.

 

[Stevio]

Do you have a creator key for 1.20 or 1.22? They're different.

i know, im not stupid, ive got one for the 1.20., one for 1.21 and another one for the 1.22.

 

[atani]

i know, im not stupid, ive got one for the 1.20., one for 1.21 and another one for the 1.22.

You have no idea how many people came with a "help, nothing works now after I updated VAM" and the reason was for not having a valid key. So I had to be sure that's what you meant as it wasn't clearly stated before.

Given that you have a valid 1.22 key, my advice is for you to download a clean 1.22 VAM in a new folder. This one should work, but worth testing first to dismiss other potential reasons.
While you download the clean VAM, with File Explorer check your old VAM folder's AddonPackages and confirm everything is there. As I said, the updater does not delete personal files, but at least you can confirm this as you're saying earlier they're not.

 

[Stevio]

You have no idea how many people came with a "help, nothing works now after I updated VAM" and the reason was for not having a valid key. So I had to be sure that's what you meant as it wasn't clearly stated before.

Given that you have a valid 1.22 key, my advice is for you to download a clean 1.22 VAM in a new folder. This one should work, but worth testing first to dismiss other potential reasons.
While you download the clean VAM, with File Explorer check your old VAM folder's AddonPackages and confirm everything is there. As I said, the updater does not delete personal files, but at least you can confirm this as you're saying earlier they're not.

I tried the key last week when I did the update and everything worked without any problems, which is why I'm so annoyed about it. Because otherwise it would be the simple problem: buy a new key and that's it. But that's definitely not the problem. I can't even change the folder's properties or grant any access to it or anything like that. It's as if the folder is locked, really weird. But it's there and it's filled with 700 GB, that can't be normal. I wouldn't be surprised if it's Windows. I backed up my data to my external hard drive before the update for just such a reason, so that it wouldn't destroy my data, which was right. The strange thing is that the Addon Packages folder on my external hard drive is empty, I've never had that happen before and unfortunately I only noticed it today.

 

[atani]

What you describe is not something that a VAM update would do, looks like an external reason. It would not delete or change properties of folders.
Where's your vam folder? Protected locations like Desktop, Users/..., Program Files, etc., shouldn't be used. What you describe sounds like permission problems of some kind or other external reasons.

 

[Stevio]

What you describe is not something that a VAM update would do, looks like an external reason. It would not delete or change properties of folders.
Where's your vam folder? Protected locations like Desktop, Users/..., Program Files, etc., shouldn't be used. What you describe sounds like permission problems of some kind or other external reasons.

I had installed it on a partition I created myself, and everything worked until the update and shortly afterward, but as I said, when I tried it again recently, that was it. Is it possible that after the update, you have to confirm certain settings, which could mean something wrong? Maybe I selected the wrong thing, and that messed up my folders. But that can't be the case, because it worked shortly after the update. It's a complete mystery to me.

 

[atani]

The update doesn't bring any setting that would block VAM like that. As you said, it worked after the update, but you can do a core check (vam_updater.exe) and see if anything's corrupted.
I expect that almost everyone is running VAM 1.22 by now and it is stable. You can always download a fresh VAM, copy over your things and try that.

 

[Stevio]

The update doesn't bring any setting that would block VAM like that. As you said, it worked after the update, but you can do a core check (vam_updater.exe) and see if anything's corrupted.
I expect that almost everyone is running VAM 1.22 by now and it is stable. You can always download a fresh VAM, copy over your things and try that.

I've already tried to check and repair it using the VAm Updater, but it says it failed, and "Repair Core" and "Repair All" say a fatal error occurred. In short, I can't fix it that way, but I'll try installing a new 1.22 version to see if it works. Otherwise, I'll have to delete everything and recompile or create it. I'm really pleased.

 

[atani]

If it fails then something is happening on your VAM folder or is a connectivity problem. For the connectivity problem, try a VPN, if a folder problem, then something in your system did this as the updater or VAM doesn't change folder/file permissions. For this it's recommended to download a new VAM, then you can move your stuff to it after testing it works.