Sabrefly

Even better. Thanks, Igor.

I have it working in P3Dv3 now. A kind soul from another forum sent me a tiny exe that easily converts fxml to flt with the same name when you drag and drop the fxml on it. Therefore RC4 can find and read the converted flt file and this works perfect, so RC4 is still good for saving and loading flight situations in P3Dv3.3-3.4 Igor.

CAG2 thanks for the excellent utility, is there a way to keep vertical speed at t/d shown longer on the screen? Thanks,

Hello, can Virtualflight run on a WideClient PC? Thanks,

Very interesting, might be used with ATC on the WideClient. Thanks,

Sorry, I forgot and couldn't find in the documents why these facilities were introduced in FSUIPC/Misc? How are they different from the main FSX/P3D menu? Thanks, PS: one avantage, and perhaps the only one, I can think of is using Explorer for loading flights and flight plans, which may be quite convenient. Any others?

I understand it does look in the flights folder, and even reads smth in the flt file, that's why a converter is needed to translate the saved fxm to flt. Renaming fxm to flt does not work. Igor.

Pete, could you share your current settings of [Traffic Limiter] section? Thanks, Igor.

Now I'm looking for fxmltoflt converter as per this thread: https://www.avsim.com/forums/topic/483684-p3d-v3-saved-flight-issue/ Unfortunately the link to the converter is dead there and I'm still looking for it. RC4 via FSUIPC (as I understad) saves fxml files OK along with its rcd files. But when loading a flight situation RC4 also looks for the flt file. So if I can find a fxml to flt converter then that should work. Thanks, Igor.

Pete, there used to be a very convenient feature in RC4/FSX to resume saved flights by loading Previously Saved RCDs. Is there a way to resume saved flights with RC4 in P3Dv3? I know that RC4 is looking for a *.flt not *.fxml flight file to resume. Is there a way around it? Thanks, Sabre.

I wish I could check and play with it, but I got into a hospital unexpectedly, hope will be back to normal in 2-3 days, will report on 4.966+ Thanks, Igor

Here's a good log of P3Dv3.3.5 + FSUIPC v4.965 + SimconnectP3D v3.0.0.13948 ********* FSUIPC4, Version 4.965 (6th April 2017) by Pete Dowson ********* Windows 10 Pro 64 Bit reported as Build 14393, Release ID: 1607 (OS 10.0) Prepar3D.exe version = 3.3.5.17625 Reading options from "F:\Lockheed Martin\Prepar3D v3\Modules\FSUIPC4.ini" Running inside Prepar3D v3 on Windows 10 Module base=53250000 User Name="Igor Petrov" User Addr="petrovigor@umail.ru" FSUIPC4 Key is provided WideFS7 Key is provided 16 System time = 13/04/2017 11:36:21 16 FLT UNC path = "\\I6\Prepar3D v3 Files\" 16 ------ Module Version Check ------ 16 acontain.dll: 3.3.5.17625 16 api.dll: 3.3.5.17625 16 controls.dll: 3.3.5.17625 16 fs-traffic.dll: 3.3.5.17625 16 G3D.dll: 3.3.5.17625 16 language.dll: 3.3.5.17625 16 sim1.dll: 3.3.5.17625 16 visualfx.dll: 3.3.5.17625 16 weather.dll: 3.3.5.17625 16 window.dll: 3.3.5.17625 16 ---------------------------------- 16 Trying F:\Lockheed Martin\Prepar3D v3\Modules\SimConnectP3D3.dll 16 Found it: trying to connect 16 FS UNC path = "\\I6\Prepar3D v3\" 79 ---------------------- Joystick Device Scan ----------------------- 79 Product= Control Manager ID #00 79 Manufacturer= Control Manager ID #00 79 Serial Number= Control Manager ID #00 79 Vendor=068E, Product=C011 (Version 0.0) 79 Assigned joystick id 0 (Registry okay) 94 GUID= {C82A9610-1924-11E6-8001-444553540000} 94 Product= Saitek P8000 94 Manufacturer= Saitek 110 Serial Number= 00200473 110 Vendor=06A3, Product=05D2 (Version 1.0) 110 Assigned joystick id 1 (Registry okay) 110 GUID= {6353CB80-18FC-11E6-8003-444553540000} 110 Product= Control Manager ID #00 110 Manufacturer= Control Manager ID #00 110 Serial Number= Control Manager ID #00 110 Vendor=068E, Product=C010 (Version 0.0) 110 Assigned joystick id 2 (Registry okay) 110 GUID= {C82C6AD0-1924-11E6-8002-444553540000} 110 Product= Control Manager ID #00 110 Manufacturer= Control Manager ID #00 110 Serial Number= Control Manager ID #00 110 Vendor=068E, Product=C013 (Version 0.0) 110 Assigned joystick id 3 (Registry okay) 110 GUID= {C87A3CB0-1924-11E6-8003-444553540000} 110 Product= Control Manager ID #00 110 Manufacturer= Control Manager ID #00 110 Serial Number= Control Manager ID #00 110 Vendor=068E, Product=C012 (Version 0.0) 110 Assigned joystick id 4 (Registry okay) 110 GUID= {C87B2710-1924-11E6-8004-444553540000} 110 Product= F16 MFD 1 110 Manufacturer= Thrustmaster 110 Vendor=044F, Product=B351 (Version 1.0) 110 Assigned joystick id 6 (Registry okay) 110 GUID= {E21EB120-1927-11E6-8001-444553540000} 110 ------------------------------------------------------------------- 219 LogOptions=00000000 00000001 219 ------------------------------------------------------------------- 219 ------ Setting the hooks and direct calls into the simulator ------ 219 --- CONTROLS timer memory location obtained ok 219 --- SIM1 Frictions access gained 219 --- FS Controls Table located ok 219 --- Installed Mouse Macro hooks ok. 219 --- Wind smoothing fix is installed 219 --- SimConnect intercept for texts and menus option is off 219 --- All links okay (except older global weather setting method) 219 ### Traffic limited by user parameter to 200 aircraft 219 ------------------------------------------------------------------- 219 SimConnect_Open succeeded: waiting to check version okay 219 Trying to use SimConnect Prepar3D 219 VRI port 1 "com3" failed to open 219 Opened separate AI Traffic client okay 30594 Running in "Lockheed Martin® Prepar3D® v3", Version: 3.3.3.3 (SimConnect: 3.3.0.0) 30594 Initialising SimConnect data requests now 30594 FSUIPC Menu entry added 30610 \\I6\Users\I6\AppData\Local\Lockheed Martin\Prepar3D v3\Prepar3D_Default.fxml 30610 \\I6\Prepar3D v3\SimObjects\Airplanes\IRIS Raptor Driver\Raptor.air 164313 === DLLStop called ... 164313 === Closing external processes we started ... 165313 === About to kill any Lua plug-ins still running ... 165469 === Closing global Lua thread 166469 === About to kill my timers ... 166672 === Restoring window procs ... 166672 === Unloading libraries ... 166672 === stopping other threads ... 166672 === ... Memory checking ... 166672 === ... Button scanning ... 166766 === ... Axis scanning ... 166860 === Releasing joystick devices ... 166860 === Freeing macro memory 166860 === Removing any offset overrides 166860 === Clearing any displays left 166860 === NOTE: not calling SimConnect_Close ... 166860 === AI slots deleted! 166860 === Freeing button memory ... 166860 === Closing my Windows ... 166860 === Freeing FS libraries ... 167860 === Closing devices ... 168860 === Closing the Log ... Bye Bye! ... 168860 System time = 13/04/2017 11:39:10 168860 *** FSUIPC log file being closed Minimum frame rate was 32768.0 fps, Maximum was 0.0 fps Minimum available memory recorded was 32768Mb Maximum AI traffic for session was 0 aircraft Traffic deletions 0 aircraft Memory managed: 14 Allocs, 14 Freed ********* FSUIPC Log file closed *********** Thanks, Igor.

Pete, honestly I didn't even try that file you posted abouve, I just downloded it, checked the version and saw that I had the same one from my previous backups, and it is working with both v4.964 and v4.965. Thanks, Igor.

Pete, I reinstalled P3Dv3.3.5 client then removed all files from Modules folder and installed the very recent FSUIPC v4.964 (made 1st March 2017) full intaller. I found that FSUIPC v4.964 installer still put in SimConnectP3D v3.0.0.13948 file. So SimConnectP3D v3.4.22.19868 in FSUIPC appeared very recently and was intended (most probably) for P3Dv3.4 hf3. I tried P3Dv3.4 hf3 with FSUIPC v4.965 (SimConnectP3D v3.4.22.19868) and it works. Unfortunately handling of VAS by P3Dv3.4 hf3 is very much inferior to P3Dv3.3.5, whereas occupied blocks of VAS don't get released like they do in P3Dv3.3.5. So, like you wrote, I'll need to use SimConnectP3D v3.0.0.13948 with your further versions of FSUIPC. Also, there is nothing seemingly wrong with my P3D installation. Just SimConnectP3D v3.4.22.19868 was intended for the latest version of P3Dv3.4 as seen above. Thanks, Igor.

