01-01-2020, 10:10 PM
I use both MFL and Wings3d. MFL for the boolean plugin and Wings3d to stay in touch with the non forked.
My question is 'Are these two so variant that the merge will never happen into one monogamous tool?'
I would like to consolidate my efforts to a single package. The MFL has many very good model design injections.
Or am I in the gray area between a standard community tool and shadow tool? My concern is at some point will my other choice files diverge from a standard Modus operandi? As in an incompatibility chasm leaving me hanging onto the edges of each usage pattern in my development?
Thanks.
My question is 'Are these two so variant that the merge will never happen into one monogamous tool?'
I would like to consolidate my efforts to a single package. The MFL has many very good model design injections.
Or am I in the gray area between a standard community tool and shadow tool? My concern is at some point will my other choice files diverge from a standard Modus operandi? As in an incompatibility chasm leaving me hanging onto the edges of each usage pattern in my development?
Thanks.