Home Creators Posts Import Register Favorites Logout

Content

Just run VaM_Updater.exe found in your install folder to update. Click the Update to 1.17.0.1 and the update will start. Enjoy!

Release Notes:

Features:

Added ability to set default creator name in User Preferences (Misc tab)

Added ability to set additional DAZ library directory in User Preferences (Misc tab) in case auto-method using registry entries does not work

Added ability to set default DAZ content directory used for browsing for DUF files in User Preferences (Misc tab)

Bug Fixes:

  • Fixed issue with user preferences always getting reset

  • Fixed DAZ auto-library determination. Now uses all library entries present in registry.

  • Fixed black tongue on female

  • Fixed male2 and male3 groin area textures

  • Fix for white bands around irises for some sclera choices for male skins

Tweaks:

  • Improved exception handling around DAZ import in case of further issues. This will at least provide error messages if there is a problem

  • UV template texture is now pure blue to allow it to be easily used for sim texture without having to remove the lines. Simply draw in pure red where you want the clothing to stick to model using the UV lines as a guide. No need to clear the blue as it is ignored in sim

  • Heatwave Shirt – set back to transparent queue as it was in 1.16. Can be adjusted using new render queue setting if desired

  • No longer update Saves/scene/default.json – this is fully under user control now. If this file is missing, it instead tries to load Saves/scene/MeshedVR/default.json

Comments

Dorvak

So what I have found is you cannot just download a clothing file from the internet and import it. It has to be in some kind of library..... I am not sure other than installing DAZ3D what other Libraries there are... So guess im installing DAZ3D lol

Zangetsu

Did anyone else got an issue after update with the character's tongue being black?

Zangetsu

ok the 1.17.01 update came out and fixed the issue already ... literally installed it 5 minutes after typing that other post, not sure if it was already out when i typed it ... i just realized .... this is its thread lolz ... i set a like on it ...

eclypse

Thanks for the super fast bug fixes as usual!

JunoVam

Im finding leap hands are well out of place on oculus, they are sitting well below where they should be, anywhere I can adjust this?

Dorvak

You may need to re-calibrate your leap motion

JunoVam

Thanks for the advice.I tried recalibrations and sadly same deal.

AK420

Thank you guys for your diligence and efficiency in releasing fixes! Much appreciated.

AK420

I know this is an exciting update, but curb your enthusiasm. ;D

DJ

A 2nd patch (1.17.0.2) will be out soon that addresses some leap motion problems. I don't know if this will fix your problem, but it might.

Sininside

I'm sure 1.17.1 is good! However, since the update I can no longer load or save ANY scenes. I've tried several times using the updater to patch it but it's not finding any errors in the files. Why have I lost the ability? Do I need to re-input my key?

Sininside

Okay so I took the time (and it took FOREVER) to do a FRESH INSTALL of 1.17.1! And guess what!? Same issue. No longer have the ability to load or save scenes. Think I may have to revert for now until this is fixed. I love how we can now go straight to desktop mode from the updater. But really that should be a function of VaM.exe.

eclypse

You must of done something wrong as I don't have that problem. Yes you need to add your key for 1.17 and after the update to 1.17.0.1. Did you install it under the C drive?

Sininside

I did add the key. It gave me a new key. It says it was accepted however the in game menu system is now missing save/load functions. I even tried reverting back to 1.16 and still the same problem. And no I have no room on my C: drive to install this. And I didn't do anything wrong. I fired up the updater, had it scan the integrity of my files. Apparently something was wrong so it patched it. Then I updated it. I even tried a fresh new install in a new folder outside of the original folder. I tried both the new version and 1.16 this way. And nothing. I'm just locked out for some reason. Which is upsetting because I am the highest level tier donator. I spent 5+ hours yesterday trying to get this to work. No dice.

Dorvak

What do you mean it gave you a new key? What did? The key for creator is the same for 1.17 and 1.17.0.1.

Sininside

The installer. It no longer accepted my original key from 1.16 so I deleted it and used the new one. Vam/keys/1.17/key.json... you know that key?

DJ

You DO need to re-input your key after updating from 1.17 to 1.17.0.1. If you neglect to do so, you're running the free version, which is why you can't save or load content.

DJ

1.17.0.1 uses the same key as 1.17. But you need to add it again.

jemoeder1993

I am a Patreon backer, I got the creator 1.17 key, got the 'key accepted', updated to 1.17.01, enabled edit mode and I cannot load/save/open save files since those options are gone in the menu, there only is an option to create a new scenes. I also cannot customize any clothing etc. It keeps telling me I need to join & back the Patreon project to unlock features. Please someone help.

Acid Bubbles

When I launched after updating to 1.17.0.1 I also "lost" my key, but I exited, launched, entered the key, put on the VR headset and it worked. Don't know if that'll help...

Sininside

Exactly my problem! Please FIX!

jemoeder1993

What do you mean by ''lost''? I am not asking for a key, I have a creator key.

Sininside

If you happen to have had the key open in text editor during the update, it will be overwritten with a new key. I also try this new key and still I cannot access my old saves or create new scenes. This is a major problem and MUST BE FIXED PROMPTLY, please and ty.

Rupert Jackson

Updating does seem to remove the keys and you have to reenter.

DJ

The program download does not come with a key. Your key.json file is outdated as soon as you upgrade, whether it was open or not. The only place to get your key is this parteon page. The key posts are directly below the post announcing the new version.

Sininside

Dude... I feel like such an ass. So I'm guessing we have to grab the "new key" with every update? Anyway, my shit's all good now (finally).

Sininside

I'm thinking maybe the key changes? Maybe done this way so that any old-backers can no longer get updated versions. That's my take on it. Only current backers have access to new keys and new updates.

jemoeder1993

I fixed it by updating as administrator!

Rupert Jackson

The .0.1 updates usually happens in the month and isn't a new version, so the code should be the same. :-)