No overlays in game about decktracker HOT 130 OPEN

@here If anyone in this thread knows programming and can compile the source code, please reproduce this issue locally and try to find the problem.

from decktracker.

@extesy I just had this issue too but managed to solve it somehow. I'll share the circumstances in case it's helpful.

I was installing on two identical computers, both Windows 10, one using Windows Defender and one using Bitdefender. Notably, both programs flagged the tracker as a virus despite the latest update.

On the Bitdefender computer, I downloaded the executable first; Bitdefender flagged it when installing, I told it to allow, but then I experienced the issue described in this thread when attempting to connect to ESL. I ended up fixing it (?) by installing using the MSI.

On the second computer, I started with the MSI, Windows Defender flagged it, I told it to allow, but the installation didn't occur. No folder where it was expected, no start menu shortcut, etc. I ran it several times, tried downloading it again, but no luck. I installed Bitdefender in case Windows Defender was the problem, but it still didn't work. Using the EXE led to the same connection issue as before, but since the MSI wasn't working at all I focused on that - eventually I got it to work by running the EXE, closing it, and then opening it from the start menu shortcut. Incidentally, I had to close Firefox for the app to access the clipboard - not sure if it could have also affected the other problem.

This all makes very little sense to me - the problems and solutions on the two computers seemed totally arbitrary. Hopefully it's of at least some help to you and the other commenters in tracking down the underlying cause. Let me know if you want any more info from me.

from decktracker.

Above messager said:
I fixed this today, not sure what was causing it but I changed a variable in the config file in AppData/Roaming/UniversalDeckTracker called isVisible to true which was set to false and now the running message is in green instead of red and everything is working properly.

My appdata/roaming/universaldecktracker is just empty.. where would I be able to find it ?? see if that helps

from decktracker.

@Vampiricangeluk It gave an error that it was unable to access the clipboard when I clicked on the export button. See #77

from decktracker.

icudesu I had the same problem as you have installed acces runtime and it works https://www.microsoft.com/en-us/download/details.aspx?id=50040 Here you have a link to the program I hope it helps

from decktracker.

@abhartman A few questions:

1. Are you starting the tracker before the game?
2. Does it show "detected running game" label in the top right corner while the game is running?
3. What color is this label while the game is running?
4. Please check if there is an error.log file in C:\Users\{profile}\AppData\Roaming\UniversalDeckTracker folder.
5. Do you have any 3rd party antivirus running?

from decktracker.

1. Yes, starting the tracker as Admin before game. Tried running the game both from desktop link and steam library.
2. It does show detected game as Eternal.
3. The label is Red while the game is running.
4. No error log in the location you listed. Folder is empty.
5. Only using Windows Defender.
6. Windows 10 Home

from decktracker.

This is helpful, thank you. By some reason the tracker detects the game but fails to communicate with it after it starts. The default timeout is 5sec, I'll try increasing it to 10sec for the next version to see if that helps.

from decktracker.

Great! I'll try it out tonight and see if I can get the overlays. Just to be clear, what is the appropriate method for using the tracker? It seems like opening the tracker is needed before starting the game, correct? Are there any other requirements, like windowed mode, resolution, settings, etc?

from decktracker.

No special requirements that I know of. Several people (not a big sample, though) has been using it already without any problems. The only issue I encountered so far is that some external antiviruses mess with the installation. If version 1.0.14 still doesn't work for you when you start it before the game then please try starting the game first and then (after you skip through all intro videos) the tracker.

from decktracker.

@abhartman try version 1.0.15, I fixed one bug that might be related to the issue you experience.

from decktracker.

Ok, I updated, tried uninstalling and reinstalling. I'm now on the 1.0.15, but it's still red when the game is running. It detects Eternal, but that's it. I did get a popup briefly saying that windows defender had stopped malware, but I uninstalled and reinstalled and haven't seen that again. I feel like there's something stupid that I'm overlooking :(

from decktracker.

It actually might be windows defender blocking the app by some reason. Can you try adding this folder to the exclusions - C:\Users\{YourProfile}\AppData\Local\UniversalDeckTracker\? If it still doesn't help then please try debug mode and send me the trace logs.

from decktracker.

Still no luck :( I added " --debug" to the end of the target property of the desktop shortcut, as such:

C:\Users\Adam\AppData\Local\UniversalDeckTracker\UniversalDeckTracker.exe --debug

Didn't get any errors when opening that shortcut, and the tracker opened. The tracker still has red text indicating that Eternal was detected. I couldn't see any files in the AppData\Roaming\UniversalDeckTracker folder.

from decktracker.

I got the attached image as a Windows Defender message regarding v1.0.14 just now. I recently tried installing v1.0.16, which has the same symptoms as other versions.

from decktracker.

Yeah, that's because the installer is packed for smaller distributive. Windows Defender is over-eager and identifies it as a threat, that's because there are very few downloads so far so it doesn't yet have enough statistics about it yet. It's not deterministic, though - on some machines WD complains, on some machines it doesn't. It might be the reason why deck tracker doesn't work on your machine. As I mentioned above, please try adding the folder above to WD exclusions.

from decktracker.

I'm updating here that I'm still not able to get the tracker to show overlays. The install proceeds fine, I've added exclusions for C:\Users{YourProfile}\AppData\Local\UniversalDeckTracker, and have also tried debug mode. Debug does not produce any output in the expected folder.

from decktracker.

I just uninstalled all versions, and installed the latest version. Same symptoms. Deck tracker runs, starts out with blue text saying it detected Eternal, then switching to red text.

from decktracker.

@abhartman I'm really out of ideas right now and don't know what's going on, I'm sorry. Can you try running UniversalDeckTracker.exe as administrator? Little chance of success, but I don't have any better suggestions :(

By the way, how many seconds does "detected game" label stay blue before it turns red? Is it turning red immediately, is it after 3 seconds or after 10 seconds?

from decktracker.

@extesy I've been using run as admin as much as I remember to, but I'll try again just to be sure. As for the time that the detected game label stays blue, I'm not sure. I'll run in Windowed mode and see how long it takes, then report back.

from decktracker.

@extesy I tried again last night with a fresh install of your tool (uninstalled previous version, d/l latest version and the nupkg files). I made sure both local and roaming Universal Deck Tracker folders were on Windows Defender exclusion list, and the Deck Tracker .exe was on the list as well.

I had the same symptoms. Deck Tracker would start just fine, would see Eternal as a game and say so with blue text. The text turns red after Eternal is done "loading" and when it gets to the start of the DWD splash screen. I started Eternal from my desktop icon, not directly through steam, if that's important.

I used the --debug option for the Universal Deck Tracker shortcut, but saw no evidence of a log file being created at all. Does the log happen even if there are no errors? If so, can you give me some more details on just how to make a log? It seems suspicious to me that there's nothing at all being logged, even though the program is opening fine and temporarily seeing Eternal running.

from decktracker.

Bumping this as I'm experiencing the same issues as @abhartman

from decktracker.

@jonathanFinnell have you had any improvements with the 1.0.26 or 1.0.27 versions? Are you getting a log file at least?

from decktracker.

I'm using 1.0.27. No log files are being generated, at least not in AppData/Roaming. I tried running it as Administrator as well as a couple of Compatability modes (Win 7/8) but neither helped.

from decktracker.

Log file is generated only when a connection is established between deck tracker and a game client. Since connection is established in two phases, I need to know which phase is not working, that's why I asked a question above about 3 vs 10 seconds between blue and red labels.

PS: I'll add more detailed logging to the offline portion of the tracker so that more diagnostics data is available to help with situations like this one.

from decktracker.

By the way, how fast are your machines (what CPU)? Also, are you using SSDs or hard drives? There is a potential timing problem in the very beginning that might be triggered if game files are not loaded fast enough.

from decktracker.

@extesy My machine isn't super fast, but it's only a couple years old. Definitely NOT a SSD. Here are the specs: AMD A8-5550M APU w/ Radeon HD Graphics 2.10 GHz, 8 GB RAM, 64 bit Windows 10 Home OS.

from decktracker.

I've added more logging in release 1.0.29 - can you please try it (with --debug option) and let me know if you see the events.log file being generated now when you start Eternal?

from decktracker.

I was able to get a log file with the latest release.

2017-06-10T02:03:57.2297879Z|Eternal|Debug|Injection state changed: Injecting
2017-06-10T02:04:00.2377736Z|Eternal|Debug|Injecting Helper.dll
2017-06-10T02:04:00.2503351Z|Eternal|Debug|Injected Helper.dll, waiting for response
2017-06-10T02:04:10.2718567Z|Eternal|Debug|Injection state changed: Failed

My CPU is Intel i5-6600K CPU @ 3.50GHz. I could try moving Eternal onto my SSD to see if that helps. The decktracker is on a different drive from the game if that might cause a timing issue.

Update: Switching to SSD made Eternal load faster, but having the same issue with the tracker.

from decktracker.

@jonathanFinnell Yes, please try moving Eternal to SSD. It doesn't matter where the deck tracker is installed since it's quite small compared to the game itself.

from decktracker.

With regards to your earlier question, it's definitely closer to 10 seconds than 3 when it changes from blue to red

from decktracker.

Yeah, I can see that now from timestamps in the log. Now I'm thinking what might be causing it. Please let me know if moving the game to SSD helps.

from decktracker.

Moving to SSD didn't change anything and the new logs don't show anything different

from decktracker.

That's unfortunate. But at least it rules out the performance theory. Let me think what else might go wrong...

from decktracker.

@
events.txt

I've recently updated to the latest version and run w/ the --debug option. My events.log file is attached. Looks like it's failing to inject your .dll.

from decktracker.

@abhartman is there also errors.log file in the same folder? If not then it seems that very first phase of dll injection fails on your machine by some reason. It could be something specific with your setup: firewall, antivirus, some user-level restrictions (no admin rights, etc). Basically, deck tracker is trying to get access to the game process in order to load its own dll but something prevents this from happening. I'll add even more logging in the injection helper to find out which step fails.

But just FYI: so far I saw 100+ people used the tracker successfully, that means whatever is causing the problem on your machine - it's rare. And rare bugs are difficult (although not impossible) to find and fix.

from decktracker.

Latest Logfile

2017-06-20T03:42:42.8446670Z|Eternal|Debug|Injection state changed: Injecting
2017-06-20T03:42:42.9804844Z|Eternal|Debug|Injecting DeckTracker.InGame.Helper.dll
2017-06-20T03:42:42.9944496Z|Eternal|Debug|WaitForSingleObject finished with result 0
2017-06-20T03:42:42.9974479Z|Eternal|Debug|Injected DeckTracker.InGame.Helper.dll, waiting for response
2017-06-20T03:42:53.0117471Z|Eternal|Debug|Injection state changed: Failed

Looks like the OS is saying the decktracker has control, but hasn't actually relinquished it?

There is no errors.log file, and I've made sure the deck tracker is excluded on both my firewall and antivirus. Let me know if there are any other local settings I can check.

from decktracker.

@jonathanFinnell your symptoms are different from @abhartman's. In your case injection succeeds but network connection can't be established between the tracker and the game. In @abhartman's case the injection itself fails so the added logging should help narrow down the problem.

Can you please run netstat -an command (without the game running) and check if you have port 50001 or 50002 in the list? If you do then please run netstat -anb and check the process name for that port.

from decktracker.

Not seeing anything on those ports with or without the game or the tracker running. Eternal is using 54925-54927 and 54929.

from decktracker.

Things have definitely changed in 1.0.41. Now the tracker stays blue for longer, flashes red for a second, stays blue for a while, then settles on red. Logs corroborate this.

2017-06-21T05:55:01.2992820Z|Eternal|Debug|Injection state changed: Injecting
2017-06-21T05:55:01.4728615Z|Eternal|Debug|Injecting DeckTracker.InGame.Helper.dll
2017-06-21T05:55:01.4843926Z|Eternal|Debug|Waiting for remote thread finished with result 0
2017-06-21T05:55:01.4879032Z|Eternal|Debug|Injected DeckTracker.InGame.Helper.dll, waiting for response
2017-06-21T05:55:21.4944806Z|Eternal|Debug|Injection state changed: Failed
2017-06-21T05:55:22.3827959Z|Eternal|Debug|Injection state changed: Injecting
2017-06-21T05:55:22.5516908Z|Eternal|Debug|Injecting DeckTracker.InGame.Helper.dll
2017-06-21T05:55:22.5582118Z|Eternal|Debug|Waiting for remote thread finished with result 0
2017-06-21T05:55:22.5613872Z|Eternal|Debug|Injected DeckTracker.InGame.Helper.dll, waiting for response
2017-06-21T05:55:42.5799063Z|Eternal|Debug|Injection state changed: Failed

from decktracker.

Thanks for checking! I've adjusted timeouts in 1.0.41 but it shouldn't have cause that effect. This is so weird... The transition from Failed to Injected is only possible if game process exited. I assume you didn't quit the game process for 1 second, so I keep looking at the source code and just can't understand wtf is going on.

Why would .NET think that the game process has exited? Do you have any security/system software installed on your machine that might be causing this? Is your windows user restricted somehow (not a main default Windows user)?

from decktracker.

Upon further inspection, it's likely that my internet just cut out right when I was connecting to the game server, which restarted Eternal for some reason. All new logs show the same behavior as before the patch, but with longer times before it fails.

from decktracker.

@extesy I'll look and see if there's an errors.log file, but I don't recall seeing it. I haven't updated to the latest build, but I can VPN in to my machine from work and try to update and run. Let me see what I can discover. Every time I install the newest version, I get the same Windows Defender message saying that it prevented the install and I have to manually tell it to proceed anyways. Is it maybe getting flagged as a suspicious program and not running properly? I still see the Deck Tracker Window, so I doubt that's the problem. I have exceptions in Windows Defender, but maybe not the right ones or enough of them? Does it matter that my home router uses some filtering to protect our kids' tablets from adult content?

from decktracker.

@abhartman latest build (1.0.41) shouldn't cause any windows defender warning anymore. The router settings don't matter, only the configuration on the machine where you are running the game and the tracker.

from decktracker.

Ok, I tried a clean install with 1.0.41, with not much difference. Initial install still had a Windows Defender SmartScreen notice that I had to override to continue. After installing, the text in the window was red and never blue that I could see. The events.log file is copy-pasted below:

2017-06-18T20:38:32.1486530Z|Eternal|Debug|Injection state changed: Injecting
2017-06-18T20:38:32.4150752Z|Eternal|Debug|Injection state changed: Idle
2017-06-22T02:12:35.3290300Z|Eternal|Debug|Injection state changed: Injecting
2017-06-22T02:12:35.5168792Z|Eternal|Debug|Injecting DeckTracker.InGame.Helper.dll
2017-06-22T02:12:35.5274168Z|Eternal|Debug|CreateToolhelp32Snapshot failed with error 299
2017-06-22T02:12:35.5294173Z|Eternal|Debug|GetProcessModuleHandle failed with error 299
2017-06-22T02:12:35.5308868Z|Eternal|Debug|GetProcessProcAddress failed with error 299
2017-06-22T02:12:35.5324194Z|Eternal|Debug|Injection state changed: Failed

There was no errors.log file.

from decktracker.

@abhartman Ok, I'm getting closer now. According to documentation error code 299 means that "the specified process is a 64-bit process and the caller is a 32-bit process". As far as I'm aware, Eternal/TESL is supposed to be a 32-bit process. So this error might mean either of two things:

1. The game somehow runs in 64-bit mode on your machine. To confirm this please start the game, then open Task Manager and find Eternal.exe. Does it have "(32 bit)" in the name or not?
2. The tracker is trying to attach to a wrong process. Do you happen to have any processes running on your machine that have "Eternal" in their name?

from decktracker.

I got error 209 once too, and Eternal process was 32 bit and I couldn't find any processes running with 'eternal' in their name. Problem is, I got this error just once, other times it looks just like this:
2017-06-22T10:15:26.8657682Z|Eternal|Debug|Injection state changed: Injecting 2017-06-22T10:15:27.0364812Z|Eternal|Debug|Injecting DeckTracker.InGame.Helper.dll 2017-06-22T10:15:27.0414872Z|Eternal|Debug|Waiting for remote thread finished with result 0 2017-06-22T10:15:27.0444912Z|Eternal|Debug|Injected DeckTracker.InGame.Helper.dll, waiting for response 2017-06-22T10:15:47.0560164Z|Eternal|Debug|Injection state changed: Failed 2017-06-22T10:16:02.6603253Z|Eternal|Debug|Injection state changed: Injecting 2017-06-22T10:16:02.7219650Z|Eternal|Debug|Injection state changed: Idle

I tried turning off Windows Defender and it still didn't help. Maybe you could add some more debug logging to check out when and why something fails? I also thought about adding switch to the executable to specify which ports should it use for connection, to check out if some different port would work.

If I can be of any help, I'll be glad to do it :)

from decktracker.

@extesy the program running in task manager is (32 Bit), and there is no other program called eternal other than eternal.exe.

from decktracker.

I tried starting the tracker before I started Eternal, and got this event.log:

2017-06-18T20:38:32.1486530Z|Eternal|Debug|Injection state changed: Injecting
2017-06-18T20:38:32.4150752Z|Eternal|Debug|Injection state changed: Idle
2017-06-22T02:12:35.3290300Z|Eternal|Debug|Injection state changed: Injecting
2017-06-22T02:12:35.5168792Z|Eternal|Debug|Injecting DeckTracker.InGame.Helper.dll
2017-06-22T02:12:35.5274168Z|Eternal|Debug|CreateToolhelp32Snapshot failed with error 299
2017-06-22T02:12:35.5294173Z|Eternal|Debug|GetProcessModuleHandle failed with error 299
2017-06-22T02:12:35.5308868Z|Eternal|Debug|GetProcessProcAddress failed with error 299
2017-06-22T02:12:35.5324194Z|Eternal|Debug|Injection state changed: Failed
2017-06-22T02:27:03.0181020Z|Eternal|Debug|Injection state changed: Injecting
2017-06-22T02:27:03.1401818Z|Eternal|Debug|Injection state changed: Idle
2017-06-23T01:50:22.4422777Z|Eternal|Debug|Injection state changed: Injecting
2017-06-23T01:50:22.6883181Z|Eternal|Debug|Injecting DeckTracker.InGame.Helper.dll
2017-06-23T01:50:22.8728355Z|Eternal|Debug|Waiting for remote thread finished with result 0
2017-06-23T01:50:22.8748351Z|Eternal|Debug|Injected DeckTracker.InGame.Helper.dll, waiting for response
2017-06-23T01:50:42.8975723Z|Eternal|Debug|Injection state changed: Failed
2017-06-23T01:59:01.6261175Z|Eternal|Debug|Injection state changed: Injecting
2017-06-23T01:59:01.7180520Z|Eternal|Debug|Injection state changed: Idle

from decktracker.

I will join the testing ... Win 7/64bit. After launching v1.0.42 received the following contents of the file events.log: (Problems with the Russian language, probably, will not be?:))
2017-06-23T05:38:12.2452092Z|Eternal|Debug|Game process: Eternal C:\Program Files (x86)\Steam\steamapps\common\Eternal Card Game\Eternal.exe
2017-06-23T05:38:12.2562098Z|Eternal|Debug|Injection state changed: Injecting
2017-06-23T05:38:12.3272139Z|Eternal|Debug|SocketStreamClient.Start
2017-06-23T05:38:12.4312198Z|Eternal|Debug|SocketStreamClient.SendCommand(Ping) timeout, sent=False connected=False
2017-06-23T05:38:12.4312198Z|Eternal|Debug|Injecting DeckTracker.InGame.Helper.dll
2017-06-23T05:38:12.4472207Z|Eternal|Debug|Waiting for remote thread finished with result 0
2017-06-23T05:38:12.4482208Z|Eternal|Debug|Injected DeckTracker.InGame.Helper.dll, waiting for response
2017-06-23T05:38:13.3342715Z|Eternal|Debug|SocketStreamClient disconnected: Подключение не установлено, т.к. конечный компьютер отверг запрос на подключение 127.0.0.1:50002
2017-06-23T05:38:14.3353287Z|Eternal|Debug|SocketStreamClient disconnected: Подключение не установлено, т.к. конечный компьютер отверг запрос на подключение 127.0.0.1:50002
2017-06-23T05:38:15.3353859Z|Eternal|Debug|SocketStreamClient disconnected: Подключение не установлено, т.к. конечный компьютер отверг запрос на подключение 127.0.0.1:50002
2017-06-23T05:38:16.3354431Z|Eternal|Debug|SocketStreamClient disconnected: Подключение не установлено, т.к. конечный компьютер отверг запрос на подключение 127.0.0.1:50002
2017-06-23T05:38:17.3385005Z|Eternal|Debug|SocketStreamClient disconnected: Подключение не установлено, т.к. конечный компьютер отверг запрос на подключение 127.0.0.1:50002
2017-06-23T05:38:18.3415579Z|Eternal|Debug|SocketStreamClient disconnected: Подключение не установлено, т.к. конечный компьютер отверг запрос на подключение 127.0.0.1:50002
2017-06-23T05:38:19.3426151Z|Eternal|Debug|SocketStreamClient disconnected: Подключение не установлено, т.к. конечный компьютер отверг запрос на подключение 127.0.0.1:50002
2017-06-23T05:38:20.3426723Z|Eternal|Debug|SocketStreamClient disconnected: Подключение не установлено, т.к. конечный компьютер отверг запрос на подключение 127.0.0.1:50002
2017-06-23T05:38:21.3427295Z|Eternal|Debug|SocketStreamClient disconnected: Подключение не установлено, т.к. конечный компьютер отверг запрос на подключение 127.0.0.1:50002
2017-06-23T05:38:22.3437868Z|Eternal|Debug|SocketStreamClient disconnected: Подключение не установлено, т.к. конечный компьютер отверг запрос на подключение 127.0.0.1:50002
2017-06-23T05:38:23.3358435Z|Eternal|Debug|SocketStreamClient disconnected: Подключение не установлено, т.к. конечный компьютер отверг запрос на подключение 127.0.0.1:50002
2017-06-23T05:38:24.3359007Z|Eternal|Debug|SocketStreamClient disconnected: Подключение не установлено, т.к. конечный компьютер отверг запрос на подключение 127.0.0.1:50002
2017-06-23T05:38:25.3369580Z|Eternal|Debug|SocketStreamClient disconnected: Подключение не установлено, т.к. конечный компьютер отверг запрос на подключение 127.0.0.1:50002
2017-06-23T05:38:26.3380152Z|Eternal|Debug|SocketStreamClient disconnected: Подключение не установлено, т.к. конечный компьютер отверг запрос на подключение 127.0.0.1:50002
2017-06-23T05:38:27.3390725Z|Eternal|Debug|SocketStreamClient disconnected: Подключение не установлено, т.к. конечный компьютер отверг запрос на подключение 127.0.0.1:50002
2017-06-23T05:38:28.3411298Z|Eternal|Debug|SocketStreamClient disconnected: Подключение не установлено, т.к. конечный компьютер отверг запрос на подключение 127.0.0.1:50002
2017-06-23T05:38:29.3551878Z|Eternal|Debug|SocketStreamClient disconnected: Подключение не установлено, т.к. конечный компьютер отверг запрос на подключение 127.0.0.1:50002
2017-06-23T05:38:30.7002647Z|Eternal|Debug|SocketStreamClient disconnected: Подключение не установлено, т.к. конечный компьютер отверг запрос на подключение 127.0.0.1:50002
2017-06-23T05:38:31.7003219Z|Eternal|Debug|SocketStreamClient disconnected: Подключение не установлено, т.к. конечный компьютер отверг запрос на подключение 127.0.0.1:50002
2017-06-23T05:38:32.4493648Z|Eternal|Debug|SocketStreamClient.SendCommand(Ping) timeout, sent=False connected=False
2017-06-23T05:38:32.4493648Z|Eternal|Debug|Injection state changed: Failed
2017-06-23T05:38:32.6263749Z|Eternal|Debug|SocketStreamClient.Stop

from decktracker.

@SergeRaz Russian language shouldn't matter. Is there also error.log file available?

from decktracker.

File error.log is not in the folder Roaming, nor in the folder Local.

from decktracker.

Hi,
I have two types of error. Sometimes tracker crashes when I start TESL, at other time the blue text change to red and nothing happen. There isn't error.log just events.txt.

https://pastebin.com/61DHpjZi

from decktracker.

OK, I think I got it. The problem is with UTF-8 characters in the path. My user name contains polish character ('Ł'), after I've copied directory with tracker from my users folder to one that didn't contain polish characters everything started working without problem :)

from decktracker.

@lukepolak That's great to know, thanks for confirming! @jonathanFinnell do you by any chance have a user profile with unicode characters?

from decktracker.

@jonathanFinnell @SergeRaz @bolem87 Try release 1.0.43 and please confirm if it helps or not.

from decktracker.

I did not, though mine did have a space in it. Removing the space did improve the situation. I am now able to get to this state.

2017-06-24T02:57:34.0583757Z|Eternal|Debug|Injection state changed: Injecting
2017-06-24T02:57:34.1195436Z|Eternal|Debug|SocketStreamClient.Start
2017-06-24T02:57:34.2294703Z|Eternal|Debug|SocketStreamClient.SendCommand(Ping) timeout, sent=False connected=False
2017-06-24T02:57:34.2319926Z|Eternal|Debug|Injecting DeckTracker.InGame.Helper.dll
2017-06-24T02:57:34.2430070Z|Eternal|Debug|Waiting for remote thread finished with result 0
2017-06-24T02:57:34.2465159Z|Eternal|Debug|Injected DeckTracker.InGame.Helper.dll, waiting for response
2017-06-24T02:57:35.1253068Z|Eternal|Debug|SocketStreamClient disconnected: No connection could be made because the target machine actively refused it 127.0.0.1:50002
(Repeat the above line several times)
2017-06-24T02:57:54.2611146Z|Eternal|Debug|SocketStreamClient.SendCommand(Ping) timeout, sent=False connected=False
2017-06-24T02:57:54.2645487Z|Eternal|Debug|Injection state changed: Failed
2017-06-24T02:57:54.3237019Z|Eternal|Debug|SocketStreamClient.Stop

This entire section appears twice for some reason. I've made sure the tracker is excluded on both my firewall and by windows defender. I checked netstat and there is nothing using port 50002.

from decktracker.

Without changes.
2017-06-24T19:11:43.4473854Z|Eternal|Debug|Game process: Eternal C:\Program Files (x86)\Steam\steamapps\common\Eternal Card Game\Eternal.exe
2017-06-24T19:11:43.4573860Z|Eternal|Debug|Injection state changed: Injecting
2017-06-24T19:11:43.5093889Z|Eternal|Debug|SocketStreamClient.Start
2017-06-24T19:11:43.6903993Z|Eternal|Debug|SocketStreamClient.SendCommand(Ping) timeout, sent=False connected=False
2017-06-24T19:11:43.6903993Z|Eternal|Debug|Injecting DeckTracker.InGame.Helper.dll
2017-06-24T19:11:44.0544201Z|Eternal|Debug|Waiting for remote thread finished with result 0
2017-06-24T19:11:44.0554202Z|Eternal|Debug|Injected DeckTracker.InGame.Helper.dll, waiting for response
2017-06-24T19:11:44.7074575Z|Eternal|Debug|SocketStreamClient disconnected: Подключение не установлено, т.к. конечный компьютер отверг запрос на подключение 127.0.0.1:50002
...
2017-06-24T19:12:03.7815484Z|Eternal|Debug|SocketStreamClient disconnected: Подключение не установлено, т.к. конечный компьютер отверг запрос на подключение 127.0.0.1:50002
2017-06-24T19:12:04.0765653Z|Eternal|Debug|SocketStreamClient.SendCommand(Ping) timeout, sent=False connected=False
2017-06-24T19:12:04.0765653Z|Eternal|Debug|Injection state changed: Failed
2017-06-24T19:12:04.4375860Z|Eternal|Debug|SocketStreamClient.Stop

from decktracker.

My problem looks to be similar or the same than abhartmans. DeckTracker wont work for TES Legends. The game label is red and I'm using Windows 10 with Windows Defender as well if that's a problem somehow

from decktracker.

I'm having the same connection error as finnell and sorge.

from decktracker.

I'm sorry guys, I really want to figure out what's causing this issue and fix it, but right now I don't have any new ideas to try. I'm planning to publish the source code soon and then hopefully someone else might try to reproduce this issue and fix it.

from decktracker.

Something I noticed that may or may not be helpful, is that when I run netstat with the deck tracker running, I don't see it listed as one of the processes on the network, regardless of whether Eternal is running or not. I appreciate you doing what you can and thanks for sticking with us this far.

from decktracker.

I would love to take a look in your code. So the problem is in the createToolHelp32snapshot function, right? It throws error 299 and so firstProcess32 and firstModule32 also fail, right? That is what events.log says. No snapshot, no injection.
So, I compile a 32 bit program in my windows 10 x64 box to take a snapshot of the (already open) 32-bit tes legend process and I don't get the 299 error. I didn't even put the createToolHelp32snapshot function in a loop. I wonder why your code isn't working to me. Here is the code that I compiled with mingw32, it it helps:

//it filters so that only modules exclusive to the tes legends process is shown
#include <windows.h>
#include <tlhelp32.h>
#include <tchar.h>
#include <stdio.h>
#include <string.h>

//  Forward declarations:
BOOL GetProcessList( );
BOOL ListProcessModules( DWORD dwPID );
//BOOL ListProcessThreads( DWORD dwOwnerPID );
void printError( TCHAR* msg );

int main( void )
{
  GetProcessList( );
  return 0;
}

BOOL GetProcessList( )
{
  HANDLE hProcessSnap;
  HANDLE hProcess;
  PROCESSENTRY32 pe32;
  DWORD dwPriorityClass;

  // Take a snapshot of all processes in the system.
  hProcessSnap = CreateToolhelp32Snapshot( TH32CS_SNAPPROCESS, 0 );
  if( hProcessSnap == INVALID_HANDLE_VALUE )
  {
    printError( TEXT("CreateToolhelp32Snapshot (of processes)") );
    return( FALSE );
  }

  // Set the size of the structure before using it.
  pe32.dwSize = sizeof( PROCESSENTRY32 );

  // Retrieve information about the first process,
  // and exit if unsuccessful
  
  if( !Process32First( hProcessSnap, &pe32 ) )
  {
    printError( TEXT("Process32First") ); // show caus of failure
    CloseHandle( hProcessSnap );          // clean the snapshot object
    return( FALSE );
  }
  // Now walk the snapshot of processes, and
  // display information about each process in turn
    do
    {
        if (stricmp(pe32.szExeFile, "The Elder Scrolls Legends.exe") == 0){
            printf( TEXT("\n\n=====================================================" ));
            printf( TEXT("\nPROCESS NAME:  %s"), pe32.szExeFile );
            printf( TEXT("\n-------------------------------------------------------" ));

            // Retrieve the priority class.
            dwPriorityClass = 0;
            hProcess = OpenProcess( PROCESS_ALL_ACCESS, FALSE, pe32.th32ProcessID );
            if( hProcess == NULL )
              printError( TEXT("OpenProcess") );
            else
            {
              dwPriorityClass = GetPriorityClass( hProcess );
              if( !dwPriorityClass )
                printError( TEXT("GetPriorityClass") );
              CloseHandle( hProcess );
            }

            printf( TEXT("\n  Process ID        = 0x%08X"), pe32.th32ProcessID );
      //      printf( TEXT("\n  Thread count      = %d"),   pe32.cntThreads );
            printf( TEXT("\n  Parent process ID = 0x%08X"), pe32.th32ParentProcessID );
            printf( TEXT("\n  Priority base     = %d"), pe32.pcPriClassBase );
            if( dwPriorityClass )
              printf( TEXT("\n  Priority class    = %d"), dwPriorityClass );

            // List the modules and threads associated with this process
            ListProcessModules( pe32.th32ProcessID );
      //      ListProcessThreads( pe32.th32ProcessID );
        }
    } while( Process32Next( hProcessSnap, &pe32 ) );

    CloseHandle( hProcessSnap );
    return( TRUE );
  }


BOOL ListProcessModules( DWORD dwPID )
{
  HANDLE hModuleSnap = INVALID_HANDLE_VALUE;
  MODULEENTRY32 me32;

  // Take a snapshot of all modules in the specified process.
  hModuleSnap = CreateToolhelp32Snapshot( TH32CS_SNAPMODULE, dwPID );
  if( hModuleSnap == INVALID_HANDLE_VALUE )
  {
    printError( TEXT("CreateToolhelp32Snapshot (of modules)") );
    return( FALSE );
  }

  // Set the size of the structure before using it.
  me32.dwSize = sizeof( MODULEENTRY32 );

  // Retrieve information about the first module,
  // and exit if unsuccessful
  if( !Module32First( hModuleSnap, &me32 ) )
  {
    printError( TEXT("Module32First") );  // show cause of failure
    CloseHandle( hModuleSnap );           // clean the snapshot object
    return( FALSE );
  }

  // Now walk the module list of the process,
  // and display information about each module
  do{
      if (strstr(me32.szExePath,"C:\\W")){}
      else{
        printf( TEXT("\n\n     MODULE NAME:     %s"),   me32.szModule );
        printf( TEXT("\n     Executable     = %s"),     me32.szExePath );
        printf( TEXT("\n     Process ID     = 0x%08X"), me32.th32ProcessID );
        printf( TEXT("\n     Ref count (g)  = 0x%04X"), me32.GlblcntUsage );
        printf( TEXT("\n     Ref count (p)  = 0x%04X"), me32.ProccntUsage );
        printf( TEXT("\n     Base size      = %d"),     me32.modBaseSize );
      }
  } while( Module32Next( hModuleSnap, &me32 ) );

  CloseHandle( hModuleSnap );
  return( TRUE );
}

void printError( TCHAR* msg )
{
  DWORD eNum;
  TCHAR sysMsg[256];
  TCHAR* p;

  eNum = GetLastError( );
  FormatMessage( FORMAT_MESSAGE_FROM_SYSTEM | FORMAT_MESSAGE_IGNORE_INSERTS,
         NULL, eNum,
         MAKELANGID(LANG_NEUTRAL, SUBLANG_DEFAULT), // Default language
         sysMsg, 256, NULL );

  // Trim the end of the line and terminate it with a null
  p = sysMsg;
  while( ( *p > 31 ) || ( *p == 9 ) )
    ++p;
  do { *p-- = 0; } while( ( p >= sysMsg ) &&
                          ( ( *p == '.' ) || ( *p < 33 ) ) );

  // Display the message
  printf( TEXT("\n  WARNING: %s failed with error %d (%s)"), msg, eNum, sysMsg );
}

and it outputs all the modules exclusive to tes legends:

=====================================================
PROCESS NAME:  The Elder Scrolls Legends.exe
-------------------------------------------------------
  Process ID        = 0x000006E0
  Parent process ID = 0x00001F2C
  Priority base     = 8
  Priority class    = 32

     MODULE NAME:     The Elder Scrolls Legends.exe
     Executable     = C:\Program Files (x86)\Steam\steamapps\common\The Elder Scrolls Legends\The Elder Scrolls Legends.exe
     Process ID     = 0x000006E0
     Ref count (g)  = 0xFFFF
     Ref count (p)  = 0xFFFF
     Base size      = 19075072

     MODULE NAME:     gameoverlayrenderer.dll
     Executable     = C:\Program Files (x86)\Steam\gameoverlayrenderer.dll
     Process ID     = 0x000006E0
     Ref count (g)  = 0x0001
     Ref count (p)  = 0x0001
     Base size      = 1200128

     MODULE NAME:     tiptsf.dll
     Executable     = C:\Program Files (x86)\Common Files\Microsoft Shared\Ink\tiptsf.dll
     Process ID     = 0x000006E0
     Ref count (g)  = 0x0002
     Ref count (p)  = 0x0002
     Base size      = 503808

     MODULE NAME:     mono.dll
     Executable     = C:\Program Files (x86)\Steam\steamapps\common\The Elder Scrolls Legends\The Elder Scrolls Legends_Data\Mono\mono.dll
     Process ID     = 0x000006E0
     Ref count (g)  = 0x0001
     Ref count (p)  = 0x0001
     Base size      = 2297856

     MODULE NAME:     FreeTypePlugin.dll
     Executable     = C:\Program Files (x86)\Steam\steamapps\common\The Elder Scrolls Legends\The Elder Scrolls Legends_Data\Plugins\FreeTypePlugin.dll
     Process ID     = 0x000006E0
     Ref count (g)  = 0x000D
     Ref count (p)  = 0x000D
     Base size      = 798720

     MODULE NAME:     sqlite3.dll
     Executable     = C:\Program Files (x86)\Steam\steamapps\common\The Elder Scrolls Legends\The Elder Scrolls Legends_Data\Plugins\sqlite3.dll
     Process ID     = 0x000006E0
     Ref count (g)  = 0x000D
     Ref count (p)  = 0x000D
     Base size      = 770048

     MODULE NAME:     CSteamworks.dll
     Executable     = C:\Program Files (x86)\Steam\steamapps\common\The Elder Scrolls Legends\The Elder Scrolls Legends_Data\Plugins\CSteamworks.dll
     Process ID     = 0x000006E0
     Ref count (g)  = 0x000E
     Ref count (p)  = 0x000E
     Base size      = 155648

     MODULE NAME:     steam_api.dll
     Executable     = C:\Program Files (x86)\Steam\steamapps\common\The Elder Scrolls Legends\The Elder Scrolls Legends_Data\Plugins\steam_api.dll
     Process ID     = 0x000006E0
     Ref count (g)  = 0x0001
     Ref count (p)  = 0x0001
     Base size      = 233472

     MODULE NAME:     steamclient.dll
     Executable     = C:\Program Files (x86)\Steam\steamclient.dll
     Process ID     = 0x000006E0
     Ref count (g)  = 0x0001
     Ref count (p)  = 0x0001
     Base size      = 11288576

     MODULE NAME:     vstdlib_s.dll
     Executable     = C:\Program Files (x86)\Steam\vstdlib_s.dll
     Process ID     = 0x000006E0
     Ref count (g)  = 0x0001
     Ref count (p)  = 0x0001
     Base size      = 360448

     MODULE NAME:     tier0_s.dll
     Executable     = C:\Program Files (x86)\Steam\tier0_s.dll
     Process ID     = 0x000006E0
     Ref count (g)  = 0x0002
     Ref count (p)  = 0x0002
     Base size      = 1142784

     MODULE NAME:     steam.dll
     Executable     = C:\Program Files (x86)\Steam\steam.dll
     Process ID     = 0x000006E0
     Ref count (g)  = 0x0001
     Ref count (p)  = 0x0001
     Base size      = 1298432

     MODULE NAME:     Steam2.dll
     Executable     = C:\Program Files (x86)\Steam\Steam2.dll
     Process ID     = 0x000006E0
     Ref count (g)  = 0x0001
     Ref count (p)  = 0x0001
     Base size      = 2887680

     MODULE NAME:     DbgHelp.dll
     Executable     = C:\Program Files (x86)\Steam\DbgHelp.dll
     Process ID     = 0x000006E0
     Ref count (g)  = 0x0002
     Ref count (p)  = 0x0002
     Base size      = 1134592

     MODULE NAME:     CSERHelper.dll
     Executable     = C:\Program Files (x86)\Steam\CSERHelper.dll
     Process ID     = 0x000006E0
     Ref count (g)  = 0x0001
     Ref count (p)  = 0x0001
     Base size      = 135168

     MODULE NAME:     bnet-sdk-cpp-fingerprint.dll
     Executable     = C:\Program Files (x86)\Steam\steamapps\common\The Elder Scrolls Legends\The Elder Scrolls Legends_Data\Plugins\bnet-sdk-cpp-fingerprint.dll
     Process ID     = 0x000006E0
     Ref count (g)  = 0x0004
     Ref count (p)  = 0x0004
     Base size      = 622592

from decktracker.

I fixed this today, not sure what was causing it but I changed a variable in the config file in AppData/Roaming/UniversalDeckTracker called isVisible to true which was set to false and now the running message is in green instead of red and everything is working properly.

from decktracker.

I did an update to the latest version, uninstalled the old version, and got the following events.log output:

2017-06-18T20:38:32.1486530Z|Eternal|Debug|Injection state changed: Injecting
2017-06-18T20:38:32.4150752Z|Eternal|Debug|Injection state changed: Idle
2017-06-22T02:12:35.3290300Z|Eternal|Debug|Injection state changed: Injecting
2017-06-22T02:12:35.5168792Z|Eternal|Debug|Injecting DeckTracker.InGame.Helper.dll
2017-06-22T02:12:35.5274168Z|Eternal|Debug|CreateToolhelp32Snapshot failed with error 299
2017-06-22T02:12:35.5294173Z|Eternal|Debug|GetProcessModuleHandle failed with error 299
2017-06-22T02:12:35.5308868Z|Eternal|Debug|GetProcessProcAddress failed with error 299
2017-06-22T02:12:35.5324194Z|Eternal|Debug|Injection state changed: Failed
2017-06-22T02:27:03.0181020Z|Eternal|Debug|Injection state changed: Injecting
2017-06-22T02:27:03.1401818Z|Eternal|Debug|Injection state changed: Idle
2017-06-23T01:50:22.4422777Z|Eternal|Debug|Injection state changed: Injecting
2017-06-23T01:50:22.6883181Z|Eternal|Debug|Injecting DeckTracker.InGame.Helper.dll
2017-06-23T01:50:22.8728355Z|Eternal|Debug|Waiting for remote thread finished with result 0
2017-06-23T01:50:22.8748351Z|Eternal|Debug|Injected DeckTracker.InGame.Helper.dll, waiting for response
2017-06-23T01:50:42.8975723Z|Eternal|Debug|Injection state changed: Failed
2017-06-23T01:59:01.6261175Z|Eternal|Debug|Injection state changed: Injecting
2017-06-23T01:59:01.7180520Z|Eternal|Debug|Injection state changed: Idle
2017-06-23T02:07:07.0612026Z|Eternal|Debug|Injection state changed: Injecting
2017-06-23T02:07:07.2362972Z|Eternal|Debug|Injecting DeckTracker.InGame.Helper.dll
2017-06-23T02:07:07.2593377Z|Eternal|Debug|Waiting for remote thread finished with result 0
2017-06-23T02:07:07.2613378Z|Eternal|Debug|Injected DeckTracker.InGame.Helper.dll, waiting for response
2017-06-23T02:07:27.2822635Z|Eternal|Debug|Injection state changed: Failed
2017-07-07T02:00:11.9364047Z|Eternal|Debug|Injection state changed: Injecting
2017-07-07T02:00:12.0279494Z|Eternal|Debug|SocketStreamClient.Start
2017-07-07T02:00:12.1374558Z|Eternal|Debug|SocketStreamClient.SendCommand(Ping) timeout, sent=False connected=False
2017-07-07T02:00:12.1384598Z|Eternal|Debug|Injecting DeckTracker.InGame.Helper.dll
2017-07-07T02:00:12.3554829Z|Eternal|Debug|Waiting for remote thread finished with result 0
2017-07-07T02:00:12.3569920Z|Eternal|Debug|Injected DeckTracker.InGame.Helper.dll, waiting for response
2017-07-07T02:00:13.1319828Z|Eternal|Debug|SocketStreamClient disconnected: No connection could be made because the target machine actively refused it 127.0.0.1:50002
2017-07-07T02:00:14.1393645Z|Eternal|Debug|SocketStreamClient disconnected: No connection could be made because the target machine actively refused it 127.0.0.1:50002
2017-07-07T02:00:15.1406362Z|Eternal|Debug|SocketStreamClient disconnected: No connection could be made because the target machine actively refused it 127.0.0.1:50002
2017-07-07T02:00:16.1425385Z|Eternal|Debug|SocketStreamClient disconnected: No connection could be made because the target machine actively refused it 127.0.0.1:50002
2017-07-07T02:00:17.1446387Z|Eternal|Debug|SocketStreamClient disconnected: No connection could be made because the target machine actively refused it 127.0.0.1:50002
2017-07-07T02:00:18.1464341Z|Eternal|Debug|SocketStreamClient disconnected: No connection could be made because the target machine actively refused it 127.0.0.1:50002
2017-07-07T02:00:19.1493882Z|Eternal|Debug|SocketStreamClient disconnected: No connection could be made because the target machine actively refused it 127.0.0.1:50002
2017-07-07T02:00:20.1516906Z|Eternal|Debug|SocketStreamClient disconnected: No connection could be made because the target machine actively refused it 127.0.0.1:50002
2017-07-07T02:00:21.1553346Z|Eternal|Debug|SocketStreamClient disconnected: No connection could be made because the target machine actively refused it 127.0.0.1:50002
2017-07-07T02:00:22.1572477Z|Eternal|Debug|SocketStreamClient disconnected: No connection could be made because the target machine actively refused it 127.0.0.1:50002
2017-07-07T02:00:22.3644318Z|Eternal|Debug|SocketStreamClient.SendCommand(Ping) timeout, sent=False connected=False
2017-07-07T02:00:22.3653620Z|Eternal|Debug|Injection state changed: Failed
2017-07-07T02:00:22.5743888Z|Eternal|Debug|SocketStreamClient.Stop
2017-07-07T02:03:57.3940020Z|Eternal|Debug|Injection state changed: Injecting
2017-07-07T02:03:57.4650055Z|Eternal|Debug|SocketStreamClient.Start
2017-07-07T02:03:57.5830123Z|Eternal|Debug|SocketStreamClient.SendCommand(Ping) timeout, sent=False connected=False
2017-07-07T02:03:57.5870119Z|Eternal|Debug|Injecting DeckTracker.InGame.Helper.dll
2017-07-07T02:03:57.6140150Z|Eternal|Debug|Waiting for remote thread finished with result 0
2017-07-07T02:03:57.6160155Z|Eternal|Debug|Injected DeckTracker.InGame.Helper.dll, waiting for response
2017-07-07T02:03:58.4765006Z|Eternal|Debug|SocketStreamClient disconnected: No connection could be made because the target machine actively refused it 127.0.0.1:50002
2017-07-07T02:03:59.4782295Z|Eternal|Debug|SocketStreamClient disconnected: No connection could be made because the target machine actively refused it 127.0.0.1:50002
2017-07-07T02:04:00.4805984Z|Eternal|Debug|SocketStreamClient disconnected: No connection could be made because the target machine actively refused it 127.0.0.1:50002
2017-07-07T02:04:01.4912014Z|Eternal|Debug|SocketStreamClient disconnected: No connection could be made because the target machine actively refused it 127.0.0.1:50002
2017-07-07T02:04:02.4928365Z|Eternal|Debug|SocketStreamClient disconnected: No connection could be made because the target machine actively refused it 127.0.0.1:50002
2017-07-07T02:04:03.4967096Z|Eternal|Debug|SocketStreamClient disconnected: No connection could be made because the target machine actively refused it 127.0.0.1:50002
2017-07-07T02:04:04.4992519Z|Eternal|Debug|SocketStreamClient disconnected: No connection could be made because the target machine actively refused it 127.0.0.1:50002
2017-07-07T02:04:05.5013756Z|Eternal|Debug|SocketStreamClient disconnected: No connection could be made because the target machine actively refused it 127.0.0.1:50002
2017-07-07T02:04:06.5066893Z|Eternal|Debug|SocketStreamClient disconnected: No connection could be made because the target machine actively refused it 127.0.0.1:50002
2017-07-07T02:04:07.5090025Z|Eternal|Debug|SocketStreamClient disconnected: No connection could be made because the target machine actively refused it 127.0.0.1:50002
2017-07-07T02:04:07.6990255Z|Eternal|Debug|SocketStreamClient.SendCommand(Ping) timeout, sent=False connected=False
2017-07-07T02:04:07.7080277Z|Eternal|Debug|Injection state changed: Failed
2017-07-07T02:04:07.7660094Z|Eternal|Debug|SocketStreamClient.Stop

I think it seems like it's not able to connect on port 50002. I did netstat -an and didn't see anything on ports 50001 or 50002.

from decktracker.

Experiencing the same issue. Here's my events.log:

2017-07-12T20:43:54.5971075Z|Eternal|Debug|Injection state changed: Injecting
2017-07-12T20:43:54.6711540Z|Eternal|Debug|SocketStreamClient.Start
2017-07-12T20:43:55.2195419Z|Eternal|Debug|SocketStreamClient.SendCommand(Ping) timeout, sent=False connected=False
2017-07-12T20:43:55.2205603Z|Eternal|Debug|Injecting DeckTracker.InGame.Helper.dll
2017-07-12T20:43:55.2405577Z|Eternal|Debug|CreateToolhelp32Snapshot failed with error 299
2017-07-12T20:43:55.2425629Z|Eternal|Debug|GetProcessModuleHandle failed with error 299
2017-07-12T20:43:55.2435598Z|Eternal|Debug|GetProcessProcAddress failed with error 299
2017-07-12T20:43:55.2445606Z|Eternal|Debug|Injection state changed: Failed
2017-07-12T20:43:55.3123261Z|Eternal|Debug|SocketStreamClient.Stop

As well as my error.log:

Exception happened while attaching to mono thread
Exception happened while attaching to mono thread
Exception happened while attaching to mono thread
Exception happened while attaching to mono thread
Exception happened while attaching to mono thread

from decktracker.

@alkis05 You can take a look at the code now. Please send a pull request if you figure out what's causing this error.

from decktracker.

