Efficient way to switch between builds of Verge3D?

This topic has 3 replies, 2 voices, and was last updated 3 years, 3 months ago by Alexander Kovelenov.

Viewing 4 posts - 1 through 4 (of 4 total)

Author

Posts
2021-08-11 at 4:41 pm #43580

jem
Customer

Hi, I have projects on different builds of Verge3D. Ideally, I would like to update all projects to the current build of Verge3D, but I cannot.
I have been switching between builds of Verge3D by installing the correct version when needed. Does anyone know of a better way to do this? Maybe I could install parallel versions and switch paths with a PowerShell or Python script?

Any ideas would be appreciated. Thanks!

Jeremy Wernick

2021-08-12 at 8:29 am #43590
Alexander Kovelenov
Staff
Hi Jeremy,
Indeed it will require some scripting. Here is the bash script we use internally to update the engine:
```
APPS=path_to_verge3d_applications_dir
echo "Copying engine to application directories"
find $APPS -name "v3d.js" -exec cp -p "$APPS/../build/v3d.js" {} \
```
So basically you need to search for “v3d.js” files and update them from the place you require (e.g the build folder).

Soft8Soft Tech Chief
X | FB | LinkedIn
2021-08-12 at 3:11 pm #43614

jem
Customer

Hi Alexander,
I understand your script. I can adapt it and make it work for me.
BTW, even though I do run Windows 10, I usually run my automation from a Bash shell in WSL, so I will not need to change your script much.

But, do I need to switch Verge3D Blender add-on if I am switching versions of the engine? I imagine that there are some changes to the add-on between builds and some of these changes might be critical to the functioning of the engine.

Thank you very much!

Jeremy Wernick

2021-08-12 at 4:34 pm #43618

Alexander Kovelenov
Staff

We always try to maintain backward compatibility for exported assets, especially if Verge3D version changed not much. So in your situation I’d recommend stick to the older version of the Verge3D for Blender add-on.

Soft8Soft Tech Chief
X | FB | LinkedIn
Author

Posts