John Fee

Sky Demon is a navigation system designed for real world General Aviation pilots. However, it is possible to fool the program into believing that the GPS output it is receiving from FSX-SE is coming from a real aircraft. I am posting this workplan as an aid to those who would like to try it out. It may not work for you in which case I apologise. Both Sky Demon and a Virtual Serial Port Device have two week trial periods. I gratefully acknowledge the advice of John Dowson in helping me get this up and flying. Preliminaries You will need the latest subscribed version of FSUIPC4 for FSX-SE. https://www.fsuipc.com/ If you plan to run SkyDemon on a LAN you will also need WideFS7; this includes WideClient for installation on your non-flying client PC/laptop. Details in para.5 and end of para.6. Read the FSUIPC and WideFS User Guides carefully. Workgroup If you are planning to run Sky Demon on a LAN, Make sure that both server (FSX-SE flying PC) and client (non-flying laptop/PC) have the same workgroup name. This is essential. There are several versions of the Windows 10 operating system e,g, Home, Pro, Enterprise. If you are using a newly installed Pro or Enterprise version you will probably find that the default workgroup name is WORKGROUP. If you need to change this, be aware that your change may not ‘stick’ after re-booting. To address this problem, login with a local account, not an MS account like: xxx@hotmail, xxx@outlook etc. Also, check in Settings-System that your computer is set up for private use and not business. 1. In the FSUIPC4.ini file (in the Modules folder of the FSX-SE folder) scroll down and check: [GPSout] GPSoutEnabled=Yes Port=WideFS Speed=19200 Leave the rest unchanged. If not there add: Sentences=RMC,GGA,GSA (no spaces) Next, find [Wide Server] and check: WideFSenabled=Yes AdvertiseService=1 Port=8002 Port2=9002 Save 2. Download the two week trial version of Eltima Virtual Serial Port Driver for Windows 10. Launch. Pair COM8 and COM9. Check in Device Manager – WinKey + X. Payware option after two weeks. Freeware VSPDs are available but I cannot vouch for these. 3. Sky Demon is designed for real world General Aviation navigation. It is payware but there is a trial version. Download and install the latest version for Windows 10. In Setup, Third Party Devices, leave boxes unchecked. Under RS232 GPS Devices set Port to COM8; Baud to 19200 Also in Setup, scroll down to Navigation Options. At the bottom of the page click on the link to Legacy Device Connectivity Options and chose ‘I have a Garmin handheld device’. You can play around with the other Navigation Options. 4. Read this only If you wish to run Sky Demon on a LAN i.e. on a non-FSX client PC or laptop. Skip otherwise. Download WidesFS7 from: https://www.fsuipc.com/ to your non-FSX (client) machine. Make sure you have registered WideFS7 – the code will have been sent to you when you purchased FSUIPC4. Extract and copy WideClient.exe and WideClient.ini to a separate folder on your client machine. I use my home folder and call this folder WideClient. Make a desktop shortcut for WideClient.exe. Edit the Port entries in WideClient.ini configuration. [Config] Port=8002 Port2=9002 Add these to [Config] ServerName=enter your flying PC’s name – whoamI - in Command Prompt Protocol=TCP Add this after the [Sounds] entries, [GPSout] Port=COM8 Speed=19200 Save 5. Running FSX-SE. Login to Steam. Run FSX.exe from your main installation. Launch the Virtual Serial Port Device and check that COM8 amd COM9 are paired. In a LAN Launch WideClient.exe on the client. In my LAN I installed the VSPD device on my client. 6. Run SkyDemon – click on Go Flying and Connect to RS232 GPS Hardware. ‘Keep the shiny side up and the greasy side down!’