Ok, If you could tell me when you added this specific version 4.22.19868 to FSUIPC installation (version number?) replacing version 3.0.0.13948 then I would figure out what could have gone wrong with my P3D install/update (if it really went wrong at all) at some point. Thanks, Igor.

I was posting my findings when I saw you posted, almost at the same time. I have no idea, when did SimConnectP3D3.dll, version: 3.4.22.19868, come along? I keep my Acronis copies of P3D folder, so I can trace back in time. Igor.

Deleted

Deleted

Ok, here's my current work around: Having gone through the logs I didn't like SimConnectP3D3.dll (version: 3.4.22.19868 not sure how it got there?) so I decided to drop in a previous version 3.0.0.13948 of SimConnectP3D3.dll. With this version FSUIPC v4.965 starts ok!! Please explain Thanks.

The above happens on Win10 x64; only with P3Dv3.3.5 + FSUIPCv4.965 combination (and P3Dv3.3.5 is important for me and for many) Please see what can be done. Thanks, Igor.

Log Name: Application Source: .NET Runtime Date: 4/13/2017 12:31:32 AM Event ID: 1026 Task Category: None Level: Error Keywords: Classic User: N/A Computer: I6 Description: Application: Prepar3D.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: exception code c0000005, exception address 5A9E4787 Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name=".NET Runtime" /> <EventID Qualifiers="0">1026</EventID> <Level>2</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2017-04-12T21:31:32.016480100Z" /> <EventRecordID>67591</EventRecordID> <Channel>Application</Channel> <Computer>I6</Computer> <Security /> </System> <EventData> <Data>Application: Prepar3D.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: exception code c0000005, exception address 5A9E4787 </Data> </EventData> </Event> Log Name: Application Source: Application Error Date: 4/13/2017 12:31:32 AM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: I6 Description: Faulting application name: Prepar3D.exe, version: 3.3.5.17625, time stamp: 0x5758bb31 Faulting module name: SimConnectP3D3.dll, version: 3.4.22.19868, time stamp: 0x58df7864 Exception code: 0xc0000005 Fault offset: 0x00004787 Faulting process id: 0x16b8 Faulting application start time: 0x01d2b3d4057df3be Faulting application path: F:\Lockheed Martin\Prepar3D v3\Prepar3D.exe Faulting module path: F:\Lockheed Martin\Prepar3D v3\Modules\SimConnectP3D3.dll Report Id: 5e2cc354-46ad-4216-9898-cc40e459ca2d Faulting package full name: Faulting package-relative application ID: Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2017-04-12T21:31:32.070625500Z" /> <EventRecordID>67592</EventRecordID> <Channel>Application</Channel> <Computer>I6</Computer> <Security /> </System> <EventData> <Data>Prepar3D.exe</Data> <Data>3.3.5.17625</Data> <Data>5758bb31</Data> <Data>SimConnectP3D3.dll</Data> <Data>3.4.22.19868</Data> <Data>58df7864</Data> <Data>c0000005</Data> <Data>00004787</Data> <Data>16b8</Data> <Data>01d2b3d4057df3be</Data> <Data>F:\Lockheed Martin\Prepar3D v3\Prepar3D.exe</Data> <Data>F:\Lockheed Martin\Prepar3D v3\Modules\SimConnectP3D3.dll</Data> <Data>5e2cc354-46ad-4216-9898-cc40e459ca2d</Data> <Data> </Data> <Data> </Data> </EventData> </Event> Thanks, Igor

So, here's FSUIPC LOG Event viewer logs will follow

I'll simplify the logs by unloading some dlls and exe's then post the logs.

I referred to this thread: Modifications you intended didn't work in Win10 x64 as I remember now. Igor.

Sounds like there's hope then! Ok, I'll send you the logs like you taught me about a month earlier, just need to search that thread on the forum. Igor. PS: the P3D just hangs up at launch at P3D Splash window.