FSACARS update ...possible problem.

[Michael Blakely]

I can tell from the logs that at least a dozen people have switched over to the new .ini
It's just a new path to the same code, so I don't expect it was the cause of what you saw, but you never know.

Anyone else see anything odd?

[Wayne Pierce]

Chris, the extra FREPS were from when you had problems with FSACARS. The program keeps in it's folder, flights which were not filed correctly and when the conditions are happy again, it files all. I have this happen to me quite often.

You cannot delete any FREP's made as only the HUB manager can delete them. Once you file, it is in the system.

WLP

[Theodore Martin]

Ditto what Wayne said. Anytime you use FSACARS and don't get a successful "send log" they are stored and sent the next time a successful send is made. For example, I sometimes fly other flights that are not in my bid but I use FSACARS to provide my landing stats for review. Since I don't send those to AAV when I do fly an AAV bid the old flight (or sometimes just a bad FREP) is sent in addition to my new bid flight. Don't know any way to delete bad/old FSACARS records.

[Michael Blakely]

(On a closely related note...is there anyway to manually delete a pending FREP so as not to annoy my Hub manager too much?)

Good feature idea. I'll add it.

[Theodore Martin]

(On a closely related note...is there anyway to manually delete a pending FREP so as not to annoy my Hub manager too much?)

Good feature idea. I'll add it.

Way to go boss...you are always right on top of things.