Ian P

I just had a similar problem in that I couldn't get anything on this notebook to connect to FSX through Simconnect, although WideFS was working perfectly. As you found, reinstalling from the installers after taking control and deleting didn't work regardless of who I gave control of the folders to, but I was able to repair the Simconnect installation on this (Vista 32) notebook by using a copy of each version of Simconnect taken from my (Windows 7 64) desktop with FSX on it. I deleted the files as described above, then copied the files from the W7 box and just pasted them into the appropriate directories on here. After a restart, everything worked fine. If you can get hold of a second PC with the appropriate files on, it might be worth a go as a last resort before reinstall? Ian P.

The Wilco 737, to be fair, is an FS8 aircraft that was updated for FS9 and again for FSX compatibility. The majority of the panel and flight functions can be controlled using the keyboard and a lot of it also supports default controls. VRInsight, for instance, control the 737PIC aircraft with their devices using keypress emulation. Much of the overhead, however, is not assignable to keys - primarily because it is not necessary for flight and unlike with the LDS767, for example, does nothing to affect the sim at all. It's clickable and makes lights flash or dials move, but that's all for the most part. Have you tried the default keys, however, for generators, engine starters, etcetera? I was surprised how many work on one of the Wilco models I tried. That wasn't the 737 (in fact I can't remember which one it was... the original ERJ maybe?) but it's still worth trying. Ian P.

Hi, The reason there are two independent licenses available for FSUIPC and WideFS is that they do different things. You can use the unregistered version of FSUIPC with a registered WideFS, but the inverse will not work - WideFS must be registered to use it. However you can use FSUIPC "stand alone" without WideFS registered. If you want to change the weather settings (one of the primary reasons I licensed FSUIPC was for the wind smoothing at high altitude), then you will need a licensed version of FSUIPC. In order to "offload" things onto the second PC - something else I do - then you will need to license WideFS. This license is handled on the FSX PC, the same as FSUIPC is, and clients (which do not need a license to install) can then connect to the licensed WideFS server. However it is worth checking the software you are hoping to connect remotely does, in fact, use WideFS. A couple of things I have looked at recently - ActiveSky X and Squawkbox, if I remember correctly - now connect using Simconnect rather than WideFS. Other things, such as for instance FSCommander, do require WideFS/Wideclient to communicate from a remote PC. Therefore, the answer to your question is that in order to use WideFS and FSUIPC's weather modifications, you will need a single FSUIPC license and, if necessary, a single WideFS license. You can, as the text you have quoted states, then put Wideclient on one or more client machine(s). I understand - although Peter will correct me if I am wrong - that both FSUIPC and WideFS licenses are only available through simMarket. The fact that Pete only includes links to sM on the page at Schiratti.com tends to support this. Therefore I believe that anywhere else offering to sell you a license would not be a legal source. Hope that helps? Best regards, Ian P.

There were a whole raft of problems regarding "lost" activations on systems that had previously been working fine, but it was a long time ago now and I can't remember the exact solution. I do seem to remember that there was a thread on the Microsoft TechNet Knowledge Base about it. If I get chance later today, I'll have a look and see if I can find it. If not, it might be worth searching the forums at places like www.avsim.com and www.sim-outhouse.com as I know it was discussed at both, back when a lot of people were experiencing the problem. Ian P.

The Aerosoft AirbusX gauges were encoded using XML, so it should work the same as anything else, regarding LUA variables. Unfortunately, every time I load it right now, it crashes FSX to desktop, so I can't confirm this at the moment. Ian P.

