Jump to content
The simFlight Network Forums

Search the Community

Showing results for tags 'fsuipc5'.

More search options

  • 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
    • FScene Support Forum
    • Taburet & DanVFR Support Forum
    • Flying W Simulation
    • AConstable Traffic Sounds Support Forum
    • CLS Support
    • Fabio Merlo Products Support Forum
    • Elite-Air Studio Support Forum
    • Nikola Jovanovic Support Forum
    • iBlueYonder Support
    • Intrasystems Support Forum
    • FSPS Support Forum (LEGACY)
  • simFlight DE
    • FS Software
    • FS Hardware
    • FS MAGAZIN Forum
  • simRussia
  • FSUIPC Client DLL for .NET


  • Community Calendar


There are no results to display.

Found 14 results

  1. I am running FSUIPC 5 1.03g, registered. I am trying to run a LUA script (via Key Presses section) that I used with P3Dv3 that controls my PMDG 737NGX home made overhead panels, etc. in P3Dv4. I exclusively use UDP to communicate between Arduinos and FSUIPC which uses Lua Sockets. I now get the LUA error: I am assuming this is because I have not compiled a 64 bit version of LUA. I installed the 32 bit version a long time ago and I muddled my way through it with Luarocks version 5.1.x, I believe. My question is, am I on the right path in believing that I need to figure out how to compile it again with 64 bit? I am not very strong on these sorts of things and I can't find any clear cut ways to do it on my Win7-64 box. The searches I am coming up with are all over the map on ways to do it. Has anyone done this yet that could advise on what I need to do or point me to a URL that explains the best way? Thanks in advance, Dustin
  2. Hi Pete One of my users has been reporting issues with FSUIPC5 when changing aircraft when multiple LUA files are in use. The user is using the Lua file multiaxis.lua which allows axes to be swapped when a joystick button is pressed. The command is communicated via the offset 0x66C0). There appears to be a conflict with LINDA when called, normally, via ipcready.lua and the [auto] section loading Lua multiaxis. Renaming ipcready.ipc prevents the crash but this means that LINDA LUA modules not being loaded. [auto] 1=lua multiaxis [LuaFiles] 1=ipcReady 2=linda 3=AirbusX_Thr1 4=AirbusX_Thr2 5=FSUIPC5_test 6=Multiaxis [Axes] 0=JX256,F,L5:V,0,0,0 -{TO SIM: luaValue Multiaxis }- [Buttons] PollInterval=25 ButtonRepeat=20,10 1=R2,4,Cx42000BC0,xC0010100 -{offset sword decrement, offset 0BC0 (Decr=256, Limit=-16383)}- 2=R2,5,Cx32000BC0,x3FFF0100 -{offset sword increment, offset 0BC0 (Incr=256, Limit=16383)}- 3=P3,3,Cx030066C0,x0000FA88 -{offset dword set, offset 66C0}- 4=U3,3,Cx030066C0,x000100E3 -{offset dword set, offset 66C0}- With P3Dv4, LINDA 3.0.2 and Multiaxis.lua running, P3Dv4 crashes on aircraft change with the Event Viewer (see attached) showing a crash in FSUIPC5.dll. I am not sure whether this problem is associated with the LUA thread management changes you made earlier. These tests were carried out with FSUIPC 5.112. The user also reported the same crash with FSUIPC4 4.971 (log attached). FSUIPC5.ini FSUIPC5-crashOnAircraftChange.log Multiaxis.lua MULTIAXIS_crash.txt FSUIPC4_Crash_LINDA_302_FSUIPC_471.log
  3. Pete, your FSUIPC4 installers have a manifest that requests escalated permissions; no need to run as admin as it will automatically request to do that. The FSUIPC5 installers do not appear to have this. Is there any chance this could be added to them? It makes running them out of the ZIP easier since I don't have to extract them from the archive. On a side note, when you do your list of changes would it be possible to list the version that each change was added? Cheers! Luke
  4. Hi, Since I switched to P3D v4 and FSUIPC5, on Windows 10, I have a crash problem. I have 5 game controlers (2 pokeys, 1 Saitek combat Rudder, 2 Saitek Throttle Quadrant) on the same USB self-powered HUB. On P3D v3 and FSUIPC4 all was good. I can install FSUIPC5 without problem, registration is ok, but when i start P3D v4 i have a CTD with error 0xc0000005 or 0xc0000374 Faulting application Prepar3d.exe Faulting module ntdll.dll If I start again P3D v4 and FSUIPC5, just after the crash, no crash P3D start ok. But when I reboot my PC, same problem: CTD then Ok on second start. Without FSUIPC, P3D v4 start all the time good and game controlers are logged. It's the same with Windows 10 (fresh install and up to date) and P3D V4 (fresh install without addons) and memory changed. I have done some tests and these are my conclusions. If I plug only 1 of the 5 game controlers P3D v4 with FSUIPC5 start all the time. If I plug 2 game controlers on the same HUB crash (for exemple: Port_#0001.Hub_#0004 and Port_#0003.Hub_#0004). If I plug 2 game controlers on HUB with differents ID (for exemple: Port_#0001.Hub_#0004 and Port_#0003.Hub_#0007) P3D v4 start without CTD. Do you see a solution ? Attached logs are after the install of FSUIPC5 Best regards. FSUIPC5.ini FSUIPC5.JoyScan.csv FSUIPC5.log
  5. Hi Guys, I am using FSUIPC 5 and today I installed the new FS2Crew for P3Dv4. As expected, I am running into problems unfortunately. So, after installing and configuring FS2Crew for P3Dv4, FSUIPC 5 is not keeping the profile saved for the same plane. Which means I have to select the profile each time I run the same plane. Any idea what or where the problem could be? Thanks in advance for your kind help and feedback. Kr, Enrico
  6. Hello, I own a registered copy of FSUIPC5, version 5.103 in P3D V4. This issue occurred in the PMDG 777. FSUIPC5 disappeared out of the addons list about 4 hours in I started P3D, and when I look in the Prepar3D v4 Files, where the Autosave files are normally placed by the sim, none are there. The sim did not crash and I continued the flight as normal. FSUIPC5 Disappears: https://www.dropbox.com/s/j1van8ekhbnwldn/fsuipc.png?dl=0 Autosave files have vanished: https://www.dropbox.com/s/spurmfvftglpiz7/Autosave.png?dl=0 My FSUIPC5.log file: https://www.dropbox.com/s/gxnmohykt4mimp6/FSUIPC5.log?dl=0 Thank you :) Félix
  7. Hello, Compiled lua files give me an error "Bad header in precompiled chunk" with P3D4 and FSUIPC 5.103. Source LUA files are OK. Everything was OK with P3D3 and FSUIPC4 : both sources and compiled files were executed. I tried x86 and x64 versions of luac53, no change, still the same error. Any idea on how to execute compiled lua scripts in P3D4 is welcome, thanks in advance and sorry for my English ... Regards, Frederic
  8. Hi, We have a win-10 machine with P3D-v4 running. After install FSUIPC5 P3D starts, but after 5 seconds it totally freeze. Reject the Modules folder P3D runs without problems. It is a fresh installation of P3D, and currently only the KA350 as default plane is used. We would like to use P3D in combination of Warpalizer, but this isn't installed yet. (first solve this issue) Of course all used software is registered... This is the log- file created by FSUIPC: ********* FSUIPC5, Version 5.10 (1st June 2017) by Pete Dowson ********* Windows 10 Pro 64 Bit reported as Build 14393, Release ID: 1607 (OS 10.0) FSUIPC5.dll version = Reading options from "D:\P3D-v4\Modules\FSUIPC5.ini" Running inside Prepar3D v4 on Windows 10 Module base=7FFEC0B40000 User Name="Matthijs Thijssen" User Addr="matthijs@flightillusion.com" User WideFS Addr="administratie@flightillusion.com" FSUIPC5 Key is provided WideFS7 Key is provided 0 System time = 27/06/2017 10:34:58 0 FLT UNC path = "\\FALCON-SIM\Users\Simulator\Documents\Prepar3D v4 Files\" 0 ------ Module Version Check ------ 0 acontain.dll: 0 api.dll: 0 controls.dll: 0 fs-traffic.dll: 0 G3D.dll: 0 language.dll: 0 sim1.dll: 0 visualfx.dll: 0 weather.dll: 0 window.dll: 0 ---------------------------------- 15 FS UNC path = "\\FALCON-SIM\d\P3D-v4\" 156 ---------------------- Joystick Device Scan ----------------------- 250 ------------------------------------------------------------------- 250 ------------------------------------------------------------------- 281 LogOptions=00000000 00000001 281 ------------------------------------------------------------------- 281 SimConnect_Open succeeded: waiting to check version okay 281 Opened separate AI Traffic client okay 1156 Running in "Lockheed Martin® Prepar3D® v4", Version: (SimConnect: 1156 Initialising SimConnect data requests now 1156 FSUIPC Menu entry added 1156 ... Using Prepar3D with Professional License 1172 \\FALCON-SIM\Users\Simulator\Documents\Prepar3D v4 Files\default.fxml 1172 \\FALCON-SIM\d\P3D-v4\SimObjects\Airplanes\Beech_King_Air_350\Beech_King_Air_350.air 12375 User Aircraft ID 2 supplied, now being used 12375 Aircraft loaded: running normally now ... 13031 System time = 27/06/2017 10:35:11, Simulator time = 14:06:20 (12:06Z) 13047 Aircraft="Beech King Air 350" 21109 Starting everything now ... 106578 **** No SimConnect events or states being received! Re-connecting now ... **** 106937 SimConnect_Open succeeded: waiting to check version okay 106937 Opened separate AI Traffic client okay Does someone know whats wrong? Thanks in advance, Matthijs Thijssen
  9. Hi Pete You will know that LINDA is built around FSUIPC4 and I have been doing some compile tests in 64-bit. The only issues/compile errors are in the code and data structures used to interface with FSUIPC. The main issue I have is with the DWORD usage - it does not appear to copy across to 64-bit in Delphi Pascal. 64-bit key types of concern are: Type FS6IPC_READSTATEDATA_HDR = packed record dwId : dword; dwOffset : dword; nBytes : dword; pDest : pointer; end; FS6IPC_WRITESTATEDATA_HDR = packed record dwId : dword; dwOffset : dword; nBytes : dword; end; Are there are changes to the FSUIPC5 external program interface data structure? LINDA will also need the full licenced version of FSUIPC5 once the ordering system is up and running.
  10. I am getting an error starting Active Sky for P3Dv4 beta using the [Programs] block in FSUIPC5.ini. It is reporting error 740 even through 2 other programs are starting correctly. I have double checked the path including cutting and pasting from the program's shortcut properties. The ASforP3Dv4 program can be started manually via the shortcut. FSUIPC5 FSUIPC5.log Screenshot of shortcut properties
  11. Hello Mr. Dowson, Thank you for the time and effort that you are putting into FSUIPC 5. I wanted to provide some feedback that may be of use to you. I have a registered version of FSUIPC 5. I am currently using beta version 5.101j. Under the Button + Switches tab, I am attempting to allocate the "kneeboard view" to a button on a CH Yoke Eclipse. After saving this button allocation and resuming the sim scenario, my scenario is fine until I access the Kneeboard with that button. Upon using that button, the Kneeboard will display, but then all of my FSUIPC defined buttons and axes immediately become inoperable. However, the sim does not freeze. If I go back into FSUIPC and clear "kneeboard view" from the yoke button, everything is fine again. This issue occurs whether or not I am using default aircraft or add-on aircraft. I've attached the LOG file below. Let me know if there's anything else that you would like me to provide. FSUIPC5.log
  12. The offset 024C is defined returning available FS memory. With FSUIPC5 5.101h this value is permanently zero (0). Is this correct?
  13. Hi Pete, You do awesome work for the whole sim community. here is what I have I use software to connect my iPad with P3D. ver 510 and 5101 non registered works great. after registering still seems good until after I use the axis calibration. Then I have problems with my iPad apps communicating with P3D v4. these app are stable on previous sim versions but the new 64 bit obviously takes some work. here is my log file. I Hope this helps. ive read through a couple threads and it seems its hard to get people to tell you what you need to know FSUIPC5.log
  14. Thanks again Pete for your great work with FSUIPC5. Looking forward to the purchase. One interesting aspect of P3D for me has been the way that it handles add-ons; Umberto from FSDT was talking about it on AVSIM earlier this week and his scenery utilities when migrating content to P3Dv4 use it. Essentially, each add-on defines its contents in a separate XML file allowing it to be easily enabled/disabled, etc. After installing FSUIPC5 into my P3Dv4 setup, I took the liberty of disabling FSUIPC5 in the global DLL.XML file and instead did the following: Created an FSUIPC directory in the $MyDocuments\Prepar3D v4 Addons directory. Created an add-on.xml file with the following content: <SimBase.Document Type="AddOnXml" version="4,0" id="add-on"> <AddOn.Name>FSUIPC5</AddOn.Name> <AddOn.Description>FSUIPC v5</AddOn.Description> <AddOn.Component> <Category>DLL</Category> <Path>D:\Program Files\Prepar3D v4\Modules\FSUIPC5.dll</Path> <DLLType>PDK</DLLType> </AddOn.Component> </SimBase.Document> Loads just fine; the directory of course will differ based on the install. I like the new install mechanism for modules and scenery; it allows better control over what to enable/disable. Something to consider for the installers going forward? It might make your life simpler as there's no risk of stepping on the toes of another add-on. Cheers! Luke