Bonfire v1.18.4
Released on 2/4/25
Last updated
Was this helpful?
Released on 2/4/25
Last updated
Was this helpful?
We replaced the need for Cause/Effect connections by adding a new Trait to DatumViewer Sparks, allowing users to directly select the Datum they want to view, update, set, add, and subtract successfully without requiring the Update node behavior. The previous Cause/Effect method is now deprecated, streamlining DatumViewer functionality. This simplifies the workflow and eliminates unnecessary node connections.
Below is a screenshot of DatumViewer's Trait, which includes a dropdown to specify which Datum it’s linked to. The DatumViewer will then display the CurrentValue of the selected Datum.
We implemented a way to access Spark metadata within Bonfire Builder. Previously, only the Spark name was visible, limiting access to important details. Now, when hovering over a Spark in the Spark Browser, a tooltip displays its full name, type, and GUID, providing essential metadata for better organization and reference.
We implemented support for using keyboard arrow keys to make precise micro-movements of symbols on a UI Panel. This functionality aligns with standard layout software behavior, allowing for more controlled and accurate positioning. Testing confirmed that symbols can now be adjusted using arrow keys as expected.
We introduced a unified login system that allows users to log in once through the Launcher, with authentication seamlessly passed to both Builder and Player. Auth token arguments have been added to ensure a smooth transition between applications without requiring multiple logins. Apps still require login when started independently from the Launcher, maintaining security while streamlining access.
We made an improvement to localization by refining the web request process. The API no longer requires a publish target when retrieving the list of languages from the localization server. Instead of including “debug” or “release” in the query, the request now fetches the full language list generically. This ensures that the Localization Language Symbol Spark consistently generates buttons for selecting all available languages, improving localization accuracy and reliability.
We adjusted localization handling for Audio Sparks to function at the Spark level rather than the instance level. Unlike Text Sparks, where localization applies per instance, Audio Sparks use a supplemental asset that remains consistent across all instances. This update ensures that localization applies uniformly to the Spark itself, improving consistency and simplifying localization management for audio content.
We enhanced debug messages to include the specific instances that triggered them. Previously, messages only displayed the Spark type (e.g., Audio (EffectAudio) invoked by Button (ButtonSymbol)), making it difficult to identify which instance was responsible. Now, the debug console also shows the instance name of the Spark that triggered the action (like a Button Spark or the instance name of an Audio Spark), making it easier to track interactions and troubleshoot effectively.
We resolved an issue in the Behavior Window of Bonfire Builder where the Comment Node lacked a Delete icon, even when selected. This fix ensures that the Delete icon now appears correctly, allowing users to remove comments from the behavior tree as expected.
We resolved an issue in Bonfire Builder where the Spark Marker Trait for Pen Size allowed excessively large values, leading to oversized drawings. Additionally, drawings from a previous book persisted when creating a new book, disrupting the workflow and causing unintended behavior. This fix enforces appropriate Pen Size limits and ensures that marker drawings are properly cleared when switching books.
We resolved an issue in Bonfire Builder where Sparks stored in symlinked folders, rather than imported directly into the project, would break upon saving and reloading. While these Sparks initially appeared functional in the Map Explorer, they would turn into placeholders and lose functionality after reopening the project. This fix ensures that Sparks not named GUID.dimxs now properly retain their functionality when used with symlinked folders.
We resolved an issue in Ember where creators were unable to properly change the red component of an RGB color when using Ember scripting. This functionality is now restored, allowing full control over RGB color adjustments as expected.
We resolved an issue where searching for nodes in the behavior graph did not consistently highlight subgraphs containing the matching nodes. With this fix, subgraphs now correctly display in search results when they contain the searched term and remain active, allowing users to open them directly. This update ensures that search functionality works as intended, improving navigation and usability.
We resolved an issue in Bonfire Builder where a NullReferenceException (NRE) was thrown upon exiting Play Mode when looping nodes were present. With this fix, the platform now transitions back to Edit Mode smoothly without errors, ensuring stability even when looping nodes exist in the book.
We resolved an issue where RPM avatars were cached locally after the first book launch, preventing updates from being fetched from the remote source. Now, RPM avatars automatically download during initialization and reflect any changes made on the RPM site. This ensures that avatar updates are properly displayed without requiring manual intervention.
We resolved an issue that caused a large error message to appear when starting Bonfire Builder. With this fix, Builder now launches smoothly without unexpected errors, improving stability and user experience.
We resolved an issue where dropping a state machine onto the Symbols tab triggered an incorrect error message stating that symbols should be added to a UI panel. With this fix, the appropriate error message now appears, providing accurate guidance for proper placement.
We resolved an issue where disabling physics on a gripped object in the VR player did not function as expected. Previously, turning off physics manually allowed objects to pass through other entities in Builder, but in VR, objects were knocked out of the player's hands while remaining attached and floating in front of them. This fix ensures that disabling physics properly allows objects to pass through other Sparks or map elements without detaching unexpectedly. Additionally, objects now correctly regain physics when dropped, improving interaction consistency in VR.
We resolved an issue in Bonfire Builder where the Spark Browser search bar failed to locate Sparks stored in the root folder. While Sparks in subfolders were searchable, those in the root folder did not appear in search results. This fix ensures that the search bar now correctly finds Sparks in both the root folder and subfolders, improving discoverability and workflow efficiency.
Additionally, please rebuild the search index whenever a new asset is downloaded so they appear correctly in the Spark Browser's root folder search results.
We resolved a problem where certain books loaded outdated content instead of the latest updates. This issue was caused by a mismatch in how the Launcher handled the release version. By updating the Launcher to use "Release" instead of "RELEASE," books now properly load the most recent content as expected.