Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Doesn't work anymore since last Playnite update (10.19) #201

Open
jaceneliot opened this issue Oct 6, 2023 · 14 comments
Open

Doesn't work anymore since last Playnite update (10.19) #201

jaceneliot opened this issue Oct 6, 2023 · 14 comments

Comments

@jaceneliot
Copy link

Hi ! i have Playnite 10.19 and GameActivity 3.1.0. It doesn't work anymore :( It doesn't track time and i can't even see the oldest activites i recorded...Is there any issue with the extension ? I resinstalled it but it still doesn't work...

I noticed it take longer than usual to load too.
image
image

As we can see, there is nothing about oldest activity except in Gantt view...

Thanks for the help.

@jaceneliot
Copy link
Author

Hi ! Is is still updated :( ?

@Clusters
Copy link

Clusters commented Dec 7, 2023

@jaceneliot don't know if that helps you in any way. But I have no such issues with 10.19 so far. Gantt and playtime records are present for my game sessions, even for the most recent ones.
...as long as they were initiated through Playnite.

@11matt556
Copy link

I don't know if it helps, but I found that I get this same error when my tracking path is incorrect.

@jaceneliot
Copy link
Author

jaceneliot commented Dec 9, 2023 via email

@11matt556
Copy link

@jaceneliot It would be in the Edit menu for the game. In my case I had defined some custom launch options in the Actions tab and had to fix some of the paths.

@jaceneliot
Copy link
Author

jaceneliot commented Dec 13, 2023 via email

@11matt556
Copy link

11matt556 commented Dec 14, 2023

At first I thought the whole extension was broken since I got an error every time I launched a game and it failed to record the session, but it turned out that all the games I had tested on had something incorrect in the Edit menu. I still get the same error from GameActivity when I first launch PlayNite as I did when launching a game with incorrect path information, but I don't get this error when I tested a fresh install on a different system. This leads me to believe I still have some path somewhere which is incorrect. but the plugin seems to be working fine despite this error (See screenshot) so I haven't put much effort into getting rid of the error on my main system.

image

@jaceneliot
Copy link
Author

jaceneliot commented Dec 15, 2023 via email

@11matt556
Copy link

  1. Right click on a game and click "Edit" from the menu
    image

  2. This window should appear

image

  1. Click the "Installation" tab. Verify the installation path is correct
    image

  2. Repeat with any paths you have entered in the "Action" tab. This is the tab I had to fix, but you may not have anything on this tab. It should be fine if this tab is empty though.
    image

If all of that is correct, the only things I know to try are completely uninstalling Playnite and then reinstalling with just the GameActivity plugin, and verifying that the RivaTuner Statatistics Server that GameActivity gathers data from is actually working.

In case it matters, I am using GameActivity with RivaTuner Statistics Server 7.3.3 and MSI Afterburner 4.6.4.16255 specifically.

@crackalackintv
Copy link

crackalackintv commented Jan 7, 2024

It is completely broken for me and there are no logs, even if I check the "log trace messages". I have checked the extension folders and the playnite.log, are there any other places where extension logs would be written to?

I verified the paths and just installed two games fresh, same issue. No session tracking and the old sessions aren't even displayed. The loading of the GameActivity screen also takes forever even though there are only a handful of entries in the gameactivity dataset.

07-01 03:58:30.436|INFO |GamesEditor:Starting Mechabellum,  [....]
07-01 03:58:30.647|DEBUG|GamesEditor:Using plugin to start a game.
07-01 03:58:39.841|INFO |GamesEditor:Started Mechabellum game.
07-01 04:00:01.119|INFO |GamesEditor:Game Mechabellum stopped after 82 seconds.
07-01 04:00:02.148|DEBUG|GamesEditor:Game session was too short for client to be shutdown.

Playnite recognized the launch and shutdown of the game fine, but the session was not recorded in GameActivity (I tried with a 20 minute session as well, turned off the 'don't log if session is shorter than...", same outcome.

It broke for me two days ago (Jan 4th 2024), which shouldn't coincide with a Playnite update, but not sure what triggered it.
I tried disabling the addon and then re-enabling it, didn't help. Completely uninstalling the addon and reinstalling didn't fix it, either.

Edit: Playnite showed me an error notification and let me export a log package then:

07-01 04:30:59.617|ERROR|GameActivity#Common:Error on getActivityByListGame()|D:\GitHub\Lacro59\playnite-gameactivity-plugin\source\Views\GameActivityView.xaml.cs|887
System.NullReferenceException: Object reference not set to an instance of an object.
   at CommonPluginsShared.LocalSystem..ctor(String ConfigurationsPath, Boolean WithDiskInfos) in D:\GitHub\Lacro59\playnite-gameactivity-plugin\source\playnite-plugincommon\CommonPluginsShared\LocalSystem.cs:line 47
   at GameActivity.Services.ActivityDatabase.get_LocalSystem() in D:\GitHub\Lacro59\playnite-gameactivity-plugin\source\Services\ActivityDatabase.cs:line 24
   at GameActivity.Models.Activity.get_Configuration() in D:\GitHub\Lacro59\playnite-gameactivity-plugin\source\Models\Activity.cs:line 47
   at GameActivity.Views.GameActivityView.getActivityByListGame() in D:\GitHub\Lacro59\playnite-gameactivity-plugin\source\Views\GameActivityView.xaml.cs:line 887

@crackalackintv
Copy link

I found the issue that caused my recording to stop and the UI to be slow. See #196 (comment) but in short: Delete the Configurations.json in the ExtensionsData folder of the GameActivity extension. For me it was written with nonsense and the reading of it failed. Once I deleted it, it got recreated properly (when I opened the addon config dialogue and saved) and it worked since then.

@jaceneliot
Copy link
Author

jaceneliot commented Jan 8, 2024 via email

@Lacro59
Copy link
Owner

Lacro59 commented Feb 7, 2024

@Lacro59
Copy link
Owner

Lacro59 commented Feb 8, 2024

Can you try with the last release?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants