Posts by lh37

Just a quick note that clickwiki.net will redirect to Please login to see this link. until 2023.

If you've got it bookmarked, it might be worth updating to avoid Please login to see this link.... though, it'll be at least 3-4 more years until that happens.

Mods, it might be worth updating the link on the forum's homepage sidebar.

Thanks!

Edit: The project has been archived and is closed for contributions. Consider it a place to preserve nostalgia for Clickteam's older products. Thanks to everyone who contributed in the past!

I haven't tested, but from memory the "My Documents" expression will still work in newer versions of Windows. The path won't be hardcoded, the help file is more like a guide to check you're saving to the intended folder.

At an OS level, there is compatibility in Windows Vista and later to map "C:\Documents and Settings\username\My Documents" to "C:\Users\username\Documents" (or equivalent) should the extension attempt to use a legacy path.

Please login to see this link. - it's even got a new dark theme -- simply click the moon at the bottom.

Not all pages were migrated in time, so a static copy is available at Please login to see this link.. If anyone's willing to help Please login to see this link., that would be appreciated!

Ohh, I didn't realise James had left, I was aware he was the "Linux" guy of Fusion 3 (who's the Linux guy now?). François left a couple of years ago I think, there was a time I noticed the red name text go back to blue. I wish them both well.

I too had wondered in the past what "VP Special Projects" could be, but I'm guessing with the stuff Danny's been involved with, this might be projects like Please login to see this link., Please login to see this link. and Please login to see this link..

If the community wants to document the masterminds behind Clickteam, there is Please login to see this link. and the Please login to see this link. on ClickWiki... but it's a bit outdated now.

Hello Clickers,

Host of Please login to see this link. here - there's a major update heading towards ClickWiki over the next week or two!

Since it's launch in 2015, we've been using MediaWiki to document Clickteam products, features and extensions. It's hosting is now running out and it's time for renewal.... or is it...?

A light bulb blinked at the start of this year that we could spice up this project, particularly as I work as a front-end web developer as my day job.

ClickWiki is now turning into a static site, powered by Please login to see this link. and Please login to see this link.. This offers a number of advantages:

• It's static, there's no database. (No waiting, no hacking, nothing to corrupt)
• GDPR is coming up -- a new data protection law in the EU. ClickWiki will no longer be storing any personal data, such as user logins to edit the wiki.
• It's open source -- you can edit practically anything.
• Our MediaWiki instance were prone to cache issues and the random "internal errors".
• Going serverless reduces costs.
• Offers flexibility -- the wiki is now portable.
• If you don't know Git (version control) already, this is a great opportunity to learn!
• If need be, you could have a copy on your computer for offline use.

What's changing?

• We will use GitHub Issues to track missing content and website problems.
• The syntax is now Markdown.
• Instead of logging in, you propose changes by forking the repository, committing changes and creating pull requests.

If you've previously contributed, thank you! Please note we will credit you from the original copies.

Sneak Peak

You can have an early look at new version at Please login to see this link.. The current Wiki remains at Please login to see this link. as usual. Once the new one goes live, old (current) URLs will be redirected.

The project is over Please login to see this link.. The new version will go live no later then Sunday 20th May. Stay tuned!

Please do consider an RSS feed for the new blog, as that's where I follow Clickteam stuff these days. Please login to see this link., but I'm not entirely sure where that leads...

Although personally, I'm mostly interested in product and team updates, which has been great with the Fusion 3 blog.

Quote

Each application cannot contain more than 3 frames.
Each frame cannot contain more than 100 backdrop objects and 30 other objects.
Each frame cannot contain more than 150 events.

See here:

Limitations of the free version - Please login to see this link.
Limitations of the free HTML5 exporter (and the objects) - Please login to see this link.

Just to clarify, is the update being installed to the same wine prefix ("bottle")? Another solution is to open explorer from Fusion and navigate to the installer program that way.

Another alternate program is WineSkin.

I'd like to bring back up dsilvers' suggestion of going towards an open source route for part (or all) of the Fusion 2.5. I agree that this is only effective if "coders" of the community are willing to help out of love, but could introduce problems when it comes to sharing copyright and the licence.

There's also having trust that the source won't be used to help the pirates get it for free or reverse engineer creations.

Possible negates aside, it means we check out the latest commits to get an idea what's being improved as it happens. Equally, it could be an incentive for a developer to prove themselves that they should be hired by Clickteam to work full time. If so many help a little, a lot can be achieved in a short space of time.

So, you could say there is a possible plan B. Unity and Unreal Engine are examples of being open to the code.

If pledging or open sourcing means there's enough developers accelerate development for both products, I'm all for it!

True, binding 1:1 of events would probably be tricky, and lead to a lot of incompatible extensions. Graphics, sounds and data elements should be a priority.

As an idea, a "ghost" of the old Fusion 2.5 events could appear alongside Fusion 3's Event Editor, the ghost objects and checkmarks remain until the user finds the new event to take over it's spot... kind of like visually porting from one to the other, but contains no legacy code.

I agree with Paul_Boland's points. It's not about creating a new product that is backwards compatible, just a tool (either integrated or stand alone) that extracts F2.5 assets and events as much as they can so that they can be quickly added to the new product's format.

Saves a lot of time for the user then going through each animation and data element to extract internal data baked into the MFA.

Quote from Paul_Boland

It was said the release details would be known soon. But then it was also said that Fusion 3 is in very early development. Those two phrases are in conflict with each other. I must admit, I was under the impression that Fusion 3 was a lot further along in development than it actually is.

I thought this too, from the "released next year" statement I thought Fusion 3 was well on its way to entering the alpha phase.

OpenShot is a very nice open source tool, but 1.x is very old and only on Linux right now. 2.0 will work on Windows, Mac and Linux -- it's near completion but it's not even released yet.
Please login to see this link.

This could be one tool to keep an eye out for...

The primary disadvantage to the Standard display mode is the fact your entire Fusion application (events, graphics) is driven by the CPU, so animations and large effects may cause the frame to stutter (for instance, rotating a large object can crawl 60 fps to 45 fps).

If you can achieve smooth performance out of it, then things might be OK, but do test the game on lower-end CPUs / slower machines.

You could support both (Hardware Rendering - Direct3D / Software Rendering) and give the user an option: Pass the Please login to see this link. to your Fusion program to force Standard mode.

Some data retrieved for Stats are no longer available in the latest stable version of MediaWiki - in particular, Top 10 Pages and Total Views count. Stats were meant to nicely present the data that were scraped (very unreliable!) from Please login to see this link. (and some other places) but since they're no longer listed, it's all fallen into the need of repair. Unfortunately I've been busy with other projects to patch this up.

At the moment, I'm thinking of re-designing Stats entirely and focus on improving the Wiki's appearance (when I put time to dedicate towards ClickWiki) - I think tabs, collapsible content and carousels would really enhance the content, like your guides So, there may be a new look on the cards for the new year.

So, Stats right now is in a bit of a mess, but other data is still fetching under the hood. I've migrated the "Check Up" section to Please login to see this link. - so anyone can update situations with exporters.

And if the message stays unconfirmed for a long time... the recipient probably never looked at it.

It's been fixed in the beta of 285.1, which hasn't yet been pushed as an official build yet.

Official and Beta builds can be found in the "Download Links" post:
Please login to see this link.

Why Fusion sometimes uses 400 MB and others times 1760 MB ... I'm not sure, but it could possibly be a memory leak? You could check if your final application is affected by using the Task Manager to check the memory usage.

Crashing only starts to occur when Fusion starts hitting the 32-bit program memory limit, which is 2 GB (2000 MB). The debugger will also be using additional memory and CPU too.

There are a lot of threads that discuss ways to optimise your application and stay safe from hitting that dead limit:
Please login to see this link.
Please login to see this link.
Please login to see this link.

The display mode (Standard / Direct3D) may also be a factor, and the size of your textures if they are not within the power of 2.

It's been nearly 9 months since the birth of our brand new Wiki. Would you say we achieving our objectives? Are we building a useful asset? Has our content helped you in any way?

Please, do take a minute to fill out the feedback survey:
=> Please login to see this link.

Your answers are anonymous, will not be published and helps shape the Wiki in the right direction.

Thank you for supporting our Wiki.

Thanks Simon. I actually forgot about the bug tracker, I could have reported it there.

It's not behaved like this last month (or before?), so it could be due to new versions of Chrome?

Here's a quick video demonstrating it:
Please login to see this link.