Jump to content

Highest Reputation Content

#417029 Updated modules

Posted by Pete Dowson on 18 October 2010 - 11:14 PM

Note that mostly this Announcement will contain only the changed modules. You will almost always need the main release installed first. For those please go to http://www.schiratti.com/dowson

The FS modules here, when supplied without Installer, need copying into the FS modules folder once extracted.

Please note the format here. The links for all the updates are listed first. For interim releases only, notes about changes are listed separately, below.

Install complete FSUIPC version 3.999z8 Install FSUIPC 3.999z8 for FS9 and before

-- For changes see the History document in the full install update.

FSUIPC version 3.999z9a only, for those with 3.999z1 or later already installed FSUIPC 3.999z9a

-- Fixes an ancient and obscure bug which nevertheless can crash FS on loading with certain INI file arrangements.



Install complete FSUIPC version 4.943 Install_FSUIPC4.943 for FSX, FSX-SE and Prepar3D versions 1.4 and 2.0-2.5

-- See included document for list of changes

FSUIPC version 4.943 only, for those with 4.941 or later already installed FSUIPC 4.943

-- Supports Prepar3D version 2.5, builds 12942-6

-- Supports FSX-SE build 62613 and 62615.

-- Fixes obtaining AI runway data via offset D000

-- Fixes occasional failure to include profile details for new ones based on another.


WideFS version 6.999m WideFS 6.999m
Full release including documentation.
-- signature removed

-- See WideClient changes below.


WideClient 6.999x WideClient 6.999x

-- 6.999x adds "ReconnectMinutes", a facility to automatically reconnect periodically.



PFC driver version 2.41 for FS9 and earlier PFC 2.41
PFCFSX driver version 4.41 for FSX, ESP and P3D PFCFSX 4.41
-- signatures removed


PFC HID device driver version 1.41 for FS9, FSX, ESP and P3D PFCHID 1.41
-- signature removed
-- 1.33 fix for AP APR mode not setting Glideslope option

-- 1.34 fix for macro name matching and proper macro file selection on aircraft change

-- 1.35 fix for a silly bug introduced in 1.34 which could significantly slow FS down!

-- 1.36 eliminates a 1-2 second pause when AutoSave options are in use

-- 1.37 added support for separate macros for positions on multiway switches

-- 1.38 and 1.39 only added clearer logging, especially for macro file selection

-- 1.41 fixes some further macro selection problems



Pete Dowson
15th August 2015

  • 3

#451010 New FSUIPC4 registrations for 2013 need version 4.859n or later!

Posted by Pete Dowson on 14 January 2013 - 05:26 PM

Oops. Same date limit was in FSUIPC4 too!

  • 2

#450631 FS Commander won't let me load flightplans?

Posted by JerryJet on 03 January 2013 - 12:42 PM

So it can save flightplans in those formats, but can't then reload those very same flightplans unless they exist in FSC's format? And I paid $40 for this??? Can I just say how stupid that is?

Flightsim Commander is released as shareware letting you evaluate the program to see if it suits your needs. You can also read the exhaustive manual which explains how and why FSC saves flightplans. Numerous different planes/companies can be chosen when saving, but one is always checked and can never be unchecked. I'll let you figure out what that means.

  • 2

#483165 Aerosoft Airbus & FSUIPC - General Question

Posted by Pete Dowson on 26 August 2015 - 11:08 PM

Do you mean:
ipc.writeUW(66C0, ALT_set)


Closer, but 66C0 will not work as it stands as it looks like a decimal 66 with C0 stuck on. It's a hexadecimal number and needs 0X in front of it (or quotes round it).


ipc.writeUW(0x66C0, ALT_set)


If you had started out just stating what it was you were trying to do, which you still haven't done, it might have been quicker. Why do you want the value in an offset in any case?



  • 1

#483162 Aerosoft Airbus & FSUIPC - General Question

Posted by Pete Dowson on 26 August 2015 - 08:10 PM

Would this work?

function ALT_set(offset, value)
ALT_set = ipc.readLvar("AB_AP_ALT_Select")

