Jump to content

rjhussel

Frozen-Inactivity
  • Content Count

    355
  • Donations

    $0.00 
  • Joined

  • Last visited

Everything posted by rjhussel

  1. We cannot replicate what you are seeing. All NAV Radios show all frequencies correctly, also the ones below 110. We tested with Panel Builder Version 2.95. If you do not have this version, you can upgrade: http://www.simplugins.com/html/panel_builder1.html
  2. How many networks cards does your computer have? You do not need to forward ports, Panel Builder traffic does not get routed and stays on the local network. What are the IP Addresses on your computers? If you look at our FAQ, there are some hints you can follow: http://www.simplugins.com/html/faq.html#DoNotReact
  3. Just a note regarding the issue with multiple network interfaces: We are working on a solution that will allow you to select which interface to use. We have some initial success with this, but still have to make it a bit easier to configure. Not sure when we can get this released. Right now, if you have multiple interfaces, windows 'decides' the best one to use.
  4. This sounds like your firewall is blocking some instruments. When you do a reinstall make sure that the 'Add instruments to firewall' is checked. This is one of the last dialogs during the install. You can see it adding them when a black box appears and it shows each instrument being added (this is fast, you probably can't read it). When using comms checker, Panel Builder should not run. It runs instead of Panel Builder to show you the values coming from the sim. It should run on the same computer as Panel Builder. So, I recommend a reinstall of Panel Builder. I don't know why it would sto working, unless something changed in your computer. How many network interfaces do you have on your computer? Check our FAQ about this on our website, http://simplugins.com Re P3D, yes, all that is required is the interface. Any P3D interface should work, even the version 1 interface. You didn't say what the issues were, only that it didn't work.
  5. The single annunciator lights are configured using the setup screen. Right click on the light once added to a panel (and after starting it), then select Settings. Here you can select from a set of pre-configured conditions. The Status Lights 10, 8 and 5 are pre-configured using the interface config file (as you have discovered). You can change them as you have done. In your second example you need to select a light that has a single status (one that starts with 1I_.....). The others are engine related lights. So , for example use this one instead: 44014|1I_L3_|sim/cockpit2/switches/yaw_damper_on
  6. You are correct, the stop button is not used any more. The panel stops now by clicking on the taskbar. In older versions this was not the case and you had to press stop.
  7. RC Simulations, the company you bought from, will contact you directly to solve the issue. Your money is not getting lost.
  8. What did you buy? You need to buy Panel Builder ('Home' is the only version that is sold, that's what you have) and the A2A C172 Add-On, which it sounds like you did. You don't need to buy anything else. What does 'simply not work'? I more precise description of the problem would by very useful in trying helping you. We have many customers that have Panel Builder with the A2A C172 Add-on.
  9. What did you install where? The simPluginsP3D Interface should be on your computer with P3D. Panel Builder should be on your 2nd computer. I suggest a reinstall of Panel Builder.
  10. It looks like you are starting Panel Builder again while the panel is already running. To stop a panel you click on Panel Builder in the taskbar (not on the Panel Builder Icon) and the panel immediately stops and you get the desktop back. How do you stop the panel? What Windows Version do you have?
  11. OK, thanks. We'll give it some more thought in this case. Thanks for your suggestion.
  12. We have no plans for it right now. Maybe if demand increases.
  13. I can confirm that there is a problem when using a second networked computer for Panel Builder. It does work when using a single computer. Also, the FSUIPC Interface seems to work ok. I believe that this has to do with the network performance/speed. I suggest using the FSUIPC Interface until we have a fix for this. It could also be a firewall issue.
  14. Yes, we do know about the issue. I probably helps somewhat if you start Panel Builder on the client computer first. Adding any more RAM will not solve the issue. It has to do with networking. The instruments adjust their behavior depending on how fast data is delivered over the network. I hardwired network connection (not WiFi) would be preferable or cross-over cable between both computers with static IP Addresses or a dedicated network for both computers would also help, but that might not be practical for everyone. We are working on a new Panel Builder Version that should solve the issue. We have done some preliminary tests already. Sorry about the inconvenience.
  15. The installation file does not contain a trojan. It is flagged as a false positive. You need to allow it through your virus scanner. I don't know how to do this in Kapersky, but other virus scanners have an option to allow a file through. We are using AVG and it is not flagging it as a virus or trojan. Reinhard
  16. Thanks for the info. There is no way for me to determine what keyboard is in use. For programming, all I have are the mouse scroll events that are not linked to a particular hardware. The + and - buttons on the other hand could be an issue if you do not have a numeric keypad on your keyboard. No I am not aware of an issue with the RPM Gauge, No one else has reported this and I have never seen this happening. I'll have to have a look.
  17. OK, but still not sure what's happening. We had the re-sizing feature since day one and had never had any issues with it. Maybe you can check that your are running windows at 100% display, go to Control Panel\All Control Panel Items\Display and make sure you are running 'Smaller - 100%'. Just a thought.
  18. No, we have not heard of this problem. The only thing I can think of is that the instrument is locked (using the right click setting lock), but you can move the instruments, so I don't think that is the issue. What computer do you have?
  19. Yes, we are ysing them already, just not for the EFIS instruments. I'll add it to the list for the next update. Yes, we are ysing them already, just not for the EFIS instruments. I'll add it to the list for the next update.
  20. It is impossible for us to create a custom interface for every aircraft add-on. If an add on aircraft provides custom offsets, you can modify the Panel Builder FSUIPC interface cfg file. There is also a way to inject LVARS back into FSUIPC if this is provided by the add on aircraft. There are some posts as about this in this forum, seatch for LVAR and A2A C172.
  21. You are correct, right now all EFIS instruments switch on with Avionics power. Right now I do not have a different option, like the battery power. This would be a big change, but I do think this is a great idea. Are you only using EFIS instruments for your engine or are you also using other Panel Builder instruments?
  22. Hi All I'm looking for the FSUIPC Offset equivalent to the Sim Connect Variable AIRSPEED TRUE CALIBRATE. Anyone come across this? It's for the calibration dial of the Airspeed Indicator setting TAS. Thanks.
  23. Great! Thanks for testing this. I'll add the changes to the next update now.
  24. I think I found a solution, can you test this for me and post what you found out? The issue is that the FSUIPC offsets for the VOR1 receiver do not know what has been set to it (NAV or GPS), but the HSI does. So the below changes use the offsets for the HSI for the VOR1 Gauge. Edit the following file : C:\Users\INSERT YOUR USERNAME HERE\AppData\Roaming\simplugins\PanelManagerPRO\simpluginsFSUIPCA2A.ini (make a backup copy first!) Scroll down until you find [Nav1] and use the following entries: [Nav1] N1OBS = short,0C4E N1HDEF# = double,2F88,{0} / 25.4 N1VDEF# = double,2F90,{0} / 23.8 N1TF = byte,2FAD N1VS = byte,2FAB N1HS = byte,2FAE Save the changes and try it out.If it works I'll make a permanent fix for it in the next update.
×
×
  • Create New...