GeorgeT93

I've set mine to 16, but it always seems to revert back to the default 32. I have not tried any other values however, since the 16 wouldn't stick.-George

1) Yes, and I'm enjoying it. I don't feel it's a replacement for my FSX, but it sure is a lot of fun.2) Yes, Hawaii Adventure Pack and the Maule. I did not (and will not) buy the P51 or any aircraft that doesn't include a cockpit.3) Yes, I will buy more DLC's in the future. Scenery areas that appeal to me, and aircraft that appeal to me (provided they have a cockpit.):)-George

There's a couple of people on the Saitek forums that are also having the problem using the BIP and TrackIR at the same time. I wasn't experiencing it myself, but after taking a peek in the batch file that I use to start TrackIR and a couple of other programs I have running during my FSX sessions, I realized that I had set the priority to below normal when launching TrackIR. That seems to keep things smooth on my system, but doesn't seem to have helped with other folks unfortunately.-George

After a little more testing, my flight was smooth using the batch file to start TrackIR at below normal priority, and the landing lights light worked for the duration of the flight, including many on-off cycles for testing. So I'm guessing that it not turning off earlier was a fluke.-George

Hi all,Saitek posted earlier today on Facebook, that they have released a new driver for the BIP panel, and a new driver for the Instrument Panel screens. I can't comment on the FIP drivers, as I don't have one of those, but the new BIP driver has fixed the parking brake light issue. The do claim better stability as well. The drivers can be found at:http://www.saitek.com/uk/down/drivers.phpI posted on their forum about my initial quick testing of the new driver, but since their forums are closed to new registrations, and can't be viewed by people who aren't registered, I'm going to copy and paste my initial impressions below.(Originally posted by me on the Saitek forums)

Does anyone know if it will be made available in an amphibious or float version? Here's a pic I found on the 'net: T =Thanks!-George

Just another shot in the dark from here. Since it seemed to happen after installing a scenery package, have you checked to see if there are any updates for that scenery, or if anyone else has encountered the same issue using the same scenery? If you disable the scenery, do your planes come back?Just throwing that out there as possible things to try, as I haven't encountered the issue myself. I hope you don't give up, and can get it sorted, as I was looking forward to your review of the GoFlight Annunciators.Sorry I can't be more helpful, but hoping you are able to get it all sorted.-George

No problem at all, Rick. Very happy to help, and glad we got it all up and running for you. :)-George

Looking forward to hearing how you make out. I know the SPAD drivers are supposed to be much better than the Saitek ones, so if those can be run over the network, then I'll be looking to finally making the switch over to the SPAD drivers. Especially now that I've got the radio panel, I would really like to adjust the sensitivity of the tuning knobs, which I'm under the impression, is possible with the SPAD drivers.Good luck, and hope you get it working! Can't wait to hear the results. :)-George

Rick, Check your messages here on avsim. :)-George

Hi Phil,I can confirm that I have 3 of my 4 Saitek panels running off a networked machine, but that is using the Saitek drivers (which use SimConnect). I don't know if Massimo's SPAD drivers will work across the network or not, as I believe his drivers interface with FSUIPC instead of SimConnect, and since I don't use FSUIPC or the SPAD drivers, I can't comment on if those two will work over the network the same way that the Saitek drivers do. I'm guessing the drivers themselves don't care, so I'd guess that the SPAD drivers *could* work (in theory) over the network, provided FSUIPC is capable of sending the data from one PC to another over the network without any additional software. Best bet is to check with the FSUIPC gurus, of which I am most certainly not, and don't want to send you on a wild goose chase if the SPAD/FSUIPC combination won't work in networked mode.For the record, the Radio, Switch, and Multi Panels, all which use the same, single executable file (saipanels.exe), works fine as long as SimConnect is installed on the networked machine and that there's a simconnect.cfg file with the connection information to your main FSX box in the 'My Documents' folder of the client pc. I am completely unable to get the BIP to work across the network, even with a 'false' fsx.exe running on the networked machine to try and convince it to keep running. So the BIP is connected to my main FSX box, and the rest of my Saitek panels are running over the network.Hope this information is helpful to you. :)-George

Rick, check your email. Just sent you another. :)

You do need to install the SDK from your Deluxe disk onto the client and server machines (you do not need to install FSX to the client, just the SDK), update them to match the service pack you're running for FSX (ie: if using FSX SP1, then only install the SDK updates to SP1a, if using SP2 or Acceleration, then you need to update the SDK to SP2 as well), then run the simconnect installer (simconnect.msi, I believe it also resides in the 'lib' folder.) Remember that both machines need to be running the same SDK version to ensure they're both using the same version of SimConnect.Since you're running XP32, the only difference in the path would be "Program Files (x86)" would just be "Program Files".SDK SP1A Download: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=24910e66-96b0-4543-9b4a-647b7e28f212SDK SP2 Download: http://www.microsoft.com/Products/Games/FSInsider/downloads/Pages/FSXSDK-SP2Update.aspxRemember that you have to install the SDK from your Deluxe disk first, then each update in order (if you're running FSX SP2 or Acceleration) onto each machine. Once the SDK's are installed and updated, run the simconnect installer (simconnect.msi) from the 'lib' folder I mentioned earlier, onto both machines.Hope this helps, and let me know how it all works out for you. :)-George

