Description
Deleting fixtures in the patch could lead to shifts of meshes in the 3D viewer.
With Setup enabled in the 3D viewer, tapping Line up in the encoder toolbar did not work as expected so fixtures were not aligned at the base. Instead the fixtures were rotated on all three axes.
With Setup enabled in the 3D viewer, tapping Directions in the encoder toolbar opened a calculator instead of a drop-down with grid directions X before Y, and Y before X.
On Windows®, changing the GPU to iGPU in the windows settings was ignored by grandMA3 onPC.
With some complex fixtures, the Follow feature () in the 3D viewer did not work as expected.

Command Line and Macro

Description
Oops did not oops recent changes in the camera and appearance pool edit pop-ups. Instead, it closed the edit pop-up.
Cloning color wheel information was not working properly.
If you stored a recipe to a cue part or a preset, in some cases, the cue part or preset would be stored without creating a recipe line.
If Create Handles was enabled in the command editor of an encoder bar object, the handle would only appear in the editor and would not be transferred to the command in the object. Executing the object would return "Illegal name" in the command line history.
If you extracted a selective preset and stored it as global, the values would still be stored as selective.
If you created a macro with the command Goto Cue 1 Page X.Y with Create Handles enabled, the command would not be converted correctly.
If you set a custom command in an executor and Create Handles was enabled in the command editor and you then imported the show using PSR, the handle would not be imported correctly.
Using Go- or Goto to play back a cue that contained a phaser sometimes would not have the same result as using Go+.
Calling a magic preset, for example Fixture Thru At Preset 21.1, inserted the values from the preset as deactivated values into the programmer.
In preview mode, IfOutput selects all fixtures outputting live onstage instead of only selecting fixtures outputting in preview.
In the onPC software, if you controlled temporary commands such as Flash or Temp with a mouse, the mouse interaction would not behave as expected.
Presets with universal and selective data additionally called selective data if the preset was called using a fixture where only universal data was stored.
After changing preset mode from universal to global, some presets did not indicate global (G) on the pool object.
It was not possible to store the remaining time of a timer in a variable if the time value was less than one minute. This bug is fixed. Additionally, the option keyword /Look could be used to write the remaining time into a variable in the same format as it is displayed in the UI.
If you called a preset containing both selective and universal data on another fixture, attributes from the selective data may be applied even if only Universal data should be activated.
If you removed global values from a preset with selective, global, and universal data, a warning pop-up about storing universal values was displayed.
Some masters indicated that they are active in the preview environment although they did not influence preview but the live environment.
If you stored grid position values into an empty preset using /Merge, the recalled values would be wrong on the x-axis.
It was not possible to use the command line to assign a preset to the absolute value or relative value properties in a phaser recipe.
The software could crash when editing the settings of a preset that contained recipes.
It was not possible to use Transfer Selection and Transfer Programmer into preview without a defined sequence.
The software could crash when executing an empty handle, for example, Store #[].
If you used swap in MAtricks, the values in the command line feedback would not be human-readable.
Commands could still be executed if desk lock was active and the keyboard shortcuts were used to execute the commands.
If you set more than one custom command for an executor, only the last one would be displayed on the executor but all commands would be executed.
Handles in custom commands of an executor displayed the internal handle instead of the readable representation of object number and object name.
It was possible to store universal and global data to a color preset for the same fixture without triggering a Global/Universal conflict warning pop-up. Additionally globally stored C1/CTO/CTC/Tint values were also applied to fixtures of other fixture types.
Merging recipe lines in a cue with directly stored selection and preset data, did not create an additional recipe line. Instead, the cue only contained one recipe line with the information from the second recipe you created.
Store Cue + triggered a pop-up for merging into the next cue with an integer instead of creating a follow up cue, when the cue number ended with a ".9". For example: Store Cue + on cue 1.9 would trigger a merge pop-up for cue 2 instead of creating cue 1.91.
If you used the on-screen keyboard for command line input, pop-ups would not be triggered.
Executing Lua "SelectedSequence():Dump()" with a running sequence displayed the wrong value for the property "CUENO" in the command line history: "CUENO = "" (Read only)". Additionally, when switching off the sequence and executing Lua "SelectedSequence():Dump()" again, the current cue "1" was displayed, instead of "".
Move Grid Cursor was set to Append X instead of Linked in auto created groups.
The CompareHandle() Lua function was documented with an incorrect number of arguments.
The software could crash when playing back a preset (Go+ Preset X) in specific showfiles.
Some UserAttributePreferences properties, for example TimeLayerResolution or PhaserLayerResolution, were not saved in show files or streamed in network.
Group At Sequence created multiple empty recipe lines when EditRecipe was enabled.
If Create Handle was enabled in the command editor, text input with decimal numbers would not be detected correctly and would apply wrong values.
In some cases, executing a valid command would return an illegal property error. But the command itself would still be executed.
If you spun the rotation encoder of a shaper past the maximum or minimum value, you could not immediately spin it in the other direction.
If you labeled an object while storing it, the first index setting would be ignored.
In the phaser editor, if you used Off to disable an attribute, then pressed Off a second time, the temporary off menu would be displayed instead of the off keyword being displayed in the command line.
It was not possible to copy a recipe line from a cue or preset to a programmer part.
It was possible to rename structural objects and delete menus in the show file, resulting in parts of the UI and show files not working.
Pressing +  followed by . removed the "+" from the command line.
It was possible to edit meshes that were locked by a user.
If On  was assigned as press and Off as release for encoders of special executors 30 and 40, the release function Off would not be executed.
In the sequence sheet, the cue command where Create Handle was enabled did not automatically update the handle when the corresponding cue number was changed.
The Lua command DataPool().sequences:SetChildren('autostart',true) could crash the grandMA3 software.
Loading a show file with corrupted groups could crash the software.
Copying a preset that contains a phaser recipe may cause the software to crash.
In some cases, presets with data of wheels, such as gobo wheels, that were stored as universal would result in invalid values in other fixture types.
The Blink mode in statuses was too slow to catch attention.
OSC messages including Swap, Temp, or Black commands did not send the corresponding sequence information anymore.
If many filters were used in a show file, the grandMA3 software could crash while storing groups.
It was not possible to record masters in timecode shows.
Storing a recipe into an preset pool could have caused the software to crash.
The conversion of cue commands referencing labeled presets of the type All to handles using Create Handle could fail, but cue commands that were not edited were still working.