John Success! 😀 Setting ServerName=Belladonna; Protocol=TCP in WideClient [config] worked some magic. I do not know if I did correctly, but I set Port=8002 (was 0) and Port2=9002 (was 0). I realise from the documents that 9002 is for folders. If wrong it seems to have done no harm. If you think it would be of interest I can write a full version of how we did this for posting in User Contributions. Setting up GPSOut for Sky Demon in FSX-SE is clearly not always straightforward. I posted how to do this for FS9 and FSX in User Contributions many years ago. Since then the Sky Demon set up has changed somewhat. I didn't bother you with that! Thanks again for all your advice and interest.

The WORKGROUP names were the same when I posted, i.e. OSBORNE. Problem was when I rebooted the laptop, it made an uncommanded name change to WORKGROUP, unbeknownst to me! The explanation (in case others have a similar problem) were incompatibilities between Windows 10 Home (PC server), and Windows 10 Pro (cllent). I appear to have these fixed now so that the Workgroups are the same (hopefully permanently) and the sharing of files and folders is permitted. That's for tomorrow. Thanks again!

Update I have just discovered that the client laptop (Dell) reverts to WORKGROUP instead of the correct name - OSBORNE. I have no idea how or why, it is not in a domain. This may explain at least part of the problem. Edit I'm detecting other problems with the LAN. Up till recently I had no problems. These all started with a second-hard A rated Dell laptop. 😢

The Workgroups are the same. When I attempt to run Sky Demon, I get a banner message across the map 'Waiting for data'. I've attached files again as requested. Thanks! WideClient.log WideClient.ini FSUIPC4.log FSUIPC4.ini WideServer.log

I've not been able to get this working. Relevant logs and .ini files are attached. Also a screenshot of the Virtual port driver. Firewalls are all off. All relevant folders are shared with Full Access - files are easily moved from one PC to the other. I am running FSX-SE in Windows 10. Perhaps STEAM software is causing some problem? Or maybe I missed something obvious. I'd be grateful for help. FSUIPC4.ini WideClient.log FSUIPC4.log WideClient.ini

Sorry, yes, of course. As you can see I'm pretty rusty. If/when I get Sky Demon working using WideClient, I will update this post with details.

Thanks! This is a good help. I will try the WideClient method first. I have WideFS but not WideClient. Should WideClient be installed on the flying PC, or the client PC, or both?

I am running FSXSE in a Win10 PC. I use Sky Demon for navigation - undocked to a second monitor. I explained the method here https://forum.simflight.com/topic/76431-gpsout-for-sky-demon-in-fs9/#comment-465701 (read down to my second post). Now, to reduce the CPU load I would like to install Sky Demon on a second W10 PC. So I need to find a way of taking GPS output from the flying PC. I cannot figure out a way of doing this - maybe it is not possible? I would be grateful for advice.

Thanks, John. Sorry for bother. I thought I put it there!

Notes: This is an update for FS9/FS2004 users who wish to use SkyDemon in Windows 10 x64. Previously I used a similar method for FS9 in Windows 7 posted here. SkyDemon has also been updated since that time. I run FS9 in Compatibility Mode: Windows XP (Service Pack 2). This method uses Eltima software for pairing COM ports (see below). This allows SkyDemon to interact in both directions with FS9 via GPSout. 1. Install a free registered version of FSUIPC for FS9, version 3.999z9b https://forum.simflight.com/topic/80977-updated-modules/ Details of how to register are provided. 2. Check the FSUIPC.ini in the FS9 Modules folder using Notepad - that the above version is installed. 3. Install GPSout from https://www.schiratti.com/files/dowson.html This is NOT included in the FSUIPC 3.999z9b download. GPSout.dll and GPSout.ini must be in the FS9 Modules folder. 4. Open the GPSout.ini file with a text editor like Notepad. Set the following: Sentences=RMA,RMC,GLL,GGA [note, no spaces] Port=COM8; Baud=19200 SAVE 5. Open Eltima VSPD - a fully functional trial is available Pair Ports, COM8 and COM9 6. Press WinKey+X. In Device Manager: Electronic Team VSP Ports COM8/COM9 should show. 7. Run FS2004 and open default airport (optionally after this, create a flight plan using FS2004 flight planner and SAVE). 8. Start SkyDemon (current version 29 Sept 2022) Menu: SetUp - 3rd party devices - set COM9 and Baud=19200 Menu GoFlying - connect RS232