Hi Rick,The sample simconnect manifest file is located inC:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Core Utilities Kit\SimConnect SDK\lib(That's on a Win7 64 system, provided you installed the SDK to the default location.)Hope this helps. :)-George

No problem, Rick. Happy to help out any way I can. From my reading over on the Saitek forums, the FIP's should all be usable across the network as well. The BIP definitely does not, but I believe I may know why. If they used the code I supplied to them to make sure that the BIP properly closes out when FSX exits, then it would only work on a locally connected PC, as the fsx.exe will never appear in the networked pc's processes list, and as such, would shut down immediately (which is what it does). I plan on posting over on their forums later today, in the thread where I originally supplied the code, and suggest they look at changing the close-out procedure to look for the SimConnect connection (like the way gmap works.) I believe that's really the only thing preventing the BIP from working across the network at this time.I'm not sure if you're registered on the Saitek forums, and if you're not, apparently new registrations are closed, but in the actual FIP forum was an excellent set of instructions that helped me with the radio, switch, and multi-panels, though there wasn't any info about the manifest file, so it's probable that the FIP driver ships with a manifest file that lists the proper version of simconnect.Anyhow, here's the link, as well as a quote of the post (as you may not be able to view it directly if you aren't registered at the Saitek forums already.)Working SimConnect.XML & CFG Files for networking (on Saitek FIP forum)Here's the instructions from the first post in that thread, by Haleymon: Good luck, and let me know how it turns out, and if there's any other information I can provide.-George

Hi Rick,The Saipanels.exe.manifest file can be found in C:\Program Files (x86)\Saitek\Pro Flight Panels. With the latest driver from Saitek, the manifest file reads as follows: <?xml version='1.0' encoding='UTF-8' standalone='yes'?><assembly xmlns='urn:schemas-microsoft-com:asm.v1' manifestVersion='1.0'> <assemblyIdentity version="1.0.0.0" processorArchitecture="x86" name="Saitek Pro Flight Panels" type="win32" /> <description>Saitek Pro Flight Panels</description> <dependency> <dependentAssembly> <assemblyIdentity type='win32' name='Microsoft.FlightSimulator.SimConnect ' version='10.0.60905.0' processorArchitecture='x86' publicKeyToken='67c7c14424d61b5b' /> </dependentAssembly> </dependency> <dependency> <dependentAssembly> <assemblyIdentity type='win32' name='Microsoft.VC80.CRT' version='8.0.50727.42' processorArchitecture='x86' publicKeyToken='1fc8b3b9a1e18e3b' /> </dependentAssembly> </dependency></assembly> For some reason, it works perfectly fine locally, but when trying to run Saipanels.exe across the network, the side-by-side error comes up because the version information specified is incorrect. I went into my SimConnect folder and looked at the sample.exe.manifest file, and noticed the differences in versions. Anyhow, I backed up the original Saipanels.exe.manifest, then copied and pasted the sample file and renamed it Saipanels.exe.manifest. So now my Saipanels.exe.manifest file reads as follows: <?xml version='1.0' encoding='UTF-8' standalone='yes'?><assembly xmlns='urn:schemas-microsoft-com:asm.v1' manifestVersion='1.0'> <dependency> <dependentAssembly> <assemblyIdentity type='win32' name='Microsoft.FlightSimulator.SimConnect' version='10.0.61259.0' processorArchitecture='x86' publicKeyToken='67c7c14424d61b5b' /> </dependentAssembly> </dependency> <dependency> <dependentAssembly> <assemblyIdentity type='win32' name='Microsoft.VC80.CRT' version='8.0.50608.0' processorArchitecture='x86' publicKeyToken='1fc8b3b9a1e18e3b' /> </dependentAssembly> </dependency></assembly> Then you just need to drop a simconnect.cfg file into your My Documents folder, configured to connect to your primary machine, making sure that it matches the main machine's ip address, and the port that is specified in the SimConnect.xml file on the primary machine, and you should be good to go.Note that I don't have any of the FIP's, I only have the Multi Panel, Switch Panel, Radio Panel (just got that today!!) :), and the BIP. So far, I have NOT been able to get the BIP to work across the network, but all the other panels work flawlessly after multiple tests now (admittedly, they've been short hops of no more than 10 minutes, as my throttles aren't hooked up, and while I'm still building, I had to fly while kneeling lol).Hope this helps! :)-George

