[PFCHid64.dll not supporting PFC430 hardware]

16 hours ago, zfehr said:

The RXP Garmin 430/530 work in FSX

You contradicted this in your previous message

17 hours ago, zfehr said:

I am mistaken on being able to recognize and program the buttons on the PFC430 in FSX though. I am sure I was able to on an earlier version but the present version is also absent in FSX.

So, I am now thoroughly confused. If it works with PFChid.dll in FSX it must also work with PFChid64.dll in P3D4/5 and MSFS. Are you now saying it doesn't work with either?

BUT I have never seen a PFC GPS device and therefore have never developed anything for it.  As it is recognised by the Scan then there's a possibility that some of the command blocks it sends to the PC are actually covered already by the PFC driver I wrote, but there are probably parts which it won't recognise. There's also the possibility that it operates as a Joystick type device in which can the buttons and switches should be visible to Windows and therefor FS and MSFS without the need for a driver.

I haven't done any development work for PFC devices for a long, long time. I assumed PFC only sold the newer devices for use with X-Plane. Did they say it worked with FS?

I am retired now and not really able to do further developments. It might be better if you asked PFC about it.

Pete

 

[PFCHid64.dll not supporting PFC430 hardware]

7 hours ago, zfehr said:

The PFC430 is a USB standalone unit which works well with xPlane v9 (FAA certified version) and FSX, I am able to get FSUIPC to recognize buttons on the PFC430 and could program them to another function if needed but since they are working with the RXP software there is no need.

Are you using PFChid.dll with FSUIPC4?

7 hours ago, zfehr said:

In MSFS2020 FSUIPC does not recognize button pushes on the PFC430 hardware and I am unable to assign any function to them.

Using the same settings as in FSUIPC4 there should be no difference at all.  As far as PFChid64.dll is concerned the only difference at all from PFChid.dll is the re-compilation as a 64-bit module instead of 32 bit.

The log appears to show that the device hung and stopped processing data sent to it, hence continuous buffer full errors.

Pete

 

[change, profile creation]

18 hours ago, tosco92 said:

hi, i should create two different profiles but which i would use with the same plane, how do i do?

The profile system isn't designed to do that. But you could do it by making another entry for the aircraft with a different title. Open the aircraft's Aircraft.CFG file and fine a section like this:

[fltsim.0]
title=F-14 
sim=F14
model=
panel=
sound=
texture=
kb_checklists=
kb_reference=
atc_id=N001
atc_airline=NAVY
atc_flight_number=001
ui_manufacturer="Grumman"
ui_type="F14"
ui_variation="Grey"
ui_typerole="Twin Engine Jet"
ui_createdby="LM"
description="The Grumman F-14 Tomcat is a supersonic, twin-engine, two-seat, variable-sweep wing fighter aircraft. The Tomcat was developed for the United States Navy's Naval Fighter Experimental (VFX) program following the collapse of the F-111B project. The F-14 was the first of the American teen-series fighters which were designed incorporating the experience of air combat against MiG fighters during the Vietnam War."

Make a copy of such a section, placing it later in the CFG file with a new number --  [fltsim.1] in the above case, or where there are more such sections, the next number in sequence after the last,=.

Then, in your new section, change the Title= line to give it a name which you can use specifically for the other profile.

Pete

 

[Opencockpits multiradio]

1 hour ago, Risto said:

I have Opencockpits multiradio and I install FSUIPC7 ( I have reg early version 43 and 4) and installed 7.

When I start MsFs2020 it starts FSUIPC7, but sim doesnt start radio.

Note that FSUIPC7 needs a different purchased registration to earlier versions FSUIPC4, 5 and 6.

How is the Sim supposed to "start" the radio? Do you mean some sort of driver for your hardware? If so it is definitely a matter for OpenCockpits support.

1 hour ago, Risto said:

Do I need install also sioc and other software ?

Sorry, I've no idea. I do not know this hardware and simply cannot support products other than our own.  I suggest you check the documentaion supplied with your radio, or contact their support for help.

Pete

 