Thank, John. I have reading to do!

Thanks for putting all this together. I need to learn about macros first and then apply that knowledge. I am not too sure where the Lvars log file is to be found. I have the 'Log Lua plugins separately' option checked under Logging. Best, John

Thanks a bunch, Roman. You're a star! I have it working on a yoke button. Oddly, I can't get it to work from a key press but that's not important. Just a comment. P3Dv4.5 doesn't have a \modules folder. I put the "P40_Hyd.mcro" file into the same default folder as the FSUIPC6 files: C:\Users\Howard\Documents\Prepar3D v5 Add-ons\FSUIPC6 And a question: May I ask where you found the "P40_Hyd.mcro" file? Just in case i want to try something similar again.

Thanks very much for this. I would be in business if I knew anything about LUA. I've perused the LUA documents and the Advanced Users pdf. I will study them more carefully over the next day or two - there's a lot in there which is probably not relevant to my problem. But maybe I need a full understanding? Do I need to learn the language? I just don't know. The bit that escapes me so far is where to enter the relevant information? Is there a LUA.ini file somewhere which can be edited? I couldn't find it. I have the Lua_Plugins_20190320 folder with the examples folder. Where on earth to begin?

Thanks, Pete. I will have look into your suggestions. I agree a button would be preferable but I have very few buttons at my disposal and they are needed for other things. I sent the log so you'd know I was using the latest iteration of FSUIPC6 for P3Dv4.5.

I am flying the A2A P-40 in P3Dv4.5. The hydraulic system in this aircraft requires manual recharging after each use (flaps, gear only). This can be done in the aircraft using a mouse to press a switch on the yoke. The problem is that the switch must be kept pressed until the hydraulic pump has completed its task. When released at that point, the pump switches off. It is not a toggle action, like a gear toggle. It is more like a trim switch in the way it works. It is very awkward to do this with a mouse in the P-40. It is a complex, vibrating aircraft with many controls and switches. In bad weather it is all but impossible. To get round this, I have tried to assign a key press -V- to this in FSUIPC6 but without information on the control I cannot confirm the assignment. On the left side, there is a 'Hydraulic Switch Toggle' option. I have tried assigning this but the switch on the yoke does not respond. In any case, a toggle switch is not what is needed. I have checked your Controls List for P3Dv4 build 34698 but there is no control listed for a hydraulic pump 'on' with repeats. I'd be grateful for advice. (log attached). FSUIPC6.log

I ran the 4.97a installer and all is well. My original settings all preserved. Remarkably so, in fact, as for whatever reason FSX hasburst into life with '3-D' perspective I never had before! Thanks again, as always, Pete. You never fail!

Until today, that was the last time I flew FSX-SE. I've lost all my FSUIPC settings too! No newer file. C:\Users\Howard\AppData\Roaming\Microsoft\Windows\Recent has the same file with today's date in Explorer, but still 30/4/2020 in the log.

I run FSX-SE on one HDD, and P3Dv4.5 on another. Windows 10. When I flew FSX-SE today, after a few month's gap, the FSUIPC options did not show on the top in window mode. I've attached the log file. I am not running the beta version from Steam, although I might once this is sorted. I'd be grateful for advice. FSUIPC4.log

Thanks, Pete. FSUIPC.ini attached. I agree that it could be caused by an addon. I have very few of these as FSX-SE has been newly installed on its own HDD on this PC. It could be hardware too, of course. It could be Steam related too I suppose. I have FSX boxed on a separate drive, so I can test the yoke, throttle quad, and rudder pedals in that sim. Regards, John FSUIPC4.ini

This time, she did it all - uncommanded Spot view, Gear Down, Brakes set whilst on autopilot, totally hands off. . Log attached. Regards, John FSUIPC4.log

