Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Posts posted by vugie

  1. Sorry to miss your post, I'm not very often here recently.


    When I rotate the view, the chain appears to rotate independently of the axes..... am I required to make a transformation myself?

    In my opinion the chain swings like it should. What could mislead you:

    1. You modified anchor position offset, so chain won't swing in YZ plane if this is what you expected.
    2. This chain is connected with ball joints. Due to cummulating numerical errors the chain may go off the plane after some time (however I'm not observing such behavior). To avoid it use hinge joint if your goal is to have bicycle-like chain.
    3. Proportions of the chain in 3D picture will be different (and more natural) than in 2D Graph, because apparently I left non-uniform scales there for x and y axes.

    Also, the mesh reference is not available (closed?) if I do not keep the drawable reference.... is this normal?

    The mesh reference becomes invalid once assigned to the object. Instead you should get the object's drawable reference and use "To More Specific Class" primitive to be able to use SetMeshParams method again (picture attached).


    Also, how can I reference the mesh by name instead of by reference ?

    You may use "Find Object" block to find an object by name and then get its Drawable property.



  2. For the record - my reply to the same question I received via PM:

    Waptia works as generic optimization algorithm - you have to provide a function on a number of parameters and algorithm tries to find such set of parameters values for which the function value is the highest. So you'd have to describe any face with a set of variables and write a function in LabVIEW which evaluates how well given set of their values describe face in the given picture. Personally I doubt Waptia is the right direction for such application and even if it is, it's only one of many blocks needed.

    • Like 1

  3. I haven't invested too much time in that. All I got was 3ds model loaded into separate window and mouse controller. It was old .NET wrapper to VTK (http://vtkdotnet.sourceforge.net/ as I remember).

    Some time ago KitWare relased their wrappers called ActiViz as open source (http://www.vtk.org/Wiki/VTK/CSharp/ActiViz.NET). I also tried it but I got only a buch .Net exceptions (also during wiring).

    In both cases it was a painful process of converting simple C# examples to LV (long, long, looooong horizontal diagrams)



    test vtk activiz.vi

    test vtk.vi

  4. Lots of Eastern Europe uses 12-XII-2012 or XII-12-2012, where the months are Roman numerals, which has the nice property of being language independent AND distinguishing the day from the month so order isn't ambiguous. I really like this one.

    I'm from Europe (And have been to eastern europe) and I would have to say that I've never seen this formatting before. Can NI output this with standard formatters?

    As a citizen of country frequently considered as Eastern Europe (being in fact Central Europe), I can say that we very often use this format in handwriting, but I have never seen it in any application...

  5. 1. Install any number of useful tools in one go: right click framework, quick drop short cuts

    2. Add useful OpenG tools

    3. Update the configuration file to set settings different from the defaults that LV offers

    4. Change the default custom probes

    5. Fix bugs that the community has prioritized

    + customized splashscreen :)

    (I still use 2009 through choice).

    How good I'm not alone...

    2. Isn't most of what you are proposing exactly what the JKI thingy is for? (and I still argue that NI should have their own)

    Maybe JKI should think of something like meta-package? As collection (but not physical) of packages to be installed together. A set of customized collections for different needs (possibly with auto choosing newer versions of updated packages) would be much easier to create and maintain than "one big patch".

  • Create New...

Important Information

By using this site, you agree to our Terms of Use.