Guides Unity AssetBundles for VaM 1.xx

[Failure]

I figured out the problem, it had to do with the daz to unity bridge. I tried going through the export route on daz, but when I load up the assetbundle in vam the models don't appear.

 

[UserBob]

The latest version of unity hub or whatever the fault is broke the project. It used to work not long ago but now I can only create new projects but can no longer import the "UnityAssetBundles-Project-20200307" you posted. Many assests are simply lost to unity making things frustrating with their hub and updates.

EDIT: The problem was the login with facebook window no longer working for some Zuck magic reason, it works if using normal unity account.

 

[jpxrz]

Just ran into an issue after a Windows and NVIDIA driver update: the project (Unity 2018.1.9f2) would crash right after the progress bar, leaving a UnityLockfile in Temp. Event viewer gave exception code 0xc0000005, unknown module.
Seems the new driver doesn't play well with Unity 2018.1's D3D11 init. The template has D3D11 as the preferred Graphics API by default, which causes the crash.

Solution:
1. Launch the project once with -force-glcore: [run CMD, then run "your unity.exe path" -projectPath "YourProjectPath" -force-glcore
2. In Unity: Edit → Project Settings → Player → Other Settings, uncheck "Uncheck Auto Graphics API for Windows", then add OpenGL Core to the list and move it to the top
After this 2 step, it opens normally via Unity Hub.

@MacGruber – maybe you could update the template's ProjectSettings to prioritize OpenGL Core (or make it driver‑agnostic)? Would save others from this headache after future driver updates.

Hope this helps anyone hitting the same crash!