event.offset("66C0", "ALT_set")




Please please do read the Lua library documentation!


The event library is there to call a function in the Lua plug in when something happens! 


event.offset("66C0", "ALT_set")


is actually wrong in any case, You missed a parameter out! which specifies the type of value being tested. A more correct line:


event.offset("66C0", "UW", "ALT_set")


would tell FSUIPC to call a function called ALT_set when the Unsigned Word at offset 66C0 changes.


You have no function called ALT_set and you are not writing anything to 66C0.


I think you are completely out of your depth, or just haven't actually studied the documentation or any of the many examples provided for you, to help.


Writing to offsets is done by other functions in the ipc library. Please go and look them up.



  • 1

#483159 Aerosoft Airbus & FSUIPC - General Question

Posted by Pete Dowson on 26 August 2015 - 08:00 PM

What the normal Offset for importing such a LVar would look like (How to write it, that FSUIPC is posible to read it - just a normal lua script?) ?


There are no 'normal offsets" for L:Vars! The L:Vars are LOCAL to specific gauges. I cannot include in FSUIPC a general facility for all possible LVars in all possible add-on aircraft!


As you've already been told, you can READ or WRITE LVars, once you know their names in Lua plug-ins. If you need a value in an offset, write the result of reading one to an offset. I already told you this, and I also told you that you can use the offsets 6C00-6CFF which are reserved for general uses like tihs.



  • 1

#483147 Aerosoft Airbus & FSUIPC - General Question

Posted by Pete Dowson on 26 August 2015 - 04:51 PM

This is the newest SDK for the Airbuses...
Is it possible to read for example the selected ALT (AB_AP_ALT_Select) with the following command:
ALT_value = ipc.readLvar(AB_AP_ALT_Select)


Sorry, I've no idea whatsoever what the names in that SDK section refer to. If they are Lvars (local panel variables, often named with L: beforehand), then, yes, Lua can read the values But names are strings, so it should look like


ALT_value = ipc.readLvar("AB_AP_ALT_Select")


You'll need to read and understand the SDK to decide, I think.



  • 1

#482650 Wishes for new airports/ major changes

Posted by Burkhard on 06 August 2015 - 08:47 PM

Thanks for the update on the airlines. That livery of GOL will need dozens of high quality pictures to get it done.


To my understanding there is no variable for AI aircraft to switch trails on - and if there were they would eat a lot of CPU power - often there are 400 or 500 aircraft in the reality box, and 2 semi transparent trails = 4 draw calls would exceed what a high end system can do even over a desert - no scene may ever exceed 1500 draw calls or every system stutters..

  • 1

#482434 Passing parameter from LUA to mouse macro

Posted by Pete Dowson on 30 July 2015 - 02:01 PM

One question: Is there a possibility in future versions of FSUIPC, that the parameter in the macro call from LUA will be passed to mouse macros as the mouseflag? 



ipc.macro("XXX:MyMouseMacro", 17)

triggers the mouse macro in file XXX.mcro with parameter 17 as mouse flag.





So no new functionality, but maybe you have a chance to check, if this enhancement could be implemented easily.


Looks to be a reasonable idea. I'll take a look. Won't be till next week though.



  • 1

#481768 Question on Paid FSUIPC

Posted by Pete Dowson on 04 July 2015 - 12:57 PM

I just got the paid version of FSuipc yesterday and have a question.  II tried for hours to program the axis settings in P3D on my Majestic Q400, and each time I had a problem. I watched the tutorial videos and read a couple of manuals, that included disabling the joystick assignments in P3D, but still had erratic results  when finished. The only  reason I wanted to do this axis editing  was to use the slope function on the joystick to tone down the responsiveness for the elevator and ailerons in the center region. I finally discovered, that if I left the control settings for each axis assigned as normal in P3D, and just calibrated the Joystick using FSuipc, including setting the slope for those 2 joystick functions, it seems to work properly when flying the aircraft. My question is, is this an acceptable way to use FSuipc to get the outcome that I am trying to achieve? 


