Jump to content
The simFlight Network Forums

Search the Community

Showing results for tags 'vrinsight mcp combo vspe'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Product Support Forums
    • FSUIPC Support Pete Dowson Modules
    • MyTraffic Support Forum
    • FeelThere Support Forums
    • FS Commander Support Forum
    • Flying W Simulation
    • AConstable Traffic Sounds Support Forum
    • Fabio Merlo Products Support Forum
    • Elite-Air Studio Support Forum
    • Nikola Jovanovic Support Forum
    • Intrasystems Support Forum
    • Taburet & DanVFR Support Forum
    • Environ Scenery
  • simFlight DE
  • simRussia


There are no results to display.

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 2 results

  1. Hello Pete, folks, My problem is, that when I'm using the FSUIPC feature for VRInsight serial devices the Prepar3D v5 flight sim does not quit all processes when I'm leaving it with CTRL+C or by the "Exit..." menu function. I have this entry in the FSUIPC ini: [VRInsight] 1=COM3,COM12 Everything works great with it besides the mentioned problem. All is set up according to the FSUIPC manual including the Virtual Serial Ports Emulator software. When I start the sim (Prepar3D v5 Hotfix 2) the VRInsight software SerialFP2 is starting and my MCP panel is functional. After the flight when I quit the sim the windows are all closing and I'm back to desktop. But a background process is left -> "Prepar3D exe" using about 2 gigs of main memory. It's visible with the windows task-manager. Another evidence of the running process is the microphone icon in the system tray which pops up when an application accesses the microphone, in this case Prepar3D v5. It remains in the tray after quitting the sim. When I shut down the background task by the task-manager function the microphon icon is removed. Commenting out or removing the [VRInsight] entry in the FSUIPC ini solves the problem, no background process remains in the main memory after quitting the sim. This is 100% reproducible for me. It doesn't matter whether SerialFP2 or Virtual Serial Ports Emulator were started. ********* FSUIPC6, Version 6.0.10 (19th July 2020) by Pete & John Dowson ********* Prepar3D.exe version = Running inside Prepar3D v5 Module base=7FFA9B9D0000 Windows 10 Home 64 Bit reported as Build 18363, Release ID: 1909 (OS 10.0) Reading options from "C:\Users\Rainer\Documents\Prepar3D v5 Add-ons\FSUIPC6\FSUIPC6.ini" Checking the Registrations now ... User Name="Rainer Meisel" User Addr="rainer@meisel21.net" FSUIPC6 Key is provided ... 672 VRI port 1 "COM3" opened 672 VRI driver port 1 "COM12" also opened ... 162125 -------------------- Starting everything now ---------------------- 162125 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N 162703 Run: "c:\Program Files (x86)\VRInsight\bin\SerialFP2.exe 0 30" 163719 VRI COM3 <--- CMDRST [to Device] 163813 Advanced Weather Interface Enabled 163891 VRI COM3 <--- CMDCON [to Device] 164453 VRI COM12 <--- CMDCON [to VRI Driver] 164516 VRI COM3 <--- CMDFUN [to Device] 164578 VRI FMER ("MCP Combi") detected on port COM3 164578 VRI COM12 <--- CMDFMER [to VRI Driver] 164703 VRI COM3 <--- CMDVER [to Device] 164750 VRI COM12 <--- CMD2.520 [to VRI Driver] 165438 Deactivated for PID=16228, "SerialFP2.exe" 165453 Lost focus to PID=16228, "SerialFP2.exe" 172735 Lost focus to PID=16228, "SerialFP2.exe" 195047 WRITE0[16228] 330A, 2 bytes: D2 07 .. 195391 VRI COM3 <--- CMDFR... [to Device] 195625 VRI COM3 <--- ALT10000 [to Device] 195828 VRI COM3 <--- DSP1*00* [to Device] 196016 VRI COM3 <--- DSP0<00> [to Device] 282610 KEYDOWN: VK=18, Waiting=0, Repeat=N, Shifts=4 282610 .. Key not programmed -- passed on to FS 289438 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y 289438 Sim stopped: average frame rate for last 129 secs = 25.0 fps 289438 Max AI traffic was 31 aircraft 289438 ------------------------------------------------------------------- 291641 === Closing session: waiting for DLLStop to be called ... 299156 === DLLStop called ... 299156 === Closing external processes we started ... 299172 VRI COM3 <--- CMDRST.. [to Device] 300360 === About to kill any Lua plug-ins still running ... 300500 === Closing global Lua thread 301516 === About to kill my timers ... 301719 === Restoring window procs ... 301719 === Unloading libraries ... 301719 === stopping other threads ... 301719 === ... Button scanning ... 301813 === ... Axis scanning ... 301922 === Releasing joystick devices ... 301922 === Freeing macro memory 301922 === Removing any offset overrides 301922 === Clearing any displays left 301922 === NOTE: not calling SimConnect_Close ... 301922 === AI slots deleted! 301922 === Freeing button memory ... 301922 === Deleting wxstationlist.bin file ... 301922 === Closing my Windows ... 301922 === Freeing FS libraries ... 301922 === Deleting wxstationlist.bin file ... 301922 === Closing my Windows ... 301922 === Freeing FS libraries ... 302922 === Closing devices ... 305422 #A Terminating VRI thread 305438 ... returned okay! Best wishes, Rainer
  2. Hello, First I do not know where to publish the question, here or send it to VRInsight support. I have FS9 and want to use the MCP Combo panel II with Qwality wings BAe AVRO RJ100. To make this work I know I have to user the combination of VSPE and FSUIPC to create macros for the different buttons, swicthes, rotary, etc. I have setup the VSPE with the pair COM2 and COM4. I have modify the FSUIPC and include the section: [VRInsight] 1=COM3, COM4 The MCP Combo is running in COM3 port. I started first the VSPE, then the FS9 and when I have the AVRO loaded I then run the VRSim, but it does not change the port in VRSim, it always show the COM3, and I guess it should show COM4. I followed the doc FSUIPC_VRInsight_mod.pdf created by Günter Steiner “guenseli”. Any thoughts? Thanks Kiko
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.