[FSX SE -FSUIPC4 DLL]

1 hour ago, RalphC said:

Once I launched FSX SE. I got the same problem, but I carried on anyway and good old FSUIPC was ther

Glad it is all sorted.

Good flying!

Pete

 

[create mouse macro button missing]

6 hours ago, Pro Flight Simmer said:

The mouse macro green area does not appear.

Many FSX cockpits don't use the standard C++ tools for their gauges. Mouse macros only work for standard C/C++ gauges becuae they depend on intercepting the code called by the mouse click.  You'll probably need to look for other methods. Best is to use whatever FS control operates the switch (detect this with event logging). There's also L:Vars to try -- list those (there's an FS control to do that, and a provided Lua plug-in to log them as they change).

For PMDG Boeings there are many added controls listed in the aircraft's SDK.

Pete

 

 

[FSX SE -FSUIPC4 DLL]

5 hours ago, RalphC said:

Flight Simulator has detected a problem with  third -party programme:

FSUIPC4 DLL FS new Universal IPC Interface Version 4.977 

I thought that the DLL might be old, but I recently purchased FSUIPC and installed it a couple of days ago... 

Any help please?

This message occurs when FSX has previously crashed with FSUIPC still trying to close things down tidily. Being the module with the last thread running, Windows wrongly attributes the failure to it and this gets marked so in the Registry.

Sometimes telling FS to carry on and load FSUIPC works and clears the condition. If this doesn't help, even after a couple of attempts, then it could be a corrupted weather file, possibly caused by the crash. For this please refer to

This thread may also be helpful:

Failing all this, you'll need to supply an FSUIPC4.LOG file after FSX crashes when telling it to load FSUIPC.

Pete

 

[FSX SP2 does CTD with FSUIPC ...Please, Help!]

1 hour ago, trisho0 said:

Keeping an eye for new Fsuipc version.

There will be no new version of FSUIPC4 for FSX. Development was frozen some time ago. The only recent changes were for the installer to cope with the Microsoft FSX-SE Beta (years ago now) and a rebuild using a later compiler version.

FSUIPC does not cause any crashes itself. It passively receives data from SimConnect to populate the offsets. It only actively does things in response to requests from applications or the assignments made by users. It is in regular use on uncountable installations of FSX, FSX-SE and P3D versions before P3D4. Crashes tend to get blamed on FSUIPC because it is ubiquitous, but they all turn out to be due to other things on the user's system.

Pete

 

Pete

 

 

[FSX CS B727-200 Flight Engineers Panel ID]

10 hours ago, elsmoko said:

Both the Overhead panel and the Engineers panel are listed on the FSX Views\New Views\Cockpit pull down menu

and I can make them popup / appear when they are selected from there; however I can find no reference to either of

them in the Panel.cfg file.

Then I don't think they are panels as such. They are just different preset views, which I think you can accomplish by moving your view around. I suspect a lot of add-on aircraft with so-called 3D cockpits don't actually bother with the traditional 2D panels as such, as you can move around and zoom in and out as you like.

From your PANEL.CFG I see panels iwth IDs 29, 10002, 10005, RADIO_STACK_PANEL, GPS_PANEL, 11004, 11223, 11005, 10050, 10007, 11040, 11041. I can't tell what they all are -- the gauge names for some are rather obscure. But you could try them.

Pete

 

 

Pete

 

[can not regester fsuip7 and widefs]

6 hours ago, John Glassberg said:

I have purchased both fsuipc7 and widefs, coppied and pasted both key numbers as instructed and I could not regester.

ALL THREE parts need to be exactly correct -- name, email and key, not just the key. And please read the documentation to make sure you are following the correct procedure.

I'm afraid if you still get no joy you may been to wait till next week as John is on holiday at present.

Pete

 

[FSX SP2 does CTD with FSUIPC ...Please, Help!]

3 hours ago, aldox62 said:

sorry this is the right AppCrashView file...

Both that and the previous one do not indicate FSUIPC as the culprit. The Log too shows normal running. I'm afraid you have something else going on.

If it NEVER crashes with FSUIPC not running then you need to check your other add-ons to see which is using FSUIPC.

Otherwise you'll need to consider an FSX re-install. Something is corrupt. It may be an add-on aircraft or add-on scenery if not the main FSX modules.  Try a different aircraft to start with. And also keep track of what scenery is in use when it crashes (i.e. where you are flying over).

Pete

 

[For every Liverie a new profile?]

Seems very strange to me. Which name is used in the selection to load the aircraft?  Will users be aware of the Air file name so they can edit the Profile sections correctly should they wish?

 I think I’ll have to leave it to John — he’s away till Monday. I assume he’s doing something different with profile matching in FSUIPC7, otherwise I can’t see how those profiles end up classified the way you describe.

Pete

 

[For every Liverie a new profile?]

3 hours ago, Scotfleiger said:

FSUIPC, as described in the User Guide, uses a name match. This wrongly assigns the FBW livery to the Asobo A320 as follows:

[Profile.A320]
1=Airbus A320 Neo Asobo
2=British Airways OperatorLand468 FBW

Sorry, I don't follow you. The names used are from the title= lines in the Aircraft.CFG, the ones used in the sim's selection list. You are saying that some substring of 
British Airways OperatorLand468 FBW
matches 
Airbus A320 Neo Asobo

Now, how do you think that can be? Please explain.

Is the title not used for selection in MSFS?

Pete

 

 

[FSX SP2 does CTD with FSUIPC ...Please, Help!]

2 hours ago, aldox62 said:

what should I do with the wxtationlist.bin file ?

Delete the one in your AppData\Roaming folder. FSX will regenerate it.

Pete

 

[FSX SE Black screen]

6 minutes ago, RalphC said:

I purchased FSUIPC for FSX SE. yesterday. Great programme. Started working with it, no problems. I returned to FSX SE to do some more editing and found that, when I launched FSUIPC.. The screen turned black. Once I closed FSUIPC, FSX SE returned an was running normally. 

The FSUIPC options display does make FS blackout the main display. But the options dialogue should show on top.

Try first setting FS into Windowed mode (ALT+ENTER). If the options then show then for some reason they were previously showing underneath the main FS display.

The only other possibility is that the options are being displayed off-screen, maybe because you've changed screen arrangements.  In this case, close FS and look in the FSUIPC4.INI file. If there's a OptionsDialogOffset parameter line in the [General] section, delete it.

Pete

 

[FSX SP2 does CTD with FSUIPC ...Please, Help!]

12 hours ago, aldox62 said:

but the CTD hits randomly - usually not earlier than 1.5-4 hours of flying
...
 

12 hours ago, aldox62 said:

The CTD appears randomly: either when I'm not sitting at the PC, or when I take some action on main FSX screen say change the flight level or work with FMC (not touching FSX menus) or when I scroll ASN16 map to keep the aircraft in view, or even when I do other things on the PC that may not directly touch the FSX environment windows on the desktop. 

Please always supply the FSUIPC4.log file after a crash (ZIP if too big), and the actual Event Viewer details from Windows, not just an offset!

As this appears to be at random it does sound likely to be a corrupted weather file, which in turn cuases something in memory to be corrupted when FSUIPC asks SimConnect to supply weather.

To test for this, try adding

NoWeatherAtAll=Yes

to the [General] section of your FSUIPC4.INI file. If this solves it then either your wxstationlist.bin file is corrupt, or one of the .wx files saved with scenarios is bad.

Pete

 

[FSX CS B727-200 Flight Engineers Panel ID]

5 hours ago, elsmoko said:

if there is a code available for the Engineer's Panel.

Find the PANEL.CFG file for the aircraft -- it'll be in a folder with Panel in the name, within the files for the aircraft.

In there look for the Ident= line.  Please refer to the explanation given here:

https://docs.flightsimulator.com/html/Content_Configuration/Instruments/Panel_Config_Definition.htm

If there is no such line, you can add one yourself giving it a unique ID number (10000 - 19999 as it says). If there's a name given, look it up here:

