Artemis Bridge Tools Change Log
v3.35
- Updated max known-good Artemis version to 2.8.0
v3.34
- Updated max known-good Artemis version to 2.7.99
v3.33
- Fixed crash when adding a chase effect using devices in reverse
order in Artemis DMX Editor
v3.32
- Fixed potential crash when trying to add new device in Artemis
DMX Editor
v3.31
- Added support for Razer Chroma keyboards
v3.30
- Added ability for cue conditions to test a
named property against a percentage threshold
- Added gauges for
named properties
- Added support for MagicLight lights
- LimitlessLED (including MagicLight) discovery is now done on all
network adapters not just the default one
v3.29
- Updated max known-good Artemis version to 2.7.5
- Added DMX state cues for
HAVE_SPARE_{HOMINGS,NUKES,MINES,EMPS,PSHOCKS,BEACONS,PROBES,TAGS} which
are set whenever at least one is in storage
v3.28
- Updated max known-good Artemis version to 2.7.4
- Fixed bug where adding an Artemis install location from Artemis
DMX Editor wouldn't install the RGB keyboard driver to that location
- Fix crashing bug when RGB keyboard lights were configured but no
such keyboard is connected
- Upgraded to Visual Studio 2019 for compilation
v3.27
- Updated max known-good Artemis version to 2.7.2
- Fixed bug in uDMX controller detection
- Fixed bug where false "duplicate" warnings would be reported when
clicking Validate if you have cues with multiple timeblocks that don't
actually conflict
- Fixed bug with Shift button where shifting a series of DMX
devices to another range of channels didn't work correctly
v3.26
- Added support for LED keyboards, mice, etc. such as Razer
devices
v3.25
- Added ability to use HELM_IN_REVERSE from client consoles
- Fixed bug where the RED_ALERT cue was incorrectly relayed to
fighter client consoles when the fighter was outside the capital ship
- Fixed bug that caused some Enttec Pro controllers to not be
detected as such
- Artemis DMX Editor:
- When bulk adding devices, channel order is now grayed out if
the channel order is static for the chosen device type
- Fixed bug where canceling a bulk device add only canceled one
of the set
- Fixed bug where the Shift button wasn't disabled when
no devices exist, and clicking the button would crash the app
- Fixed bug in Helm and Weapons console simulator screens
where the Shields checkbox was incorrectly disabled when
PLAYER_SHIELDS_RAISED/LOWERED are used without PLAYER_SHIELDS_ON
- Fixed bug in Helm console simulator screen where the
Nebula checkbox was incorrectly disabled when ENTERING/EXITING_NEBULA
are used without WITHIN_NEBULA
- Fixed a few cosmetic issues where some labels had the
wrong width, resulting in some truncated labels
v3.24
- Artemis DMX Editor:
- Added a Fighter console control simulator to the Test Active
functionality
- Added a Game Paused checkbox to the Test Active functionality
- Added ability on the device configuration screen to "shift" a
set of devices to another range of DMX channels
- Fixed bug where the Test button on the Hue device
configuration screen didn't work right
- Fixed bug where, for some screen resolutions, the text was
cut off on the "Change DMX Device Profile" screen
- Fixed bug where a 0 device count was incorrectly allowed when
adding a chase effect
v3.23
- Added ability to use named colors that map to tube loading
progress
- Fixed bug with the JUMP_IN_PROGRESS cue where it wasn't cleared
if the jump fizzled
- Artemis DMX Editor:
- Added Helm, Weapons, and Engineering console simulators to
the Test Active functionality
- Added a "game in progress" checkbox to the Test Active
functionality to simulate game start/end
- Added ability to select ship type in the Test Active
functionality
- Fixed bug where the Test Active functionality would not
display DMX cues used only in conditions
- Fixed a memory leak
v3.22
- Added ability to use named colors that map to engineering heat,
energy, and coolant levels (requested by RockStar)
- Added ftdiutil.exe utility to assist with Enttec Open and Enttec
Pro troubleshooting
- Fixed bug with Hue lights (reported by DrD)
- Fixed Artemis DMX Editor display issue where message on "Change
DMX Device Profile" screen was cut off
v3.21
- Added support for Artemis 2.7.1
- Added new mission stats to Artemis Mission Browser
- Make Enttec Open show up on a device scan even if some channels
are already in use
- Fixed bug with Hue lights
v3.20
- Added support for Artemis 2.7.0, including native DMX cues
TORP_{PSHOCK,BEACON,PROBE,TAG}_FIRED
- Added DMX cues
TUBE{1-6}_{LOADING,READY_TO_FIRE,UNLOADING,FIRED}_{BEACON,PROBE,TAG}
- Added ability in Artemis DMX Editor to filter
commands/timeblocks/devices to display only those affecting specific
devices
- Automatically detect available audio devices when adding devices
in Artemis DMX Editor
- Added validation check in Artemis DMX Editor to check for
duplicate device entries in the same timeblock
v3.19
- Automatically detect available device types when adding devices
- Added ability to configure ranges of "Other" type channels
- Removed "Validate" button warnings about LOADING_TUBE{1-4} and
UNLOADING_TUBE{1-4} cues since Artemis Bridge Tools v3.18 makes them
work as expected
- Made Aurora, Hue, and WeMo device enumeration work even if
multiple network interfaces exist
- Made LimitlessLED device configuration screen's Group ID value
default to the next unused value
- Fixed bug in automatic discovery of Aurora devices
- Fixed bug where cloning a device would copy the ID prefix from
the last device rather than the cloned device
- Fixed bug where WeMo event value incorrectly changed from Off to
On when changing the device, or changing the device profile for a
command profile
v3.18
- Made the native LOADING_TUBE{1-4} and UNLOADING_TUBE{1-4} cues
work as expected
- Added built-in support for devices with more than 4 channels,
rather than requiring the workaround of representing them as multiple
devices
- Artemis DMX Editor dialogs now show the more friendly device type
names
- Fixed column widths in Artemis DMX Editor and Artemis Mission
Browser on Windows 10 Creators Update with text display set to a size
other than 100%
- Fixed bug where the Test Active screen would correctly play audio
effects but wouldn't display the associated value on screen
- Fixed a bug where adding a new device could have defaulted to
reusing already used DMX channels
- Fixed a recent bug where transparent channel values wouldn't be
grayed out in the color editor
- Fixed a bug where canceling changing the device profile for a
command profile would display the wrong device profile name afterwards
- Fixed formatting issue when resizing the Test Active dialog
- Fixed bug where the Validate button would incorrectly warn about
duplicate commands when commands actually differ by condition
v3.17
- Added support for LimitlessLED/Mi-Light v6 bridges and lights
- Added ability for Artemis DMX Editor to discover addresses of
LimitlessLED/Mi-Light (bold old and new) bridges
- Added ability to test a LimitlessLED/Mi-Light light from within
the LimitlessLED/Mi-Light device configuration dialog
- Made the "Test Active" dialog in Artemis DMX Editor only show
cues that have events in the active command profile
v3.16
- Added support for Nanoleaf Aurora
lights (requested by DVersion)
- Added support for 4-channel lights with brightness ranges other
than 0-127 (requested by Kip Murray)
- Added *_OVERHEATING cue for each system (requested by RockStar)
- Fixed bug where setting intensity of a 4-channel device to a
value out of range caused problems in Artemis DMX Editor
- Fixed bug in Artemis DMX Editor when changing an output device
from a DMX to a non-DMX type
v3.15
- Added FIGHTER_BAY{1-5}_EXISTS cues
- Added FIGHTER_BAY{0-5}_{REFITTING,READY}_{SHUTTLE,FIGHTER,BOMBER}
cues
- The Validate button in Artemis DMX Editor will now warn about
effects that would not be noticeable because they're redundant with an
earlier wider effect (e.g., NORMAL_CONDITION_1 or ALWAYS_ON)
- The Validate button will now do some device profile validation
checks as well
- Fixed bug where SOMETHING_HITS_PLAYER was not seen on a client
after deselecting the main screen console
v3.14
- Fixed crashing bug with Artemis 2.6 fighter bay status packets
v3.13
- Added support for Artemis 2.6
- Added Accent Color slider on the "Test Active" screen
- Added support for RGBW lights on the "Test Active" screen
- The SOMETHING_HITS_PLAYER cue is now triggered on any machine,
not just the server (requested by k6lego)
- Native cue glitch protection is now enabled even if only native
cues are used in the DMXcommands file (requested by mgatland)
- When setting a light's color to a named color in Artemis DMX
Editor, the start and end color will both be set
- Fixed bug where fighter cockpit cues weren't set correctly if a
client joined and was assigned to an already-launched fighter
- Fixed UI bug in Artemis DMX Editor where "Add One" device didn't
scroll the new device into view
v3.12
- Added support for the Infestation scenario in Artemis Mission
Browser
- Added new INCOMING_COMMUNICATION_* cues for use with Artemis
2.5.107 message categories
- Fixed bug where Artemis Mission Browser displayed some mission
versions incorrectly on the first screen
v3.11
- Added support for Artemis 2.5.107
v3.10
- Added ability to set a light's color to the ship's Accent Color
- Added FIGHTER_BRAKING and FIGHTER_BOOSTING fighter cockpit cues
(suggested by Mark Bell)
- Added fighter cockpit support for BEAMS_EXIST and TUBE1_EXISTS
cues
- Make advanced mission scripting commands work with EntTec
Open/Pro controllers
- Fixed PLAYER_SHIELDS_ON cue for fighter clients
- Fixed bug where DMX state on a main screen client wouldn't reset
if it got disconnected from the server
- Fixed bug where DMX state on a fighter cockpit client wouldn't
reset if the Fighter console was unselected
- Fixed bug where RGBW lights weren't emulated or logged correctly
v3.9
- Update "Test Active" functionality to work automatically without
needing to edit device profile to add emulated devices to the profile
(requested by weretygr)
- Show Artemis Version on Mission Browser dialog showing list of
attempts for a mission
- Add "Colors Used" to color picker in Artemis DMX Editor to allow
easily reusing the same colors (requested by Sandman and Martin
Prinzler)
- Add support for creating "named color" settings that
automatically change all commands using the named color when changing
the associated value in Artemis DMX Editor (requested by Sandman and
Martin Prinzler)
- Fixed bug in Artemis DMX Editor when changing the color
associated with a timeblock containing both 3- and 4-channel devices
where the 3-channel device would end up with a darker color
v3.8
- Added new DMX cues for ANY_FIGHTER_READY (requested by Cap Naes),
JUMP_DRIVE_EXISTS, FIGHTER_BAY_EXISTS, BEAMS_EXIST, and TUBE{1-6}_EXISTS
- The ALL_FIGHTERS_DOCKED cue is no longer triggered on ships with
no fighter bay (requested by Cap Naes)
- Added to Artemis DMX Editor the ability to change the color of
all devices in a command with multiple timeblocks, if they all started
as the same color (requested by Martin Prinzler)
- Changing the initial color of an effect via the color picker in
Artemis DMX Editor now also updates the final color
- Fixed bug in Artemis DMX Editor where cloning a DMX command
didn't copy the command's comment or condition
- Fixed bug in Artemis DMX Editor where changing the white value of
multiple RGBW devices in a collapsed timeblock didn't work
- Fixed placement of some buttons when resizing some Artemis
Mission Browser dialogs
v3.7
- Added ability in Artemis Mission Browser to click "More info"
from an installed mission dialog, to get to the TSN Nexus page with the
description, forum URL, records, etc.
- Fixed bugs with Hue lights (reported by tznkai)
v3.6
- Added ability in Artemis Mission Browser to find new missions to
install
- Mark Artemis 2.5.101 as supported by default (previously required
user to manually set it)
- Fixed bug with multiple universes with Art-Net controllers
(reported by Tiwato)
- Installing mod to an additional Artemis install location no
longer changes the active command profile
v3.5
- Added support for using 2 universes, allowing up to 1024 channels
rather than just 512 (requested by Dave Bemrose). This allows using
multiple DMX controllers at the same time, whether or not the
controllers are of the same type. Note that uDMX and Velleman
controllers only support universe 0.
- Added built-in support for 4-channel RGBW lights, rather than
requiring them to be manually added as separate RGB and 1-channel W
devices (requested by Dave Bemrose)
- Added ability to change the (only) device in all timeblocks of a
command in Artemis DMX Editor, when the timeblocks are collapsed into a
single row for the command
- Display WeMo switch values as "on" or "off" rather than trying to
display it as a color
- Fixed bug with Art-Net and Velleman controllers
- Fixed channel order bug when an RGB-order device appeared after a
device with a different channel order, where the RGB device would be
incorrectly interpreted as having the other channel order
- Allow CUSTOM_* cues to be used with EntTec controllers without
causing problems
- Fixed bug in Artemis DMX Editor when adding a 1-channel device to
a timeblock with a 4-channel device
- Fixed bug in Artemis DMX Editor when changing a DMX command's
device from a light to a video player, where the dialog's controls
weren't updated correctly
v3.4
- Fixed crashing bug with Enttec Open controller by reverting fix
from v3.2 for bug where additional mission script commands don't work
unless a CUSTOM_* cue was also used. As such, CUSTOM_* cues
should not be used with Enttec Open controllers until a better fix
comes along later.
- Finished support for uDMX controllers, now confirmed to work
(thanks to BillCat for donating a controller to the cause)
- Added a File->Settings dialog to allow testing future versions
of Artemis
- Added ability to bulk-add any device types (previously only some
types were bulk addable)
- The Validate button in Artemis DMX Editor will now complain about
non-zero change values on video devices and WeMo switches
- When adding new devices, default to the same type as the last
device added
- Support Artemis 2.5.1 by default
- Fixed automatically generated comments in DMXcommands file for
commands that play videos
v3.3
- Added ability to play a video on a specified monitor (attached to
the server, or main screen computer of another ship) in response to a
DMX cue (requested by AmnonLiu)
- Added a way to cancel a video played by a mission script or
socket command
- If Artemis is upgraded to a newer version than the one Artemis
Bridge Tools understands the protocol for, protocol parsing will be
skipped rather than potentially crashing
- Fixed bug with (non-AllSeen) LIFX bulbs
- Fixed display of "Change" button in Artemis DMX Editor when a
timeblock has devices of different media types (e.g., both audio and
lights)
v3.2
- Added DMX cues for AUTO_BEAMS_ON and WEAPONS_TARGET_SELECTED
(requested by Cap Naes)
- Added DMX cues for SCIENCE_TARGET_SELECTED and
CAPTAIN_TARGET_SELECTED
- Added glitch protection for PLAYER_SHIELDS_ON, ANY_TUBE_EMPTY,
and ANY_TUBE_READY_TO_FIRE
- Added ability for a mission script or socket client to trigger
playing a video on the main screen or an alternate monitor
- Fixed bug where scripting commands to preserve state into another
mission didn't work unless a custom DMX cue was also used
v3.1
- Added ability to preserve state from one mission to another
(requested by Menbailee)
- Added support for Velleman DMX controllers (requested by
DagShadow)
- Replaced glitch compensation algorithm (added in v2.12) with a
better one but only for the RED_ALERT cue so far
- Fixed bug where non-native cues weren't working with missions
that change the ship name
- Fixed bug preventing quotes and backslashes from appearing in
mission rating comments
- Fixed bug in mission rating dialog where comment box wasn't
initially disabled until a rating number exists
v3.0
- Added integration with TSN Nexus server to keep
statistics such as records (lowest time, highest difficulty, etc.) and
crash reporting
- Added ability to rate missions and provide comments
- Fixed placement of Save button in Artemis DMX Editor when
resizing the event configuration screen
v2.13
- Added MAIN_SCREEN_{FORE,AFT,PORT,STARBOARD}_VIEW cues
v2.12
- Added support for
WeMo switches
- Added workaround for Artemis bug causing 31ms glitch in native
state cues
v2.11
- Added support for DMX cues for fighter cockpits
- Fixed BEAM cues on Artemis v2.3 and later
- Fixed bug where FIGHTER_LAUNCHED would fire on Artemis when a
fighter launched from another player ship
v2.10
- Added support for LimitlessLED
lights (requested by Christian Klos)
- Make MissionLog.csv be more readable in a spreadsheet
- Make mission logging work correctly with modded race names
v2.9
- Fixed bug where mission results would not be logged if a Ximni
ship was chosen
- Display mission version in Artemis Mission Browser
- Make main screen clients, not just the server, log mission results
- Include PvP mission results in the mission log
- Log player race
- Log number of player deaths in PvP and CoOp games
- Added support for personal mission comments in Artemis Mission
Browser
v2.8
- Added support for Artemis v2.4.0
- When running Artemis DMX Editor or Artemis Mission Browser after
upgrading Artemis, they will now detect that Artemis Bridge Tools needs
to be reinstalled to the relevant locations and do so
- Added button to event configuration screen to Save without
closing dialog (requested by Kip Murray)
v2.7
- Added REVERSE_IMPULSE cue (requested by Sandman)
- Combined install/uninstall mod to Artemis location functionality
into one manage locations dialog, and display the version of Artemis in
each location
- Subsequent upgrades after this one should reinstall mod to all
Artemis locations it was previously installed to, rather than just one
- If no audio devices are configured in the active profile, the
Play button on the audio file config screen will now use the system
default playback device rather than giving an error message
v2.6
- Added JUMP_IN_PROGRESS cue (requested by Sandman)
- Added support for Art-Net DMX controllers (requested by Christian
Klos, davisn456, and TommiH)
- Allow resizing the Device Configuration screen in Artemis DMX
Editor
- Fixed bug in algorithm guessing Device Configuration of an
imported DMX commands file, where multiple devices could end up with
the same ID
- Fixed bug on Device Configuration screen where column headers
were editable
v2.5
- Fixed potential flicker when a 4-channel light transitions to max
intensity
- Allow resizing the "Test Active" dialog in Artemis DMX Editor
- When adding another device to a timeblock in Artemis DMX Editor,
copy the previous device's color settings by default
- Fixed bug on the "Add Chase Effect" dialog when using 4-channel
lights transitioning to max intensity
v2.4
- Fixed bugs in support for Artemis v2.3.0
- Added FIGHTER_LAUNCHED, FIGHTER_DOCKED, and ALL_FIGHTERS_DOCKED
cues
- Fix bug when when changing an Audio device to an emulated
1-channel output device
- In Artemis DMX Editor, if an audio clip fails to play, give a
useful error message
v2.3
- Added support for Artemis v2.3.0
- Fixed Hue configuration bugs that caused Artemis DMX Editor to
sometimes get stuck "Searching..." for Hue bulbs
- Allow resizing the Hue configuration screen (requested by William)
- Reverted gamma correction (added in v2.2) for Hue bulbs based on
feedback
v2.2
- Add support for simple "if" conditions on DMX commands, to only
trigger when another state is true or false
- Added gamma correction to Hue bulbs to get closer to RGB color
- Added ability to reorder data columns in Artemis Mission Browser
without deleting and re-adding them
- Allow "Add Many" devices to add Hue bulbs, but each still needs
its Param set individually afterwards
- Fixed Hue bulb flicker when going to/from black
- Fixed potential hang on the Hue device configuration screen
- Validate button and status bar didn't work with window resizing
in Artemis DMX Editor
- Fix potential hang ending "Test Active" mode in Artemis DMX
Editor when a client is connected to tracing port
- Fixed default intensity value on add gauge screen in Artemis DMX
Editor
v2.1
- Added a "Validate" button on the DMX commands configuration
screen to check for common problems with the configured commands
- Fixed bug in v2.0 preventing configuring audio clips on a DMX
command in Artemis DMX Editor
v2.0
- Support integration with multiple Artemis SBS installs in
different locations (requested by Newcommerin)
- Add ability for any continuous cue to have special timeblocks
that occur only on "entrance" or "exit" (requested by Sandman)
- Add TUBE{5-6}* cues (requested by Mark Bell)
- Add BEAM{5-10}_FIRED cues (requested by Mark Bell)
- Allow updating the color for all devices in the same timeblock
together in Artemis DMX Editor (requested by Sandman)
- Allow resizing the main window and the DMX commands window in
Artemis DMX Editor (requested by Sandman), as well as the missions and
mission details windows in Artemis Mission Browser
- Display a Final Color column next to the Initial Color column
when configuring DMX commands (requested by Sandman)
- Disable RGB transparency and channel order settings for 1-channel
devices since they have no RGB channels
- Disallow setting a 3-channel device with RGB all transparent,
since that would result in simply deleting the device from a DMX command
- Fixed bug where the "Add gauge" screen displayed the wrong device
count for an energy gauge
- Prevent configuring duplicate input device IDs on the DMX device
configuration screen
v1.25.1
- Added ability to fade in/out an effect from the previous color
(requested by AmnonLiu and Kip Murray)
- Fixed another bug with Hue lights
v1.24
- Fixed bug when using a Hue hub with lots of lights
- Fixed default sort column in Artemis Mission Browser's mission
details screen
- Allow data columns in Artemis Mission Browser to have arbitrary
order
- Make comment box in Artemis Mission Browser wrap text
- Added "Artemis DEMO" directories to list of directories the
installer looks for Artemis in
- Allow installing Artemis DMX Tools when cannot find Artemis
- Allow enabling/disabling DMX Tools mod in an arbitrary Artemis
install location
v1.23
- Fixed bug that could cause Artemis to crash if the server sends a
very large packet as some scripted missions do
- Log results of non-scripted missions as well, for
viewing in Artemis Mission Browser
- Allow viewing individual mission attempts in Artemis Mission
Browser, rather than just the aggregate summary of all attempts per
mission
- Allow commenting on missions from within the mission attempt
stats screen of Artemis Mission Browser
- Make Artemis Mission Browser notice new mission attempts without
restarting the app
v1.22
- Fixed issue where non-native DMX cues sometimes caused lights to
flicker
- Added additional columns in Artemis Mission Browser for Artemis
version and various game over reasons
- Allow sorting rows in Artemis Mission Browser by clicking on
column headers
- Added ability to open the mission log in a spreadsheet, from
Artemis Mission Browser using File→Open
log file in spreadsheet
v1.21.1
- Add more scripted mission stats visible in Artemis Mission
Browser: date the mission was last played, and highest difficulty
completed
- Improved configuration experience for multiple Hue lights
(requested by Allen Cobb)
- Allow configuring IP address of Hue hub if discovery doesn't work
for whatever reason (requested by Allen Cobb)
v1.20.2
- Log scripted mission stats to a MissionLog.csv file
- Add ArtemisMissionBrowser.exe tool to easily view past mission
stats
- Make non-native DMX cues work even when Artemis port is not 2010
- Fix potential crash when using custom DMX cues and logging is
enabled
v1.19
- Added CUSTOM_EVENT_{1-4} and CUSTOM_STATE_{1-4} cues for use by
missions and scripts
- Added support for "dmxset" command to set custom cues via mission
script (requested by Mike Substelny)
- Added support for "dmxset" command to set custom cues via tracing
socket (requested by AmnonLiu)
- Added stats line at bottom of DMX command editor screen
- Updated log format to shorten "value=" to just "="
- Fixed bug on DMX command editor screen where device profile combo
box should not allow arbitrary text
v1.18
- Added SHIP_INTEGRITY_* cues that address the problems with the
native SHIP_DAMAGE_* cues and allow effects that, for example, only
trigger in response to other cues when a ship is heavily damaged
(requested by AmnonLiu)
- Added support for bulk adding gauge effects for hull integrity
and (positive) energy
- Added ability to trace DMX triggers in real time via a socket
- Updated sound file picker to be able to select .mp3, .wma, .au,
and .mid files in addition to .wav files
- Fixed bug in ArtemisDmxEditor where "Stop Testing" would turn off
the ALWAYS_ON effect
- Fixed bug in computing decreasing colors when bulk-adding a stack
of related events on the same light
- Fixed a potential prompting bug when Artemis loads a device
profile with no devices
v1.17
- Added ability to view/edit timeblock comments
- Added support for adding a gauge effect with devices in reverse
order
- Simplified DMX channel configuration in ArtemisDmxEditor, to
prevent misconfiguration
- Fixed bug where cloning a timeblock didn't clone the timeblock
comment, if any
- Fixed bug in v1.16 where adding a device into a timeblock added
it without setvalues by default
v1.16
- Added GAME_PAUSED cue
- Added ability to bulk-add a set of related commands to achieve a
gauge or stacking effect
- Added ability to set only red, green, and/or blue channel,
leaving the other channel(s) unaffected
- Added ability to add a moving light chase effect that includes a
fading trail or a corona (i.e., both trailing and leading)
- Display a wait cursor while loading/saving large DMXcommands files
- Increased max number of devices that can be bulk added to 170
- Fixed bug where copying a device profile didn't copy non-RGB
channel order
v1.15
- Added TUBE{1-4}_FIRED_{HOMING,NUKE,MINE,EMP,PSHOCK} cues
(suggested by cikrusapan)
- Improved ability to configure and use AllJoyn light bulbs
v1.14
- Added {FRONT|REAR}_SHIELD_{20,40,60,80,100) cues (requested by
Scionica)
- Fixed potential flicker at end of non-native cue effect that
fades to black
- Fixed bug in editor where "Stop Testing" didn't always turn off
DMX lights
v1.13
- Added support for lights with a channel order other than RGB
- Added ability to bulk-add a non-moving effect (such as a series
of lights all fading on at the same time) via the "add chase effect"
screen
- Fixed display bug on "add chase effect" screen, where the initial
color was displayed wrong
- Preserve a comment at the top of a timeblock (before a setvalue)
when editing a command profile. Such a comment is not
currently editable via Artemis DMX Editor
- Added additional error checking when parsing responses from a Hue
hub
v1.12
- Added BEAM_FIRED and BEAM{1-4]_FIRED cues (requested by
cikrusapan)
- Added ALWAYS_ON cue to allow ambient lighting effects outside of
game play
- Improved ability to configure and use Hue light bulbs
- Fixed bug when trying to change a command profile's device
profile to one where a referenced device id doesn't exist
- Installer will now automatically detect if "C++ Redistributable
for Visual Studio 2012 Update 4" is needed and install it if required
v1.11
- Various UI bug fixes to Artemis DMX Editor
- Fixed potential crashing bug after running a huge number of
Artemis games in one session before exiting
v1.10
- Added ability to bulk-add a set of devices, such as an LED light
strip
- Added ability to bulk-add timeblocks for different types of chase
effects
- Added support for non-AllJoyn-compliant LIFX light bulbs
- "Test" screen in editor will now signal event-type cues each time
the Apply button is pressed, rather than requiring the user to first
Apply with the event's checkbox clear
- Using editor to add another timeblock to an existing command will
now use the previous timeblock duration as its default duration
- Fixed bug where Artemis would not finish exiting when using an
Audio device
- Fixed category of shields raised/lowered/on cues on "Test" screen
in editor
- Adding a 2nd timeblock in editor didn't add a button to collapse
timeblocks, and caused display problems if the command was then deleted
- Fixed editor bug where "# Outputs" box incorrectly showed 0
instead of 1 when adding a new input device
- Fixed potential crash in editor when changing the device profile
associated with a command profile with a timeblock containing only
partial setvalues for a device
- Fixed editor bug where "change" attribute was not getting
converted when changing the device profile for a command profile, when
converting from a 4-channel device to a 3-channel device
v1.9.1
- Fixed bug in Play button when configuring sounds
v1.9
- Added support for multiple audio playback devices
- Allow playing sound effect files located anywhere, in response to
DMX cues
- Fixed bug in Enttec Pro controller support [needs testing]
- Added prototype support for UDMX controllers [needs testing]
v1.8
- Added new DMX cues for IMPULSE_{1,20,40,60,80,100} (requested by
wookiemart)
- Added support for playing audio clips in response to DMX cues
- Fixed bug causing some DMXcommands.xml files to not load
- Allow configuring username to use with Hue lights
- Fixed bugs with using Hue lights
- Preserve name of active command profile across future upgrades
v1.7
- Added support for native ITEM_COLLECTED and WAR_TURN_WARNING cues
in Artemis 2.2
- Added new DMX cues for
TUBE{1-4}_{LOADING,UNLOADING,READY_TO_FIRE}_PSHOCK
- Added ability to minimize emulated device window
- Will now also look for Artemis in %LocalAppData%\Artemis and
%UserProfile%\Desktop\Artemis when installing
v1.6
- Added ability to delay an effect, to allow transitioning into a
continuous effect (requested by AmnonLiu)
- Double clicking on a profile in Artemis DMX Editor is now the
same as clicking Edit
- Fixed various bugs in ArtemisDmxEditor.exe
v1.5
- Added new DMX cue for engineering system overheating
- Added new DMX cues for tube statuses
- Now saves XML files using UTF-8 instead of UTF-16
- Added support for displaying more than four emulated DMX devices
at a time
- Fix upgrade behavior so future Artemis DMX Tools upgrades will
preserve device profiles
- Fixed DMX command editor "Add Device" to add default setvalues
v1.4
- Added new DMX cues for incoming communications
- Added new DMX cues for science scans
- Added new DMX cues for warp speeds
v1.3
- Added File→Open
File Location to make it easier to find files to edit by hand
if desired
- Added desktop shortcut and Start menu item for Artemis DMX Editor
- Preserve all command profiles (not just the active one) on
uninstall and upgrade to versions later than 1.3
- Fixed more bugs in DMX command editor reported by MallocArray
v1.2
- Fixed bugs in DMX command editor reported by MallocArray
- Expanded setvalue comments in command profiles
v1.1
- Added support for Enttec DMX PRO controllers
- Added support for single-channel DMX devices
- Added support for naming devices with readable labels, for ease
of display
- Auto-detect types of DMX devices based on your existing
DMXcommands configuration
- Added support for multiple DMX device configuration profiles and
ability to switch between them for a given DMXcommands profile
- Added support for converting DMXcommands configurations between
3-channel and 4-channel lights, e.g., to easily convert the stock
3-channel DMXcommands file to a 4-channel lamp
v1.0