Using Windows 7.
If you guys are importing using HistoryDB, this is a known issue. A work-around is to rename your in-game player name to "YOU" under the combatant rename option.
The reason this happens is the that plugin records the player's in-game name in the log file so that regular parsing can automatically do this renaming. HistoryDB only does a partial import, so it skips this log line and the manual mapping is necessary.
The ACT Import tab can import a full log file to bypass this issue, so that is what I use instead. HistoryDB doesn't work very well with the FFXIV plugin for other reasons. The DoT simulation requires prior log data to estimate the DoT tick amounts. If it only processes a partial import, it will use whatever previously-loaded data to estimate. It also may miss some combatant details such as job and pet ownership. Job can affect the application of some buffs to DoTs that have job-specific effects. There's probably more going on too. If SE ever includes individual DoT ticks, then I can discard the DoT simulator and a lot of these issues will go away.
I've seen this once, it was caused because ACT was left minimized when shutting down the computer. It remembers the window setting and tries to load minimized to the icon tray, and triggers an issue in the .net framework that results in a stack overflow.
The only reliable workaround we found was to delete the ACT configuration file in AppData. You may be able to fix it by just changing a line in the configuration file:
<Form Name="FormActMain" X="0" Y="0" W="1111" H="605" WindowState="Minimized" />
changed "Minimized" to "Normal" and it should work, if this is the same problem.
My Act is stock settings for the most part, but it keeps displaying fights in pieces. It usually cuts the parse off into a new piece when a boss jumps or there is slight inactivity. Is there a way to display total dps of the fight with the jumps?
You can merge together the individual pieces, but it wont count the elapsed time during jumps (this is why merged parses are typically higher DPS).
If you want to change the time before it creates a new encounter go to Options>Main Table/Encounters>General and then change the value for "Number of seconds to wait after the last combat action to begin a new encounter" to ~20 seconds
Oh ok, so would that be considered a more honest parse for a fight?
I'd consider an "honest" parse to be one that accounts for all downtime in the fight, yes.
Excluding downtime is just artificially inflating the DPS numbers to look more like a test dummy, it's not an accurate representation of your performance in a given situation.
eh, that's not entirely true. Some points you sit around waiting longer because you are better. You kill Snakes in T5 too fast and can wait 10-15s for Twintania. Kill Dalmud's faster and you sit around waiting for Megaflare longer. An "honest" parse to me would be one which simply states the context of said parse.
Obviously you wouldn't compare an un-merged 320dps parse to a merged 380 dps parse but both are "honest" as long as you don't try to claim the 380 is un-merged.
It's really just as simple as one is a record of the whole fight from pull to boss kill and the other has parts missing/removed. I recognise that most of the time it's because it's the default setting and usually not dont maliciously and "honest" is probably not the right word but "correct"? might be more suitable.
I don't think correct would be the right word either, as all parses need context with them to show the entire story. Normal, usual, most common, method. The only things removed are downtime in which nobody is really doing anything.
Merged gives a pretty big benefit in fights like Turn 9 though, as you can quickly and easily look at each individual stage and determine if someone is under performing at certain points. Not killing Dalmuds fast enough? Look at that section to see who is doing what. Want to push 3 meteors but stuck at 4? See who needs to up their DPS at the start. Sure, you can still do that with timelines in un-merged but it's a little more work.
Yeah having it split has actually been pretty good to show me exactly how high I can perform in each phase of a fight. I wish there was a way to show the fight segmented like that but also have a complete duration parse as well.
Have a second person parse, if you want both un-merged and merged.
Well I guess for analysis reasons - the "correct" one is the one that works best. But I guess I'm thinking as use as comparison to other full fights (i.e. WoW style World of Logs, and other aggregated log websites). Like you said, statistics are inherently neutral - it's all about how you use them.
I'm pretty sure it's fairly simple in ACT to "unmerge" existing fights (by combat log or similar). Though I can't recall the exact way this was done.
You can re-parse an encounter in ACT:
- Go to Import/Export Tab
- In the treeview, click the Import a Log File node
- Click the 'Select File' button
- Navigate to the FFXIVLogs folder (%appdata%/Advanced Combat Tracker/FFXIVLogs), and pick the relevant log file. You can also find this folder by going to Plugins ->FFXIV Settings tab and clicking the 'Open Folder' button
ACT will scan the file, then ask whether to use the default character name, or if you want to supply a custom name. Clicking the left button should work for your own parses.
question!
how to change the target and focus target color and size/look? '3'
The most easiest way is to have Clickthrough disabled (Plugins > FFXIV Overlay settings > Target etc.) so you can click on the overlay. Left click moves it around and holding right click over it allows you to expand and contract the overlay bar to whatever size you want. Once you have it set, enable clickthrough again. The color is changed in the in the StartHP and EndHP boxes so you can set it to be a specific color at certain HP% thresholds or just make it so it's the same color no matter the %.
This is how I have mine set.
omfg that is so smart
Damn Lokus, best idea ever, thanks!
Is there any way to get rid of the borders around the mini window?
I don't really use it but I might if it didn't stick out so much.