[quote="Arima":1tu7odff]Honestly, if you're going to do anything 3D, even if its 2.5D, you should probably use something else. Construct's 3D is quite limited. It doesn't even have basic lighting. While technically you could make your own 3D engine with events, it's overly complex and wouldn't run as fast as other options like unity would.
You seem to sound a bit comforted by what we said, and maybe in particular from what I said. Maybe a bit too comforted. I don't mean to leave you with the impression that what I mentioned is the only issue I face with my game - it's simply the only one I haven't managed to find some way to work around. Some of them are easy to avoid, like the or condition which causes crashes, or the layout object which among other things doesn't register left clicks. Some of them are a lot weirder, like I have an old event that crashes the IDE if I try to move it in the event sheet (though I can deactivate it) and a layout I can't use without my game going haywire - easy enough to work around by making another layout and not using the bugged one, but seriously distressing until I figured out how to work around it. One of my event sheets with 5000 events takes 10 minutes to open due to some weirdness (though I have an old processor, which certainly contributes, but it shouldn't take that long regardless as a newer event sheet with 1000 events only takes a few seconds to load).
Then again, I also started this project 2 1/2 years ago, so a lot of the bugs that I face have already been fixed.
I feel somewhat nervous about what I said before actually, because it seems it's kind of hard to predict what quirks might arise for a user, and I really don't want anyone to risk financial ruin based upon my experience alone, because there is one user I know who has encountered a showstopper, though he's the only person I know of who has encountered that particular problem. Because of that, and how unpredictable construct's quirks can be, I don't feel comfortable recommending anyone risk their financial future on the chance they might encounter something they can't work around. Perhaps I'm being overly cautious, but I really, REALLY don't want you to encounter something that forces you to scrap your project and lose a lot of money, especially from my advice.
What I'm trying to say is, can you? Most likely. Will you encounter quirks that you can work around? Almost undoubtedly. Will you encounter a showstopper? Probably not.
But risking a business on a probably not probably isn't the best idea.
Again, I feel much more comfortable recommending you wait for construct 2 instead. It's far, far more stable than construct classic was at this point in its development, therefore there's much, much less risk of quirky weirdness, and it'll also help you in the long run for porting to different platforms. It's a much better business decision.[/quote:1tu7odff]
Thanks mate, I really apreciate your concern. No worries, I am getting a general view that is more or less suitable and with separate tests and getting everything working before adding into the main build, you could get an stable game.
I'd wish to wait to Construct 2, but we are ready to go. Perhaps we could build a prototype using Classic and jump into Constrct 2 once it's done. Game assets will be re-usable, so, in the worst case, only we would lose time on coding.
Thanks everyone else for the comments, I'll take into consideration all of them