After talks earlyer today with Element. I think there should be a page to report broken trainers. That require mandatory information inputed. E.g.
Game name: Fallout 3
Game version: 1.7
OS Version: Win 7
IE Version: 9
AV Name: AVG
FW Name: Windows
Followed TSG: Yes
Details: (Detailed report of what happened and what you did to do to fix it) The game crashes with the current trainer. I ran the trainer, steam and game in admin mode. Also told my AVG and FW to ignore the trainer. I have also tried it with out the AVG or FW runing.
Something like this so the CHT have something to go on instead of it dosent work!
[Edited by ServiusTheBear, 6/30/2015 7:04:43 AM]
I wonder if they could put something in the trainer's themselves that notified them of trainer fails and sends them a report. That let's them know the reason ie antivirus or real break.
But I would not know if that is feasible in anyway shape or form.
I like my return to requests que idea personally.
After talks earlyer today with Element. I think there should be a page to report broken trainers. That require mandatory information inputed. E.g.
Game name: Fallout 3
Game version: 1.7
OS Version: Win 7
IE Version: 9
AV Name: AVG
FW Name: Windows
Followed TSG: Yes
Details: (Detailed report of what happened and what you did to do to fix it) The game crashes with the current trainer. I ran the trainer, steam and game in admin mode. Also told my AVG and FW to ignore the trainer. I have also tried it with out the AVG or FW runing.
Something like this so the CHT have something to go on instead of it dosent work!
[Edited by ServiusTheBear, 6/30/2015 7:04:43 AM]
I wonder if they could put something in the trainer's themselves that notified them of trainer fails and sends them a report. That let's them know the reason ie antivirus or real break.
But I would not know if that is feasible in anyway shape or form.
I like my return to requests que idea personally.
To do that they would need to have the trainer activly scaning and gathering the information. So more processes at the same time.
Are you sure about that? You could not have a exception inserted in the code to notify when a "trainer fail" response is executed?
I don't know why you would need constant scanning.
Active scanning would show what is runing and what caused the failure then creates a log of the data for the failure. Just like in the Event Veiwer in the Admin section on windows.
Or you some how hook into the event veiwer to copy the error log from there. Like this one.
Faulting application name: Magic The Gathering - Duels of the Planeswalkers 2014 - Trainer , version: 0.0.0.0, time stamp: 0x523c74d4
Faulting module name: ltc_game32-96675.dll, version: 1.0.0.1, time stamp: 0x55555504
Exception code: 0xc0000417
Fault offset: 0x000a20e4
Faulting process id: 0x199c
Faulting application start time: 0x01d0b2fa725c4bed
Faulting application path: C:\Users\ServiusTheBear\Documents\My Trainers\Magic The Gathering - Duels of the Planeswalkers 2014 - Trainer (PATCH 09.20.2013) -Toki.exe
Faulting module path: C:\PROGRA~2\Raptr\ltc_game32-96675.dll
Here it shows that raptr is somehow interfering with the Trainer. The only way at this moment to stop that from happening is to turn off Raptr.
*typo
[Edited by ServiusTheBear, 6/30/2015 10:00:37 AM]