// Panel identifiers
#define IDENT_MAIN_PANEL                         0
#define IDENT_MAIN_PANEL_ALT1                    1
#define IDENT_MAIN_PANEL_ALT2                    2
#define IDENT_MAIN_PANEL_ALT3                    3
#define IDENT_MAIN_PANEL_ALT4                    4
#define IDENT_MAIN_PANEL_ALT5                    5
#define IDENT_MAIN_PANEL_ALT6                    6
#define IDENT_MAIN_PANEL_ALT7                    7
#define IDENT_MAIN_PANEL_ALT8                    8
#define IDENT_MAIN_PANEL_ALT9                    9
#define IDENT_THROTTLE_PANEL                    10
#define IDENT_RADIO_STACK_PANEL                 50
#define IDENT_COMPASS_PANEL                     75
#define IDENT_MINI_CONTROLS_PANEL               100
#define IDENT_ANNUNCIATOR_PANEL                 125
#define IDENT_ANNUNCIATOR2_PANEL                150
#define IDENT_IFR_MAIN_PANEL                    175
#define IDENT_COLLECTIVE_PANEL                  200
#define IDENT_GPS_PANEL                         225
#define IDENT_OVERHEAD_PANEL                    250
#define IDENT_PARKING_BRAKE_PANEL               251
#define IDENT_FLAPS_TRIM_PANEL                  252
#define IDENT_FUEL_PANEL                        253
#define IDENT_ELECTRICAL_PANEL                  254
#define IDENT_TRIM_PANEL                        255
#define IDENT_LANDING_GEAR_PANEL                256
#define IDENT_MISC_POPUP_1                      260
#define IDENT_MISC_POPUP_2                      261
#define IDENT_MISC_POPUP_3                      262
#define IDENT_MISC_POPUP_4                      263
#define IDENT_MISC_POPUP_5                      264
#define IDENT_MISC_POPUP_6                      265
#define IDENT_MISC_POPUP_7                      266
#define IDENT_MISC_POPUP_8                      267
#define IDENT_MISC_POPUP_9                      268
#define IDENT_MISC_POPUP_10                     269

to get the ID.

Then you should be able to toggle the panel on and off using the PANEL_ID_TOGGLE control, or open / close it using PANEL_ID_OPEN and PANEL_ID_CLOSE.

Pete

 

[[P3Dv4.5] FSUIPC6 not recognizing Honeycomb Yoke]

12 hours ago, softpxl said:

IT WORKED, It freaking worked haha!! Both the yoke and the hotas throttle do not interfere with each other from what I notice and it seems that all the axis' and buttons/switches are being recognized separately from each other.

I'll post the files just in case you still wanna take a look at it.

Oh, easier than I thought. The Log still shows this error:

    172    WARNING: Joystick ID 1 is duplicated in Registry
But it seems that this doesn't adversely affect the outcome.  I think the "other" device ID 1 must be the data channel on the X56, used (I think) only for firmware updates.

Good flying!

Pete

 

[[P3Dv4.5] FSUIPC6 not recognizing Honeycomb Yoke]

11 hours ago, softpxl said:

I have uninstalled the Hotas software and unplugged the hotas throttle. Funny enough the Yoke is being recognized by the axis assignment and button & switches tab in the FSUIPC control panel.

The problem seems to be that both devices are Registered with the same ID, as indicated by this error message in the Log:

      219    WARNING: Joystick ID 1 is duplicated in Registry

So, first thing to try is changing this part of the INI file

[JoyNames]
AutoAssignLetters=Yes
0=Alpha Flight Controls
0.GUID={FB3177A0-6E0F-11EB-8014-444553540000}
A=X56 H.O.T.A.S. Throttle << MISSING JOYSTICK >>
A.GUID={FB3177A0-6E0F-11EB-8014-444553540000}
B=Alpha Flight Controls
B.GUID={FB3177A0-6E0F-11EB-8014-444553540000}

To this:

