03-01-2016, 07:31 PM
I'd say that it is long past the point where Wings will get any kind of mass adoption. Tools have moved so far beyond simple polygon modeling that Wings will be hard pressed to retain any kind of foothold in an actual working pipeline.
I am not saying that it has no place at all, but the vast majority of industries out there reliant on computer graphics, are also reliant on high density meshes -- for whatever the purpose.
This is why the core tools and methodologies are better suited to be ported over to another package like blender or Maya, where the userbase far exceeds that of Wings. Because that is where Wings shines best, is in the way it approaches polygonal modelling workflows. The strength, in my opinion, has always been in the depth of its toolset and ease of use for quality of life features. It does one thing and it does it REALLY WELL.
You can see its methodologies in so many other packages these days, from Maya's now-native Nex tools (simply called its modelling tools), to basically all of Silo and even through to packages like blender and Modo (though modo strays from the traditional by doing alot of things differently. But the core is still there.
But, even with all of that, none of them do it as well as Wings was ever able to. (again my opinion).
I will be very curious if/when the C++ version ever releases how widely it is adopted and how well it works. I think having retopology capabilities within Wings itself would kick it right to the forefront of most other retopo solutions. Being able to retopo and more in one package would be deadly.
Yes you can do that in Maya, but I've never been a huge fan of Maya's lackluster approach to modelling. It has gotten better over the years, but with a package as massive as it is, the development of some tools simply gets left behind.
I am not saying that it has no place at all, but the vast majority of industries out there reliant on computer graphics, are also reliant on high density meshes -- for whatever the purpose.
This is why the core tools and methodologies are better suited to be ported over to another package like blender or Maya, where the userbase far exceeds that of Wings. Because that is where Wings shines best, is in the way it approaches polygonal modelling workflows. The strength, in my opinion, has always been in the depth of its toolset and ease of use for quality of life features. It does one thing and it does it REALLY WELL.
You can see its methodologies in so many other packages these days, from Maya's now-native Nex tools (simply called its modelling tools), to basically all of Silo and even through to packages like blender and Modo (though modo strays from the traditional by doing alot of things differently. But the core is still there.
But, even with all of that, none of them do it as well as Wings was ever able to. (again my opinion).
I will be very curious if/when the C++ version ever releases how widely it is adopted and how well it works. I think having retopology capabilities within Wings itself would kick it right to the forefront of most other retopo solutions. Being able to retopo and more in one package would be deadly.
Yes you can do that in Maya, but I've never been a huge fan of Maya's lackluster approach to modelling. It has gotten better over the years, but with a package as massive as it is, the development of some tools simply gets left behind.