Jump to content

Rossdavey

Frozen-Inactivity
 View Profile  See their activity

  • Content Count

    20

  • Donations

    $0.00 

  • Joined

  • Last visited

Posts posted by Rossdavey

  2. Posted

    Not sure why it's happening, thought I'd ask here before submitting a support ticket, here's the log.

     

    "An exception has occured!

    Please contact PMDG support by submitting a ticket at http://support.precisionmanuals.com for help with resolving this issue.
    Press "Copy to clipboard" below and then paste the information into your support ticket.
    Additionally, a log file has been created at:
    c:\users\ross davey\appdata\roaming\pmdg\pmdg operations center\PMDG Operations Center.log
    Please attach this file to better help us fix this issue.

    The application will now exit.

    03/07/17 15:23:48     Exception:  Unknown Exception at 0x54E8AF3E
    54E00000  C:\WINDOWS\SYSTEM32\MSVCR100.dll  +0008AF3E  (0, 0, 0)
    54E00000  C:\WINDOWS\SYSTEM32\MSVCR100.dll  +0008AF8A  (0, 0, 0)
    0FFE0000  c:\program files (x86)\pmdg operations center\Product Module 747 QOTSII P3D.dll  +0001AE92  (FFFFFFFF, DDC6D00, 10)
    71150000  C:\WINDOWS\SYSTEM32\Cabinet.dll  +00011160  (FFFFFFFF, DDC6D00, 10)
    71150000  C:\WINDOWS\SYSTEM32\Cabinet.dll  +00010772  (10, FFFAE70, DDC7FDC)
    71150000  C:\WINDOWS\SYSTEM32\Cabinet.dll  +0000EA4F  (10019C5C, 0, FFFA790)
    0FFE0000  c:\program files (x86)\pmdg operations center\Product Module 747 QOTSII P3D.dll  +0001A409  (848EF0, DDCF238, 10019C5C)
    0FFE0000  c:\program files (x86)\pmdg operations center\Product Module 747 QOTSII P3D.dll  +00023081  (623C0ECD, 0, 10095720)"

    Thanks in advance!

    Ross Davey

  12. Posted

    I'm just as excited about SP1 and the 300ER, especially after watching the two Datalink Demo vids, it looks chuffing marvellous!

    The tactic I employ to distract me from impatience include burying myself in the FCOMs we already have, I suppose it depends how seriously each individual takes it, either way, for me there's always something new to learn about this great machine, literally 1000's of pages of info relevant to both the current release and the 77W. It also serves as a reminder as to how much effort goes into the FCOM's from PMDG. Always worth the wait. Always.

  14. Posted

    What do you mean with RTO's?

    What is it? The autobrake?

     

    "Rejected Take Off", it's the autobrake setting armed in case of a mishap occuring prior to 'V1' whilst departing down the runway.

  15. Posted

    This might be a freak coincidence but I'm willing to put it out there as I feel the pain everyone else is going through at the moment.

     

    Anyway, I'm on a long haul and then surprise surprise, the "Flying without a joystick can be difficult" message popped up mid flight, so, with rage in full swing I went to the task manager and with my irrational anger selected FSX and right clicked by accident, then something odd happened, the very instance I hit the right click, In the background FSX briefly paused itself, grey textures flashed and the ENB shading I switched off earlier in the flight came back on which caught my attention, so I ignored the force quitting rage to see what was going and incredibly, my joystick was alive. I've deliberately unplugged my joystick and successfully re-connected over 5 times within the same flight to test it, the joystick is consistently working, this might be a fluke, I hope it's not. But try it out and let me know. 

     

    Crossing fingers! :(  :mellow:

    • Upvote 1

  17. Posted

    Just encountered this issue with the doors.

     

    Noticed that I had accumulated over 1300 pages of panel state files in the FMC.

     

    On further investigation, found some 19000-odd files / 826MB in the 777 panel state folder, the vast, vast majority were autosave files *.RTE, *.FMC and *.SAV, I assume courtesy of an over-enthusiastic FSUIPC.

     

    Binned all the autosaved ones, problem gone.

     

    +1

     

    Ross Davey

  19. Posted

    I have the door issue too,

     

    My temporary solution is to load the A/c fully running at a gate/stand and then to perform a 'short' shutdown, I then saved the panel state and tested it at various airports with various combinations of GSX running and not running, anyway, doors work fine! Obviously not an ideal solution but the problem seems to be deep rooted and beyond my already terrible technical knowledge, I'm sure it'll be addressed within SP1, until then try it out! hope it helps :)

×
×
  • Create New...