Connections

Description
A particular USB flash drive was not recognized by grandMA3 onPC when running on macOS.
If you loaded a show file on a console in session, the volume level of the onPC macOS would change.
If you deleted a DMX-key in the output configuration and always automatically inserted a new output configuration for a fader wing, it would not be possible to change the device type to DMX-key.
If OSC was configured to have a feedback loop to itself and the mode was set to TCP, the UI would freeze during playback.
When rebooting the master console after changes were made on a second connected console, the Session Data Merge pop-up did not appear, preventing the user from selecting the show file that already existed on the second console.
While in session and rebooting a high-priority console (master), tapping Cancel in the Session Data Merge pop-up made the high-priority console idle and the other console standalone.
The MIDI input did not work after a clean start was performed. Instead, MIDI Data Mode had to be changed in the output configuration first, and then the MIDI input was received again.
In some cases, the software could crash when altering MAtricks values of phaser recipes in macros.
The MIDI Data Mode in the Output Configuration menu had no Off setting.
In a session, playing back a cue with the Goto command, for example Goto Cue 5, then disconnecting and connecting a console again, reloaded the current cue after reconnecting.
Starting the onPC software on macOS would change the sound output.
In some cases, interacting with a filter pool on a web remote would crash the software.
It was not possible to assign masters to timecode tracks.
In session, bitmaps sometimes would not work after changing show files.
If you set a gateway in the extended tab of the My Network Interfaces menu, it would not be saved once you closed the menu.
Handles should not be recogniced in macros if the name contained square brackets. For example "#[Macro 'Test[1]']".
The software could crash if web remote displayed a sheet with a filter that had one of these filter rules: ID Type, Name, Patch, or Environment.
The selected NDI source was not synced over network and changes were not displayed on connected stations.
Changing the multicast base of another station with the command ChangeMulticastBase IP "172.16.70.21" /Type "Alternative" caused the destination station to enter a continuous network initialization loop.
If the multicast base address was changed in the network, it would not automatically unsubscribe from the previous one.
Connecting a node via grandMA3 onPC Terminal App could crash the software.
In a session with two consoles and one console set to high priority, loading a show file from USB on the connected console without saving it and then making changes while the master console was rebooting could result in the show file being empty after the master console took over the control of the session.
After a crash on a connected station, a full show upload was triggered after rejoining the session instead of a partial upload, which led to long loading operations with bigger show files.