I can confirm that at least the stuff that runs off of SaiPanels.exe (Radio, Switch and Multi panels at least) will work on a networked machine using only SimConnect. I just set it up today actually. I have not gotten around to moving the BIP over there and trying that yet. You just need to install SimConnect onto the networked machine, then install the saitek drivers there (and remove the reference to saipanels.exe from your exe.xml file on your main host machine.) You then have to create a simconnect.cfg file to drop into your my documents folder. I did have an issue at first, where I kept getting a side-by-side error, but found that it was because the saipanels.exe.manifest file is looking for an older version of simconnect (I'm all updated to the latest version). Going into the simconnect folder and looking in the sample manifest file in there gave me the right versions to specify in the saipanels.exe.manifest, and it's all working beautifully. As far as actual FSX performance is concerned, I can't really comment on that yet, as I'm still working on building my sim-pit desk surface, so I haven't done any flying with the panels moved over to the networked machine. I only got them working and tested them out, and they all worked as expected in my preliminary tests.Hope this info is helpful to you in some small way. :)-George

Hi Grits,I've had no issues with the BIP and TrackIR, but I am running TrackIR 5. Have you tried the TrackIR 5 software to see if that fixes the issue? It's supposed to work just fine with TrackIR 4 hardware. One question about your workaround though, (sorry if this is obvious and you've done it already) if you're plugging in the BIP after starting FSX, are you manually launching the BIP's executable? The BIP's executable will get loaded by FSX's exe.xml file by default, but if the panel isn't connected, it typically unloads, so if you plug the panel back in after FSX, I'd guess you may need to launch the BIP's executable file manually. Just a thought in case you haven't tried this already.One other thing worth mentioning is that on Saitek's facebook page, I got a response from someone from Saitek who said a new BIP driver was in the works. That said, he told me that it would be out this past Friday, and as far as I can see, no new driver has been released yet, but it at least makes me hopeful that they may actually be working on improving the driver, and that there should be one coming soon. He definitely didn't commit to anything about the parking brakes light getting fixed though, but did say they were "looking into it as we speak". :\If you go to Saitek's facebook page, and find the post from May 20 that says "Excellent review of the Saitek Pro Flight B.I.P. on the Flight Simulator Network, written by Jessica Bannister-Pearce", you can see where the person posting on behalf of Saitek said the driver could be out last Friday.Best of luck in getting things sorted, and sorry I couldn't be more helpful.-George(Edit, just realized you asked this a couple of months ago. Very sorry for taking so long to respond, and I hope you've already got things working.) :)

Thanks Bjorn! Hoping to get some work done on the throttle quad box today, and I still need to decide what I'm going to do with the shelf on top of the panel. I don't know if I'm just going to give it a dark stain, or if I'll pick up some vinyl fabric and wrap it in that. But I can't get myself distracted... throttle quads first LOL! :)-George

Hi all, I've been working on a generic, desktop cockpit for a little while now, and I finally feel it's progressed enough that I thought I'd share some pics of it with my fellow simulator enthusiasts. :) Now it's no where near as good as some of the stuff I've seen built, I can admit that right off, but it was designed to have to fit into a corner, and to make my own life easier, I built the main pc components right into the desk itself, giving me easy access to the power button, front usb/audio, and my dvd drive. There's still some work to be done, but I finally feel it's far enough along to share what I've done. Hope you guys like it. :)My Desktop Cockpit Progress on my Facebook page - http://www.facebook.com/media/set/?set=a.211581122208761.58456.100000706246908&l=d1758d2dc5-George

I've never tried this, so I don't know if you'll get it working, and if you do, whether or not it will be an improvement. So I'm very curious about your results should you get it working. One thing I can think to suggest (though I have no idea if it would make any difference or not at all), is try putting the simconnect.xml file on the client pc into the 'my documents' (or 'documents') folder. I know that this is supposed to work with the Saitek panels (though I have not yet tried it myself), so it's a shot in the dark, but maybe that could get it working. Good luck, and I look forward to hearing your results should you get it working over the network. Source:http://www.saitekforum.com/showthread.php?t=18063Good luck!-George

Hi Erich,I use a CH Yoke and 2 Saitek throttle quadrants (as well as a few of their panels) and everything works fine for me.I can't comment on your second question, as I haven't used the Saitek yoke, so have no honest basis for comparison.Hope this helps a bit. :)-George

Thanks for the replies. :) I'll let it update to IE9 then. Thanks again, very appreciated. :)-George

Hi all,This morning, Windows Update informed me of an "Important" update that's available. The "important" update turns out to be Internet Explorer 9. I was wondering if anyone has been running IE9 already (even a beta version), and if there are any issues with it and FSX. I only ask because I had read (during an early beta of IE9) that some people were having problems with the kneeboard displaying after installing IE9, and I want to know if it's safe to install and doesn't break anything in FSX, or if I should just hide that update, ignore it, and just keep IE8 on my FSX box. Any insight is appreciated.Thanks!-George

Hi Mike,AFAIK, the BIP uses SimConnect to 'talk' to FSX. So it sounds like possibly a simconnect problem. Make sure your friend has simconnect installed and updated. Sorry if this doesn't help, just the only thing I could think of as to why it's not communicating with FSX.Good luck!-George