Welcome to our brand new Clickteam Community Hub! We hope you will enjoy using the new features, which we will be further expanding in the coming months.

A few features including Passport are unavailable initially whilst we monitor stability of the new platform, we hope to bring these online very soon. Small issues will crop up following the import from our old system, including some message formatting, translation accuracy and other things.

Thank you for your patience whilst we've worked on this and we look forward to more exciting community developments soon!

Clickteam.
  • Found this one, assigning the same pixel shader to an object or class of objects over and over again each frame will slow down the file, presumably due to whatever overhead is used in loading the shader, even if its a redundant assignment- shouldn't the function check if its the same shader the object already has and just skip it? Not a big priority, but can cause some bad slowdown for those unaware of it. The slowdown is pretty huge, as you can see from this example

    This only applies for loading effect files in HWA, not loading the built in ones

    example: Please login to see this attachment.

    For everyone else, just make sure you aren't redundantly assigning shaders, until its fixed. "Once while action loops" or only when an object is created works best

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!