I don't actually publish a "tutorial", only the User guide and the reference Advanced Users guides.


FSUIPC's calibration facilities can be used no matter where you assign the axes, FS or FSUIPC. The facilities for assigning in FSUIPC were added later, a long time after the calibration, for the main purpose of allowing different assignments for different aircraft -- eg stick for Airbus or military, Cyclic etc for Helo, and yoke for other airliners and GA.


If you had erratic behaviour when assigning in FSUIPC compared to assigning in FS there MUST have been some sort of conflict. Probably you didn't actually disable the controllers in P3D -- merely unassigning the individual assignments is not usually sufficient, and can get wiped out on the next reload.


There are some aircraft which don't like assigning in FSUIPC to anything other than the normal FS controls ("axis .... set"), mainly because they need to see these controls. So assigning "direct" in FSUIPC (generally the most efficient way) doesn't work with those. However, usually, if that is the case, calibrating in FSUIPC doesn't work either as such aircraft are effectively bypassing whatever FSUIPC is doing. If you can calibrate okay in FSUIPC with your aircraft then the problem with assignment would definitely be some conflicting assignment.



  • 1

#481727 Departure Gates for New York Sector-Tracon!2012

Posted by FeelThere on 03 July 2015 - 08:04 AM

You can edit the SIDs and STARs.

  • 1

#481658 Timer to refresh data

Posted by Paul Henty on 29 June 2015 - 08:16 PM

To log events when offsets change you need to keep a copy of the previous values. Then test against the current values. If they are different you can write the new value to the log. After every 'tick' you must update the last values with the current values.


Below is some code that shows logging 'pause/un-pause' and when the gear is put up and down.


1. Create variables to store the last values. These can be the same type as the raw 'value' of the offset (that's what I've used), or they could be the real-world values after conversion. These are at the form/class level, the same as the offsets.

        private Offset<ushort> pause = new Offset<ushort>(0x0264);
        private Offset<int> gearPositionNose = new Offset<int>(0x0BEC);

        private ushort lastPause;
        private int lastGearPositionNose;

2. Create a method to set these values from the current values of the offsets:

        private void setLastValues()
            this.lastGearPositionNose = this.gearPositionNose.Value;
            this.lastPause = this.pause.Value;

3. Call this method after open to set the initial values:

            { // Attempt to open a connection to FSUIPC (running on any version of Flight Sim)
                // Opened OK
                // start the timer
                timer1.Interval = 250;
            catch (Exception ex)
                // Badness occurred - show the error message
                MessageBox.Show(ex.Message, AppTitle, MessageBoxButtons.OK, MessageBoxIcon.Error);

4. In the TIck, test the current values of the relevant offsets and log if they are changed. Finally call the method to update the last values with the current ones (ready for the next tick).

        private void timer1_Tick(object sender, EventArgs e)
            // Pause
            // If pause changed write it to the log
            if (this.pause.Value != this.lastPause)
                log("Sim was " + (pause.Value == 1 ? "PAUSED" : "UN-PAUSED"));
            // Gear
            if (gearPositionNose.Value == 0)
                this.textBox4.Text = "Gear Up";
                if (this.lastGearPositionNose != 0)
                    log("Gear UP");
            else if (gearPositionNose.Value == 16383)
                this.textBox4.Text = "Gear Down";
                if (this.lastGearPositionNose != 16383)
                    log("Gear DOWN");
                this.textBox4.Text = "Gear In Transit";

5. For this demonstration, my 'log' method just adds an item to a ListBox on the form.

        private void log(string message)
            string logLine = DateTime.Now.ToString() + ": " + message;





  • 1

#481486 GoogleEarth runtime error 429 (solved)

Posted by henk.brouwer on 23 June 2015 - 02:34 PM

FSC9.6 is running as admin and connected with success with FSX in other computer through registered widefs and fsuipc last versions.
Google earth 7.1.5 installed at default folder on same pc as FSC9 and works fine. The correct folder is selected in the Options window for GoogleEarth.
FSX as server in other pc. Both PC windows 7 x64.
When GoogleEarth is started, I get a run time error 429: "ActiveX component can't create object"
Get same result after disabling firewall and virusscanner.
Suggestions greatly appreciated.


  • 1

#480179 The folder of Google Earth does not meet the expectation of the operating system

Posted by bigcav on 15 May 2015 - 05:34 PM

Hello all


I know this is an old post, but l have been having the same problem.


"The folder of Google Earth does not meet the expectations of the operating system"


I am running Windows 7..... FSX gold.... FSC 9.6 (tried this in 9.2 and it also works)


I think l have found the problem.......The newer versions of Google Earth.


I went into "Google Earth auto updates" and downloaded and installed Version 6.1.

(We are now on 7.4)


Everything now works fine, Google Earth auto-loads as soon as you click

"show position in Google Earth"







  • 1

#479793 MyTraffic X installation not working - checklist

Posted by Burkhard on 04 May 2015 - 07:10 AM

Please try the Communicator attached here, just is programmed for excessive size of scenery.cfg - never had assumed FSX to work with more than 200 addons, and you have 800 :)

