Fusion3 Blog - Frame Editor Improvements (Patreon)
Downloads
Some files exceed the archive size limit and weren't saved: 1 file. Please note these limits are in place to keep this site running long term, without costing a fortune. You can favorite the creator though, certain milestones increase the limit.
Content
Frame Editor Improvements
Since Linky joined the team, he’s been hard at work adding new features and improvements to F3’s frame editor. He’s added rulers, improved object snapping and rotations, and implemented the ability to click and drag grid lines to quickly adjust the grid size, among many other tweaks.
In the case of grid controls, They now have a convenient popover that can be quickly adjusted any time. Previously the only way to edit the grid was by manually typing in the values you want, but now Linky has added the ability to click and drag the grid in the frame editor while the popover is open. Currently, dragging adjusts the grid in increments of 8 units; you can always type in more specific values by hand.
Improved Frame Object List
In the frame editor, you normally have a tool panel docked to the left side that shows all the objects in the frame, giving you a convenient spot to drag in new instances from. Clicking an object in that list selects all instances on visible layers. In F2.5, that’s the extent of the functionality. In F3, we’ve converted it into a tree view where you can expand each object to show a list of coordinates and layer names for each and every instance of that object in the frame. Checkboxes allow selecting and deselecting specific instances, so you can easily select objects on specific layers only without having to hide other layers. The design is still in flux, we plan to condense the information display so it can fit in narrower widths and still be useful.
While specific instances are selected, you’ll be able to customize properties for them. You can think of this as an expansion of the instance value system that was added in F2.5. In F2.5, you can add alterable values/string/flags to objects, but each instance can only customize the instance value. In F3, each instance can customize any of the values/strings/flags. For example, you can have a Flower object with various instances placed around an environment, and each instance can have a different color value set, allowing you to create flower color patterns in the frame editor without needing separate workarounds. You will of course be able to revert an instance to using the default property value for the object type, so when you change the default value in the object properties, all instances using the default will be changed too.
Instance Overview Panel
In addition to the aforementioned improvements to the frame object list, we’re also making a dedicated tool panel to show a spreadsheet-style view of all the object instances in the current frame, with columns for position, layer, and other properties set on each instance. This will serve as a convenient way to see which object instances have custom initial values set for their object properties, and to edit all the values too. The columns in the instance overview panel will be determined by which properties have been customized for instances. To add a new column, just customize a new property on any instance, then you can compare it with all other instances to see if you need to customize it on others as well.
The instance overview panel will dock to the bottom of the frame editor by default, and the design is currently WIP. If you have ideas about design or features related to this, let us know!
GUI Progress
We acknowledge that the GUI theming and in Fusion 3 may not be the hottest as of now. Please note that it's all WIP and does not represent the final product. There is a lot of room for improvements, but we are currently focusing on making the actual engine work well - getting the infrastructure stable, flexible, and most importantly: done. Visuals and aesthetics will improve over time.
We are continuously adding new features to the editor, with plans to later improve the theming. Since Fusion 3 isn't an electron web-wrapper and is not using any 3rd party UI libraries like ImGui, we have to implement all GUI functionality ourselves. This allows us to guarantee consistent support on all platforms including game consoles, with a focus on being fast, flexible, and full of theming possibilities and options to play around with. Your apps and games will be able to use the GUI functionality we’re creating as well, via nucleus.
Nucleus is the base runtime library used by both the Fusion 3 IDE (spark), and your own apps and games that you create in Fusion 3. The GUI components we’re creating can be used in your own apps since they’re part of the default library of Fusion Objects you can add into your projects. Custom GUI is a big task, but we’ve made significant progress so far. Most of it is already mostly done and is just getting tweaks and additional features and themes now, such as optionally using native platform UI where available.
The GUI library within nucleus is so flexible that most controls support zooming by default (e.g. Ctrl + Mouse Wheel), but many platform native UIs don’t support all the same features, so we’re prioritizing making our own versions the best they can be. Accessibility hooks are a tricky area that is still WIP, for example.
Make to subscribe here and on Youtube so that you can see the latest information on Fusion3. We look forward to showing you more Frame Editor improvements in the near future!
Personal note from new Fusion3 programmer Linky
Hey, I'm Linky! I joined Clickteam about a month ago to work on Fusion3, and a bit on Fusion 2.5 when there's some spare time, though my main focus is definitely pushing Fusion3 forward!
Some of you might know me from the community - maybe through MFAs, tools, or extensions like TMO and DeltaX. I really love Fusion and what it stands for as a visual scripting-first engine. The Event System, Properties, and all that.
One of our top goals with Fusion3 is to keep the original Fusion spirit alive: user-friendly design, visual scripting, and visual editors. Events are Fusion's heart and soul-without them, what's the point? But we're not limiting ourselves either. Fusion3's Events got huge upgrades: they're native, compiled to machine code, running as fast as C++. Plus, more data types, custom actions/conditions/expressions/properties, better expressions, and improved object selection. This makes them both powerful and easy to use.
People often ask what Fusion's programming language is and why it seems like there isn't one. The answer is simple: Fusion's language is Events. And hopefully, you won't ever feel limited by Events in Fusion3. We're adding even more visual editors than before. For example, in MMF2 and Fusion 2.5, you had to write shaders manually in HLSL, often multiple times for different platforms and languages. In Fusion3, that's changed with our new visual shader editor introduced earlier - you just create it once, fully visually, and it works everywhere.
The big picture for Fusion3 is: stable, fast, powerful, cross-platform, and most importantly, visual.
In just the last month, we've made a lot of progress both visually and under the hood. That doesn't even include all the planning and design talks we've had about F3. Not all changes are visible, but they're crucial for making the engine run smoothly, including the visual parts. Think of it like the gears inside a clock that keep it ticking.
For example, my lead Nicholas (LB), who's a C++ and system design pro, worked on a new AJT system (Abstract JSON Tree). This is basically the main source of truth for data, which drives things like the editor's UI and what data it shows and edits! We also fixed some tricky bugs, like icons not rendering properly in some cases. These fixes might go unnoticed but are super important and take a lot of effort.Nicholas and I are working hard every day to move Fusion3 forward, and we'll do our best to keep you updated. I'm really excited to be where I am right now, and I hope we build something great that truly lives up to the Fusion name.