![]() MoX provides this online, but I see no reason why the client couldn't just hold on to the raid numbers for later. This makes it difficult for officers to analyze the performance of the raid at their convenience. When a player leaves the parser, their stats leave with them. ![]() It's possible that this was caused by players logging into alts without leaving parsec or switching instances/planets, not sure. It is as if the parser considers us still to be in the 'current fight' but for some reason the stats have been blanked. When I do so, all I see is current fight at the bottom and the fight before the last fight 2nd to bottom. A lot of times I see that my main 'raid' tab has become blank (usually 1 player in the group with all 0's) and I go to the drop down to try and go back to the last fight. This has the unfortunate side effect of having it appear like raiders are under-performing when they may be doing just fine. Several fights show the DPS/TPS/HPS numbers continually going down. Still seeing issues with stealth classes, especially with their own views. has officially picked this up! We're liking it for the most part. We especially like the stability of it - having it not crash is awesome! Overall, we like the ease of use and simple setup. I understand that passing off only the "numbers" keeps your bandwidth down and makes the updates faster - so I don't have any suggestions towards this end. To parrot what others have said, I'd like to be able to drill down on raid member's abilities to find out anything that's going wrong preferably without having to upload it TorParse. While I don't have a solution for dealing with bandwidth or other problems that would arise, but I miss the implementation of having full raid data within the client, i think it was swMONITOR that did it. Like it doesn't remember from fight to fight what the magnification was set to, or just erroneously re-sizes the available frame. My raid group has been using this for a week or so, here some of our thoughts.įirst, we like bars they are purdy.can we get bars? Second, special characters are not handled very well and result in an WingDing character or something.Īn issue that I have run into is sometimes overlays will adjust themselves in terms of size. For example you could create MyGuild 1, MyGuild 2 both with passwords GuildPass. I envisioned guilds having several Raid Groups that they can use and they all can share a password. This results in more accurate results more often.Īs for groups inside raid groups, the intent of the design was that raiders can create as many groups as they need to support their activities. Since the Combat End Event is many times printed in the log file out of order with the killing blows of a fight PARSEC opens a window to capture combat for 1 second after a combat end event is found. ![]() The difference is most likely the way PARSEC designates the combat end event. Like our guild is using 1 Raid group, it would be nice if it could arrange so people doing 1 operation doesnt get mixed up with other people doing a flashpoint or another operation One thing that would be awesome, but dunno if its possible is to have groups inside the same Raid group? There are certainly more challenges that make this difficult such as the variance in system clocks and latencies or the differences in peer network security.Awesome software, but some times I see difference in DPS results between this and Torparser/Mox ? However this will most likely initially be a simple viewer though it may grow more robust. My plan for the future is to create a hybrid system that allows a user to view other members logs via a peer to peer connection, but still keep the client server architecture for raid data. Switching to a peer to peer architecture would make the bandwidth issue go away but adds a layer of complexity to the software. This is something that is not feasible from a cost standpoint. ![]() A shared combat log system architected this way would use a tremendous amount of server bandwidth. Parsec is currently architected as client-server software. Purely the additional network traffic or would the amount of parsing on each individual system be problematic? Does Parsec feature a shared combat log? What are the technical challenges in creating such a feature?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |