Prophet_LHA

Just did a flight everything was normal.

I flew an IFR flightplan yesterday. On clearance I was assigned a SID route. At climb the departure controller handed me over to oceanic center. Today, I checked everything in VOXATC. The SIDs and STARs are recognized in ProcedurePronunciationEditor. When I load an IFR flightplan made by PFPX or the default VOXATC one to eppley into flightplan trainer I get clearance to climb three thousand and to turn to 180 after departure. I have selected an airliner call sign, though. Did I forgot a setting.

I have installed VoxATC 7.41 (main program) on the FSX SP2 server. The VoxATC panel was installed into the aircraft I was using. VoxATC Remote Panel and VoxATC Net Server is installed on the client. I ran the VoxATC Net Server and VoxATC Network Client on the server. Then, I ran and enabled the VoxATC Panel on the client. The VoxATC Panel of the VC was not enabled. The traffic was injecting into FSX and I could hear the AI requesting clearence. The mic on the Laptop was activated and working. I clicked the button on my joystick and also tried it via the delete key to talk to ATC. I couldn't hear the sound of pressing the button and ATC didn't respond. The joystick....exe of VoxATC showed correctly when I pressed and released that button. I have to use the mic of my Laptop, don't I? Thereafter, I removed the VoxATC Panel from the aircraft to run it via the VoxATC Panel Proxy and also installed VoxATCRemote Panel on the server. When I am trying to run VoxATC Panel Proxy of the server I get two application error: Faulting application name: VoxATCPanelProxy.exe, version: 1.0.0.0, time stamp: 0x57eda90d Faulting module name: KERNELBASE.dll, version: 10.0.15063.502, time stamp: 0xc3955624 Exception code: 0xe0434352 Fault offset: 0x000eb802 Faulting process id: 0x220c Faulting application start time: 0x01d33f626be4ea89 Faulting application path: C:\Internal Workings\Remote\VoxATCPanelProxy.exe Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll Report Id: f7250808-c902-4b3e-8f63-01688b270874 Faulting package full name: Faulting package-relative application ID: and Application: VoxATCPanelProxy.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.IO.FileNotFoundException at GaugeProxy.Window1.Window_Loaded(System.Object, System.Windows.RoutedEventArgs) at System.Windows.RoutedEventHandlerInfo.InvokeHandler(System.Object, System.Windows.RoutedEventArgs) at System.Windows.EventRoute.InvokeHandlersImpl(System.Object, System.Windows.RoutedEventArgs, Boolean) at System.Windows.UIElement.RaiseEventImpl(System.Windows.DependencyObject, System.Windows.RoutedEventArgs) at System.Windows.UIElement.RaiseEvent(System.Windows.RoutedEventArgs) at System.Windows.BroadcastEventHelper.BroadcastEvent(System.Windows.DependencyObject, System.Windows.RoutedEvent) at System.Windows.BroadcastEventHelper.BroadcastLoadedEvent(System.Object) at MS.Internal.LoadedOrUnloadedOperation.DoWork() at System.Windows.Media.MediaContext.FireLoadedPendingCallbacks() at System.Windows.Media.MediaContext.FireInvokeOnRenderCallbacks() at System.Windows.Media.MediaContext.RenderMessageHandlerCore(System.Object) at System.Windows.Media.MediaContext.RenderMessageHandler(System.Object) at System.Windows.Media.MediaContext.Resize(System.Windows.Media.ICompositionTarget) at System.Windows.Interop.HwndTarget.OnResize() at System.Windows.Interop.HwndTarget.HandleMessage(MS.Internal.Interop.WindowMessage, IntPtr, IntPtr) at System.Windows.Interop.HwndSource.HwndTargetFilterMessage(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)

I have installed NGX version 1.20.8443. I have also reinstalled/-activated VFX central thereafter. The engine ingestion and condensation effect is still on the wrong engine.

Issue solved.

I have installed Net Server v7.41 and VoxATC v7.41 on the FSX server and the Remote Panel v7.41 on the client. I ran the VoxATC indexer. When I run the Net Server and Remote Panel the scenery is still FSX default.

I'm using VoxATC with my traffic v6. The taxi speed of the AI is about 5mph. Can I increase it. I'm also using GSX and AES.

Please, post an image of the legs page where ABBOT is on the top. Somewhere in the forum or manual is mentioned that the FMS has known issues of generating a correct bend or self-calculated wps. It could be a bug, but also the limited capability of programming a FMS in a 32bit environment.

I took a closer view. The eng jet wash is on the correct side, now. But the engine ingestion and condensation effect isn't.

I got the update, today. The effects are still shown on the engine opposite. My installed NGX Version is 1.20.8396.

Today, I uninstalled the 737 immersion package, deleted all files of the fsx folder in the appdata\local Directory and the .cfg and installed the package again. VFX and fsfx is registered in the new .cfg. The mentioned effects of the engine are still shown on the engine opposite. I'm using FSX SP2, FSUIPC 4.969, DX10 Scenery Fixer Version 3.3, Cloud Shadows Version 1.8 and Shade. I didn't have that issue with a prior version of FSUIPC, DX10 Scenery Fixer Version 3.2, Cloud Shadows Version 1.6 and Shade.

When I use the throttle Lever of engine #1 (also indicated on CDU and by steering to the right), I see the effects on engine # 2 (engine #2 was not running), and vice versa. But the cold start smoke is not at the wrong engine.

When the NGX is powered by DC only, the aileron movement is limied to 4 units on the aileron trim scale. Is the cable drive feature not modeled?

lol the orbxsystems forum is extended after I sign in

I have a ground texture in EDDW (payware airport) that is shimmering through the ground and displacing the payware scenery ground texture. It's only close around the aircraft (5-50m). I was able to detect the cause and it doesn't happen when I disable ORBX!VECTOR_EXX in the scenery library. I also have mesh sparks about 5km and a height of about 500m north of this airfield. There was a (private) fix (for my second issue) provided by an ORBX staff member but I can't find it in the forums. My ORBX products are up-to-date .