Skip to content

Version 3.6.0.274

Compare
Choose a tag to compare
@EQAditu EQAditu released this 23 Dec 18:10
· 17 commits to master since this release
be91efb

Internal Changes
Adding data to encounters is being split from the log parsing threads. The most obvious effect of this is that log parsing may use up to 1-2 cores instead of only one. Typically you will only see this much saturation during log file imports, but there may be situations where live log parsing could potentially benefit from this depending on your setup/plugins.

TTS - Text to Speech
The TTS options have been split out into a different configuration page. You may now choose direct SAPI as a TTS method, though the volume scale will be different. You may now add custom find/replace corrections to change how the TTS engine sees certain words or phrases. This is to correct how the TTS engine pronounces things. There is a textbox/button to test these settings or to test TTS in general.

Miscellaneous
Added RelativeTime column to the bottom level table that shows the time since the encounter began. When importing a log, the progress bar will no longer marquee animate while waiting for user input. Internally one of the form names has changed, which may cause a config warning. If the Custom Trigger thread crashes, it will now automatically restart, but also dump the queue that crashed it. TraySliders, aka notifications, will use a different location calculation method that may work for more multi-monitor layouts. The Death Report should now be compatible with fractional seconds. The -minimize flag will now affect the ActLoader form that shows the progress.

Plugins/API
Added FormActMain.AfterCombatActionDataLock property, used to pause data being added to encounters. The purpose of this is more efficient calculation of large encounters that may be changing while being calculated. UncachedFileSave() no longer writes if the destination file already has that content(unless you use the overload method to force it). The FormEncounterLogs class now has a LogTypeToColorMapping property. This can be used so that the View Logs window colors different log lines to specific colors based on the LogLineEventArgs.detectedType. If EncounterData.SetAllies() is called, automatic ally detection will be disabled for that encounter. Setting it to null/empty will re-enable.

Requirements
ACT now requires v4.6 of the .NET Framework instead of only complaining about not having it. For other plugins, it's recommended that you have v4.8 just in case.