Raid Hub Version 1.1.27 Released 03-12-2013

Tue, Mar 12, 2013

NEW FEATURES

  • New detection delayed action!  New tab “Delayed Action” in the editors let you specify a secondary action to be performed N seconds after a detection has been made. Need to wait 10 seconds before calling out a cure curse? Use this to specify an additional TTS to be spoken after N seconds of detection of a spell or trigger. Full variable substitutions are supported. 
Here’s an example spell timer that uses Delayed Actions for the Drinal Curse
<SpellTimer Name="Power Over Death IV" SpeechName="" AlertWindowDisplayName="" AlertWindowForegroundColor="Black" BroadcastEnabled="False" CanSwipe="False" DeltaEnabled="False" DeltaSeconds="0" DeltaCount="0" DeltaReset="0" DeltaDetectionCount="1" DetectAllHits="False" DetectionSoundEnabled="False" DetectionSound="" DetectionSpeak="Jump Curse on ${VICTIM}" DetectionText="${NAME} Detected! (Victim - ${VICTIM})" DetectionTextColor="Red" DetectionTextEnabled="True" DetectionTTSEnabled="True" DetectionMacroEnabled="False" DetectionWriteFile="" DetectionWriteFileText="" DetectionSecondaryActionDelay="10" DetectionSecondaryActionOutputEnabled="True" DetectionSecondaryActionOutputContent="Cure Curse on ${TARGET} NOW!!" DetectionSecondaryActionTextColor="Orange" DetectionSecondaryActionTTSEnabled="True" DetectionSecondaryActionTTSContent="Cure Curse on ${VICTIM} NOW!!" DetectionSecondaryActionSoundEnabled="False" DetectionSecondaryActionSound="" FilterFighter="False" FilterMage="False" FilterPriest="False" FilterScout="False" IsEnabled="True" IsInfection="True" InfectionRemedy="WAIT Cure Curse" InfectionRemedyColor="White" InfectionRemedySuccess="Cure Curse" InfectionRemedySuccessTTS="${VICTIM} cured!" InfectionRemedySuccessTTSEnabled="True" InfectionExpirationSeconds="0" RemoveSeconds="10" ResistType="Curse" TimerSeconds="15" WarningSeconds="5" WarningSpeak="Cure Curse" WarningSpeakOffset="2" WarningSoundEnabled="False" WarningSound="" WarningTextEnabled="False" WarningText="WARNING ${NAME} coming in ${WARNING_SECONDS} seconds!" WarningTextColor="Yellow" WarningTTSEnabled="False" />
Here are the parts that matter:

DetectionSecondaryActionDelay="10"
DetectionSecondaryActionOutputEnabled="True"
DetectionSecondaryActionOutputContent="Cure Curse on ${TARGET} NOW!!"
DetectionSecondaryActionTextColor="Orange"
DetectionSecondaryActionTTSEnabled="True"
DetectionSecondaryActionTTSContent="Cure Curse on ${VICTIM} NOW!!"
The above settings will: After a 10 second delay from detecting the spell say “cure curse” and the victim needing the cure. It will also write this info to the chat window. You’ll get a heads up that they have the curse at initial detection, and their name will appear in the infection window if you enable the below settings. If you want to track it as an infection, you can set these:

InfectionRemedy="WAIT Cure Curse"
InfectionRemedySuccess="Cure Curse"
InfectionRemedySuccessTTS="${VICTIM} cured!"
InfectionRemedySuccessTTSEnabled="True"
Adjust as needed, it’s obviously very noisy as-is. You will probably want to disable the detection tts, and the infection remedy success tts.
  • Now inspects video card for maker and amount of RAM. – If AMD is detected, the ati/amd bugfix is auto-enabled – If less than 512MB video ram is detected, then hardware acceleration is disabled. This will help with the out of memory crashes (the mostcommon crash happening currently).

CHANGES

  • EQDKP+ 1.0RC3 support is now more robust. Lag/timeouts to your site are now handled more gracefully to ensure raid are added and loot is submitted as expected. EQDKP communication in general has been enhanced by these changes.
  • TTS system now defaults to Zira voice for Windows 8 if none is selected.
  • Reduced trace output – have all the info needed!
  • Loot window no longer lowercases the names (for real this time!)

FIXES

  • DirectX Injection stability – no longer requires all windows to be displayed without crashing – no longer crashes if EQ2 cannot be brought to the foreground during injection
  • General stability – possible crash if there were pending TTS or audio items to be played during shutdown – On first run, copying over an existing UISettings.xml could result in a crash. – Will no longer crash rh-loot.csv is in use during delete operation – Possible crash when cancelling strategy editor changes – The combat parser could crash if a value over 2 billion is detected – now handles this gracefully.  Who is hitting for 2 billion???  Went ahead and protected the rest of   the parsers to zero out the value if it exceeds 2 billion.
  • Editor Fixes – No longer crashes when adding a new zone through either editor.