Hmm. How interesting! The Gear Down/Up action was unrelated to my use of the elevator trim buttons on the yoke. Yes, it can happen hands off. I began to use the Offset SWord setting because it gave me finer iterations with some plane which I flew in the distant past, probably in FS2002. I just kept using that way of setting up trim with each new simulator that came along. I never had trouble with it. It just worked fine, so why change? I have changed now and it'll be interesting to see if using the normal FS control via FSUIPC will solve the problem. The antiskid brakes thing is a total mystery. Even if I wanted to I have no idea how to set that up. I couldn't find a switch or lever for cockpit activation. I'll run that particular problem past the C-47/DC3 chaps. Some test flying to do before I report back. Thanks again. John

Thanks. The FSX controllers are all disabled. This time, (only the second occasion it's done this) when I landed the plane the brakes appeared to come on full without command from me. Whatever way this worked it stopped the plane dead in its tracks as if it landed on glue. Had I done this myself with differential brakes, I'd have tipped the old girl over on her nose and spoiled her day. Log attached with button/key and events log as requested. Seems some problem with toggle engine failure. John FSUIPC4.log

log file: ********* FSUIPC4, Version 4.974b (14th March 2018) by Pete Dowson ********* Windows 10 Home 64 Bit reported as Build 18362, Release ID: 1903 (OS 10.0) fsx.exe version = 10.0.62615.0 Reading options from "F:\FSX_Steam\steamapps\common\FSX\Modules\FSUIPC4.ini" Running inside FSX Steam Edition on Windows 10 Module base=56CF0000 User Name="John Fee" User Addr="gooneybird@yankeedodge.com" FSUIPC4 Key is provided WideFS7 Key is provided 0 System time = 29/04/2020 12:18:42 15 ------ Module Version Check ------ 15 acontain.dll: 10.0.62615.0 15 api.dll: 10.0.62615.0 15 controls.dll: 10.0.62615.0 15 fs-traffic.dll: 10.0.62615.0 15 G3D.dll: 10.0.62615.0 422 language.dll: 10.0.62615.0 422 sim1.dll: 10.0.62615.0 422 visualfx.dll: 10.0.62615.0 422 weather.dll: 10.0.62615.0 422 window.dll: 10.0.62615.0 422 ---------------------------------- 437 Trying to connect to SimConnect Steam ... 500 FS UNC path = "\\RUDOLF\FSX\" 562 ---------------------- Joystick Device Scan ----------------------- 562 Product= Saitek Pro Flight Rudder Pedals 578 Manufacturer= Saitek 578 Vendor=06A3, Product=0763 (Version 1.1) 578 GUIDs returned for product: VID_06A3&PID_0763: 578 GUID= {DAA2C6C0-EC02-11E7-8008-444553540000} 578 Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R511,U0,V0,X127,Y127,Z0 578 Product= CH ECLIPSE YOKE 578 Manufacturer= S 578 Vendor=068E, Product=0051 (Version 0.0) 578 GUIDs returned for product: VID_068E&PID_0051: 578 GUID= {DAA25190-EC02-11E7-8006-444553540000} 578 Details: Btns=26, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R895,U1023,V1023,X1006,Y1023,Z1023 593 Product= GF-TQ6 Throttle System 609 Manufacturer= GoFlight 609 Vendor=09F3, Product=0200 (Version 1.0) 609 GUIDs returned for product: VID_09F3&PID_0200: 609 GUID= {DAA29FB0-EC02-11E7-8007-444553540000} 609 Details: Btns=4, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R225,U215,V219,X209,Y220,Z221 672 ------------------------------------------------------------------- 672 Device acquired for use: 672 Joystick ID = 2 (Registry okay) 672 2=Saitek Pro Flight Rudder Pedals 672 2.GUID={DAA2C6C0-EC02-11E7-8008-444553540000} 672 Device acquired for use: 672 Joystick ID = 1 (Registry okay) 672 1=CH ECLIPSE YOKE 672 1.GUID={DAA25190-EC02-11E7-8006-444553540000} 672 Device acquired for use: 672 Joystick ID = 0 (Registry okay) 672 0=GF-TQ6 Throttle System 672 0.GUID={DAA29FB0-EC02-11E7-8007-444553540000} 672 ------------------------------------------------------------------- 703 FSUIPC couldn't run: "F:\FSX-Steam\steamapps\common\Modules\FSX.bat" [Error=2] 703 LogOptions=00000000 00000001 703 ------------------------------------------------------------------- 703 ------ Setting the hooks and direct calls into the simulator ------ 703 --- CONTROLS timer memory location obtained ok 703 --- SIM1 Frictions access gained 703 --- FS Controls Table located ok 703 --- Installed Mouse Macro hooks ok. 703 --- Wind smoothing fix is fully installed 703 --- SimConnect intercept for texts and menus option is off 703 --- All links checked okay 703 ------------------------------------------------------------------- 703 SimConnect_Open succeeded: waiting to check version okay 703 Trying to use SimConnect Steam 703 Opened separate AI Traffic client okay 2468 Running in "Microsoft Flight Simulator X", Version: 10.0.62615.0 (SimConnect: 10.0.62615.0) 2468 Initialising SimConnect data requests now 2468 FSUIPC Menu entry added 2484 \\RUDOLF\FSX\flights\other\FLTSIM.FLT 2484 \\RUDOLF\FSX\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.air 6562 Weather Mode now = Theme 14297 \\RUDOLF\Users\howar\AppData\Roaming\Microsoft\FSX\Previous flight.FLT 54968 User Aircraft ID 1 supplied, now being used 54968 Aircraft loaded: running normally now ... 55265 System time = 29/04/2020 12:19:38, Simulator time = 05:32:41 (03:32Z) 55281 Aircraft="Aircreation582SL red" 163922 Starting everything now ... 167093 Advanced Weather Interface Enabled 191672 \\RUDOLF\FSX\SimObjects\Airplanes\Douglas C-47 3.1406-MVC\Douglas_DC3_v1.5.air 192281 Aircraft="Douglas C-47 Piedmont Airlines MVC" 281953 Sim stopped: average frame rate for last 89 secs = 28.1 fps 281953 Max AI traffic was 9 aircraft (Deleted 0) 1132828 Sim stopped: average frame rate for last 735 secs = 28.7 fps 1132828 Max AI traffic was 9 aircraft (Deleted 0) 1134781 === Closing session: waiting for DLLStop to be called ... 1142390 === DLLStop called ... 1142390 === Closing external processes we started ... 1143390 === About to kill any Lua plug-ins still running ... 1143562 === Closing global Lua thread 1144578 === About to kill my timers ... 1144797 === Restoring window procs ... 1144797 === Unloading libraries ... 1144797 === stopping other threads ... 1144797 === ... Button scanning ... 1144922 === ... Axis scanning ... 1145031 === Releasing joystick devices ... 1145031 === Freeing macro memory 1145031 === Removing any offset overrides 1145031 === Closing all WideFS threads 1148468 === Clearing any displays left 1148468 === NOTE: not calling SimConnect_Close ... 1148468 === AI slots deleted! 1148468 === Freeing button memory ... 1148468 === Closing my Windows ... 1148468 === Freeing FS libraries ... 1149484 === Closing devices ... 1149484 === Closing the Log ... Bye Bye! ... 1149484 System time = 29/04/2020 12:37:52, Simulator time = 05:46:48 (03:46Z) 1149484 *** FSUIPC log file being closed Minimum frame rate was 26.0 fps, Maximum was 28.9 fps Minimum available memory recorded was 2146Mb Average frame rate for running time of 846 secs = 28.7 fps Maximum AI traffic for session was 9 aircraft Memory managed: 207 Allocs, 206 Freed ********* FSUIPC Log file closed ***********