• Hi Guest!

    We are extremely excited to announce the release of our first Beta for VaM2, the next generation of Virt-A-Mate which is currently in development.
    To participate in the Beta, a subscription to the Entertainer or Creator Tier is required. Once subscribed, download instructions can be found here.

    Click here for information and guides regarding the VaM2 beta. Join our Discord server for more announcements and community discussion about VaM2.

Struggling to figure out Unity and adding custom unity assets to VAM (read desc)

dankfrank

New member
Joined
Feb 26, 2021
Messages
7
Reactions
1
I am brand new to Unity in general, so there may be some things that I've missed, but heres a summary:

I took a 3d scan of my bedroom and converted it to an obj file to open in Unity. Looked at every tutorial under the sun. Made the obj into a prefab, added the AssetBundle builder, used it, packed it into a var and everything seemed good, until i actually tried loading it and the error log just said "Not valid". Then I looked it up and learned that you need to use a very specific older version of Unity in order for it to be compatible with VAM. So I thought, ok cool, I'll just install that version and do the same thing. I don't see any way of using/adding any of the tools that I was using in the current version (AssetBuilder Browser, assetbuild exporter, etc). Searching on google, reddit, or here did not help, so I am completely stuck. All I want to do is add my bedroom as a CUA to VAM. If anyone here is willing to just do all of this for me I can email you the obj file and its textures and will compensate you if youd like.

Please don't link any tutorials from here, I'm pretty sure I've seen them all.
 
Following MacGruber's guide for Unity assetbundles works great for me. Try making something else as an assetbundle and loading that into VAM. Afterwards, you can compare if there was something you missed when doing the bedroom.
 
I’ve struggled with similar issues when working with VAM and Unity, especially because VAM requires such an old Unity version that a lot of the modern tools just don’t work there. The “Not valid” error usually means something about the asset or the Unity version isn’t matching up. Honestly, it can be really frustrating, and unless you’re used to that older workflow, it’s tricky to get everything right. If you’re stuck after trying all the tutorials, it makes sense to find someone who’s familiar with that exact setup to help out, since it’s a pretty niche skill now. If you want, I can suggest some places where people do this kind of work or even take a quick look at your files, but just make sure whoever helps knows the exact Unity version VAM needs, because one wrong step and it won’t work at all.
 
Back
Top Bottom