このマスタークラスは、H18での Vellum クロスシミュレーションの改善点、解像度非依存性や新しいコンストレインを紹介します。

コメント

  • BabaJ 4 年, 11 ヶ月 前  | 

    Cool..thanks for this. I like how you make use of other nodes - I don't know why I 'missed' knowing about the point velocity node but glad I found out about this - saves writting out a few lines of vex.

  • jennyfong 4 年, 10 ヶ月 前  | 

    Thanks Jeff! These are exactly what we wanted!

  • aneta_cevelova 3 年, 10 ヶ月 前  | 

    hello Jeff, what does "gold release" means please?

  • jlait 3 年, 10 ヶ月 前  | 

    Without a timecode, I'm not sure if it was something else I said unintelligibly that just sounds like "gold release".

    But if I said gold release, I probably was referring to https://en.wikipedia.org/wiki/Software_release_life_cycle

    Back when we distributed physical media to release software; you'd have to make the version that would be sent to whoever was mass producing the media. In the case of CD duplication, this would be the "gold master". Now that we release our software on daily process, the "gold release" is the version released to the world of that version number.

    One thing that hasn't changed since the physical days is that the Gold Release will miss a lot of features/bug fixes that may be in the first daily build. However, this is not because we had to lock down a version for a CD printing plant. Instead, it is because any bug fix, no matter how simple, may itself create a new and worse bug. So we have a separate branch that will become the Gold Release where we only apply the most critical bug fixes.

    Since we don't expect people to use daily builds in production; we also have a cadence of "Production Builds", which are daily builds we've deemed suitably stable. (Every daily build is *SUPPOSED* to be better than the previous. But again, if we knew the full consequences of each bug fix; we'd not have bugs in the first place :>)

Please log in to leave a comment.