|
Post by Piggly on May 9, 2016 8:28:43 GMT -5
I really need help. I am no good at cfg. files and donĀ“t understand any of it... But FsCaptain seems to be installed all correctly and running well.. It is just my FCOM/FCDU that is black screen (No white Turn On button) I have read all these threads and googled the problem and read everything about this issue. but nothing seems to help..
Please help me.. My OS is Windows 10
Thank you in advance
|
|
|
Post by peter on May 9, 2016 16:42:41 GMT -5
Hi Piggly,
never despair, we're happy to help. A black rectangle usually means that the FCDU gauge is not properly installed. Did you try to launch the FCDU.exe from outside FSX?
To analyze the problem, can you send us (see blue link below) a zip file with your FSCaptain\Data\Log folder? Please send the email to all of us and copy the address of this thread into your message so that everyone on the FSCaptain team knows what the logs are for.
Cheers, Peter
|
|
|
Post by davicho61 on Nov 12, 2016 12:18:36 GMT -5
Just changing FCOM by FCDU and works well in PMDG 737, 744, MD11, PSS-B757, LevelD B763, Feelthere B733-35, B772, but with Feelthere Airbus 318 - 346 it doesn't appear well, and with Leonardo MD82 the same, I continue to use FCOM, but still a problem, il appears after some seconds and have to wait... and wait, maybe because I don't use VC panel. FS9.1 Win 7. Thanks for your help.
|
|
|
Post by Dutch Owen on Nov 12, 2016 23:47:46 GMT -5
Just changing FCOM by FCDU and works well in PMDG 737, 744, MD11, PSS-B757, LevelD B763, Feelthere B733-35, B772, but with Feelthere Airbus 318 - 346 it doesn't appear well, and with Leonardo MD82 the same, I continue to use FCOM, but still a problem, il appears after some seconds and have to wait... and wait, maybe because I don't use VC panel. FS9.1 Win 7. Thanks for your help. I think we can help you with this, if you could post or send us your panel.cfg file from the airplane. Dutch
|
|
|
Post by davicho61 on Nov 13, 2016 1:30:18 GMT -5
Thanks Dutch I'll send you my panel.cfg to the A318 and to the MD82. I think if you fixed the A318 I'll have to do the same for the A319 - A346. Thanks again panel.cfg (10.13 KB) panel.cfg (5.76 KB) Attachments:panel.cfg (5.75 KB)
panel.cfg (10.13 KB)
|
|
|
Post by Travis on Nov 14, 2016 22:39:45 GMT -5
Hi Davicho61,
Your panel.cfg files both appear bad - they're similar to the last one you submitted to us - multiple FCOM/FCDU gauges, and no FDR in non-VC placements.
Here are my attempts at corrections - but as I don't run FS9, they may not be perfectly correct....
Maddog panel.cfg (5.65 KB)
A318 panel.cfg (10.13 KB)
Regards,
|
|
|
Post by davicho61 on Nov 15, 2016 4:20:59 GMT -5
Thanks a lot Travis, but I've this little problem with FCOM, only in Feelthere Airbus and MAddog.
|
|
|
Post by Travis on Nov 17, 2016 0:58:27 GMT -5
Thanks a lot Travis, but I've this little problem with FCOM, only in Feelthere Airbus and MAddog. That looks like a ZORDER issue. Try adding this line before both of your ACARS gauge references: zorder=99So it would look like this... [Window09] size_mm=373,447 position=8 visible=0 ident=24477 zorder=99 gauge00=FCOM9!ACARS,1,1,373,447... and this... [Window14] size_mm=373,447 position=8 visible=0 ident=24477 zorder=99 gauge00=FCOM9!ACARS,1,1,373,447Regards,
|
|
|
Post by davicho61 on Nov 17, 2016 7:59:54 GMT -5
Thanks Travis, right now with zorder99 all is ok. Thanks!
|
|