Hi Ken, I don't think that's an AICarriers message - it's certainly not one I've seen before and as I said earlier, I've broken AICarriers fairly regularly! However it is fairly easy to work out whether any of WinchX, CumulusX or AICarriers are creating that message - all of them place a file in your FSX "modules" directory (the same place you'll find FSUIPC). Can you move CumulusX.dll and WinchX.dll out, temporarily, to another location (such as your desktop?), then run FSX and see if the message goes away? I've just looked at the user manual for both and it appears that neither require FSUIPC to function directly - it's not listed in the requirements for either, at least. From this, I would presume they both use Simconnect - which would tie in with Pete's suggestion that this is primarily a Simconnect issue, but doesn't explain that error message. I do wish people writing dialogue boxes for Windows would put the name of their product in the title bar and the message in the window, rather than the message in the title bar and just buttons in the window. It really does make fault finding a lot more difficult. :angry: Ian P.

It apparently doesn't use FSUIPC at all any more, so whether the version I fixed was pre-2r2, or whether it was unrelated and just happened to be part of what I did, I'm not sure. From the AICarriers2r2 manual: Which does make it look like Ken's problem may well be Simconnect related, as you say. Ian P.

OK. Not sure why putting the up-to-date FSUIPC module (at the time!) back into \modules fixed that problem then... I'll shut up and go away. Possibly after reading the AICarriers documentation again. ;) Ian P.

AICarriers is an external module that injects aircraft carriers into the sim and controls them, using pop-up dialogue boxes, Pete. It uses FSUIPC as an interface to inject the objects as AI, I believe? I know that I had a problem with it a while ago that was solved by reinstalling a newer version of FSUIPC after another tool/add-on had installed an older version of the dll. That was a long time ago, though, and I can't remember specifics. There are internal (dll) and external (exe) versions of it. Whether both use FSUIPC to interface I don't know. Ian P.

If you have an FSUIPC4 license key, it is valid for all versions of FSUPIC4.xx - as Pete is currently at 4.6 (4.651, a quick check in downloads tells me, at the time of writing), your current license is still valid. You just need to ensure that you use the same registration details as you did at the time of purchase when running the installer. Ian P.

I'm wondering if it might be a hardware problem? Pete - if a device momentarily lost connection, the same as my old joystick used to do as the USB connection failed, could that be detected as a new device each time? Ian P.

