Hoeller

I finally solved this! Problem was that FS PC was in english localisation and Panel PC in french. I set up panel PC to english language, checked units (decimal separator), and now it's working fine. It seems you must have both systems set to the same language. Now I can test this, looks very good. Olivier.

I would say the future C172R hopefully coming in a few weeks, it certainly will be a best seller, anyway there's great expectations. I also noticed you sell add-ons gauges for P51 and Spitfire, A2A's versions of those two are outstanding. As I understand it, panel builder gauges won't be accurate with accusimed aircrafts, simply because they don't directly use offsets. If you read the MAP offset for one of their planes and compare it to the reading of the gauge of the VC, it's not the same value. They use a lot of LVars and their own engine. It's the same problem with the DA20, you have to process Lvars with a LUA script to inject the data in a free offset. I did it on my previous home cockpit for the Cub gauges with Gauge composer freeware, it works but it ain't pretty. It would rock to have out of the box gauges set for any of their accusimed planes actually, as you did for the Dodo. But I understand things are more complicated with A2A.

As for DHCP vs Static IPs, I need to keep the FSX PC on a static IP to have a remote access to it. I tried to set both PCs to dynamic addresses for testing, but that changed nothing. Then I installed your utility on the panelbuilder PC, and it's getting stranger... I can see values changing using both Simconnect or FSUIPC interface so the data do actually reach my gauge PC... What I did is test with RPM, I can see the RPM0 value change in the comms checker as I change power settings in the sim PC. If I disconnect Comm Checker and launch panel builder with the RPM gauges, the needles don't move. One thing I noticed, I accidently launched a night flight for testing, and the gauges on the panel PC darkened into "night mode", but needles stick to zero... Thanks for your help

I'm very interested in the answer to that, it's the same problem with A2A addons, I can make gauges with Gauge Composer but it's a lot of work and the result isn't by far as pretty as panelbuilder graphics.

Still no way to make this work... My network config: PC FSX: IPv4 192.168.1.101 / Subnet 255.255.255.0 / Gateway 192.168.1.1 / DNS 192.168.1.1 PC PanelBuilder: IPv4 192.168.1.221 / Subnet 255.255.255.0 / Gateway 192.168.1.1 / DNS 192.168.1.1 Both PCs are on the same Workgroup : they were'nt in the first place and it caused a problem with Widefs, now widefs is operational, still not PanelBuilder What I did since yesterday: - Install new windows 7 pro x86 on the panelbuilder test machine. - Added Reliable MultiCast protocol on both PC (seen that on a microsoft tech forum) - Try with FSUIPC version or Simconnect version - Installed wireshark on the client, I can see the packets broadcast. I don't understand... Panelbuilder works fine on the FSX PC, so I guess that means that simconnect configuration is OK and I'm dealing with a network problem. Any idea?

Hi, thanks for your quick response, I'm confident there is no IP settings problem in my LAN, there is a router with DHCP enabled, but the two PCs involved here have static IPs (outside of the DHCP range) and in the same network subnet. Both can browse the internet and both can share files with each other (sorry but English is not my first language, I hope I make myself clear). Funny thing in this is: I would think that FSX PC doesn't see PanelBuilderPC but this isn't true because: A- When I click START button on the simplugins interface on FSX PC, panelbuilder opens on the second PC B- I can ping FSX PC from panelbuilder PC and vice versa C- I can share files in windows from or to FSX PC from or to PanelBuilder PC. So I would think the problem is with data send via ports (hence disabling the firewall)?

Hi, I have problems making panelbuilder (demo mode for now) work on my network. After installing Simplugins FSX on the flight sim PC and PanelBuilder on a second PC (fresh install of windows 7 x64), here's what I get: I load a flight in FSX, then click connect on the simplugins interface, status bar shows "connected to FSX", everything looking good. Now on the second PC I launch panel builder, click start and the six gauges appear, but out of sync with the sim, needles stuck to zero, nothing moving. Here's what I tried to do: - install panelbuilder on the flight sim PC: it works as it should, needles moves in sync with the sim. (not a solution as my interest in the product is to have gauges on a networked PC, but trying to pinpoint the problem) - disable windows firewall on both machines, disable antivirus. No improvement. - If I click on the fligh sim PC/ Simplugins interface/ PanelBuilder remote control START, the gauges pop open on the second PC as they should (so it seems they do communicate some way), but still not moving. I don't have any idea what is going wrong... I have nothing special on my LAN (3 PC, a media box) I'd like to see how smooth it runs on the network before buying so if any help would be appreciated Regards Olivier

Hi,Here is a video I made showing two french Fouga Magister jets in the Patrouille de France 1966 livery.Hope you enjoy!