Lobo3433 posted at 12:35AM Fri, 14 June 2019 - #4352886

I agree I would check this if we had some more posters from what ever modeling software they used I know right now I am self learning Lightwave took advantage of the recent upgrade pricing to go from 11.6 to the current version still having issues with transferring Blender knowledge and tools sets to Lightwave. One thing I would love to see someone take on maybe a groups of people can take this one but putting together a sort of tool name translation lol I mean in Blender an inset function looks to similar to the bevel function it Lightwave, the connect function in Hexagon looks almost like the loop tools bridge tool and I will be honest the fact that the different software's don't use a more universal naming convention for tools can be really annoying Sorry got on a soap box

I had, ages ago now, created a cheat sheet of sorts for myself for going from LW to Blender; stuff was organized by LightWave's tools/uses/hotkeys. I haven't the foggiest where it is now, nor would it be much use to someone else unfortunately, as my hotkeys in LW are largely customized to my workflow, and most of the cheat-sheet referenced those.

For what its worth, I think its maybe easier going TO LW from Blender than the other way around, at least from a modeling standpoint, cause if nothing else with LigthWave being split into two halves you're not tripping over rigging/lighting/rendering tools in the Modeler side of things, you're just always in edit mode, and tools functions/hotkeys won't vary based on the mode you're in.

A lot of times there aren't necessarily 1:1 equivalents. Like your "inset" vs "bevel" comparison, they do some of the same stuff, in that they both introduce a ring of polygons around your selection, but Blender's "inset" also has some of the functionality of LW's "smooth shift" tool, while LW's "bevel" kind of falls on its face when used with multiple polygons selected. So in that case, you'd use "inset" for single and multiple polygon selections in Blender, but in LW you'd want "bevel" for single polygons, and probably want "smooth shift" for multiple polygon selections.

It would be nice if there was a common naming convention, but you'd need common functionalities as well, and they've barely managed to sort a universally supported file format with .OBJ in all these years. You've still got some software packages that don't recognize certain aspects of .OBJ format that others do. The best thing you can do, is create your own cheat-sheet as you go.

---

LuxXeon posted at 1:50AM Fri, 14 June 2019 - #4353130

I hope there are more people out there interested in general 3d modeling, but I'm glad to see a few familiar faces here.

I've been on a bit of a modeling hiatus myself, but this is one of the forums I do check a couple times a week usually.

Core i7 950@3.02GHz | 12GB Corsair Dominator Ram@1600mHz | 2GB Geforce GTX 660

Lightwave | Blender | Marmoset | GIMP | Krita