|
Post by g5flyer on Nov 6, 2012 0:29:16 GMT -5
anyone have any luck with the flight1/coolsky dc9? I'm getting the acars not linked to fdr message. I tried auto and manual install without any luck.
|
|
|
Post by Travis on Nov 6, 2012 2:20:28 GMT -5
It's possible, but this is one complex and tough bird to work with, and you will have to make a compromise to manually install an FCOM / FCDU gauge. It's very much worth the effort if you like older jetliners to fly. Espen was most gracious to allow beta-tester access late spring, and honestly I didn't want to bother Espen with a lot of "Hey, can you support us while you're getting the kinks out of your product?" questions. Now I haven't been in a position to install the DC9 Beta Service Packs... and my difficulties also pre-dated FSCaptain 1.3.1, so I'm offering this as a possible work-around. (I'll do an 1.4.1 FCDU install from scratch tomorrow just to check.) 1. Check that your FCOM / FCDU gauge window appears before the Splash window. Bad things seemed to happen if I placed anything after the Splash window. (Before = lower window number and After = higher window number) 2. Manually move your FDR from [VCockpit01] into your FCOM / FCDU window. [Window08] size_mm=318,741 position=8 visible=0 ident=24477 gauge00=FCDU!ACARS,1,1,318,741 gauge01=FCDU!FDR,1,1,1,1
Dutch might cringe upon seeing that, but.... Attachments:
|
|
|
Post by g5flyer on Nov 6, 2012 6:15:27 GMT -5
Thanks Travis!!!!
|
|
|
Post by g5flyer on Nov 8, 2012 17:18:45 GMT -5
Travis, any chance of getting a copy of your flight1 dc9 interface?
|
|
|
Post by Dutch Owen on Nov 9, 2012 10:12:54 GMT -5
Travis won't be available for a bit as he's on family business but I'm sure when he gets back he'll share.
Dutch
|
|
|
Post by g5flyer on Nov 23, 2012 11:17:51 GMT -5
Travis, if you are back, any chance of getting a copy of your flight1 dc9 interface?
|
|
|
Post by Travis on Nov 23, 2012 11:22:28 GMT -5
Ah... I thought I had posted that, dadgummit. Let me run a systems check that all works ok and I'll post it in the Files area. .... that'll be this afternoon. I've a huge scheduled backup running now, so my system's unavailable for fun stuff.
|
|
|
Post by Travis on Nov 23, 2012 14:26:33 GMT -5
|
|
|
Post by Cpt McGill R J on Feb 5, 2013 23:28:57 GMT -5
I am not sure if you have tried to use your message and file share board or not. I am not having any luck weeding through all the mess. I love you program and it works seamlessly with most of my hanger. The DC9 is one I can't seem to get and most of the dang links are dead. I am a 44yr old NAVY vet with little tolerance for inefficiency. You can't search nor find what you need. I just need to put the dang guage in my 9 so I can fly and not waste time. I read in some post and most examples include fsx and 9 directions. 1 set, on sim one os. much cleaner and easier to understand.
|
|
|
Post by Svilen Vassilev on Feb 6, 2013 4:54:18 GMT -5
Greetings, Cpt McGill!
The Coolsky DC9 interface is no longer present in the file library, because it is included in the base product now. If you're already running the latest version of FSCaptain, you can enable the DC9 interface by following these steps:
Add the following line to the PANEL WINDOW SECTION THAT CONTAINS YOUR FCOM/FCDU in your panel.cfg files in [Flight Simulator] \SimObjects\Airplanes\F1 DC-9\ folder:
[Window08] size_mm=318,741 position=8 visible=0 ident=24477 gauge00=FCDU!ACARS,1,1,318,741 gauge01=FCDU!FDR,1,1,1,1 gauge02=FCOMPNL!InterfaceCoolskyDC9, 1,1,1,1
NOTE! Both the FSCaptain Flight Data Recorder and the FSCaptain Interface references should be listed in the same panel window as the Communicator gauge (FCOM / FCDU) FOR THE COOLSKY DC9.
The FSCaptain installer will place the FDR into the [VCockpit01] section, but multiple reports indicate it will not function when placed there! So use the setup method listed above and remove the FDR entry from the [VCockpit01] section if it's present there.
|
|
|
Post by rjmcgill on Feb 7, 2013 11:15:18 GMT -5
Thanks a million man. This was getting frustrating. Works like a champ. ;D Cpt. out.
|
|
|
Post by Spikehughes on Apr 15, 2013 23:01:47 GMT -5
I have issues with trying to get FSCaptain 1.4.4 working with this aircraft. I am plainly doing something wrong as each time I manually modify the Panel.cfg I note I already have a window 08 file - do I overwrite this?
Also any modification results and a crash when subsequently trying to load the DC 9
So far FSCaptain=0 - Coolsky DC9=1
Any step by step installation would be most useful from anyone who has accomplished this - as I find the explanations very confusing
|
|
|
Post by rjmcgill on Jun 1, 2013 8:30:59 GMT -5
Sorry man I see were you asked a question I might be able to help you with. The way I got mine working was to do away with the checklist as the speed cards set the index for Airspeed indicator. You have to make up your mind what window you will do without. Because you can't add anymore. I don't know why but mine works this way. So if you don't want the radar replace it with FCDU or what ever. Hope this helps. I had the same problems at first. Once you get it working make a backup of the file. Because take it from me if you reinstall the aircraft you will have to figure this all out again. Which ever window you replace will determine which key combination to press to open the window. If you can't remember just count your windows and shift + whatever should open it. Good luck Cpt out.
|
|
|
Post by Blodhemn on Sept 22, 2013 14:39:53 GMT -5
Having same problem with the A2A B-17G, But this fix does not appear to work with that. :(
I dont have the following line in mine though, as I dont have the Coolsky DC9
gauge02=FCOMPNL!InterfaceCoolskyDC9, 1,1,1,1
Any ideas?
|
|
|
Post by Dutch Owen on Sept 22, 2013 17:38:36 GMT -5
That's the interface, and it's specific for each airplane, and we don't have one for the A2A B17 (yet) - but it's optional for using the airplane. It just connects FSCaptain to parts of the simulated systems that FS doesn't handle - or the add-on developer chose to avoid.
An interface is only non-optional when such weird things as the Q400's replacement of the standard FSX FDE is done. Then we have to step in and "bridge the gap" so to speak.
Dutch
|
|