Keep in mind that developers need to work with files outside of Unity

Unity Services
,
1

First off I want to say that I’m very happy with the work being put into Plastic SCM and I’m looking forward to a great Unity integration. But I’d also like to stress that the workflow of using Gluon + Plastic SCM GUI was the original reason why my team decided to go with Plastic. The new Unity integration plugin advertises that it will be designed for all disciplines in mind. To me, this sounds near impossible as the needs of tech vs art people differ so greatly. At my studio, artists and designers work with Gluon, while programmers use branches in the full GUI. This separation works very well for us, but both have in common that we need to work with files outside of the Unity project in the same repository. For example, folders for external build tools or art source files that are not imported into Unity. We also regularly edit and checkin files without having Unity open.

So, just wanted to voice my opinion that Gluon and Plastic GUI will still be needed albeit the Unity plugin. I hope your market research doesn’t tell a different story. :smile:

1 Like
2

Hi @Xarbrough_1 ,

Thank you for taking the time to provide us with this feedback! While we have been heavily focused on Unity integration for Plastic, I can assure you we are also committed to the improvement of our client experiences and are working diligently on improvements that we expect to release iteratively over the next year. Making Plastic a great experience for all creators, regardless of the engine or tools you are using, is a key objective for our team.

We would love to hear more! If you are interested to share your experience in more details with us and/or participate in studies related to Plastic SCM, please sign up here! :slight_smile:

1 Like