Patch

Description
If you tapped Revert in the edit appearance pop-up of a fixture type in the live patch, the software could crash.
If a locked sequence was imported with PSR, the sequence would be imported without any cues.
Temporary filtering in the Feature column of attribute definitions in the patch did not filter correctly.
The selection pop-up for temporary filtering in the Target Space and Movement Space columns in the patch did not display any values.
If you replaced a fixture type in GDTF format by the same fixture type in XML format in the patch, additional dimmer values were added to color presets that previously had no dimmer values stored.
Fixture types that included modes without real channels (for example, the Bitmap Control fixture) showed a DMX footprint of -1. This bug is fixed. Such fixtures now correctly display a DMX footprint of 0.
In rare cases, the software could freeze when deleting a fixture type in the patch.
If there was already a patched fixture in the show file and you inserted a second fixture, Insert New Fixtures would open with the Library tab instead of the Show tab.
Exchanging a large number of fixture types in the patch, unpatching and then patching them again, could crash the software.
If you exported an MVR file, names of groups would not be exported.
In some cases, if you deleted fixtures in the patch and set an FID for a fixture, the software would crash.
Some truss MVR files were not affected by Hide Environmental. Therefore, they remained visible when the setting was enabled in the patch.
Names of already existing variables could be lost in show file after PSR.
After modifying the order of layers and classes in an MVR file and re-importing it via PSR, the changes were not applied. Instead, the files were sorted by their fixture type index.
After importing MVR files, unused classes and layers of fixtures could be deleted from the patch.
Changing subfixtures in the patch could break related filters on groups.
Importing a sequence with cues that have different timestamps could lead to cue loss in the newly imported parent sequence due to a comparison process in PSR.
If calling a color preset with universal and global values for multi instance fixtures, the universal values could be deleted in some instances.
Previously exported files were not displayed in the Export dialog of the patch when exporting from grandMA3 and Entire Patch. The grandMA3 file was exported to "gma3_library\patch\stages" while the dialog listed the files of the directory "gma3_library\patch". This bug is fixed. Now, the exported files are listed and the selection option Entire Patch was renamed All Stages.
If Split View was enabled in the patch, some modes for fixture types were not displayed when unfolding the fixture type with ▶.
Using PSR, show files with illegal fixture type information could cause the software to freeze and a full install was required.

Phaser

Description
If you set a value for measure in a phaser recipe and enabled Adaptive Measure, the measure cell and shape editor would still display the value that was set manually and you would still be able to edit it.
In some cases, if you stored a phaser recipe preset using the command line, the software would freeze or crash.
Phaser data could get lost after certain patch modifications, such as changing the fixture type of an affected phaser.
The software could crash or the station could drop out of a session if you copied a phaser recipe line in a preset. This bug is fixed. This action now triggers a command line error message in the message center.
Imported shapes did not have the correct values when the readout was set to any decimal or hex readout.
Storing a phaser recipe with a selection in a preset with an active Input Filter, displayed the preset as it had no selection and calling the preset did not run the phaser. The preset was only usable with an auto-cook.
If merging template phaser recipes with the same shape but different attributes to a cue, the already existing attributes in the cue recipe line were overwritten instead of being added to a new line.
Phaser recipes without a selection that had presets as value sources would not list these presets as references.
The second number in the phaser step indicator would not display the number of total steps for all steps but the first and last step of the phaser.
In some cases, it was not possible to add a new value source to a phaser recipe immediately after deleting a value source.
If you imported a phaser recipe preset that had a filter as the attribute, the filter would not be referenced in the imported preset.
In the recipe editor, the values calculator would always open to the bottom tab. Now, if a preset is set for a different step, the calculator opens to the corresponding tab.
If a phaser recipe was created in the recipe editor without a selection, and a second phaser recipe used the first recipe as a source for its shape, the references would get lost after the recipes were stored in a preset pool.
In rare cases, if you tapped Insert New Value Source in the recipe editor, the software would crash.
The software could crash when a 65th step was added, for example, by tapping + in the 1D tab in the shapes editor.

