|
|
Post by peter on Dec 21, 2013 18:58:44 GMT -5
Hi Dutch and Travis,
thanks for the 1.5 release. I didn't try it under P3D yet because I have severe issues with that simulator (will be resolved in the next release).
However, I had one issue with FSC 1.5: the new stand-alone program is really slow on my system. Any connection to FSX takes 5 seconds or so. Also, the passengers were very slow to deboard. Did anyone else have these issues?
Mery Xmas,
Peter
|
|
|
|
Post by shadow on Dec 22, 2013 12:55:47 GMT -5
Just signed up and bought FSCaptain and I can report it all seems to be working fine in Prepar3D v2.0
|
|
|
|
Post by Aviator992 on Dec 22, 2013 16:36:08 GMT -5
By the sound of it, you have installed the FCDU but retained the gauge dimensions of the FCOM. Make sure your panel entry looks like this (note the red text): [Window08] size_mm=380,320position=8 visible=0 ident=24477 gauge00=FCDU9!ACARS,1,1, 380,320 The window number is up to you, of course  For additional reference, the manual installation of the gauge is described in the User Manual, page 146. And don't forget to also install the FDR Good luck! Thank you!!! That was the problem, not sure how I managed to miss that. Been awhile since i've fiddled around with .CFG's, getting rusty!! |
|
|
|
Post by nickatc on Dec 22, 2013 20:20:15 GMT -5
Hi Dutch and Travis, thanks for the 1.5 release. I didn't try it under P3D yet because I have severe issues with that simulator (will be resolved in the next release). However, I had one issue with FSC 1.5: the new stand-alone program is really slow on my system. Any connection to FSX takes 5 seconds or so. Also, the passengers were very slow to deboard. Did anyone else have these issues? Mery Xmas, Peter I'm having the same problem, Peter. I thought it was something in my pc... but it seems I'm wrong. Mine doesn't take as long as yours, but 2 seconds of delay in any click. I decided to install the FCDU in the panel as it was done before and works flawlessly. |
|
|
|
Post by nickatc on Dec 22, 2013 23:57:14 GMT -5
Travis, Here are the results of the error I'm having with the WILCO E195 and the seat belt sign: 1. If I turn off the Seat Belt Sign, in the TEST FS SIGNALS and in the INTERFACE DATA they are both off, as they should work.  2. But when I turn on the SBS, in the INTERFACE DATA they turn on (as they should work) BUUUUUTTT in the TEST FS SIGNALS they remain off:  The same thing happens with the interface included in the V 1.5 and one you modified for me some time ago Interface_fT175195.xml (4.84 KB). The only difference between them, is that the one you modified (and that is attatched) the temperature can be modified and that can be seen on the INTERFACE DATA in cabin Temperature. For me, the one you modified works better. Any ideas on this? Thanks. |
|
|
|
Post by nickatc on Jan 10, 2014 15:58:57 GMT -5
Any idea on the issue posted above??
|
|
|
|
Post by peter on Jan 10, 2014 16:56:36 GMT -5
I only have the E170/E190 package, but I dimly remember there might be an issue with some inconsistent switch positions in the VC and 2D panels. Have you checked (without FSCaptain) that 2D panels and VC show the same settings?
Cheers,
Peter
|
|
|
|
Post by Travis on Jan 10, 2014 18:25:51 GMT -5
Nick, I'm sorry, your previous question slipped past me (and my holiday eggnog  ) !! Data from the Interface page (#60) always takes precedence over the data on the Signals page (#66). In the case of these ERJs, the interface is bypassing the MSFS-defined SIGNAL and telling the ACARS the state of those signs. In some aircraft I've found that it's better to manipulate the actual SIGNALs, and in other aircraft it's better to talk directly to the ACARS. For instance in the next iteration of the Twin Otter Extended interface, I'll expose a new Engine Anti-Ice Interface variable (which will bypass the SIGNAL value). Regards, |
|
) !!