Page 2 of 2 FirstFirst 12
Results 11 to 17 of 17
  1. #11
    500+ This must be a daytime job Nick1150's Avatar
    Join Date
    Jun 2009
    Location
    Athens
    Posts
    720
    Contribute If you enjoy reading the
    content here, click the below
    image to support MyCockpit site.
    Click Here To Contribute To Our Site

    Re: Problem with build 484

    Hi to both,

    I am not sure if you are refering to me to Garys...

    Nevertheless I do not have pmSystems.

    I am still having issues. Everytime my 3 clients are switched on, windows startup opens WideFS and PM glass cockpit as it has always been doing since the beginning. The WideFS opens and then the PFD.exe (Topmost = on in the ini file) is opened in a maximized mode, and I used to seeing all gauges in my 3 clients.

    Since 484 version, the pfd.exe is opened in a maximized mode as always but there are no gauges.

    By minimizing the pfd.exe window and re-maximizing again, the gauges appear in their saved place on the screen.

    As read above Garys has solved this problem by connecting via VNC, but I do not have such an issue cause my clients are laptops connected with a VGA cable to the MIP screens, so I can see the MIP screen through the laptop screen...

    Thanks

    Nick

  2. #12
    10+ Posting Member
    Join Date
    Apr 2006
    Posts
    14
    Contribute If you enjoy reading the
    content here, click the below
    image to support MyCockpit site.
    Click Here To Contribute To Our Site

    Re: Problem with build 484

    I also autostart the gc like you Nick. What I found that had happened is that I run two instances of the GC on each machine for cap and f/o and upper and lower Eicas in an expanded desktop setup. I always had the f/o and lower eicas start first on each machine as the first monitor is the one with the desktop icons. After quiting the gc software with the q key I started them up indivdually to find that the f/o and lower Eicas were defaulting to a minimized state on the first monitor instead of the second monitor causing the second monitor to go blank. Starting the cap and upper eicas would then again start on the first monitor in a minimized state over the top of the f/o and lower eicas which is why I assume the w key was working the way it was.

    Once I could see what was happening I was then able to start each one individually again, move to its respective screen, resize and save.

    @ Blue sky.. Thanks for the desktop icons tip. I never knew you could do that.

    Gary

  3. #13
    75+ Posting Member Aaron's Avatar
    Join Date
    Nov 2010
    Location
    Spain
    Posts
    101
    Contribute If you enjoy reading the
    content here, click the below
    image to support MyCockpit site.
    Click Here To Contribute To Our Site

    Re: Problem with build 484

    Same issue here.

    Blank screen (well, I must say black hehe) at the start. I can see the gauges after minimize and the restore, or via the W key.

    The issue appears right after the update (from 482 to 486 in my case). Tomorrow we will try installing VNC, and resizing and quiting with the Q key as gary does, to see if this help.

    In addition to this, I must say I have multimonitor setup (very much like Garys, with Captain PFD and EICAS2 in one computer and FO PFD and EICAS1 on another (and two monitors in every computer, of course))

  4. #14
    500+ This must be a daytime job Nick1150's Avatar
    Join Date
    Jun 2009
    Location
    Athens
    Posts
    720
    Contribute If you enjoy reading the
    content here, click the below
    image to support MyCockpit site.
    Click Here To Contribute To Our Site

    Re: Problem with build 484

    Quote Originally Posted by Aaron View Post
    Same issue here.

    Blank screen (well, I must say black hehe) at the start. I can see the gauges after minimize and the restore, or via the W key.

    The issue appears right after the update (from 482 to 486 in my case). Tomorrow we will try installing VNC, and resizing and quiting with the Q key as gary does, to see if this help.

    In addition to this, I must say I have multimonitor setup (very much like Garys, with Captain PFD and EICAS2 in one computer and FO PFD and EICAS1 on another (and two monitors in every computer, of course))
    Hi Aaron,

    Enrico helped me out in this and to be honest I am very happy ith PM support !!!

    So Aaron, can you please check if StartElec=off in the your pfd.ini file ?

    Another question... Do your standby instruments appear, when at the same time EICAS is not ?

  5. #15
    25+ Posting Member
    Join Date
    Dec 2005
    Location
    Italy
    Posts
    46
    Contribute If you enjoy reading the
    content here, click the below
    image to support MyCockpit site.
    Click Here To Contribute To Our Site

    Re: Problem with build 484

    The StartelecOff option is for those who *want* dark screens when the GC starts up, and do not use pmSystems. It simply waits for a keypress or the FS battery to be on to fire up the Glass Cockpit.

  6. Thanks farrokh747, DHABERT thanked for this post
  7. #16
    75+ Posting Member Aaron's Avatar
    Join Date
    Nov 2010
    Location
    Spain
    Posts
    101
    Contribute If you enjoy reading the
    content here, click the below
    image to support MyCockpit site.
    Click Here To Contribute To Our Site

    Re: Problem with build 484

    Thankyou Nick and Enrico.

    Im on holydays right now, but I will test it as soon as I arrive home. I think its a great feature for cold and dark option.

    I am very happy with PM support too!!!

  8. #17
    75+ Posting Member Aaron's Avatar
    Join Date
    Nov 2010
    Location
    Spain
    Posts
    101
    Contribute If you enjoy reading the
    content here, click the below
    image to support MyCockpit site.
    Click Here To Contribute To Our Site

    Re: Problem with build 484

    I was unable to replicate this problem on my home PC, but in my simulator is still happens.

    I do not use the project magenta stand by instruments because I have analog ones by simkits, but I activated them to see if they appears or not, and the result is not. The startelecoff is off in the ini file.

    Finally, after a couple of hours and some test I found the problem is something with wideclient. If I run PFD.exe without wideclient already running, the glass cockpit works perfectly as usual, but If I run them with wideclient already running, its show me the blank screen with no gauges.

    I have also checked and this issue only happens with PM Glass cockpit 484 or 486, with 480 version there is no problem, and GC always show the gauges (With or without wideclient)

    Ive changed the order of running aplication at startup (first GC then wideclient), and everything is running fine, but still sound extrange for me!

    My configuration is one PC (two monitors, win7x64, ati 5550) for captain PFD/ND and lower EICAS (two monitors) and another (two monitors, win7x86, nvidia) for FO PFD/ND and upper eicas). Both of them with last version of wideclient and the server with last FSUIPC

Page 2 of 2 FirstFirst 12

Similar Threads

  1. Problem with build 170 (starter switch 1
    By PeterH in forum PMSystems
    Replies: 0
    Last Post: 10-28-2010, 06:13 AM
  2. Build 472 problem
    By 767300 in forum PM Boeing GC
    Replies: 1
    Last Post: 02-24-2010, 11:31 AM
  3. build 452 boeing gc problem
    By 767300 in forum PM Boeing GC
    Replies: 6
    Last Post: 12-13-2007, 03:50 PM
  4. build 452 boeing gc problem
    By 767300 in forum PM General Q & A
    Replies: 6
    Last Post: 12-13-2007, 03:50 PM
  5. Re: GC latest build problem
    By JAMES WEBSTER in forum PM General Q & A
    Replies: 1
    Last Post: 01-11-2006, 08:34 PM