Playback

Description
Custom commands were not executed when they were assigned to SpecialExecutor 5 (Grand Master).
If you triggered Top for a sequence that had an off cue with a follow time, in some cases the timing would be inconsistent.
Labels for speed masters would display * if the speed scale was set to one. This bug is fixed. Now, they will display * if a speed scale is applied to the speed master. If speed scale is one, no * will be displayed.
Addressing executors using the FromAddr() Lua function, for example  Lua "FromAddr('14.14.1.12.1.101')" could crash the software.
In some cases, nodes would crash if bitmap was used.
Changing the Speed Master or Speed Scale within a cue required reassertion to take effect.
With a phaser recipe in a sequence, a Release preset assigned in the phaser, and Off when Overridden enabled, the phaser stopped immediately when playing back the sequence.
After executing FastSync on a running phaser with an active NShot value, the NShot value was no longer respected.
After setting the timing master to "0" and setting it as the OffCue fade time, then changing the timing master value to a number greater than "0", the cue still didn't fade out and went off immediately.
In some cases, if you removed a recipe line from a cue, it would not update immediately and the cue would play back as it was before.
The phaser recipe playback direction was not inherited on assign, for example, when executing Assign Preset 21.1 At Programmer 0.1.
Moving the last cue of a timecode event to the last frame of the duration did not always trigger this cue during playback.
Store Overwrite Cue x did not refresh the values automatically in the tracking sheet.
In specific show files fixtures did not move linear to their fade time when the next cue was triggered which did not contain additional cue info. For example, fixtures could speed up or slow down instead of moving at a constant speed during the fade time.
MIB with cue recipes could stop working after changes were made to the patch.

Windows, Views, and Menus

Description
Repetitive Agenda events could have wrong countdown time.
Disabling the sACN input did not update the indicator text, for example "sACN In", in the corresponding pool object of the Universes pool.
Tapping Max in the calculator for editing a color in the encoder bar did not set the value to 100.
Toggle Preview in the Encoder Bar window and Command Wing Bar window was not displayed in the toggle button style.
Universe pool objects still displayed sACN In even if sACN input was disabled for the universe.
The TCSlot column in the user profile settings was limited to 8 TCSlots instead of 16.
Deleting a layout that was displayed in the layout viewer, and then selecting <Link Selected> in Layout of the layout viewer, displayed multiple Lua errors in the system monitor.
A number of presets were grayed out, even though they could be selected if you worked in another world, except "World 1".
Assigning a tag to a sequence using the label pop-up of an executor, did not display the tag in the "Assigned" area of the pop-up, even though the tag was assigned to sequence.
Shuffle was missing in the MAtricks editor of the recipe editor.
If you tapped   and selected a value source of a phaser recipe in the sequence sheet, a blank recipe editor would open.
Tapping NShot Stay multiple times, did not toggle between Yes and No. Instead it displayed a numeric value.
The displayed parameter count in the tooltip for the status "Not Enough Parameters" did not match the parameter count in the system info window.
If you tried to select text in pop-ups, it would sometimes be only partially selected.
Reset Blades in the special dialog did not reset the value. Instead, the value was set to 0.
Enabling Edit Title Bar in the selection grid window settings, did not display the Title Buttons tab in the settings.
If you had two Shaper dialog windows next to each other, one in Graphical and the other one in Faders view, and then turned the encoder bar shaper encoders for each shaper, the result would be different in the two views.
If you moved a large range of DMX universes, for example by executing Move DMXUniverse 492 Thru 882 At 100,  and oopsed this task, this action could freeze the UI.
Temporary filtering in the Action column of the agenda window did not work as expected.
In the calculator for individual fade and delay times, a 0 would be added every time the calculator was opened.
If Group by Attribute was enabled in the recipe editor, Insert Step would be grayed out and disabled after adding a step to the recipe.
If you opened the Add Window pop-up, some UI elements, such as pool objects and layouts would not get darker.
The Store View pop-up on screens 6 and 7 did not open in the center of the screen and was slightly too big for the two screens.
Temporary filtering in the agenda viewer was not correctly retrieved.
If you assigned an object to a layout element, the vertical text alignment in the layout element would change to Above, regardless of the previous alignment.
Flash did not work in the pool actions for the tags pool and ListRef was not available in the pool action for the tags pool.
In the recipe editor, if you pinned the context area in the MAtricks Editor tab and tapped another cell in the recipe grid, the context area would sometimes go blank.
If the context area in the recipe editor was pinned and you cleared the programmer, the pinned context area would still be displayed.
If you pinned the MAtricks editor in the context area of the preset editor and turned the preset into a recipe or added a recipe, the MAtricks editor would break.
In the recipe editor, you could open the tabs Pool and Sheet in the context area, even though the displayed values could not be selected.
If you were in Edit Recipe mode and pressed MA, a yellow frame would be displayed around selected pool objects instead of the green frame.
The software could crash if you increased the height of a layout element via encoder rotation.
If you set a range of attribute values in multiple fixtures in the content sheet or track sheet, for example, 21 through 30, it would result in a long loading operation and the value 21 would be applied to all selected fixtures.
In the Encoder Bar, the wrong physical values would be shown if Highlight was active while the highlight value was in the same range on another channel function.
An unused user profile would require confirmation if it was deleted.
was not displayed in referenced pool objects in the executor configuration pool.
Editors that display the lock icon would not update and change correctly between lock icon and pool icon if you locked or unlocked the object.
The virtual keyboard in the Lua input editor would stretch across the whole window regardless of the window size.
Appearances could still be edited if they were locked.
The input value range of relative calculator values did not match with the value set in Readout. For example, with Percent selected in Readout, it was not possible to put in negative values.
The World Master status was not displayed if a world that was not selected was assigned to an executor and was not at 100%.
The Timecode Viewer was missing the Tags column, which would appear when at least one single track was added.
In the tags pool, the default pool action List Reference was not available anymore.
The tooltips of shapes pool objects were misleading.
Tapping Adjust Shape in the context area of the recipe editor did not take you directly to the Editor tab of the shape column. Instead, the Pool tab was displayed.
In the bitmap editor, if you tapped an encoder icon, the calculator would open.
Opening the context area for recipes in a preset and tap , closing the editor again and opening any editor for a preset again, was still active and the context area was pinned to the column that was selected before.
If a preset contained a recipe, Recast Preset was not available and grayed out in the preset editor.
Selective presets with Preset Mode set to Global, did not display "G S" on the preset pool object.
In the Fixture Sheet with Preview enabled, show files could display markers from the Live environment, such as Phaser markers.
The temporary pool menu (opens when pressing List+Preset) did not follow the selected feature group and only displayed the Dimmer pool.
The Trig Type BPM in the Sequence Sheet was not working.
The dynamic function "Edit Recipe" , such as Edit StandardRecipe 1,  in the edit settings of a preset pool, was not available.
The Edit tab in the assign menu was empty, after closing the temporary MAtricks editor while creating a recipe.
In the My Interfaces menu in the extended mode, the two-finger tap would only work in the table, not in the empty area below the table.
When Lock Position was enabled in the Layout Viewer window, the Lasso Filter button was grayed out.
In preview, the fixture sheet in Dimmer+ or Sheet/Filter mode did not display playback values.
If you created a new MAtricks object in the recipe editor, the first index that was set in the MAtricks pool settings would not be adopted.
Filters would not be applied to phaser recipe presets that had no selection and were used in standard recipes.
In some cases, the MAtricks header in the recipe grid of a preset would not be expandable.
Template recipe presets with a selection would not display a feature group indicator bar.
Cues that included a standard recipe with a phaser recipe preset as the value would not display the preset name in the cue.
In some cases, MAgic presets would be grayed out even if they could be applied to the current selection.
If the MAtricks header in the recipe editor was collapsed and you moved the column, the software would crash.
If you deleted a mirrored sequence, the mirror icon would not disappear in the other sequence immediately.
In a session, if you set a default cue part for an All preset pool, phasers that were stored in that pool would not run if you called them into the programmer on a connected station.
With a Readout set to Decimal8, editing a WithX value of a shape, the calculator offered a range of "0" to "0".
If you added a phaser recipe after adding a standard recipe, the column order and sorting would be different than if you added a phaser recipe first.
In some cases, previewing an object, and then leaving preview mode, still displayed the preview encoder bar instead of the live encoder bar.
In some cases, the status for Highlight was active with the "ext" marker, even though no highlight was active.
The feedback when a cue was loaded (Load Cue)was not displayed in the corresponding pool object.
Double-tapping on an executor configuration in the assign menu would overwrite the executor configuration.
If the selected attribute in the encoder bar was unavailable for the newly selected fixture, the encoder bar would automatically switch to an available attribute. However, the dynamic preset pool would not follow accordingly.
In some cases, Display Mode in the playback window settings displayed a number instead of Text+Icon, Text, or Icon.
In some cases, the scrolling behavior in pools was not working as expected after resizing pools on consoles. Scroll positions changed unexpectedly, and the focus on pool objects sometimes shifted.
Hovering over the network status icon when it was green, changed the color of the icon to white implying a different status.
When MA was latched in the command section, the text on the Deactivate, Programmer, ListReference, FixtureType, FeatureGroup and AlignTrans buttons was cut off.
In the Scribble editor, the last drawn line could not be removed by pressing Oops.
Referencing shapes in two phaser recipe lines in cues or presets to each other, would lead to a freeze in the software.
The web remote login pop-up could disappear after resizing the browser window, potentially allowing access without entering the required password.
Parts of the UI remained darkened after closing the update menu on multi-screen devices until additional user interaction occurred, such as tapping anywhere in the UI or pressing ESC twice.
The preset update indicator was displayed in the sequence update color. Presets now correctly use the cyan update indicator, while sequences use the yellow update indicator.
Loading a stored view including the message center did remove the filtering and the title bar was not updated when changing the category filter.
With Split View enabled in patch,  and  were hidden in the title bar instead of grayed out.
The attribute toggle buttons above the curves in 1D tab of the shapes editor displayed <No Attribute or Filter> instead of <From Preset> with a preset selected as a value source.
Pressing Oops after deleting a mesh, did not restore the link from the model to the mesh. Therefore they were also not displayed in the 3D viewer anymore.
When selecting multiple cells with Track Sheet enabled in the sequence sheet and entering a value range in the calculator (for example, “21 Thru 30”), the value range was not applied. Instead, all selected cells were assigned the same value.
Changing the POV fader in the Shapers tab of the special dialog with multiple fixtures selected, and then going through the selection with Next, applied the changed POV value only to the last fixture.
The MAtricks columns in the recipe editor were sorted differently depending on whether a standard or a phaser recipe was added.
Previewing a mirrored sequence, put another sequence from the pool in preview.
With Adaptive Measure enabled, the measure column of phaser recipes was still displaying a value and was not indicated as blocked, even though the value was invalid with adaptive measure active.
The Update menu of presets with Preset Update Mode set to Add New Content did not list in some cases to all presets that can be updated.
If a selected sequence was disabled, the Info window would not refresh and would still display the current cue.
After executing the command Lua "DumpAllHooks()" multiple times, the System Monitor output became unreadable because several lines of text overlapped.
Tapping and holding on a Selection cell of a recipe line of a sequence, opened the edit pop-up of a group, but displayed data of the sequence.
In some cases, the desk lock would flicker if a pop-up was open while desk lock was activated.
Values in the 3D viewer and layout viewer Setup encoder bar were calculated wrong using + or *, for example setting Pos Z to "4 thru 5" in the calculator, and then enter "+1", did not set the values to "5 thru 6".
The timecode slot indicator in the upper-left corner of the Timecode Pool object did not display the correct number for the selected timecode slot.
The input pop-up for the Absolute cell in the phaser recipe editor opened with the wrong tab of presets on the right side of the pop-up.
In the pool tab of the context area in the recipe editor, the name of the pool was not displayed.
If you tapped on the fader area in an encoder bar window while the setting Encoder Label was disabled, a calculator would open but it would not be possible to apply values in it.
If you changed the custom text of a layout element, the text on the element would only change after updating the layout.
The temporary views pool wrongly had a data pool setting in the title bar.
With Delete + Menu, it was possible to delete the main menu, so it could not be opened anymore.
After selecting a new encoder bar, the programmer indicator would be wrong.
In the running playbacks window and off menu in sheet style, the number that indicates the total number of cues in brackets in the No column would include cue zero and the off-cue.
In the timecode viewer, columns that were hidden would reappear after selecting an empty timecode object.
If you cut events in the timecode viewer, they would not be indicated as such.
With some fixture types, the shaper rotation in the special dialog window turned in the opposite direction as expected.
Some valid presets were incorrectly discarded for a step value in the context area for the Absolute Value cell in the recipe editor.
Deleting a quickey as a layout element, printed "Delete" in the command line every time Clear was pressed.
It was not possible to edit a quickey as a layout element in the layout viewer.
In the Info window, the tab counter when List Reference was executed and Tabs in the window settings was disabled, was incorrect.
If you converted a phaser preset into a phaser recipe, warning pop-up would not appear. This bug is fixed and now a pop-up warns users that the values will become hard values.
The active datapool would not be transferred to preview if Transfer Selection and Transfer Programmer were enabled.
In a timecode event, it was not possible to enter Fade Override 0 in an empty cell.
In the layout viewer, the size of the displayed scribbles and appearances changed in previous versions.
In the sequence sheet in the Adjust MAtricks pop-up, it was not possible to open the Fade From X calculator.
Editing cells for attributes, for example, for dimmer in the tracking sheet, displayed no matching preset pool objects in the calculator.
If closing the off menu, some graphical issues were visible for a second.
Executing a Clear quickey printed an echo with "MSTATE = 1!" in the system monitor.
In preview mode, the encoder bar window and the command wing bar displayed the wrong name for Preview Bar. Also the encoders inside the corresponding window would not update ifPreview Bar was toggled.
Quickeys assigned with MA1 or MA2 codes could not be unlatched.
It was not possible to latch Prvw in the command section on grandMA3 onPC.
In a specific show file, the number of phasers displayed in the phaser bar in the command line would not decrease if ClearAll was executed after the phaser bar was drastically increased.
Migrated show files could omit the pie charts in presets, for example, for appearances without an associated image. Additionally, appearances could be wrongly displayed in front of preset pie charts.
The battery pop-up was missing the state of charge icon in grandMA3 devices with UPS battery.
If you tapped a MAtricks recipe line, all None columns in the Editor tab of the contextual area would receive '..' characters after Adjust MAtricks was tapped.
It was not possible to lock a recipe line in the preset editor via the Lock column. Also the lock state was expected in Lua and you could not set it via a property.
Screenshots of NDI streams would swap the colors red and blue.
In some cases, the Display pop-up that opens with the menu pop-up would be empty on onPC rack-units.
If deleting multiple objects, for example Delete Sequence Thru, and some of the objects were locked, the command line response did not show the correct information.
Property controls in a network menu could get stuck in a disabled state. If ReloadUI was executed, the property controls were enabled again.
The encoder bar window would not reset if the preview preparation bar was canceled using Esc.