# New version: 2.0.3

**URL:** <https://discourse.shapr3d.com/t/new-version-2-0-3/639>\
**Category:** Release notes\
**Created:** [December 19, 2016, 8:16pm UTC](https://discourse.shapr3d.com/t/new-version-2-0-3/639 "2016-12-19T20:16:58Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![Istvan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.shapr3d.com/istvan/32/23668_2.png) [@Istvan](https://discourse.shapr3d.com/u/Istvan)\
**Post date:** [December 19, 2016, 8:16pm UTC](https://discourse.shapr3d.com/t/new-version-2-0-3/639/1 "2016-12-19T20:16:58Z")

</div>

This release contains lots of bugfixes, and new version of the geometry kernel (OpenCASCADE). For you this means that many operations are much more robust now, especially the shell tool now works like a charm even for really complex objects. Also, boolean operations have been vastly improved, and performance and reliability in general.

The next version (2.0.4) is already on it’s way to the App Store, with even more bugfixes 🙂

---

<div class="post-metadata">

**Author:** ![PhotoWorkPlace](https://avatars.discourse-cdn.com/v4/letter/p/278dde/32.png) [@PhotoWorkPlace](https://discourse.shapr3d.com/u/PhotoWorkPlace)\
**Post date:** [December 20, 2016, 6:42am UTC](https://discourse.shapr3d.com/t/new-version-2-0-3/639/2 "2016-12-20T06:42:52Z")

</div>

Can’t thank you enough  
Hard to explain how much we have come to depend on Shapr  
When it’s not working well everything kind of grinds to a halt! 🙂

---

<div class="post-metadata">

**Author:** ![Istvan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.shapr3d.com/istvan/32/23668_2.png) [@Istvan](https://discourse.shapr3d.com/u/Istvan)\
**Post date:** [December 20, 2016, 7:49am UTC](https://discourse.shapr3d.com/t/new-version-2-0-3/639/3 "2016-12-20T07:49:23Z")

</div>

Sorry for the inconvenience, that was a big step forward, and big steps unevitably come with some problems, but we are working really hard to fix all the issues ASAP. The app store review process does not help however to deploy the fixes quickly ☹

---

<div class="post-metadata">

**Author:** ![PhotoWorkPlace](https://avatars.discourse-cdn.com/v4/letter/p/278dde/32.png) [@PhotoWorkPlace](https://discourse.shapr3d.com/u/PhotoWorkPlace)\
**Post date:** [December 20, 2016, 4:24pm UTC](https://discourse.shapr3d.com/t/new-version-2-0-3/639/4 "2016-12-20T16:24:22Z")

</div>

Istvan  
Just getting a chance to check things out quickly  
The legacy lines left when extruding, will those be automatically removed in the next update?  
When trying to delete them manually the whole object is deleted  
And again it just makes for a busy looking model when there are random lines all over the place  
Joseph

---

<div class="post-metadata">

**Author:** ![Istvan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.shapr3d.com/istvan/32/23668_2.png) [@Istvan](https://discourse.shapr3d.com/u/Istvan)\
**Post date:** [December 20, 2016, 4:30pm UTC](https://discourse.shapr3d.com/t/new-version-2-0-3/639/5 "2016-12-20T16:30:47Z")

</div>

> [@PhotoWorkPlace](#):
>
> Just getting a chance to check things out quicklyThe legacy lines left when extruding, will those be automatically removed in the next update?When trying to delete them manually the whole object is deletedAnd again it just makes for a busy looking model when there are random lines all over the placeJoseph

Can you send me the problematic workspace please?

---

<div class="post-metadata">

**Author:** ![Istvan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.shapr3d.com/istvan/32/23668_2.png) [@Istvan](https://discourse.shapr3d.com/u/Istvan)\
**Post date:** [December 20, 2016, 4:31pm UTC](https://discourse.shapr3d.com/t/new-version-2-0-3/639/6 "2016-12-20T16:31:38Z")

</div>

Oh, you mean after extruding a face of the existing shape, right? No that will take some time to fix, few days maybe.

---

<div class="post-metadata">

**Author:** ![PhotoWorkPlace](https://avatars.discourse-cdn.com/v4/letter/p/278dde/32.png) [@PhotoWorkPlace](https://discourse.shapr3d.com/u/PhotoWorkPlace)\
**Post date:** [December 20, 2016, 4:43pm UTC](https://discourse.shapr3d.com/t/new-version-2-0-3/639/7 "2016-12-20T16:43:01Z")

</div>

Yes that is the issue  
No rush, just wanted to know if it was a design feature that was escaping us! 🙂

---

<div class="post-metadata">

**Author:** ![PhotoWorkPlace](https://avatars.discourse-cdn.com/v4/letter/p/278dde/32.png) [@PhotoWorkPlace](https://discourse.shapr3d.com/u/PhotoWorkPlace)\
**Post date:** [December 20, 2016, 4:44pm UTC](https://discourse.shapr3d.com/t/new-version-2-0-3/639/8 "2016-12-20T16:44:33Z")

</div>

Once fixed is there any chance that the fix will remove the line from previous objects, or can they manually be deleted, or would we have to start from scratch?

---

<div class="post-metadata">

**Author:** ![Istvan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.shapr3d.com/istvan/32/23668_2.png) [@Istvan](https://discourse.shapr3d.com/u/Istvan)\
**Post date:** [December 20, 2016, 4:46pm UTC](https://discourse.shapr3d.com/t/new-version-2-0-3/639/9 "2016-12-20T16:46:02Z")

</div>

We have some very exciting things in the pipeline for that 🙂 Maybe you will be able to do even more 😉

---

<div class="post-metadata">

**Author:** ![PhotoWorkPlace](https://avatars.discourse-cdn.com/v4/letter/p/278dde/32.png) [@PhotoWorkPlace](https://discourse.shapr3d.com/u/PhotoWorkPlace)\
**Post date:** [December 20, 2016, 4:54pm UTC](https://discourse.shapr3d.com/t/new-version-2-0-3/639/10 "2016-12-20T16:54:36Z")

</div>

More is always fun! 🙂

---

<div class="post-metadata">

**Author:** ![Victor\_Shapr3D](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.shapr3d.com/victor_shapr3d/32/3502_2.png) [@Victor\_Shapr3D](https://discourse.shapr3d.com/u/Victor_Shapr3D)\
**Post date:** [September 20, 2019, 2:53pm UTC](https://discourse.shapr3d.com/t/new-version-2-0-3/639/11 "2019-09-20T14:53:42Z")

</div>