Ali_Akbar
November 27, 2016, 7:00am
1311
Okay, after 2- 3 hours of playing with this we love it. However there are issues that again need to be described. I shouldnt have to spend this much time playing with it to be able to create things. Things we have noticed (might be on your roadmap for dev)
Snap points need to have the ability to limit what snaps to them. This way you can restrict other snap points from connecting to it give you full control of how the level looks. I dont want to two bridges to snap together if they are downwards bridges, but it can happen right now.
We were able to understand how snaps work only when we enabled the option for “remove double doors”. before enabling that it just looked like snap points were disappearing randomly based off of collisions. So we play with the collision option which just made things more confusing. It wasnt till we found that option, enabled it, we could see that it was removing one of the doors. (still unclear as to which one gets removed an how i could control that)
All in all great plugin, but really needs some more documentation so that we can toy with it. I am super hyped and despite having some more important stuff going on today I wanted to do nothing but spending time figuring this thing out. I still dont know how “source” control works with this since I only get crashes when we work within a source control project. However, we did figure out why it was crashing outside of source control options. When you assign a static mesh to the Snap point it crashes on level load. However if you make the static mesh a BP and assign a BP to the Snap point no crashes. Might be a bug… dont know
Hey riuthamus, Snap builder is still a early WIP and will undergo a major changes in the near future. I will be using an alternate method to store modules (instead of having them in separate level files) which causes these issues.