>
> > I thought the issue was 3rd party reliance
> >
> The only remotely practical way to write a set of cross-platform native exporters would be to rely on some kind of existing framework or library, which... relies on third parties. I struggle to see why this is an argument for native exporters.
>
>
> > 80% games are CPU bottlenecked and only 20% are GPU bottlenecked.
> >
> This contradicts what I've seen, and I've done profiling for some of the largest C2 games like Airscape. As ever, I am absolutely keen for anyone with poorly performing .capx files to send them to me (preferably in minimal form like a bug report) so I can optimise anything that needs to be. I repeat this with every thread that ever crops up like this, so I've said it a lot, and I am either sent nothing, sent games which are incredibly inefficiently designed, or games which are GPU-bottlenecked. So even if what you say is true, I'd be very interested to see any examples of that, because I almost never see them myself.
>
Would you be able to write a tutorial, or instructions on how to handle big projects events? That would save you time in the long run, and help others not to make bad events and then complain things are not working well.
That's a fair request. I'm working on a pretty big project and I have my own way of optimizing it but it would be nice to have other practical examples and optimization tricks besides the very broadly applicable guidelines on some of the blog posts.