rjhussel

What Version of Panel Builder do you have and what Interface are you using (simPluginsFSUIPC or simPluginsFSX)?

The Radar Altitude Label in the EFIS instrument set has no limits (I assume that is the gauge you are referring to) and shows what the flight sim shows. I can add a limit as requested. I have a look at the other issues. What fuel gauge are you referring to? Is this the Fuel remaining gauge? Also, what version of EFIS Panel Builder do you have?

What version of Panel Builder do you have? It should be fixed in the latest (2.92). For upgrading see here: http://www.simplugins.com/html/panel_builder1.html

Sorry not yet.

We are constantly improving our products, this includes the A2A Add-On. Thank you for your suggestions. We will consider them for our next update.

The A2A C172 Add-On for Panel Builder gives you a new Interface. The shortcut is placed on your desktop. You need to use this Interface (simPlugins FSUIPC A2A) when using the A2A Plane in FSX. For any other plane in FSX you use the standard Interface that came with Panel Builder (simPluginsFSX or simPlugins FSUIPC). You also want to build a panel using the instruments from the Add-On. When adding instruments to a panel make sure you select the Instruments from the Instrument Set dropdown called 'A2A_C172'

I have a look at the Radio Altimeter if the code for the ButtonMapper is missing. Re the Saitek Trim Control: Unfortunately there is not much I can do. In my view it has a design fault. Why would the control 'disappear' from Windows if not used for a while. No other controller does this. I'm not sure what you mean by 'Button Mapper goes offline'. If you could clarify I can investigate further. Also I don't know why this should affect Button Mapper. There are several types of Clocks in Panel Builder. Some or auto-setting (get set by the flight sim) other you have to set every time before each flight. This is just like in the real world. Some clocks only work when battery power is applied and therefor need to be set after engine start. I checked the Radio Altimeter Decision height. It works in the latest version of Panel Builder and Button Mapper. But each button press (or encoder click) increase/decreases the value by 1 (foot), so this is a small value and you to press a lot of time to so a change. I've adjusted the increase to +/- 10 feet for each click. This will be available in the next version update. I checked the Radio Altimeter Decision height. It works in the latest version of Panel Builder and Button Mapper. But each button press (or encoder click) increase/decreases the value by 1 (foot), so this is a small value and you to press a lot of time to so a change. I've adjusted the increase to +/- 10 feet for each click. This will be available in the next version update.

Please send me an image/picture to support@simplugins.com. I see what I can do.

The latest version is compatible with Prepar3D. After purchasing you can update the product on our website, see here: http://www.simplugins.com/html/add_ons.html

There are 2 version of the PropSync Gauge, one for X-Plane (PropSync) the other for FSX (PropSyncFSX). Which one are you using?

There is a section in the manual (Interface Modification, page 105) that explains how to change port numbers. Basically you need to edit the configuration file for the Interface and then the port number for the instrument in the panel.

The VAC/AMP gauge is working correctly, we tested with the default C172 in 10.30. Make sure you have the latest version of Panel Builder (2.92). Also do not forget to update the X-Plane Interface as well. Here is how to update: http://www.simplugins.com/html/panel_builder1.html

We don't have a demo for the DCS P51 version, only the standard Panel Builder for FSX/P3D or X-Plane.

You need to change the screen font in windows control panel to 100%.

1) The P3D Interface Add-On is sufficient. 2) Panel Builder has nothing to do with any panels inside FSX/P3D/X-Plane. It provides its own instruments and runs completely outside of the sim as an external application. Hope that helps. P.S. You can download a trial version from http://simplugins.com/html/downloads.html

What is the network configuration of your Panel Builder (second) machine and how are they connected (cross-over cable, via a switch or via a router) ?

We had reports previously from customers using a wireless network that the performance of the instruments can lag. We therefor recommend a wired connection only. Also if you have no router in your network (only a switch), you need to assign fixed IP addresses to each computer. That is also necessary for cross-over network cable connections.

Please supply more information: What sim are you using? What aircraft in the sim? What version of Panel Builder? How are the PCs networked? Do the other gauges work?

The X-Plane plugin architecture is much more powerful and allows for faster processing. FSX and P3D use simConnect which is not as fast as the X-Plane Interface. Also I think your computer might be slightly under-powered to run everything on one PC (with FSX and P3D anyway). We have many users running on a single PC (I7, with 16GB RAM) and X-Plane. There are a few thing you can do to improve the speed on FSX and P3D: 1. Reduce the update rate. Go to simPluginsFSX (or simPluginsP3D), then Network Configuration and change the Update Interval to maybe 300 or 350 milliseconds. 2. Disable instruments in the config file you are not planning to use. The config file is located in C:\Users\[YOUR USERNAME]\AppData\Roaming\simplugins\PanelManagerPRO. Edit the file simPluginsFSX.ini (or simPluginsPrepar3D.ini). Find the following section: [instruments] Airspeed=41001 HeadingIndicator=41002 VerticalSpeed=41003 Altimeter=41004 ArtificialHorizon=41005 TurnIndicator=41006 RadioAltimeter=41007 AOA=41008 GForce=41009 GPS=41010 RPM=42001 EngOilTempPress=42002 BatteryVoltsAmps=42003 FuelTank=42004 EngEGTMAP=42005 TurbITT=42006 TurbN1=42007 FuelFlow=42008 EngTRQ=42009 CyldHdTemp=42010 CarbTemp=42011 EngEGT=42012 EngMAP=42013 EngRAD=42014 FuelPressure=42015 TurbN2=42016 BusLoad=42017 BusVolts=42018 PropSync=42019 EngEGTFF=42020 Nav1=43001 Nav2=43002 HSI=43003 ADF=43004 Compass=43005 AutoPilot=43006 DME=43007 Annunciator=44001 AirTempDisp=44002 OMI=44003 Clock=44004 AnalogClock=44005 HobbsMeter=44006 AnnHelo10=44007 AnnHelo6=44008 StallWarning=44009 TrimIndicator=44010 GearIndicator=44011 FlapsIndicator=44012 Suction=44013 StatusLight10=44014 StatusLight5=44015 SpoilerIndicator=44016 AircraftReg=44017 FuelTankSelector=44019 HydrPress=44021 Wind=44022 StatusLight8=44023 ;HeliTurbRotorRPM=46001 ;HeliTRQ=46002 ;HeliTurbTemp=46003 ;HeliLoadFuelPress=46004 ;HeliGasGen=46005 ;HeliEngOilTempPress=46006 ;HeliTransOilTempPress=46007 ;HeliFuelTank=46008 ;HeliEngRotorRPM=46009 ;HeliManifoldPress=46010 ;HeliEngRobinson=46011 Radios=47000 Global=99999 Place a semicolon ( in front of any instruments that you are not using, as shown above for the instruments starting with Heli... . This will disable the data from being pulled from FSX (or P3D). The smaller the number of instruments, the quicker the it will be. The entry after = is the port number. So you could build your panel and check all the port numbers of instruments in Panel Builder and then disable everything else you do not need. This is if you have mainly one or two panels you are using. If you need any other instruments, you then need to re-enable them in the config file. If you make changes to the config file, you need to restart the interface (simpluginsFSX or simPluginsPrepar3D). Hope that helps

You can also change the settings in the panel and specify which monitor to use for the panel.

There are command line arguments for: PanelBuilder.exe start (starts Panel Builder, loads the last used panel and starts the panel) simPluginsFSX.exe start (loads simPluginsFSX and connects) ButtonMapper2.exe start (loads ButtonMapper2 and clicks on 'Run') Yes, a .cmd file would work.

We will have a configurable N2 gauge (just like the N1) in the next update coming shortly. We are just finishing the update.

There will be an update shortly that will also support P3D.

The installer does not check the available memory. Running a small panel on 2GB might work. We have many customers running a 4 screen system on a single computer. Unfortunately I cannot make any statements regarding of the performance of Panel Builder on the suggested architecture. If any other users of Panel Builder have experience with system like this, please respond tho this post.

What Panel Builder Version do you have? I have been trying to make it fail, but cannot replicate the problem.