Page 2 of 2 FirstFirst 12
Results 16 to 22 of 22

Thread: bullet dynamics sim 13% cpu?

  1. #16
    Quote Originally Posted by gamedesign1 View Post
    I have the same issue with other features in LW. For example Catmull Clark. It has never really worked with all of the modelling tools. It has never been fixed with an update and my only option would be to buy a new version. I personally don't think thats fair as its a feature of the software I have paid for already. With the small scale projects I do, Lw2015 is great, but it has always bugged me that I can't use CC.
    Catmull Clark was implemented in version 9.0 along with edges and neither one of them have ever fully worked so versions 10, 11, and 2015 all have that in common as far as not addressing the issue.

  2. #17

    they need to abandon Modeler.

    then start fresh by creating the new Modeling algorithms/tools in Layout.
    LW vidz   DPont donate   LightWiki   RHiggit   IKBooster   My vidz

  3. #18
    Registered User
    Join Date
    Oct 2014
    Location
    UK
    Posts
    519
    Quote Originally Posted by hrgiger View Post
    Catmull Clark was implemented in version 9.0 along with edges and neither one of them have ever fully worked so versions 10, 11, and 2015 all have that in common as far as not addressing the issue.
    Thats even worse then ☹️

    - - - Updated - - -

    Quote Originally Posted by erikals View Post
    they need to abandon Modeler.
    I
    then start fresh by creating the new Modeling algorithms/tools in Layout.
    I think thats their plan

  4. #19
    Registered User
    Join Date
    Aug 2016
    Location
    a place
    Posts
    496
    Quote Originally Posted by erikals View Post
    they need to abandon Modeler.

    then start fresh by creating the new Modeling algorithms/tools in Layout.
    i don’t know. i find modeler to be the best part of lightwave.
    i’d abandon layout. guess that’s what luxology did

  5. #20
    Quote Originally Posted by gar26lw View Post
    i don’t know. i find modeler to be the best part of lightwave.
    i’d abandon layout. guess that’s what luxology did
    No thats not at all what they did. They built a framework called Nexus and from that Modo was created. The first version of Modo only had the modeling tools but Nexus was capable of creating applications with modeling, rendering, animation, etc.... So they didnt create a modeler and start bolting stuff on top of it.

  6. #21
    they need to abandon Modeler, then start fresh by creating the new Modeling algorithms/tools in Layout.

    Difficult to think of a worse way to model, even Unity or Unreal understand asset generation is a wholly separate function to scene setup and animation, as in it's a process you do elsewhere, yes have tools that support setup and placement fine but even in Modo I find it uncomfortable, would rather run two apps one dedicated to each.

  7. #22

    Difficult to think of a worse way to model,
    i disagree. in fact, very few (even at NT) agrees to your statement.

    they can make a closed environment, would solve it.

    if done right, one would hardly notice the change.

    however, if done wrong, yes, it will turn out clumsy.
    LW vidz   DPont donate   LightWiki   RHiggit   IKBooster   My vidz

Page 2 of 2 FirstFirst 12

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •