# Prime tower issues

**URL:** <https://forum.snapmaker.com/t/prime-tower-issues/39392>\
**Category:** Snapmaker Orca\
**Created:** [May 9, 2025, 5:44pm UTC](https://forum.snapmaker.com/t/prime-tower-issues/39392 "2025-05-09T17:44:30Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![knutsoned](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.snapmaker.com/knutsoned/32/28970_2.png) [@knutsoned](https://forum.snapmaker.com/u/knutsoned)\
**Post date:** [May 9, 2025, 5:44pm UTC](https://forum.snapmaker.com/t/prime-tower-issues/39392/1 "2025-05-09T17:44:30Z")

</div>

I have done some experimenting with 1.2.1 and it looks like Orca is causing the toolhead to return to the X=0, Y=0 position even though a prime tower is used. This is causing the separation of objects from the print sheet. Here is a screenshot. Note the position of the prime tower behind the object.

 ![Orca window showing travel to 0,0 position](https://us1.discourse-cdn.com/flex022/uploads/snapmaker/original/3X/d/8/d80a6090542ffeaad38eb3879f405b3a80a5e739.jpeg)

The prime tower feature in general seems like a source of at least two other issues:

1. Sometimes the second material is generated with an increasing -Y offset, so that successive layers are generated closer and closer to the front of the print sheet, and cause a G-code out of bounds error. This requires toggling the prime tower off, slicing, turning it on again, and slicing again. Sometimes this process must be repeated.
2. Orca often crashes while slicing a print with a prime tower enabled.