Page 1 of 1
FSACARS FREP Reporting Fix in Beta
Posted: 10-07-2018 11:17 PM
by Michael Blakely
I've implemented a fix for the FSACARS FREP reporting bug that started on Sep 24. This is considered BETA until we get some more successes with it.
Please reply to this thread indicating if your FSACARS FREPs are successful or fail.
If failed, please note this information: date, flight number, from/to airports, anything else you notice.
Thanks all.
Re: FSACARS FREP Reporting Fix in Beta
Posted: 10-11-2018 07:26 PM
by Todd Meek
I successfully completed a flight on October 10th from KSEA to PANC using FSACARS and it sent it to the website. I was able to edit the FREP just like before. I did have to manually submit my last two FREPS since I wasn't aware there was a problem until I noticed that I wasn't getting credit for a couple of flights I did prior. I went into edit FREPS and there was nothing there so I just manually put them in.
Re: FSACARS FREP Reporting Fix in Beta
Posted: 10-15-2018 05:33 PM
by Norberto Rivera
I keep getting the "tampered log" error.
Re: FSACARS FREP Reporting Fix in Beta
Posted: 10-15-2018 09:38 PM
by Michael Blakely
Norberto Rivera wrote:I keep getting the "tampered log" error.
Delete these files:
AAL476.dat
flightlog.csv
flightlog.dat
If that doesn't work, then email me the sendlogreport.html file.
Re: FSACARS FREP Reporting Fix in Beta
Posted: 11-02-2018 12:58 PM
by Michael Blakely
Thank you all for the feedback.