I broke it.
Not sure how.
But the client is most certainly, broken.
Just after getting things all piped up properly I broke the UI somehow when refactoring the button layout and somehow reduced the FPS to 2-8 or so. Yup.
Put simply. We might just be in too deep for a two man team with our time constraints. The only way I can figure to lower the water level in the boat is to cut back on graphics as we aren't willing to sacrifice functionality or playability. Additionally, it is fairly straight forward for us to add more dimensionality to the graphics because the overall logic will always remain 2.5D.
Zach and I will spend this next week tearing down all of our expectations and building a new super clean SAP model/design. Granted, it feels like this will be a process of upheaval and chaos but it is really just the next step in creating a slick, maintainable end-product.
With our connection success we have proved that our framework does work. The excitement of having a communicating framework has sparked debate about simplifying the client in order to speed up the iteration process. We are actually both in agreement about the fact that simplification needs to be done (yet again), and are currently just debating which of the graphical components must make it into the SAP.
It seems we forgot to weight graphic workload as heavily as we should have. I believe it was partly do to the artist in me not wanting to sacrifice all the pretty polygons.
Once we find the minimum balance between iconographic communication and speed of iteration we will be unstoppable.
Here's to a great quarter.
Thanks for reading,
Clay Francisco
No comments:
Post a Comment