Post by jasonbirdsall on Jul 11, 2020 21:08:55 GMT -5
Recently upgraded to 1.8.2 after an extended hiatus. After upgrading, I am unable to call up flights dispatched under FSCaptain Administrator. The dispatched flight show up as "other commitments" although they never appear as open flights (or, indeed, at all) in the administrator flight log. Completing a flight which I manually dispatch in the FCDU behaves normally, except it never writes to the Admin log -- not open, dispatched, closed, or any appearance at all.
It's almost like Admin and FCDU aren't talking to each other. Version is P3d V4.5
Dutch and Travis might know right away what is going wrong, but I can start with some speculations. Your logs look fine, but I see that you have two different pilots (number 457 and 310507) with the same name. It could be that you committed your flight for one pilot, but fly it with the other. Also, the "other commitments" message usually show up if you are in the wrong plane, or at the wrong airport, or at the right airport at the wrong time. I suggest the following
- Check that the pilot number in the admin and in the FCDU are the same - Check the airplane type in Admin and FCDU - In the Admin, go to "Flight Dispatch", select "<Unlisted Type>" and click on "List FLights". This will show you if your airplane is actually recognized by FSCaptain. Let us know the results of these tests.
Post by jasonbirdsall on Jul 12, 2020 8:13:44 GMT -5
Thank you for the quick response. I had considered the possibility of dispatching under the wrong pilot id and checked all three pilots (the FSC default "Joe Pilot" included) -- no record of the dispatched flights under any of them. The flights are not listed under unlisted type either. The most likely scenario is that there is some problem with airplane type as the AH DC-3 is still comparatively new, but I can't find any problems within the aircraft.cfg and the ID on FCDU sure appears to match the ID on FSAdmin. FSADmin dispatches the aircraft under "DC3 Douglas DC-3"; FCDU calls up the "other commitments" flights under "DC3:". When I manually dispatch the same aircraft from FCDU, the flight remains after arrival as an "other commitment" under "DC3:BEA". Previously-committed flights do not appear in the FSAdmin log, regardless of whether they were dispatched by FSAdmin or FCDU.
As an added precaution I completely deleted FSC from my computer -- including logs, careers, etc -- and reinstalled a "clean" version. The problem persists after having rebuilt only career, so I am pretty sure I can rule out the duplicate pilot possibility.
As an additional wrinkle, I need to amend my earlier statement because FCDU and FSAdmin are clearly communicating -- any defaults or options I set in Admin carry through to FCDU and the Admin-dispatched flights are present as "other commitments". More precisely, it appears that FSAdmin is unable to write a dispatched flight to log, even if the flight is already completed (such as the flights I dispatched by FCDU).
P3d and, therefore, FSC exist under the P3Dv4 directory at the root of the D: drive on my computer, so access or write protection shouldn't be an issue here.
FSADmin dispatches the aircraft under "DC3 Douglas DC-3"; FCDU calls up the "other commitments" flights under "DC3:". When I manually dispatch the same aircraft from FCDU, the flight remains after arrival as an "other commitment" under "DC3:BEA".
Let's solve this problem one step at a time and first ignore that your flights are not saved. This description may give some clue: there could be a type mismatch between the AH DC3 and what FSCaptain expects. Specifically, your flight is dispatched for an airplane of type "DC3", but your log seems to indicate that your airplane is recognized as "DC3 BEA". You can open the aircraft.cfg file of the AH model using Notepad.exe and search for all instances of "atc_model". This variable should have a consistent type (always DC3, or always DC3 BEA), but sometimes airplane modellers (even the very best) enter inconsistent data, which can confuse the FCDU.
Edit all instances of atc_model so that they all equal DC3. If you need help, just send us the aircraft.cfg file. Then let us know whether this changes the behavior of the FCDU.
Please ZIP and email your Orbit.log file (or post it here) and I'll take a gander. (I'm hatching a few guesses... but I'd rather see the details from your company log.)
Everything else looks okay. Your AH DC-3 uses the Type of "DC3" so we're matching the type configuration file. (The "BEA" string should be your aircraft's registration ID.)
You may want to create an Override file with the name of "AH_Douglas_DC3.cfg" so you can tweak the differences from the base DC3.cfg file. That itself may help to reduce the instances of "other commitments." Plus you can then make a load map, if you so choose.
Post by jasonbirdsall on Jul 18, 2020 12:43:47 GMT -5
Still at a loss. I went into the fscaptain/data folder and deleted **every** **file** I could find, and then when starting Admin again it wouldn't let me build a new flight, asking if I want to "redispatch flight 1 from KSFO to KSLC?" Clicking yes brings up the stale data -- after the manifests and logs have been deleted, no less. Clicking No does nothing whatsoever. Where is it pulling these data from, and why can't it write to these data?
Is the dispatcher writing to a log outside of the FSCaptain folder, by any chance?
It is possible, but it should only happen if you changed the default location for logs in options.cfg. Open that file in Notepad.exe and search for "C:" and "D:", that should let you find all directories that are accessed by FSCaptain outside of its own directory.
Post by jasonbirdsall on Jul 19, 2020 7:56:12 GMT -5
Thanks for the follow up Peter. The NavData path defaults to my C:\users\documents, while fscaptain points to my default d:\P3d drive. They are both the defaults, and I can't find the stray dispatches/flights in either location.
Options.cfg attached, I dunno if perhaps there is something here I'm missing. The redispatch option has continued with 100% repeatability, so the program is pulling a prior flight from somewhere but won't list it as an open flight and darned if I can't find the offending file.
Post by jasonbirdsall on Jul 20, 2020 11:31:53 GMT -5
I have restored all deleted \data\ files, per your recommendation -- although not from the previous installation, those are gone for good -- and am attaching the backup zip nowBackup.zip (1.75 KB)
Admin only indicates the default pilot (ID 1: Joe Pilot) and my present pilot. I have not dispatched any flights under "Joe Pilot", and there are no others. Previous flights might reference earlier installations, but those should have disappeared with the uninstall/reinstall. No paths have been altered for fscaptain on this computer since the computer was built, so I'm not sure where it is getting all this.
Hope this helps, I can zip and send the entire directory if you wish.