quantumleap

I agree that it does look like it is related to checking of code signing based on the packet analysis. As a recent Windows Update revoked a number of certificates, I am wondering if at that time, it cleared them all out so they are slowly being re-added. Have checked and the digital signature for the FSUIPC DLL is "OK". Thanks, Jeff

Pete, Thanks for the information. Not sure what is happening then (maybe I'll snoop the packets and see what is being transmitted). In my tests I had disabled all other entries in the dll.xml apart from FSUIPC and removed all lines in the [Trusted] section of the FSX.cfg to make sure nothing else was running which used FSUIPC. This was with version 4.80. I noticed that a newer update was available and installed it. Interestingly the installer for 4.827 also made a similar network request to one of the previously listed sites (Cybertrust Ubizen in Belgium). I then updated the FSUIPC.dll further to 4.839b. With this newer version, I no longer get the network requests. Regards, Jeff

I have a firewall on my system which alerts me to outgoing network requests. When FSUIPC is enabled in the FSX dll.xml, when I start FSX it flags that it is attempting to connect to four sites in Europe (Verizon Business in Belgium, Cybertrust Ubizen in Belgium, CloudFlare EU and Telecom Italia Mobile) and one in the US (CloudFlare Inc). Why is this? If FSUIPC is disabled in the FSX dll.xml these network requests do not happen. I do not get this notification for any other software on my system, just FSUIPC. Regards, Jeff

If you are using the VB 2008 Express version you should definitely be using the VB.Net example code rather than trying to get the old VB6 examples running. Like Pete notes, if you have not already done so, I'd actually highly recommend that you look at Phenty's FSUIPC Client DLL for .Net (viewtopic.php?f=54&t=53255) which makes things even simpler. Jeff

I use the latest versions of FSUIPC4 and WideClient on my Vista 64 bit systems with no issues at all. Jeff

Usually a "Stopped Responding" means that it is very busy processing (or stuck in a loop) or it is sat waiting to talk to the network or some driver and has had no response yet. Personally, if I was seeing a similar issue in code I had written, I would install the VB development environment on the Vista machine and run it under the debugger. My gut feeling is that it is still most likely an issue with your SimConnect installation on the Vista machine. Have you guaranteed that SimConnect is working on your Vista machine to remotely talk to your FSX machine? Another thing, when you compile the app on your Windows XP machine, are you setting the build configuration for the platform to be an "x86" app or leaving it at the default "Any CPU"? If left at "Any Cpu" when run on 64-bit Vista it will look for 64-bit versions of SimConnect libraries and there are not any available. Jeff

There should be no differences in how you write the VB code for XP or Vista. I develop on my XP system, and run the same built app on it and my Vista machine all the time. I suspect a simple reason. Do you have SimConnect installed on the Vista machine? If it isn't, then the first time you try to actually use it you'll get a crash because the imported reference to SimConnect in your VB code cannot find it. Note that when you get the "your app has stopped working" dialog in Vista, there is a control at the bottom which allows you to view the problem details. In the case of SimConnect not being installed one of the problem signature lines will say something like System.IO.FileNotFoundException. Jeff

A few things to start. Brake values are not normally just on/off but a range of braking from none through to 100% (as would be done if they were handled by rudder pedals and not switches). Buttons on the yoke can effectively send a signal just on activation or when held. The latter is normally done by having the signal sent at a repeat interval (set via the FSX Control Settings dialog buttons/keys section). From what you describe it sounds as if your assigned brake buttons are being seen just on activation with no repeat. You therefore need to look to set the buttons to repeat so check you buttons/keys section in the FSX Control Settings dialog. FSUIPC will not normally intercept buttons unless you have progam them to do so. You'll need to check that you have not done so via the 'Buttons + Switches' tab or you have changed the calibration of the left/right brakes under 'Joystick Calibration'. Jeff

You don't show the code or describe the method by which you are writing the data into the mySQL database. Any chance that it is accidently being written into it as a string? Jeff

You say the value isn't what you want, but is it correct? While you do not say where the aircraft actually is, I would guess that you are trying your code with the default FSX starting flight near Friday Harbor which does in fact have a longitude near -123.029740092334 in decimal degrees notation which is what your code is written to return. If you want it to appear in another format like degrees minutes seconds (e.g. W123 1' 47'') or degrees and decimal minutes e.g. (W123 1.784') you are going to have to do the conversion yourself. Jeff

WideView and FSUIPC/WideFS are completely different programs written by completely different people doing completely different things. I do not think that they are available on disk, but as you obviously have some access to the Internet, even if your flightsim PCs do not, they are such small packages that you could download them on the machine you do have on the Internet and then copy them via something like a USB thumb-drive or burn a CD yourself. To find out what FSUIPC and WideFS do, download them from http://www.schiratti.com/dowson.html and read through the very complete manuals included in them. A full FAQ on what WideView does is available at http://www.wideview.it/faq.htm Jeff

If you installed FSX in the default location it will be something like Program Files->Microsoft Games->Microsoft Flight Simulator X->Modules->FSUIPC4 Install.log Jeff

Sort of... It is now officially available in a "release to manufacturing" version to those who have a valid MSDN subscription and/or TechNet Plus subscription. Details can be found at http://technet.microsoft.com/en-us/wind38089.aspx Jeff

As a data point, I have no issues installing, configuring and running 4.25 (or previous versions) under Vista Home Premium 64 bit. Jeff

Thanks Pete! You learn something every day :D Have a great Christmas and New Year. Jeff