JoyNames]
AutoAssignLetters=Yes
0=X56 H.O.T.A.S. Throttle
0.GUID={FB3177A0-6E0F-11EB-8014-444553540000}
3=Alpha Flight Controls
3.GUID={FB3177A0-6E0F-11EB-8014-444553540000}
A=X56 H.O.T.A.S. Throttle
A.GUID={FB3177A0-6E0F-11EB-8014-444553540000}
B=Alpha Flight Controls
B.GUID={FB3177A0-6E0F-11EB-8014-444553540000}

Also there are unwanted assignments in the [Axes.Twin-jet] section:

4=2X,256,D,1,0,0,0    -{ DIRECT: Aileron }-
5=2Y,256,D,2,0,0,0    -{ DIRECT: Elevator }-
6=2R,256,D,3,0,0,0    -{ DIRECT: Rudder }-

Remove those as you no longer have a device with ID 2.

Let me know how that goes when you have both devices connected (same files again please). If there's still a clash we may need to look at editing the Registry. (Ugh).

Pete

 

 

[pilot2atc setup]

18 hours ago, John Dowson said:

.you should really contact Pilot2ATC support

As John points out, this is a question for Dave at Pilot2ATC. The support forum is here:

https://www.avsim.com/forums/forum/713-pilot2atc-users-forum/

Pete

 

[Product Key]

15 hours ago, Andre Tucker said:

I recently downloaded a the FSUIPC 4 for FSX/P3d but no product key. How can I get the key?

You need to buy one from SimMarket --  https://secure.simmarket.com/pete-dowson-fsuipc4.phtml

Pete

 

[MakeRunways]

2 hours ago, surfcandy said:

I followed these instructions and have installed it without issue with PDv4. Now trying to install in PDv5 the executable (MakeRunways) isn't doing it's thing and loads zero instead of the many airports etc. Do I need the Lorby AddonOrganizer also? Thanks

No, the LorbySceneryExport program does the job of making a scenery cfg file which includes all scenery.cfg layers and the Add-Ons xml layers too, in the correct processing order.

Using it for P3D5 is exactly the same as for P3D4, so it needs installing in the same way, and running in the same way ("as administrator"). If you are getting no results check the MakeRwys_scenery.cfg file and look at the Runways.txt file to see if any errors are reported.

Pete

 

 

[FSUIPC7 vs PFC Avionics Rack]

12 hours ago, Ericdaspremont said:

i am have some difficulties installing pfc drivers in fsuipc

could you provide me some help?

What problems do you have? If you mean the PFC COM and/or HID DLLs, then there's no "installation" necessary other than placing them into the same folder as the FSUIPC7 DLL. 

Pete

 

[Rudder Trim Indicator]

1 hour ago, Alpin-Flier said:

0C02 2 Aileron trim value/control: –16383 to +16383 [NEW!] Ok-SimC ?-SimC
0C04 2 Rudder trim value/control: –16383 to +16383 [NEW!] Ok-SimC ?-SimC

I tried 0C04, but it outputs always a 0. Where does this value come from? Is it from SimConnect? If so, is it possible, that NGUx bypasses SimConnect in some way?

The trim values in FSUIPC offsets are from SimConnect, but they all relate to the built-in subsystems. Detailed addon aircraft such as those from PMDG tend to provide their own subsystems supplanting the default ones. This is why the PMDG SDK is so important -- these's no otherway to set or get subsystem values.

The fact that the current trim vales aren't available from the SDK (and hence not from the PMDG offsets either) is rather strange. I suggest that you ask PMDG about that.

Pete

 

[Throttle Set vs Axis Throttle Set]

17 hours ago, ark1320 said:

What is the difference between using Throttle Set vs Axis Throttle Set under the FSUIPC7 Axis Assignment Tab?

The ThrottleN_Set sequence of controls date back to FS98 or earlier, and provide a reverse thrust zone as well as forward thrust. That's what FSUIPC supports them and uses them for reverse/forward calibration.

The Axis ... Set controls are relatively new and provide no reverse zone. Some add-on aircraft work better with those than they do with the older ones.

Pete