rjhussel

Right now there is not. I'll investigate what would be required to achieve this.

Try to disconnect your WiFi and try again. Even if you have only one computer, it still uses networking.

Something must have changed, it just doesn't stop working by itself. The problem you are describing is normally having different Windows language settings on two networked computers. Otherwise you need to give me mote details of your flight sim setup.

OK great! I mark the issue solved.

You only need to copy this file there if this is where your FSX is installed on. If FSX is installed somewhere else, you need to find the Microsoft Flight Simulator X\Modules folder and copy it there. You can have both interfaces on the FSX computer, but only start one at a time.

So, it's still not working? How about the port number of the RPM Gauge? Its on the first screen of Panel Builder with the list of instruments. Is it set to 42001? Do you have a registered version of FSUIPC? It is required by this add-on.

Are you suing the simPlugins FSUIPC A2A Interface (The one that came with the A2A C172 Instrument Add-On)? Did you install the lua export script during the install? Check to see if you have a file called ipcinit.lua in the following folder: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules

Which RPM Gauge are you using? There are multiple available.

Do you have the same Windows language setting all all computers?

You are correct, the issue is with Prepar3D (and FSX). When running in full screen mode, it will take over all monitors that are part of your desktop. But X-Plane for example limits it full screen mode to the actual monitor it is on. So the solution is: - For Prepar3D and FSX you need to run in window mode if you have 1 computer with 2 monitors. - If you have 2 network computers (one for the sim the other for instruments), you can run in full screen mode - X-Plane can run in full screen, no limitation.

We haven't done much testing at all. We have done some work for Flying Cliffs 2 a while back, but not much besides that. The advice I gave you is based on the software architecture we have implemented in the DCS Interface. Yes, there is a switches add-on that will be released shortly, it will be free!

OK, I see what you mean. I think there is a aileron trim indicator in one of the instrument add-ons. But I'll add one to the standard set as well.

There was an issue with ButtonMapper in that when you used more than one joystick/board of the same type, it would only recognize the first one. We made a fix for this, you can download the new version of ButtonMapper (V1.5) from here: http://www.simplugins.com/ButtonMapper2Install.exe

1. The lua Interface script that comes with the DCS Version has been made specifically for the DCS P51D cockpit instruments. But it might work with other DCS aircraft as well. We haven't done much testing though. You can also modify the lue script to support other aircraft if required. 2. Yes, the original Panel Builder Gauges will work as well. But remember, there are only a limited number for instruments that have been implemented in the Panel Builder DCS Interface. But this can also be modified. The file you need to modify is c:\Users\[your username here]\AppData\Roaming\simplugins\PanelManagerPRO\simPluginsDCS.ini So basically, you can extend the DCS Interface very easy by: 1. changing the lua script to add/modify the datapoints being extracted from the DCS sim 2. changing the simPluginsDCS.ini file to reflect those changes (this file is used by the simpluginDCS Interface to send the data points to the correct port numbers of Instruments). The data point names (variable names) are fixed for each instrument. To find out what is what, go to the standard Panel Builder FSX Interface and select "Simconnect Configuration". Here you can see each instruments data points that are supported. If you decide to change them, make sure you keep backup copies of the files you modify (but I guess you could always re-install if required).

Thanks for the tip!

The Airspeed Indicator with TAS is currently fixed to 180 Knots. This has to do mainly with the TAS scale, which is a bit difficult to handle when changing the max speed. We are looking for a way to do this though for one of our next updates. We never had an Aileron Trim Indicator (what document did you see this referenced?). We'll add one for the next update. The switches Add-On is basically finished. We might be releasing it as a 'free' add-on. Thanks for reporting the issue with custom size. Will be fixed. We have a new night mode already in planning that will include the background as well. Too early to tell you more.

The A2A C172 Instrument Add-On is an Add-On to Panel Builder FSX (or any other Panel Builder Version). It contains the instruments and a special Interface based on FSUIPC to support the A2A C172 Trainer. You still need a standard Panel builder as some instruments for the Panel you might want to take from the standard set of instruments. The A2A Instruments will work with any stock aircraft if you use the simPluginsFSX or FSUIPC Interface instead of the Interface that comes with the Panel Builder A2A C172 Instrument Add-On. But the A2A Instruments have been 'tuned' to the A2A C172 and are reliant on the correct data coming from any aircraft,

You are correct. The ADF is included in the 'standard' instrument set of Panel Builder, whereas the other C172 instruments were made specifically for the A2A Add-on for Panel Builder. I'll update the ADF for the next Panel Builder update.

That doesn't really matter as the C172 has a direct drive prop (not a gearbox). But I would do Engine.

The latest version is 2.98. Get it from here: http://www.simplugins.com/html/inst_add_ons.html

The NAV1/2 selecting is already supported, but only using X-Plane. X-Plane has a dataref(variable) to indicate the HSI source. For FSX/P3D I couldn't find a variable, so it is fixed to NAV1 right now. I could add a configuration option for NAV1 or NAV2, but that would require a source selector switch for Panel Builder, which we currently don't have.

Not very likely a port problem. We use multicast networking. Unless the tablet apps use the same multicast network (224.11.5.62), this is should not be network related. I don't use those tablet apps, so I can't help much. How are they communicating with P3D?

Make sure that the P3D Interface is the same version as Panel Builder. Some people forget to update the Interface when updating Panel Builder.

You need to tell me more about your setup: How many computers? How are they networked? Are you suing Wifi? What else is on the network? What Version of Panel Builder? What kind of networking issues did you have? Looks to me like that something has changed in your computer (windows update?).

Are you using the latest version of Panel Builder (Version 2.94)? Make sure that both Panel Builder AND the P3D Interface have the same version number. Are the instruments otherwise working?