• Content count

  • Joined

  • Last visited

About bsmfinegan

  • Rank

Contact Methods

  • ICQ
  1. It's Active Sky that produces those effects not ASCA.
  2. Thanks Gerald, Works great thank you. I have one other problem for you to have a look at which Ben was dealing with, but he asked me to wait for the Fslabs airbus to release. Problem concerns miss dialling of altitudes when aircraft are airborne with autopilot connected and LNAV and VNAV are activated. Problem aircraft are the PMDG 747x and the MD11x also from PMDG. Commands are correctly recognized (red text), but co pilot will dial altitude knob back sometimes as much as 4000 ft before turning the other way, but will always overshoot the commanded altitude. Any further attempts to correct the altitude results in co pilot dialling altitude all the way to 50000 ft and even then the knob can be seen turning for some time afterwards. So clearly MCE is not reading the position of the altitude bug correctly in these aircraft. Would appreciate if you could take a look. Thanks Bryan.
  3. Unbelievably arrogant is closer still. Bryan.
  4. Here you go Gerald
  5. MCE crashed when attempting to select TTS voice in interface, and co pilot does not board aircraft...just hangs at splash screen. Have reset MCE to default but same problem occurs when I attempt to re select the TTS voice. The TTS voice is 32bit compatible from Cerecrop. Log Name: Application Source: Application Error Date: 24/12/2016 19:21:17 Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: Bryan-PC Description: Faulting application name: mce.exe, version:, time stamp: 0x585bcaad Faulting module name: mce.exe, version:, time stamp: 0x585bcaad Exception code: 0xc0000409 Fault offset: 0x00031b2c Faulting process id: 0x4b8 Faulting application start time: 0x01d25e1ac17a3fe1 Faulting application path: C:\Program Files (x86)\Multi Crew Experience\mce.exe Faulting module path: C:\Program Files (x86)\Multi Crew Experience\mce.exe Report Id: 245a8f8d-ca0e-11e6-98d5-fcaa149e3be2 Event Xml: <Event xmlns=""> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2016-12-24T19:21:17.000000000Z" /> <EventRecordID>64964</EventRecordID> <Channel>Application</Channel> <Computer>Bryan-PC</Computer> <Security /> </System> <EventData> <Data>mce.exe</Data> <Data></Data> <Data>585bcaad</Data> <Data>mce.exe</Data> <Data></Data> <Data>585bcaad</Data> <Data>c0000409</Data> <Data>00031b2c</Data> <Data>4b8</Data> <Data>01d25e1ac17a3fe1</Data> <Data>C:\Program Files (x86)\Multi Crew Experience\mce.exe</Data> <Data>C:\Program Files (x86)\Multi Crew Experience\mce.exe</Data> <Data>245a8f8d-ca0e-11e6-98d5-fcaa149e3be2</Data> </EventData> </Event>
  6. bargain

    FTX Central is a free download and is required to install FTX products. Bryan.
  7. Using MCE 2.6.67. Problem with PMDG 747x, haven't tried any other aircraft. Problem is repeatable, namely co pilot failing to dial correct altitude when commanded. For example commanding altitude 22,000 feet using the words "altitude twenty two thousand" always results in co pilot setting altitude to 2200 despite command clearly being ecognized by red text. If I use the words " flight level two two zero or "altitude two two thousand" co pilot sets correct altitude. Thanks.
  8. Some anomalies with PMDG 747x. Commanding altitude fl 360 co pilot correctly reads back command and then proceeds to dial random altitudes such as 41000 feet or 32100ft for example. This does not happen all the time but annoying all the same. Co pilot also has problems with selecting correct altitude when asked for a specific altitude using the words "altitude twenty one thousand two hundred" will dial 6000ft for example. When co pilot is asked to cancel dialling the incorrect altitude he then sets the altitude bug back to some random altitude as if he has forgotten the original setting. Thanks.
  9. My feeling is PMDG feel the FSX add on market is shrinking as time goes on. That means less potential revenue for them. In addition customers are demanding ever more complex aircraft which of course leads to increased dev time. I would not be at all surprised to PMDG release their next aircraft as very close to $100 or more. Bryan.
  10. I'm pretty sure the decision to release FTXG now was for two purely financial reasons. 1. For the benefit of ORBX, get some money flowing into the coffers now rather than wait for the LC to be available. 2. For the benefit of the customer, he/she gets the product into their hands now without having to wait, and also by staggering the release of FTXTG and the LC products purchasing costs are reduced in the short term, thereby enabling the customer to spread the cost.
  11. I get about a 15 sec delay from clicking a link to getting full page display. Same time frame clicking back to original page.
  12. Posting from Uk, Tracert Ping statistics for Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 90ms, Maximum = 92ms, Average = 90ms C:\Windows\system32>tracert Tracing route to [] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms BThomehub.home 2 7 ms 7 ms 7 ms 3 7 ms 7 ms 7 ms 4 8 ms 8 ms 8 ms 5 8 ms 8 ms 8 ms 6 8 ms 8 ms 8 ms 7 8 ms 8 ms 8 ms [109.1 59.249.82] 8 13 ms 8 ms 15 ms [109.159.2 49.7] 9 9 ms 8 ms 8 ms [213.121.193 .95] 10 9 ms 9 ms 9 ms 11 99 ms 89 ms 103 ms [] As can be seen the only lag occurs on the last hop.