Don't have an account yet? Then register once and completely free of charge and use our wide range of topics, features and great options. As a registered member on our site, you can use all functions to actively participate in community life. Write posts, open topics, upload your pictures, put your videos online, talk to other members and help us to constantly improve our project and grow together! So, what are you waiting for? Become a part of us today!
To get support for a technical issue such as installing the software, to query a purchase that you've made/would like to make, or anything other than using our software, please visit our Customer Service Desk:
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!
Sorry guys, I've been traveling towards the Click Convention all day, didn't have any time to fix this until now. Can you check again? It should work now.
I'll be having a presentation about Anaconda at about 11:00 tomorrow, so make sure to tune in
One question: is the Anaconda Shaders example working for others? I'm not getting the error messages previous posters saw, so I think that issue is fixed. But there is no change to the main Active graphic when I click any of the "Apply shaders" buttons, either when I run the example within MMF or when run from an Anaconda application build. I've tried both Direct3D 9 and Direct3D 8 display modes. Curious if there's some setting I need to change besides setting the display to a Direct3D mode and the build type to Anaconda to make it work.
(I'm running R252 and MMF's built-in HWA shader effects work if I run in normal 'Stand-Alone Application' mode, so normal HWA shaders are working on my setup.)
jjsonick: You need to place the shaders in the data directory, I guess.
Hi Mathias. AnacondaShaders.json and AnacondaShaders.png (as well as Anaconda.bld) are already in my Data/Runtime directory from my initially installing the Anaconda files. I just now copied TestShader.frag, TestShader.vert and TestShader2.frag into Data/Runtime as well to see if that made a difference, but there's still no change to the graphic when I run the example and click on the buttons.
All the Anaconda files are installed in their respective directories within my root MMF2 directory. I am able to build, for example, an Anaconda OS X app that runs on my Mac. It's only the shaders that don't seem to be working.
Nivram, OK I put all related files - AnacondaShaders.json, AnacondaShaders.png, TestShader.frag, TestShader.vert, TestShader2.frag, and AnacondaShaders.mfx all in the MMF2 root (though I'm puzzled why one would want to this - do extensions placed in the root directory override extensions placed in the usual directories?).
Still no shader effect applied when the example is run.
Did you mean only a subset of those files should be put in the root? And should the ones in their usual locations (Extensions and Data/Runtime) be deleted?
No, not the mfx's. I think this has turned into a circus and probably my fault. Only the files you were speaking about. Maybe the author should look at what is happening and give his guidance, if he is not too busy.