Jump to content

Pandanator 2

Frozen-Inactivity
  • Content Count

    69
  • Donations

    $0.00 
  • Joined

  • Last visited

Posts posted by Pandanator 2


  1. My MS flight days feel so ancient now! Hard to believe it was only a few months ago I was still playing religiously.... Haven't launched since the shutdown date though...

     

    But this sounds like great news! I hope good comes out of it. I also heard of the news that FSX was coming to Steam, but didn't know they had intentions for Microsoft Flight. Is there anything new to find?


  2. I never had any install issues. If you mean the start-up issue I had with the Add-on Builder, I fixed that by taking your advice and installing the C++ you linked. Fixed the issue.

     

    Here's what happened in the event viewer (windows logs-applications)

     

     Faulting application name: Flight.exe, version: 1.1.1.30063, time stamp: 0x5052284a

    Faulting module name: ntdll.dll, version: 6.3.9600.16408, time stamp: 0x523d45fa
    Exception code: 0xc0000374
    Fault offset: 0x000e2fd8
    Faulting process id: 0x6924
    Faulting application start time: 0x01cf07b4853c71c2
    Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight\Flight.exe
    Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
    Report Id: d564dc02-73a7-11e3-be8c-9c2a7068feb2
    Faulting package full name: 
    Faulting package-relative application ID: 

  3. Panda, can you check the Event Viewer to see if there were any errors with Addon Builder? (Type Event Viewer into the search window in the Control Panel, and then click "View Event Logs", and look under Windows Logs\Application)

     

    Also, what version of Windows are you using?

    I am using windows 8, and here is what I found in the events log, these are only errors, not the information ones. If you need the information ones I can get those too.

     

    Faulting application name: AddonBuilder.exe, version: 0.9.0.0, time stamp: 0x52b6b2ce
    Faulting module name: KERNELBASE.dll, version: 6.3.9600.16408, time stamp: 0x523d4548
    Exception code: 0xe0434352
    Fault offset: 0x00012eec
    Faulting process id: 0x2c0c
    Faulting application start time: 0x01cf00473d4ec72f
    Faulting application path: C:\Program Files (x86)\Flight Tools\Flight Toolkit\AddonBuilder.exe
    Faulting module path: C:\WINDOWS\SYSTEM32\KERNELBASE.dll
    Report Id: 7b7b1250-6c3a-11e3-be86-9c2a7068feb2
    Faulting package full name: 
    Faulting package-relative application ID: 
     
    Application: AddonBuilder.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an unhandled exception.
    Exception Info: System.Windows.Markup.XamlParseException
    Stack:
       at System.Windows.Markup.WpfXamlLoader.Load(System.Xaml.XamlReader, System.Xaml.IXamlObjectWriterFactory, Boolean, System.Object, System.Xaml.XamlObjectWriterSettings, System.Uri)
       at System.Windows.Markup.WpfXamlLoader.LoadBaml(System.Xaml.XamlReader, Boolean, System.Object, System.Xaml.Permissions.XamlAccessLevel, System.Uri)
       at System.Windows.Markup.XamlReader.LoadBaml(System.IO.Stream, System.Windows.Markup.ParserContext, System.Object, Boolean)
       at System.Windows.Application.LoadBamlStreamWithSyncInfo(System.IO.Stream, System.Windows.Markup.ParserContext)
       at System.Windows.Application.LoadComponent(System.Uri, Boolean)
       at System.Windows.Application.DoStartup()
       at System.Windows.Application.<.ctor>b__1(System.Object)
       at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
       at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
       at System.Windows.Threading.DispatcherOperation.InvokeImpl()
       at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(System.Object)
       at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
       at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
       at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
       at System.Windows.Threading.DispatcherOperation.Invoke()
       at System.Windows.Threading.Dispatcher.ProcessQueue()
       at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
       at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
       at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
       at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
       at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
       at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
       at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
       at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
       at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
       at System.Windows.Threading.Dispatcher.PushFrame(System.Windows.Threading.DispatcherFrame)
       at System.Windows.Threading.Dispatcher.Run()
       at System.Windows.Application.RunDispatcher(System.Object)
       at System.Windows.Application.RunInternal(System.Windows.Window)
       at System.Windows.Application.Run(System.Windows.Window)
       at FlightAddonBuilder.App.Main()
     
    Faulting application name: AddonBuilder.exe, version: 0.9.0.0, time stamp: 0x52b6b2ce
    Faulting module name: KERNELBASE.dll, version: 6.3.9600.16408, time stamp: 0x523d4548
    Exception code: 0xe0434352
    Fault offset: 0x00012eec
    Faulting process id: 0x4e4
    Faulting application start time: 0x01cf00473599957d
    Faulting application path: C:\Program Files (x86)\Flight Tools\Flight Toolkit\AddonBuilder.exe
    Faulting module path: C:\WINDOWS\SYSTEM32\KERNELBASE.dll
    Report Id: 74d856c6-6c3a-11e3-be86-9c2a7068feb2
    Faulting package full name: 
    Faulting package-relative application ID: 
     
    Application: AddonBuilder.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an unhandled exception.
    Exception Info: System.Windows.Markup.XamlParseException
    Stack:
       at System.Windows.Markup.WpfXamlLoader.Load(System.Xaml.XamlReader, System.Xaml.IXamlObjectWriterFactory, Boolean, System.Object, System.Xaml.XamlObjectWriterSettings, System.Uri)
       at System.Windows.Markup.WpfXamlLoader.LoadBaml(System.Xaml.XamlReader, Boolean, System.Object, System.Xaml.Permissions.XamlAccessLevel, System.Uri)
       at System.Windows.Markup.XamlReader.LoadBaml(System.IO.Stream, System.Windows.Markup.ParserContext, System.Object, Boolean)
       at System.Windows.Application.LoadBamlStreamWithSyncInfo(System.IO.Stream, System.Windows.Markup.ParserContext)
       at System.Windows.Application.LoadComponent(System.Uri, Boolean)
       at System.Windows.Application.DoStartup()
       at System.Windows.Application.<.ctor>b__1(System.Object)
       at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
       at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
       at System.Windows.Threading.DispatcherOperation.InvokeImpl()
       at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(System.Object)
       at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
       at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
       at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
       at System.Windows.Threading.DispatcherOperation.Invoke()
       at System.Windows.Threading.Dispatcher.ProcessQueue()
       at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
       at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
       at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
       at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
       at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
       at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
       at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
       at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
       at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
       at System.Windows.Threading.Dispatcher.PushFrame(System.Windows.Threading.DispatcherFrame)
       at System.Windows.Threading.Dispatcher.Run()
       at System.Windows.Application.RunDispatcher(System.Object)
       at System.Windows.Application.RunInternal(System.Windows.Window)
       at System.Windows.Application.Run(System.Windows.Window)
       at FlightAddonBuilder.App.Main()
     
     

     


  4. Great read Luis. Agreed on all points. 

     

    Having flown some real planes I can confirm that Flight hits the spot for flight models. Really great.

     

    In my opinion, Flight will always have a special place. It's the reason I started flying real planes. I have it to thank for learning a lot about aviation and getting me into flight simming. It's never leaving my hardrive. 


  5. Kaluhui has always been my favorite Flight airport in Hawaii. Just because it had everything, a VOR, an ILS (bet you can tell I love IFR!) 2 easily accessible runways and amazing scenery. If you're ever looking for a challenge , fly into the canyons at the north tip and try to make it all the from one end to the other. It's like a maze in there.


  6. So I had this happen to me for the first time ever. 

     

    n92BN5Q.jpg

    Never had this occur before. In fact I was able to run Flight on medium-high graphics before. 

     

    I know my graphics card is a bit outdated, but it's always been able to run Flight perfectly fine. Any tips? Hope it's not a permanent problem.


  7. Come on guys, let's not let this spiral into another insult thread. Microsoft Flight was not a "failure" from an economic standpoint. It was making money (a good amount too I'd think) but it wasn't enough for Microsoft. So they pulled the plug far too early

     

    Of course we are all entitled to our opinion, but we respect other's sim of choice. Simply because you think that Flight was a failure does not mean everyone does. Nor does it mean that you can come in here and say Flight is a failure and that we should just move on. I'd refer you to the Microsoft Flight Archive to see what that leads to.

     

    Far more than 15 people play Flight and enjoy it. Perhaps if you logged into Flight for just one more time and looked for a multiplayer server you would see this. Many people were purchasing content until the Microsoft point cutoff. Many still enjoy the big island in a biplane and a floatplanes. 

     

    Now please guys, if you hate Flight, simply leave it alone. If you have nothing nice to say, say nothing at all.

×
×
  • Create New...