Jump to content

michaelengl

Members
  • Content Count

    27
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

0 Neutral

Profile Information

  • Gender
    Male

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    I belong to both VATSIM & IVAO
  • Virtual Airlines
    Yes

Recent Profile Visitors

506 profile views
  1. OK Thank you. Are you the Developer of vrm modelmatching Client for Vatsim? Could you provide the file? Thank you Best Michael
  2. Hi Nico, can I use your AIL Generator for modelmatching in vpilot? Instead of xml rename in vrm? I will use the new MTL with VATSIM. Best Michael
  3. same like me MSVCP140_Atomic.dll Michael
  4. Hi , many month ago I have downloaded slopedrwyAI.dll. It was a link in simflight . de Now I see the download file in the first thread its called AI.dll Is there an Update? Soukld I delete slopedrwyAI.dll and change it to AI.dll? I the last day I have CTD with slopedrwyAI.dll. Best Michael
  5. Hi Kiek, is there any idea or Solution? I use also on the same Notebook FS-FlightControl. My Problem is That failure with disconecct from the Internet. Best Michael
  6. Hi, the application goes in red button and on end there is a failure like sim connect heartbeat. Any idea? Best Michael
  7. Hi, the camera position does not work after a normal start. All the saved views were inside the aircraft. I have to restart the chaseplane client, and than it works. Is there any trick? Best Michael
  8. Hello, has anybody the same problem with P3D v4.4? Best Michael
  9. I have problems with my P3Dv4 (latest version). If the simulator is loading the it takes 2 sec. to load ChasePlane (or EZDOK) and then I can use it. In this Moment i hear a USB connected sound. At the same time my simulator crashed. If ChasePlane is active in exe.xml there are 3 failures and the software Active Sky prompt "Cannot control ambient weather parameters" 1. Name der fehlerhaften Anwendung: PREPAR3D.EXE, Version: 4.3.29.25520, Zeitstempel: 0x5b2c3263Name des fehlerhaften Moduls: ntdll.dll, Version: 10.0.17134.376, Zeitstempel: 0x60d78cf9Ausnahmecode: 0xc0000374Fehleroffset: 0x00000000000f4d7bID des fehlerhaften Prozesses: 0x3434Startzeit der fehlerhaften Anwendung: 0x01d4737db9783be4Pfad der fehlerhaften Anwendung: D:\_P3Dv4\PREPAR3D.EXEPfad des fehlerhaften Moduls: C:\WINDOWS\SYSTEM32\ntdll.dllBerichtskennung: ae451073-6b60-4cb9-aeda-bd405c773980Vollständiger Name des fehlerhaften Pakets: Anwendungs-ID, die relativ zum fehlerhaften Paket ist: 2. Application: ChasePlane.exeFramework Version: v4.0.30319Description: The process was terminated due to an unhandled exception.Exception Info: System.AccessViolationExceptionat Microsoft.Win32.NativeMethods.ShellExecuteEx(ShellExecuteInfo)at System.Diagnostics.ShellExecuteHelper.ShellExecuteFunction()at System.Diagnostics.ShellExecuteHelper.ShellExecuteOnSTAThread()at System.Diagnostics.Process.StartWithShellExecuteEx(System.Diagnostics.ProcessStartInfo)at System.Diagnostics.Process.Start()at System.Diagnostics.Process.Start(System.Diagnostics.ProcessStartInfo)at A.Y.A()at A.Y..ctor(ChasePlane.MainWindow, System.Windows.Window, System.Collections.Generic.List`1<a.ab>)at ChasePlane.MainWindow..ctor()at a.aB.A()at a.aB.A(System.Object, System.Windows.StartupEventArgs)at System.Windows.Application.OnStartup(System.Windows.StartupEventArgs)at System.Windows.Application.<.ctor>b__1_0(System.Object)at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)at System.Windows.Threading.ExceptionWrapper.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 MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(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 MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, 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 System.Windows.Threading.ExceptionWrapper.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.Application.RunDispatcher(System.Object)at System.Windows.Application.RunInternal(System.Windows.Window)at System.Windows.Application.Run(System.Windows.Window)at a.aB.c()3. Name der fehlerhaften Anwendung: ChasePlane.exe, Version: 1.0.9.0, Zeitstempel: 0x5bc2bfe5Name des fehlerhaften Moduls: ntdll.dll, Version: 10.0.17134.376, Zeitstempel: 0x4358e406Ausnahmecode: 0xc0000005Fehleroffset: 0x00046adcID des fehlerhaften Prozesses: 0xab8Startzeit der fehlerhaften Anwendung: 0x01d4737dcfab26a6Pfad der fehlerhaften Anwendung: D:\Program Files (x86)\OldProp Solutions Inc\ChasePlane\ChasePlane.exePfad des fehlerhaften Moduls: C:\WINDOWS\SYSTEM32\ntdll.dllBerichtskennung: 73d59367-e6b7-48db-a8e5-8c1d92af9e98Vollständiger Name des fehlerhaften Pakets: Anwendungs-ID, die relativ zum fehlerhaften Paket ist: If ChasePlane was deactivated I get also 3 failure:1. Name der fehlerhaften Anwendung: PREPAR3D.EXE, Version: 4.3.29.25520, Zeitstempel: 0x5b2c3263Name des fehlerhaften Moduls: ntdll.dll, Version: 10.0.17134.254, Zeitstempel: 0xa5a334d4Ausnahmecode: 0xc0000374Fehleroffset: 0x00000000000f4d3bID des fehlerhaften Prozesses: 0x19b4Startzeit der fehlerhaften Anwendung: 0x01d47369dd3270c1Pfad der fehlerhaften Anwendung: D:\_P3Dv4\PREPAR3D.EXEPfad des fehlerhaften Moduls: C:\WINDOWS\SYSTEM32\ntdll.dllBerichtskennung: c3016c34-1d0d-4112-92ac-b3e8a8575b8dVollständiger Name des fehlerhaften Pakets: Anwendungs-ID, die relativ zum fehlerhaften Paket ist: 2. Die erweiterbare Leistungsindikator-DLL rdyboost kann nicht geladen werden. Die ersten vier Bytes (DWORD) des Datenbereichs enthalten den Windows-Fehlercode. If ChasePlane was not active and I have restart ProSim the I hear also the USC connected sound an P3D crash. Is anybody know what could be the reason. All drivers are the latest, Shaders deleted and the normal procedures in this forum i have made. Best Michael 3.Die Open-Prozedur für den Dienst "BITS" in der DLL "C:\Windows\System32\bitsperf.dll" war nicht erfolgreich. Die Leistungsdaten für diesen Dienst sind nicht verfügbar. Die ersten vier Bytes (DWORD) des Datenbereichs enthalten den Fehlercode.
  10. Hello Guys, i have installed PTA and I have failure in installation. I think no backup was generated, see red lines. What can I do? Is anybody in the forum they have these files? PTA screen Backup shader folder best Michael
  11. I have the impression that there is a mistake when I start the P3D for the first time. The second start works mostly. According to the manufacturer http://www.wideview.it is the versions for P3Dv4. Wideview and Widetraffic are server-client applications. The modules are installed on both computers. It seems like only the server is having difficulty. I only use the flight model from ProSim (Homecockpit). I have no other flight model installed. I did not understand the point with CMeteoXmlx64.dll. Should I deactivate something? Thank you Best Michael
  12. Name der fehlerhaften Anwendung: Prepar3D.exe, Version: 4.3.29.25520, Zeitstempel: 0x5b2c3263 Name des fehlerhaften Moduls: ntdll.dll, Version: 10.0.17134.254, Zeitstempel: 0xa5a334d4 Ausnahmecode: 0xc0000005 Fehleroffset: 0x000000000000f6d9 ID des fehlerhaften Prozesses: 0x383c Startzeit der fehlerhaften Anwendung: 0x01d452bdcb01c8e7 Pfad der fehlerhaften Anwendung: D:\_P3Dv4\Prepar3D.exe Pfad des fehlerhaften Moduls: C:\WINDOWS\SYSTEM32\ntdll.dll Berichtskennung: 11fa7ff9-5232-47de-8ce9-c2740f6d237b Vollständiger Name des fehlerhaften Pakets: Anwendungs-ID, die relativ zum fehlerhaften Paket ist: After the reboot, at the first start, the error comes, mostly the second start is good. I use wideview 64 and widetraffic 64, if I have deactivated both , it works. Now its this failure 0xc0000005. Is this another reason? Best Michael
×
×
  • Create New...