Це відео не доступне.
Перепрошуємо.

Onshape's new Repair manager - "What's broken can (now) be fixed"

Поділитися
Вставка
  • Опубліковано 5 лип 2024
  • A really quick one (for a change) - I was in the process of doing something else and came across a really simple but nice usage for the new Repair manager - something we introduced in Onshape's 1.183 release June 28, 2024.
    The two-viewport visualization along with nice highlighting and synched view manipulation is very handy indeed. And since Onshape is... well... Onshape, it means that you can compare your broken part studio to any history entry that ever existed. From yesterday's session, from when you were working on a different computer, before that unexpected power outage... and so on. Unprecedented power - let's take a quick look!

КОМЕНТАРІ • 6

  • @5Lax
    @5Lax Місяць тому +1

    Great stuff. I've played the rebuild game many times, so I know how much time this can save in a model.

  • @jonathanhutchinson5649
    @jonathanhutchinson5649 Місяць тому

    I didn’t quite understand this feature the first time seeing it. But what it looks like is whilst you’re in this repair manager state, changing the ‘broken thing’ changes the downstream appearances of that thing to what you replaced it with?

    • @servicestechniquesericgauthier
      @servicestechniquesericgauthier Місяць тому

      In fact, it lets you compare the actual broken state with the previous unbroken state so you can quickly see and fix the problems.

    • @gregbrown-onshape7555
      @gregbrown-onshape7555  26 днів тому +1

      Indeed - and as mentioned in other replies the fact you can compare to any state that has ever existed makes it very powerful.

  • @harryhaberle5672
    @harryhaberle5672 27 днів тому

    does this only work if we save manual some versions?

    • @gregbrown-onshape7555
      @gregbrown-onshape7555  27 днів тому +2

      In fact it works on all history states that are automatically created every time you do anything. This is the superpower of Onshape, you don't need to explicitly "save" anything. All of the actions you take, edits to a dimension, hiding of an instance, etc etc are transactions to the database. We keep them all.