Issues qhen reading sms_stats_data.son with pcars2-stats-master by m1ndgames

[thisisrhun]

Hi,

I have strange issues when reading my sms_stats_data.json files with filldb.pl inside pcars2-stats-master (github (dot) com/m1ndgames/pcars2-stats).

The main issue is that it seems the "members" arrays of each session are not always complete and I can't find a pattern. Sometimes the full array is empty... Only "participants" array has actual driver data in it, but it has not the same information nor structure, and sometimes the key of each driver entry is present, sometimes it is not.

I managed to upload correctly to my DDBB the practice laptimes, as well as the driver names, car IDs and livery IDs from the "participants" subarray when it's not available in the "members" one, but the setup each driver uses is not present in the "participants" array, so I cannot extract the "RaceStatFlags".

Is this normal? Have any of you found this issue as well? I have read every post I've found regarding sms_stats_data and its potential issues, and don't know where else to look.

[satco1066]

never heared of that app before
seems like an old and abandoned project by someone who writes "Beware! I didnt know any PHP and Javascript, so its hacky and ugly..."
Sounds not amazing

[thisisrhun]

It's the only way I have managed to get working periodic uploads from sms_stats_data.json to a database, to present a hotlaps table in my website.

Anyway, the question is still the same, and is not regarding this app, but the sms_stats_data.json file instead. From file inspection, I find it is not consistent as not all drivers are stored in "members" subarray. Does anyone here use any solution to upload times to a website in a customized way?

[m1ndgames]

never heared of that app before
seems like an old and abandoned project by someone who writes "Beware! I didnt know any PHP and Javascript, so its hacky and ugly..."
Sounds not amazing

Yes! Old and abandoned (i just found this post by accident)

The php code is just simple sql queries, but i had a hard time with the js hence the warning. The magic is mostly in the perl script that parses the json and pushes it into a sql database. I guess i should have documented it better, but last time i used it, it was infact working.
I suspect the json changed and thats why it broke?!