Can't seem to get it to work

Question

Can't seem to get it to work

adamwilborn opened this issue 2 years ago · 7 comments

Hey there! So I've been trying to use your plugin ever since you released v2 but I haven't been able to get it to work. I download the file like I do for other plugins, accept the popup to install it, and then add it to my stream deck. When I'm in a raid I hit the button but the only thing that happens is the yellow triangle with the exclamation point pops up. Would really love to use this extension, could you help me debug what I'm doing wrong?

Answer 1 · 2022-07-14T13:39:02.000Z

I recomend you use the latest release - there was some bugs in the previous versions that might cause what you describe. I hope this helps otherwise please let me know.

Thank you for the feedback!

Answer 2 · 2022-07-14T14:18:36.000Z

I just tried that release again in a scav run and it didn't work. Wonder if it's somehow tied to your computer and it's a path thing? I can give you my discord or another form of contact if you want to help walk through this issue.

Answer 3 · 2022-07-14T15:22:56.000Z

I will do what i can to help - including discord communication but I noticed you write that you tried the plugin in a scav run?
What precisely do you mean about that?
The plugin should work independantly all the time no matter if EFT is running or not.

Answer 4 · 2022-07-14T15:25:31.000Z

I was under the impression that it only worked in raids but I see now that's not the case. But yeah it doesn't work for me when I'm in Tarkov and not in Tarkov. Here is my discord if you want to reach out to me on there: AWilborn#0571

Answer 5 · 2022-07-15T05:37:23.000Z

Can you look in %appdata%\Elgato\StreamDeck\Plugins\com.cmdrflemming.tarkovtime.sdPlugin\log and tell me if you find log-files in that folder?
I sendt you a Discord request a few seconds ago.

Answer 6 · 2022-07-15T08:29:05.000Z

The logfile will be named sampleplugin.log because i did not change that filename to reflect the relation to com.cmdrflemming.tarkovtime - it will be fixed in next release.

Answer 7 · 2022-07-15T19:50:18.000Z

After some investigation together with @adamwilborn we figured out that my plugin require .NET Core 3.1

After installing the .NET Desktop Runtime 3.1.27 from here https://dotnet.microsoft.com/en-us/download/dotnet/3.1 the plugin immediately started to work as intended.