CLR is #$%&*. I tried it 3 times and every time it crashes my game. DON'T get it.
You should check if the Windows Defender or the realtime protection of your antivirus program is trying to scan the Combatlog.log-file, which is created by STO. That is often a reason for gamecrashes, when your STO is writing that file.
The CLR does only read that file and has no direct interaction with the game at all.
Even though I am affiliated with the Original (and official) DPS League & Channels, I believe I can offer as close to an unbiased approach as possible.
Install/Launch Issues:
CLR - If you have any issues w/ CLR, first, uninstall any older versions of Java, then install the latest version. In extreme cases, you may need a Java removal tool prior to installing the latest version. Once done, if CLR still does not load, copy the "lib" folder into the same folder that CLR is located. That typically will take care of it.
SCM - Make sure you have .NET 4 installed and working properly. There are .NET cleaners and installers available from Microsoft. I linked them in the http://stodps.com thread containing the parser. Once the .NET issues are resolved, click the installer and you're off. For some people, UAC may prevent you from opening/reading the log. Either set UAC to a level comfortable to your liking, or SHIFT-RIGHT CLICK and select Run as Administrator to get it to run properly.
As a good practice, rename your Combat.log file after every run. I use YYYY-MM-DD_MAP_Toon_NOTES.log for ease of filing, because I'm TRIBBLE like that
Both logs have their pro's and con's right now, of which most of it is due to features and aesthetics. You have your favorite, you can continue to use it.
For those who will slam SCM because it doesn't do 'this or that', neither did CLR when it was first implemented. Remember, we're comparing one program that has had years of development, testing, improvements, and collaboration, vs something that has been out for a few weeks.
~~ BIAS ~~
I am excited to see what SCM will come out with in their future versions. I am also interested to see if CLR will continue to be refined in the coming months.
We prefer Capitalism, which means we can say anything we want about your product as long as it's true.
I also prefer capitalism, which is why I side with the product that best serves my self interests, a product that is easy to use, causes no performance issues, and gives me the most detailed data possible.
That product is CLR.
In a free market of products and ideas, when you make incorrect claims, it's worse than the potential for libel or slander; It's the damage you do to your own credibility when confronted with a knowledgeable audience.
Agreed. This just works, hands down. Super effective stuff. My maintenance engineers use this to clean out plasma manifolds. It's a little known secret among Klingon maintenance crews. We get it smuggled in from Earth through Ferengi traders.
Agreed. This just works, hands down. Super effective stuff. My maintenance engineers use this to clean out plasma manifolds. It's a little known secret among Klingon maintenance crews. We get it smuggled in from Earth through Ferengi traders.
And, it makes good scotch.......no serious try it!
Comments
You should check if the Windows Defender or the realtime protection of your antivirus program is trying to scan the Combatlog.log-file, which is created by STO. That is often a reason for gamecrashes, when your STO is writing that file.
The CLR does only read that file and has no direct interaction with the game at all.
Parser: CombatLogReader (CLR)
Install/Launch Issues:
CLR - If you have any issues w/ CLR, first, uninstall any older versions of Java, then install the latest version. In extreme cases, you may need a Java removal tool prior to installing the latest version. Once done, if CLR still does not load, copy the "lib" folder into the same folder that CLR is located. That typically will take care of it.
SCM - Make sure you have .NET 4 installed and working properly. There are .NET cleaners and installers available from Microsoft. I linked them in the http://stodps.com thread containing the parser. Once the .NET issues are resolved, click the installer and you're off. For some people, UAC may prevent you from opening/reading the log. Either set UAC to a level comfortable to your liking, or SHIFT-RIGHT CLICK and select Run as Administrator to get it to run properly.
As a good practice, rename your Combat.log file after every run. I use YYYY-MM-DD_MAP_Toon_NOTES.log for ease of filing, because I'm TRIBBLE like that
Both logs have their pro's and con's right now, of which most of it is due to features and aesthetics. You have your favorite, you can continue to use it.
For those who will slam SCM because it doesn't do 'this or that', neither did CLR when it was first implemented. Remember, we're comparing one program that has had years of development, testing, improvements, and collaboration, vs something that has been out for a few weeks.
~~ BIAS ~~
I am excited to see what SCM will come out with in their future versions. I am also interested to see if CLR will continue to be refined in the coming months.
Fleet Defiant Kinetic Heavy Fire Support | Fleet Manticore Kinetic Strike Ship | Tactical Command Kinetic Siege Refit | Fleet Defiant Quantum Phase Escort | Fleet Valiant Kinetic Heavy Fire Support
Turning the Galaxy-X into a Torpedo Dreadnought & torpedo tutorial, with written torpedo guide.
"A good weapon and a great strategy will win you many battles." - Marshall
I knew using Kinetics would be playing the game on hard mode, but what I didn't realize was how bad the deck is stacked against Kinetics.
The download link for SCM is https://www.dropbox.com/s/0q2wjehs597m938/SCM_Beta_Setup.zip?dl=0
More information can be found at http://stodps.com/sto-combat-meter/
Got it, thanks! I think I was being dished up a cached page or something. This link works fine.
It's pretty nice. I like the player summary particularly. It is a bit slow first loading up but never hurts to trim a couple weeks off the logs.
Also, both parsers clean log files, has never worked for me!
Praetor of the -RTS- Romulan Tal Shiar fleet!
I am only ever able to clean the log file when I start up CLR. After that, it remains greyed out.
For myself it is never greyed out, but when I click on it, it always comes back with some failure report.
I have to literally, clean them manually, that or delete them!
Praetor of the -RTS- Romulan Tal Shiar fleet!
I also prefer capitalism, which is why I side with the product that best serves my self interests, a product that is easy to use, causes no performance issues, and gives me the most detailed data possible.
That product is CLR.
In a free market of products and ideas, when you make incorrect claims, it's worse than the potential for libel or slander; It's the damage you do to your own credibility when confronted with a knowledgeable audience.
Agreed. This just works, hands down. Super effective stuff. My maintenance engineers use this to clean out plasma manifolds. It's a little known secret among Klingon maintenance crews. We get it smuggled in from Earth through Ferengi traders.
And, it makes good scotch.......no serious try it!
[Sarcasm at no additional charge]
Praetor of the -RTS- Romulan Tal Shiar fleet!