Jump to content
Shino

DPSMate - A combat analyzation tool

Recommended Posts

Как юзер официально заявляю дпсмейт пшет криво. Начиналось все с того что писал лично для гильдии с включенной и выключенной синхрой порой недоумевая от логов на сайте решил попросить еще несколько людей что бы писали. В итоге за два месяца юза этого крапа назаписали кучу кривых логов. Короче либо аддон недопиленый либо еще что, но важно это знать что пишет он криво!

Share this post


Link to post
Share on other sites

Is there any reason to have the DPSMate de/fr/ru/cn localizations installed if you're playing on a english client anyways?

I'm thinking maybe for syncing purpose or does that not matter?

Share this post


Link to post
Share on other sites

I just modulized it so you only have to load it if you actually use this locale.

Speeds up loading time.

DPSMate won't sync with other locales anyway.

Share this post


Link to post
Share on other sites

[2017/03/13 01:56:09-644]: DPSMate_Healing\DPSMate_Healing.lua:134: attempt to index local `a' (a nil value)
DPSMate_Healing\DPSMate_Healing.lua:134: in function `ShowTooltip'
DPSMate\DPSMate_Options.lua:2120: in function `ShowTooltip'
<string>:"DPSMate_DPSMate_ScrollFrame_Child_StatusBar...":2: in main chunk

  ---

Share this post


Link to post
Share on other sites

We forbidden any raider to use your addon, it causes heavy lagg for the whole raid especially in suppression room. Just wanted to let you know!

Share this post


Link to post
Share on other sites
Just now, Plask said:

We forbidden any raider to use your addon, it causes heavy lagg for the whole raid especially in suppression room. Just wanted to let you know!

Just pushed an major optimization commit, please report back if it got better

Share this post


Link to post
Share on other sites

Hello Shino,

At the end of my raid session I can't upload the results of my raid.

And when I try to re-upload them... KO :

************** Texte de l'exception **************
System.FormatException: Le format de la chaîne d'entrée est incorrect.
   à System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
   à System.Number.ParseInt64(String value, NumberStyles options, NumberFormatInfo numfmt)
   à LLLauncher.GUI.Reupload_Click(Object sender, EventArgs e)
   à System.Windows.Forms.Control.OnClick(EventArgs e)
   à System.Windows.Forms.Button.OnClick(EventArgs e)
   à System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   à System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   à System.Windows.Forms.Control.WndProc(Message& m)
   à System.Windows.Forms.ButtonBase.WndProc(Message& m)
   à System.Windows.Forms.Button.WndProc(Message& m)
   à System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   à System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   à System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Assemblys chargés **************
mscorlib
    Version de l'assembly : 4.0.0.0
    Version Win32 : 4.6.1586.0 built by: NETFXREL2
    CodeBase : file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
LLLauncher
    Version de l'assembly : 1.0.0.0
    Version Win32 : 1.0.0.0
    CodeBase : file:///F:/Jeux/World%20of%20Warcraft%20Classic/LLLauncher.exe
----------------------------------------
System.Windows.Forms
    Version de l'assembly : 4.0.0.0
    Version Win32 : 4.6.1586.0 built by: NETFXREL2
    CodeBase : file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
    Version de l'assembly : 4.0.0.0
    Version Win32 : 4.6.1586.0 built by: NETFXREL2
    CodeBase : file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
    Version de l'assembly : 4.0.0.0
    Version Win32 : 4.6.1586.0 built by: NETFXREL2
    CodeBase : file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
mscorlib.resources
    Version de l'assembly : 4.0.0.0
    Version Win32 : 4.6.1586.0 built by: NETFXREL2
    CodeBase : file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/mscorlib.resources/v4.0_4.0.0.0_fr_b77a5c561934e089/mscorlib.resources.dll
----------------------------------------
System.Configuration
    Version de l'assembly : 4.0.0.0
    Version Win32 : 4.6.1586.0 built by: NETFXREL2
    CodeBase : file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Core
    Version de l'assembly : 4.0.0.0
    Version Win32 : 4.6.1586.0 built by: NETFXREL2
    CodeBase : file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Xml
    Version de l'assembly : 4.0.0.0
    Version Win32 : 4.6.1586.0 built by: NETFXREL2
    CodeBase : file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Windows.Forms.resources
    Version de l'assembly : 4.0.0.0
    Version Win32 : 4.6.1586.0 built by: NETFXREL2
    CodeBase : file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms.resources/v4.0_4.0.0.0_fr_b77a5c561934e089/System.Windows.Forms.resources.dll
----------------------------------------

************** Débogage JIT **************
Pour activer le débogage juste-à-temps (JIT), le fichier de configuration pour cette
application ou cet ordinateur (machine.config) doit avoir la valeur
jitDebugging définie dans la section system.windows.forms.
L'application doit également être compilée avec le débogage
activé.

Par exemple :

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

Lorsque le débogage juste-à-temps est activé, les exceptions non gérées
seront envoyées au débogueur JIT inscrit sur l'ordinateur
plutôt que d'être gérées par cette boîte de dialogue.

 

I use the v.32 of the client and I use the last version of DPS MAte...

I don't know what happen.

Share this post


Link to post
Share on other sites

I am on Windows 10 Pro 64-bit

Regarding the .net framerwork... I don't know how to get this information

I am using the last b98 release, do you think it could be a problem ?
https://github.com/Geigerkind/DPSMate/tree/b98

Oh! and I have already made a successful reporting on legacylogs with an older release (b90) of DPS Mate :
https://legacy-logs.com/Vanilla/Raids/Evaluation/index.php?rid=5472

I have the archive of our two last raid, as a workaround solution is there any mean to upload our raid in another way please ?

My mates are counting on me because these reporting are part of our first raid and we have a lot to analyse particularly on our first try hard session on Onyxia yesterday night :(

Edited by Malga

Share this post


Link to post
Share on other sites

I don't know.

I fixed some bugs and made some optimizations in B99 now, will continue to optimize the next days, because some are reporting performance issues.

You can find the archieve in WTF/LLSave.

If you upload it here I can reupload it manually for you.

cheers!

Share this post


Link to post
Share on other sites

Thanks for your upload :)

I think the problem comes from the client.

Do you have some advises to provide in order to re-initialize its installation please ?

Share this post


Link to post
Share on other sites

I'd suggest to try the java version in the meantime actually, because im just shipping a portable version, meaning a reinstall won't do much.

I'll need to find the bug and fix it.

Share this post


Link to post
Share on other sites
On 3/12/2017 at 3:46 PM, Plask said:

We forbidden any raider to use your addon, it causes heavy lagg for the whole raid especially in suppression room. Just wanted to let you know!

Same. Great concept just a bit flawed in that matter as well as it not really being accurate as it sometimes counts stuff twice or 3x, as well as being inaccurate in uploading. Thank you for your hard work in trying regardless. Would be a great addon if all the bugs / kinks get ironed out.

Share this post


Link to post
Share on other sites
6 hours ago, Papertank said:

Same. Great concept just a bit flawed in that matter as well as it not really being accurate as it sometimes counts stuff twice or 3x, as well as being inaccurate in uploading. Thank you for your hard work in trying regardless. Would be a great addon if all the bugs / kinks get ironed out.

Could you tell me what is tracked twice, so I can fix these bugs :> ?

I think build 100 will solve the lag issue completly. Optimized as much as I could :>

Share this post


Link to post
Share on other sites
41 minutes ago, Mattias said:

Hi Shino, love your addon, but it seems all the issues we get come from parsing the logs that are uploaded to the legacy-logs site.

I did create an issue https://github.com/Geigerkind/Legacy-Logs-Bugtracker/issues/76 and just updated it now with another problem I spotted, is this OK or do you need information to work from?

The more the better :>

Also prob, provide me a dl of your logs if you still have them.

----------------------------------------------------------------------------------------------------------------------------------------------

Build 100:

Optimization and Bugfixes

cheers!

Share this post


Link to post
Share on other sites
2 hours ago, Shino said:

Could you tell me what is tracked twice, so I can fix these bugs :> ?

I think build 100 will solve the lag issue completly. Optimized as much as I could :>

Alot of stuff seems to get tracked twice. DIspells, Dmg, Healing, it deosnt happen everytime but it definitely does happen often.

 

Another issue is the fact that it seems to cause client crashes as well. for alot of us. for the few weeks we ran dpsmate when server came back it was a problem that constantly prolonged raids a=due to waiting for ppl to log back in etc. once we went back to swstats and realmplayers the issue ceased entirely.

 

Dont get me wrong Shino, i am not here to talk shit or hate on your addon. i love the concept and i love how in-depth legacy logs is as far as tracking goes. and if all these bugs can get fixed it can be one of the most amazing addons ive seen for this type of thing. you are really doing a great job and we all do appreciate the hard work you have put into this in getting it to be the best it can be!

Edited by Papertank

Share this post


Link to post
Share on other sites

I do want to ask you 1 question however. Ive heard rumors of dpsmate bugging out if someone in raid is using swstats. is this rumor true? or just a rumor? I would possibly like to test the new build of dps mate in an upcoming raid yet if it does conflict with swstats, i may have to not as we all use swstats primarily.

Edited by Papertank

Share this post


Link to post
Share on other sites
1 minute ago, Papertank said:

I do want to ask you 1 question however. Ive heard rumors of dpsmate bugging out if someone in raid is using swstats. is this rumor true? or just a rumor? I would possibly like to test the new build of dps mate in an upcoming raid yet if it does conflict with swstats, i may have to not as we all use swstats primarily.

This is a rumor.

DPSMate does not work properly if you use both DPSMate and SWStats, because SWStats changes some combatlog strings that DPSMate expects to be different.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×