camtah

Just rebuilt my FSX machine with Win10 (clean install). I have the standard FSX w/Acceleration Installed. I have all the install DVDs. Up until now, I have been using FSUIPC4 and WideFS. I want to try simconnect and dabble in other SDK areas. I also use SPAD.Next and want to try A2A aircraft in the future. So based on the SDK Wiki, my setup (10.0.61637.0) should have access to the SDK package installation. The instructions do not work as the process insists that I need install a SDK first from the the Deluxe DVD1. The STD disk does not have this. I have seen many forum comments about following the /Wiki and it appears that my configuration is not supported. What are my alternatives and can the Wiki be updated? Thanks

I guess I spoke too soon...I misspoke..I was running v2.92 when I got it to work. I originally had v2.95 installed but I backed it out during my testing. I re-installed v2.95 and now I cannot get it to work....(more head scratching)...

Thank you for your reply. I have it working and this is what I found: When both interfaces on PC1 are up I have the multicast 224.0.0.0 routes: 224.0.0.0 240.0.0.0 On-link 127.0.0.1 224.0.0.0 240.0.0.0 On-link 192.168.17.5 <--Wireless IF to home network/internet 224.0.0.0 240.0.0.0 On-link 192.168.27.1 <-- Private Ethernet to PC2/Panelbuilder (192.168.27.2) When I disabled the Wireless Interface, the multicast route for it was no longer displayed on the table. I thought this was correct, yet I still could not get PB to function across the network. I then rebooted and decided to do leave the wireless interface up, but do a route delete on the multicast address instead and viola ..it worked.... Oh well..at least I have a work round. I only use the home network portion to backup my system to my WHS and update/download SW. Thanks again for making me revisit what I thought I already looked at....I must admit I was exhausted after fighting with this..

Hello all. Sorry I don't have any cliff notes for you to read :-) Background: My current FSX setup involves 2 PCs. PC1 is FSX running Win 8.1. PC2 is running Panel Builder, Saitek modules, etc. It is running Win 7 Home 64b. I use FSUIPC-4 and WideFS on PC2. I also use SPAD drivers for all the Saitek devices I use and they are based off PC2. The Yoke, throttles and pedals are all on the main FSX PC. I currently have PB 2.95 loaded and I use the PB-FSUIP driver on the FSX PC .I might add that the FSX computer and 2nd PC are dedicated to FSX. I do not use Internet connection sharing between them as PC2 has no reason to reach the outside world at this time. Up until a few weeks ago, these systems were part of my home network, all the same subnet 192.168.17.0 ( I work with networks in the real world) via Ethernet and Cat 6. I haven't had much time to enjoy the system in that past few weeks, but I am sure it was working fine when I last messed around. The Issue started when I had to re-arrange my office/play room. I This meant that I had to use the built in wireless adapter (5G and router is 6' away.) to connect to the home network on the existing subnet and I created an private subnet, 192,168.27.0 for both PC, and directly connected them via their respective Ethernet interfaces and a x-over cable. Problem: The PB gauges on PC2 no longer respond at all. I can ping between the 2 devices, I can start WideFS and I see a connection on PC via WideFS when FSX starts up. The Saitek modules via the SPAD drivers all work thru FSX. Therefore I concluded that the network is up and running fine. I suspect that the issue revolves around the multicast protocol between 8.1 and the Win7. I have tried a lot of different combinations, such as shutting down the wireless adapter, added the reliable multicast protocol to each interface. On PC1, I made sure the Ethernet was listed first under the advanced settings, etc. I downloaded the checker program from PB and I get no data coming over at all on PC2 I did install the PB gauges on the FSX PC using the the simconnect driver and they work in this case. I was able to throw the battery switch on the Saitek multipanel and watch the PB fuel gauges spring to life. I only have 2 IP addresses: 192.168.27.1 for the FSX, 192.168.27.2 for the networked pc. I had to set a default gateway on PC2 pointing to the FSX PC1 Interface. No default gateway is set on this interface. The multicast route is correct on both PC. The firewalls for both PC on this private network is turned off. I did check the box to add the devices to the firewall anyway. I even backed down to version 2.92 to see if that might have an issue. The only thing I can think of is that PC1 gets all the updates and PC2 I don't (it is isolated from the internet and there are other reasons). I am at a loss here and I wonder if anyone else has any ideas. Maybe 8.1 and 7 don't get along anymore. Not interested in going to 10 base don my experience with my laptop (another story) Thanks for the ear. I know this was a lot to digest...

Hello All: ------------------------------------------------------------------------------------------- Longtime lurker, former student pilot and part time simmer here: ------------------------------------------------------------------------------------------- I have been away from my FSX setup for a while and I am revisting my setup. I recently re-aquired an PC that I built for a family member and want to integrate it into my new FSX setup (via FSUIP/WideFS) * Currently have FSX on a I7-930 system ( on separate HD, ATI 6890 Eyefinity and (3) 24" IPS monitors). This PC servers as a dual purpose unit that also does music production. This is on Win7, 64 Pro. The re-aquired PC is currently a Q6600 on XPsp3 and I will be reformating to Win7-32. * I currently have a roll up table with Saitek Yoke, dual throttle, pedals, (2) radio, mult and switch panel. I also had a 17" monitor for gauges (undocked plane gauges windows). This currently runs off the main PC video card as a fourth monitor. * I am rebuildng my sim panel to include a new Desktop Aviator GPS panel monitor and (possible) Saitek BIP (jury out on this one). I am also considering using PIEX GA gauges on the 4th monitor. Now for my quesitons regarding networking the PC and to put what HW on what PC. Lookng for the best option listed below: 1) Use existing FSX PC for program and outside display only. Use the new PC for all the peripherals (yoke, pedals, display gauges, etc) via FSUIPC...<-- is this even a possible valid setup? -or- 2) Use existing FSX PC (program/outside displays) and control surface HW (yoke, pedals, throttles) and use the new PC for all the Saitek panels and gauge displays (via the the display monitor). The PC's would be networked and using FSUIPC and WIdeFS in the appropriate PCs ..or is there an option that I am overlooking? Thank in advance for any advice