Hello there. I just recently got into Lumberyard, and it seems pretty neat. I like the engine, I like the license, and I like the overall idea. I can look past the necessity to use command line tools and the bugs, Lumberyard is in beta, after all (and honestly I like command line)
What I really don’t understand is why it is necessary to completely rebuild an entire project every time I want to add a Gem, or why it takes about 2 hours for me to just build a new project.
I understand that Gems are meant to make the engine modular, and I really like the idea behind them. However, it currently feels very counter-intuitive to me to use them. I feel like I could save more time by just enabling all the Gems and building the project once, then when I approach release just remove any Gems I never used and rebuild.
I really want to know why it takes so long to even just start a new project. It took me more than an hour to build a new “Default” template project.
Besides those two issues, I really like the way this engine is going, and I think in a few years it could be the next big thing, and really pay off with its integrated cloud services. I just think that an engine that seems to be heavily marketed towards indie devs should be a bit more friendly to people who don’t have things like IncrediBuild to accelerate their build-times.