Sign up Calendar Latest Topics
 
 
 


Reply
  Author   Comment   Page 18 of 18     «   Prev   15   16   17   18
Dave Thaler

Registered:
Posts: 488
Reply with quote  #256 
Artemis Bridge Tools v3.29 is now released.  Changes include:
  • 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 (requested by notsabbat)
notsabbat

Avatar / Picture

Registered:
Posts: 1,294
Reply with quote  #257 
Thats amazing! Thank you!
__________________
-Captain of the TSN Gungnir JN-001
-Eastern Front online group member
-My continuing bridge build:
http://artemis.forumchitchat.com/post/immersion-bridge-build-in-progress-7335195?pid=1290158413
xscape

Registered:
Posts: 3
Reply with quote  #258 
Hi,

Is anyone else having a similar issue with the latest update for Artemis Bridge Tools? I installed the latest update and started to get the following error "error: Can't find RT_CreateDeviceInfoList" when I tried to add a new DMX device to an already working config.

Then I started to get the error when I created a new DMX device. I uninstalled and re-installed and I have gone back to my previous version. Now I get this error even in older versions. I am no longer able to create ANY new DMX devices and I have deleted all of my previous. 

I'm thinking a file somewhere is corrupted now but not sure where to start looking, really do not want to have to uninstall my Artemis as well.

Any help is greatly appreciated. 

Chris

--------- 
NVM I just re-installed Artemis and that resolved the problem. It would be good to know what is the root cause so I can resolve it without resorting to a complete re-install if it does occur again. 
Dave Thaler

Registered:
Posts: 488
Reply with quote  #259 
Quote:
Originally Posted by xscape
I installed the latest update and started to get the following error "error: Can't find RT_CreateDeviceInfoList" when I tried to add a new DMX device to an already working config.  NVM I just re-installed Artemis and that resolved the problem. It would be good to know what is the root cause so I can resolve it without resorting to a complete re-install if it does occur again.


I've never seen that before and I don't know what caused your problem but I can explain the symptom.  The message "Error: Can't find FT_ListDevices" is generated when Artemis Bridge Tools can't find the correct ftd2xx.dll that shipped with Artemis.  Longer version: When Artemis Bridge Tools is installed, it renames the original ftd2xx.dll to ftd2xx-orig.dll and puts the Artemis Bridge Tools code in ftd2xx.dll (which internally calls into ftd2xx-orig.dll to do the original work), which is how it forces itself to be loaded when Artemis runs.  That message means it did find a ftd2xx-orig.dll but it wasn't what was expected (perhaps the DLL was corrupted?) so it couldn't call into it to do the normal DMX functionality.   Presumably reinstalling Artemis got back the original ftd2xx.dll library that had been corrupted.
Roy151

Registered:
Posts: 2
Reply with quote  #260 
Hello!

Long time user of DMX tools, Love it!

I've been working on new panels, and would like to incorporate more DMX cues for Engineering. I looked through the forum and saw that there are difficulties treating heat, energy and coolant as you do with shields and impulse. For example, my plan was to have 5 lights for impulse energy, lighting up one at a time with the energy level. Is there a relatively easy way to do this or should I come up with a different plan? Is there a way to convert these into percentages like shield integrity? I experimented with the named colors but it didn't really do what I wanted. 

Thanks,

Ben Roy
Dave Thaler

Registered:
Posts: 488
Reply with quote  #261 
Quote:
Originally Posted by Roy151
I've been working on new panels, and would like to incorporate more DMX cues for Engineering. I looked through the forum and saw that there are difficulties treating heat, energy and coolant as you do with shields and impulse. For example, my plan was to have 5 lights for impulse energy, lighting up one at a time with the energy level. Is there a relatively easy way to do this or should I come up with a different plan? Is there a way to convert these into percentages like shield integrity? I experimented with the named colors but it didn't really do what I wanted.


Named colors (as discussed in the walkthrough here) can be used to change the color of one or more lights, based on the heat, energy, or coolant level.   It sounds like you want the color to be constant, either on or off, with a gauge across lights.  I don't know of a way to do that at present.

The other gauges work by having multiple DMX cues for different fixed thresholds (Artemis has a number of native cues that work that way), and thus the number of lights has to be the same as the number of DMX cues, so if one person wanted 4 lights on their bridge and another person wanted 6 lights on their bridge, you can't please both people.  For engineering there's so many different systems and attributes that having a fixed number of cues for each one would still be an explosion in the number of cues.

A better way, I think, to address this in the future would be to allow conditions that test properties against whatever threshold you want, so there's no new cues needed, and different bridges can have different numbers of lights and hence different thresholds.  Today Artemis Bridge Tools does support conditions of a sort (discussed here), but the condition can only test whether a given state cue is set or not.  I can add to my todo list to see if the conditions can be expanded to support testing properties (as used in named colors) against thresholds.
Dave Thaler

Registered:
Posts: 488
Reply with quote  #262 
Artemis Bridge Tools v3.30 is now released.  Changes include:
  • Added ability for cue conditions to test a named property against a percentage threshold
  • Added gauges for named properties (requested by Roy151)
  • Added support for MagicLight lights (requested by HaydenBarca)
  • LimitlessLED (including MagicLight) discovery is now done on all network adapters not just the default one

So Roy151's scenario is now easily supported using the gauge HowTo and picking heat, energy, and coolant properties to create gauges from.

I've also updated the conditions HowTo with a second example that looks like this in the XML:

<event type="IMPULSE_20" continuous="yes" if="systemCurEnergyImpulse > 0%">

Roy151

Registered:
Posts: 2
Reply with quote  #263 
Thank you!

Tested it and it does exactly what I was looking for! 

Ben
Previous Topic | Next Topic
Print
Reply

Quick Navigation:

Easily create a Forum Website with Website Toolbox.