Geometry Cache vs. Content Cache - Grasshopper 1 - Rhino 8 - Components compared - Caching explained

Поделиться
HTML-код
  • Опубликовано: 21 окт 2024
  • Comparing Geometry Cache with Content Cache - what has changed?
    Pt. 2 to the Content Cache video. For some reason the quality of the recording was scuffed, my apologies for that, try to bear.
    Disclaimer
    The information provided in this video is for general informational purposes only.
    L*-channel and its creators do not provide any warranty or guarantee as to the accuracy, timeliness, completeness, or suitability of the information and content contained in this video. It is based on our personal experiences, research, and opinions. It is not intended to be professional advice. Always seek the advice of a qualified professional or expert in the relevant field before making any decisions or taking any actions based on the information provided in this video.
    L*-channel and its creators are not responsible for any direct or indirect losses, damages, or harm that may result from the use of or reliance on the information and content contained in this video.
    Rhinoceros® and Grasshopper® are property of Robert McNeel & Associates. This video is intended for educational purposes regarding the applications. No rights to the programs are claimed by the L*-channel or its creators. L*-channel has no financial connections to Robert McNeel & Associates.
    www.rhino3d.com/
    Some of the links in this video's description may be affiliate links. If you make a purchase through these links, L*-channel may receive a small commission. This helps support the channel and allows us to continue creating content. We only recommend products and services that we personally use and believe in.
    By watching this video, you agree to the terms and conditions outlined in this disclaimer.
    #rhino
    #rhino3d
    #grasshopper
    #grasshopper3d
    #computationaldesign

Комментарии • 1

  • @inomanoms9988
    @inomanoms9988 3 месяца назад +2

    Thank you very much for taking the time to do this for me! I, in the meantime, had researched the two components in order to understand them better, and yes, it would seem that the geometry cache is the predecessor of the content cache, thrown together in about a day by David Rutten some 13 years ago. It now languishes in the geometry panel as a broken legacy component.
    The promise of what the content cache can do is large, but intimidating and convoluted. I sincerely feel as though the developers need to rethink how they plan to address the interopability and means by which geometry travels between Rhino and Grasshopper.