Hi, just tried using the latest download but still comes up with the red message at the top :(

from decktracker.

@Vampiricangeluk That location is empty for me as well. @extesy Is there a file manually we could download in there? Maybe that is the piece that is missing. Again, it is empty for me and Vampiricangeluk

from decktracker.

Files will be generated in this folder if you start the application with --debug command line parameter.

from decktracker.

good lord... I'm googling how to do that..but not having much luck.. so if anyone can tell me how to do the debug command thing I'd be appreciative

from decktracker.

Hi Mnefstead.. what do you mean by "the app to access the clipboard"?

from decktracker.

Ive tried everything I can think of..nothing works for me :(

from decktracker.

What got it working for me properly was starting the tracker after the game is loaded, only then I'd get the green message and it would function as expected.

from decktracker.

Just downloaded the update and I have the same problem still :(

from decktracker.

@mnefstead Thanks for the detailed report! The only conclusion I can make so far is that antivirus sometimes behaves differently and doesn't let the program work as intended. And I can't understand why would it happen because all antiviruses show it as clean: https://www.virustotal.com/en/file/3ee94f39608651c513366ad99072ca17af11b750035157d1bba3237369c08885/analysis/

from decktracker.

Extesy I have my antivirus turned off and it still is the same

from decktracker.

@extesy This is interesting..hope it helps fix the problems. (im on a home network with multiple computers)
events.txt

from decktracker.

Update: the "fix" seems to be sporadic, as I'm still having trouble getting it to work. ¯\_(ツ)_/¯

from decktracker.

@extesy Any chance to have missed code-base for DeckTracker.InGame.dll ?
In case, it was done on purpose - please, make clear statement in README file about proprietary code in use.

from decktracker.

@VitaliyKulikov It's on purpose, but temporary. There is some code there I don't want to publish yet so I need to refactor it out first. You can just copy this dll from the latest distributive and everything will work.

from decktracker.

@extesy no pressure bro )) i just need this code to improve some in-game overlay features and add some useful ideas. i feel that you can refactor this code fully to c#, but it's not necessary i suppose.

from decktracker.

@extesy I'm having issues with the tracker recognizing ESL. It works on my desktop, and my other laptop (died last week). I'm trying to get it on this laptop now. The text shows ESL is detected but it is red.

My log file:

2017-07-23T05:38:56.6366312Z|TheElderScrollsLegends|Debug|Injection state changed: Injecting
2017-07-23T05:38:56.7357200Z|TheElderScrollsLegends|Debug|SocketStreamClient.Start
2017-07-23T05:38:56.8518259Z|TheElderScrollsLegends|Debug|SocketStreamClient.SendCommand(Ping) timeout, sent=False connected=False
2017-07-23T05:38:56.8583326Z|TheElderScrollsLegends|Debug|Injecting DeckTracker.InGame.Helper.dll
2017-07-23T05:38:56.8808504Z|TheElderScrollsLegends|Debug|Waiting for remote thread finished with result 0
2017-07-23T05:38:56.8883588Z|TheElderScrollsLegends|Debug|Injected DeckTracker.InGame.Helper.dll, waiting for response
2017-07-23T05:38:57.7476333Z|TheElderScrollsLegends|Debug|SocketStreamClient disconnected: No connection could be made because the target machine actively refused it 127.0.0.1:50001
2017-07-23T05:38:58.7731123Z|TheElderScrollsLegends|Debug|SocketStreamClient disconnected: No connection could be made because the target machine actively refused it 127.0.0.1:50001
2017-07-23T05:38:59.7840850Z|TheElderScrollsLegends|Debug|SocketStreamClient disconnected: No connection could be made because the target machine actively refused it 127.0.0.1:50001
2017-07-23T05:39:00.7934969Z|TheElderScrollsLegends|Debug|SocketStreamClient disconnected: No connection could be made because the target machine actively refused it 127.0.0.1:50001
2017-07-23T05:39:01.8014318Z|TheElderScrollsLegends|Debug|SocketStreamClient disconnected: No connection could be made because the target machine actively refused it 127.0.0.1:50001
2017-07-23T05:39:02.8143148Z|TheElderScrollsLegends|Debug|SocketStreamClient disconnected: No connection could be made because the target machine actively refused it 127.0.0.1:50001
2017-07-23T05:39:03.8237677Z|TheElderScrollsLegends|Debug|SocketStreamClient disconnected: No connection could be made because the target machine actively refused it 127.0.0.1:50001
2017-07-23T05:39:04.8326621Z|TheElderScrollsLegends|Debug|SocketStreamClient disconnected: No connection could be made because the target machine actively refused it 127.0.0.1:50001
2017-07-23T05:39:05.8410906Z|TheElderScrollsLegends|Debug|SocketStreamClient disconnected: No connection could be made because the target machine actively refused it 127.0.0.1:50001
2017-07-23T05:39:06.8500038Z|TheElderScrollsLegends|Debug|SocketStreamClient disconnected: No connection could be made because the target machine actively refused it 127.0.0.1:50001
2017-07-23T05:39:06.9025490Z|TheElderScrollsLegends|Debug|SocketStreamClient.SendCommand(Ping) timeout, sent=False connected=False
2017-07-23T05:39:06.9146180Z|TheElderScrollsLegends|Debug|Injection state changed: Failed
2017-07-23T05:39:07.1928087Z|TheElderScrollsLegends|Debug|SocketStreamClient.Stop

I don't know what that IP is referencing--it's not any of my local IPs.

On a separate note, I've tried giving you a one-time donation via the link on the front page numerous times and I keep getting a 'Something went wrong' error after signing into Paypal. Hopefully that's something that you can forward on to your donation provider service.

from decktracker.

@Burt2004 Hi Burt. Thats the same messages I get too.

from decktracker.

Few days ago UDT worked on Windows 7 Ultimate. Today i cleaned HDD and installed Windows 10 Entertainment and UDT didn't worked (blue ~10 seconds, red ~2-3 seconds). Then I upgraded Win 10 Ent to Windows 10 Pro, added UDT to antivirus exclusions - the same.

from decktracker.

Hi, I donwloaded newest version. The game is up to date. I am using Win10. I can start the tracker, but when I start the game, the tracker crashes with a windows note "program crashed due to an error". And all I can do is close the program.

Any idea?

from decktracker.

Figured it out. Was the VPN network. Deactivited it, started app as admin and it worked.

from decktracker.

@demek12345 @extesy Thanks, demek. Installing this fixed my problem!

from decktracker.

I don't understand why it helps because deck tracker does not use Access, but I'm glad that it works for you guys.

from decktracker.

After formatting my computer i tried everything and it only worked btw deck tracker is great thx extesy

from decktracker.

@demek12345 @extesy ...that actually works..thanks so much for sharing Demek! YAY

from decktracker.

@abhartman @jonathanFinnell can you also try @demek12345's solution?

from decktracker.

hello, i have same problem than burt2004 and other with the : SocketStreamClient disconnected: No connection could be made because the target machine actively refused it 127.0.0.1:50001

try solution from @demek12345 and... well, that works. so for some reasons i couldn't explain, it seems that this deck tracker NEED acces runtime, or maybe acces runtime change one setting in computer or registry that is needed for deck tracker to work...
anyway, the resulat is here, without acces runtime : dont work . with it : work

from decktracker.

⚡️Magic!⚡️

from decktracker.

i had same issue SocketStreamClient disconnected: No connection could be made because the target machine actively refused it 127.0.0.1:50001 under wine. Running tracker after game makes trick.

from decktracker.

@VitaliyKulikov hi, you should try the fix that @demek12345 mentioned in the above post... it worked for me and some others! Good Luck

from decktracker.

Many thanks to @demek12345 for the post with the download of Access 2016 Runtime! The tracker has earned. Perhaps in my case the installation of a new version of C ++ helped.

from decktracker.

@extesy adding the Access 2016 Runtime fixed it all for me. Weird, but glad it got working.

from decktracker.

This is so weird. My theory is that this runtime fixes a bug in some of the standard Windows system dlls which is normally benign but somehow interferes with the deck tracker. Access 2016 runtime probably provides a new version of that dll with the bug fixed.

from decktracker.

I didn't have to use all the steps that @mnefstead did, but when I opened the deck tracker from the link in the start menu (as opposed to the desktop link or downloads folder), then it worked.
I can't imagine what difference that would make, but that is what caused it to run (once so far) properly for me.

from decktracker.