How are you calibrating your levers? I only ask because I just went through something similar, re-assigning all my levers on three Saitek quads. The critical thing is where you are assigning your central zones on the levers. If you calibrate them after assigning and, once calibrated, move the levers from one extreme to the other, watch the "Output" box next to each and check that it does, indeed, smoothly move from one extreme to the other. In order to make all the levers I assigned (2 throttle, 2 pitch, 2 mixture, 1 gear done using arcs, 1 flaps and 1 spoilers) work as expected, some of them needed the central "deadzone" settings at the maximum, some at the minimum and some at zero, in the middle of the arc. I can't check which were which at the moment, but it's worth looking into. The way I assign reverse, however, is rather different to yours (it's called "cheating", I think...) - I assign the "reverse detent" switch on both levers 1 and 2 to "Throttle x dec", where x is 1 or 2 as appropriate, and tick repeat while held. I then set button release to be "Throttle x cut", thus as soon as I move the levers back to the idle detent, the engines go back to idle. That works fine for me, but it does tend to mean all or nothing on reverse thrust. Ian P.

If that is the case (it's still worth scanning with Malwarebytes or something to make sure) then the problem is that your DNS (Domain Naming Service) tables are wrong. These are usually supplied automatically by your ISP, but you can change them in your computer's network settings to use a different service, which might actually work correctly. I've never used it, but one I've seen mentioned a lot is OpenDNS. A quick Google search has turned up this rather useful page, which explains exactly how to change you change it: http://use.opendns.com/ Might be worth trying? Cheers, Ian P.

That does sound like malware of some description, as Pete says. What happens if you open a command window (hold down the windows key next to left Alt and press r) and type "tracert www.simmarket.com"? Ian P.

You'll often find that turboprops (I'm not sure about the Caravan specifically) will taxi with the engines in a "ground" position on the condition lever, which limits the power produced and thus the forward pull of the prop. By pulling the condition lever back to a more suitable position, you will have much finer control over taxi speed, as moving the throttle out of the "idle" position will no longer just cause the aircraft to speed off along the taxiway. Ian P.

Moved to FSUIPC Support forum. Ian P.

I'm sorry, your question still doesn't make sense! :unsure: AES, to my knowledge, is Airport Enhancement Services - a package that adds "life" to add-on airports and has nothing to do with the weather. According to the manual for FS Captain which I just looked at on their website; (Emphasis mine) In other words, the weather that you see in FS Captain is downloaded from the Jeppesen website - the same as FS does if you ask for "real weather" - and it does not come from a source inside the simulator at all. FSUIPC does not allow any changes to where FS Captain gets its weather from - it is not a program designed to do that - so the answer to your question is "no". However, as FSCaptain's "Get Weather" button downloads it from the same source that FSX uses itself, you are already using the FSX weather engine, effectively, if you use FSCaptain's internal facility. Ian P.

Hello, You're actually not using the latest version of FSUIPC - by quite a way. :) The first thing to try is downloading and installing version 4.6 of FSUIPC from here: http://www.schiratti.com/dowson - your registration details will work fine with this version, they're valid for all 4.x releases. You'll probably also want to download the latest update to that, 4.645, which is available from the downloads section of this support forum, here: http://forum.simflight.com/topic/66139-updated-modules-19th-december-2010/ See if that helps and let us know how you get on, please? Cheers, Ian P.

To be honest, you would be far better asking for support on the VRS Hornet from the VRS Support Forum at their website, as most people here won't have the add-on to be able to assist you! ;) However, presuming that this is just a simple control assignments question, if you go to Settings - Controls - Buttons/Keys inside FSX, you will see a list of all the internal functions available to FSX. Unless you have specifically assigned them using FSUIPC, in which case I'd hope you'd know what functions you were looking for anyway, then they will be assigned through this page. Simply scroll down to Cowl flaps (close incrementally) and Cowl flaps (open incrementally), select the line and press the "Delete Key Assignment" button below the middle column to remove the key mapping. HOWEVER... remember that if you want to use the cowl flap key controls in any other aircraft, you will need to reassign them through this interface. The default controls are CTRL+SHIFT+C for close incrementally and CTRL-SHIFT+V for open incrementally. Cheers, Ian P.

Thanks. I'm sorry I can't help with your problem - I'm a fairly amateur FSUIPC user as they go (although I think I'm about to get sucked in by something I need to try and do...) but hopefully someone with more knowledge than I, or Pete himself, will be able to help you shortly. All the best, Ian P.

Hi Steve, Pete will only ask you this anyway, but rather that saying "latest version" of FSUIPC, can you give an exact version number, please? I know that the module has been updated several times in the very recent past, as people have been discussing features and problems, so what was "latest" yesterday may well not be today! :) Cheers, Ian P.

The "buy now" key only adds the product to your basket. If you look at the top right corner of the screen, you will see the contents of your shopping cart and the "checkout" button. You need to click that to begin the payment process. Ian P.

This isn't helped by the fact that PMDG make civilian, not military, aircraft and thus have never released an F/A-18E. Presumably the original poster is referring to the VRS SuperBug, but even then that specifies that you do not need to register FSUIPC in order for the aircraft to function - again, that's in the documentation. Ian P.

It's a silly question, but you'd be amazed how many people it catches out. Are you ensuring that the details you are typing into the registration screen exactly match those used for the purchase (e.g. no extra spaces, capitalisation, etc.)? It's worth using copy and paste if you can. Ian P.

Silly question, but FS handles fuel imbalance appallingly. What happens if you burn fuel from the other wing tank first? We've had this problem with a number of aircraft that have fuel tanks in the wings that the imbalance makes them roll, no matter how much trim is applied and no matter how small the imbalance is - although the amount of roll depends on the amount of difference between tank contents. Ian P.