Verge3D 4.11 pre1 available!

This topic has 18 replies, 7 voices, and was last updated 1 month, 3 weeks ago by Yuri Kovelenov.

Viewing 4 posts - 16 through 19 (of 19 total)

← 1 2

Author

Posts
2025-09-11 at 12:27 pm #84585

Alexander Kovelenov
Staff

I believe Maya users are very important for Verge3D ecosystem as a whole. First, they make really awesome applications such as the famous ESA Tour and the Bunker Ship (there are more). These apps attract more users to Verge3D even if the newcomers use Blender or 3ds Max. Second, the Maya version is an important component of the Verge3D Ultimate package which is quite popular and thus helps to maintain the financial security of our company.

Soft8Soft Tech Chief
Want more Verge3D updates? Follow me on X, Facebook, or LinkedIn

2025-12-10 at 8:18 pm #85696

omeletee
Customer

”
We’re now zeroing in on a new bunch of features inherited from Three.js long ago which we consider obsolete for the Verge3D pipeline. We already removed them from the Developer Reference. If there will be no special request regarding these features from Verge3D users, they might be removed altogether in the future.
”
Is it too late for me to say I hope to maintain compatibility with three.js?

I frequently consult the three.js community for resources when using JavaScript extensions. While the quality varies, they are very useful. Reducing compatibility will make this increasingly difficult; I’ll have to build the entire app from v3d.module.js, which is too demanding on my JavaScript skills.

Thank you for your hard work on software updates. I know maintaining compatibility will add extra burden to the work, but I hope you will consider it.

2025-12-10 at 10:16 pm #85697

xeon
Customer

Keeping three.js compatibility is key for advanced users that rely on integrating Three.js in its projects. I hope V3D maintains and constantly improves compatibility with Three.js.

Xeon
Route 66 Digital
Interactive Solutions - https://www.r66d.com
Tutorials - https://www.xeons3dlab.com

2025-12-11 at 6:42 am #85703

Yuri Kovelenov
Staff

Hi guys,

There is no intention to break compatibility with Three.js just for the sake of breaking. However, Three.js devs recently started to change their APIs and internals quite radically and without much regard for the existing user base. I believe this is a major issue of any open source library. This makes it very difficult for us to keep it up this their kinda obscure decisions. Therefore splitting with Three.js upstream seems unavoidable.

On the positive side, Verge3D users are now less likely to hit any issues when updating to newer versions because our code base is now naturally more stable. Ideally, it should allow to update Verge3D apps in the App Manager to any subsequent version by just clicking the button (i.e. without the need to make any changes in the app).

Chief 3D Verger | LinkedIn | X
Author

Posts