Attached Files

  • 1

#479633 Patch to MyTraffic 6.0

Posted by Der Flieger on 01 May 2015 - 07:30 PM

I think the 707s have been withdrawn since 2007 actually. So for quite a while now... ;)

The problem in Joburg is, that I only get the Kulula and Comair flights (Kulula is indeed a subsidiary of Comair) and many other airlines like SA Airlink, 1time, etc when putting my slider above 50%. When I have my traffic set to 50% I just have the SAA aircraft and a few foreign widebodies displayed.

Mango aircraft are never displayed, not even at 100%...even though the repaints are in the 737 folder. And just as a sidenote, 1time also has been closed for several years now...I think they ended operations in 2012.

As you can see the SA skies are a bit outdated in Mytraffic. Please have a look at a random day and time on flightstats where you can see the typical traffic for Joburg: http://www.flightsta...tusByAirport.do

Thanks! :)
  • 1

#479620 Updated modules

Posted by Roland on 01 May 2015 - 01:10 PM

Hi Pete,

LINDA 263 has problems with 4.939m, especially NGX737 Modul 3.3, no knobs of the VRInsight MCP are working.

Also with LINDA 1.3

  • 1

#479240 FSX FIBER ACCELERATOR doesn't run on FSX-SE update

Posted by BD-FSPS on 24 April 2015 - 10:43 AM

Naturally yes ... Expect it in the next days. (To get the update - allowing the app to check for it - run Fiber alone, not along FSX Steam as it will produce an error that way).


(Most webstores notify their customers for any update however. You can get the full installer from there to be sure).


EDIT: We managed to compile the code very fast this time, so the update is online already. Just follow the above procedure to get it or follow this link directly:


  • 1

#479219 Possible to transfer settings?

Posted by Gypsy Baron on 23 April 2015 - 10:43 PM

I used to have a dual-boot Win7/XpPro setup and did the 'copy ini files' with no problems. As I recall, I jsut made sure the letter assignments for my controllers matched in FSUIPC4 between the two OS's. I always use the 'assign letters' for controllers so that any renumbering of the devices by Windows doesn't negate my many, many hours of 'customizations' ( My current INI file is 5595 lines long! )



  • 1

#478726 FSX SDK installs but no simconnect.dll exists

Posted by flying-w on 14 April 2015 - 02:48 PM

Hello Ray,

The SDK is only part of the equation.  It does not install the SimConnect client (.dll) in its own right, but once you have the SDK you will have access to an MSI installer from which you can install the client.  When you installed FSX, that would have deployed the SimConnect client also, and after removing it so to was the client removed (or at least in some part to make it unusable). 


The STB user guide has reasonable coverage of all of this, starting on page 83. 


I wish Microsoft had made SimConnect redistributable, would have saved a world of pain.



  • 1

About simFlight - simflight.com - simflight.de - simflight.fr - simflight.nl - simflight.pt - simflight.es - simflight.it - simflight.jp - simrussia.com - simMarket