Pete Dowson

Okay. You have a problem with the part of FSX called SimConnect: It's very odd that you seem to have SP2 or Acceleration installed, or at least its SimConnect, but not the earlier update, SP1 or, by the looks of things, even a valid base version of this fundamental part. Have you installed FSX, then SP1, then SP2 or Acceleration? Or have you done something like installed FSX only, then tried installing a later SDK or SimConnect? I'm really not sure how these messes can arise, so I need to understand exactly what you've done. (This area is a real bag-of-worms Microsoft left us with when they killed further development). The FSUIPC Install log might help too -- it checks on the version of FSX.EXE, which must match the latest version of SimConnect you have installed. Another reason for this sort of horrible problem is a copy of SimConnect.dll wrongly placed, possibly in the FSX or FSX Modules folders, or in any of the Windows folders other than where they should be, in WinSxS. Regards Pete

[quote name="JSkorna" If FS undergoes either a position change or if the time gets changed by more than one minute' date=' FS does re-load the scenery.[/quote] Well, the textures at least. He should check whether he's enabled FSUIPC's clock sync option. I use that without any problems but only to keep the seconds synced, which it does "on the minute" (as you can only set zero seconds, no other values). So it never corrects for more than a minute in any case. Provided you have it sync'd to the minute at the start (as I do with FSRealTime), looking after only the seconds keeps it in sync forever -- provided of course you don't visit menus or use pause or time dilation! ;-) Okay. FSUIPC's clock sync with minutes sync'd too could do it, as can FSRealTime set to sync automagically. Don't know of anything else. Regards Pete

XP and Win7 use different default workgroup names. that is usually the problem. I don't know of anything using netbios. Did you try the WideFS user documentation at all? Please do read the section headed: Configure your Network IT IS IMPORTANT FOR ALL USERS TO READ AT LEAST PART OF THIS! The red emphasis at the top of that section is there for a reason. You'll find details there for either correcting the mismatched workgroup or working around it, as you wish. Regards Pete

Okay. Glad you resolved it! Pete

First check the FSX Modules folder. If there's an FSUIPC4.LOG file there then the problem will not be with the DLL.XML file. If you have Windows set to hide file types from you, you will need to change that option in order to identify files properly. To change that option you need to use Windows Explorer's Folder Options -- View, and uncheck "hide extensions ...". Whilst there also check "Show hidden files ..." since else you may not see the DLL.XML. If there is an FSUIPC4.LOG file, show its contents to me here -- load it in notepad or any editor and cut and paste it all into a message. If there isn't one, then it is going to be a DLL.XML problem. To help you find that I'll need to see the FSUIPC Install log, which you will find in the FSX Modules folder. Regards Pete

Sorry, I don't know how they've implemented their mouse actions. Have you tried adding different action interpretations (the ,number at the end as described in the FSUIPC documentation)? Maybe the different results are obtained by right-click, centre button, or mouse wheel operation? If not, then they must be decoding the actual mouse position within the defined rectangle corresponding to the routine at 16bf20. If so you'll certainly need to find another way to do what you want. Surely FSL are not repeating the mistakes of PMDG and not providing any way of mapping all of their controls to keys or buttons? Have you checked? Isn't there an SDK or anything for that aircraft? I would make inquiries of FSL if I were you. Regards Pete

You mean the FSUIPC options screen, from the menu? That's most definitely a video driver problem, a clash with the way FS drives the video in full screen mode. The FSUIPC options are a normal, standard everyday Windows dialogue, same as you see in any Windows program. They aren't normally used in full screen mode, but they should work perfectly, and do with most video cards and drivers -- when they don't it is always an incompatibility in the driver. There's nothing I can do about it because it happens in Windows or driver code, not in my code. In fact all FSUIPC has done is called a standard Windows API to ask it to draw the dialogue, which is a normal resource. Regards Pete

You have instability in FS9? Wow, that's not been heard of for many years. The stability of FS9 is why many stick to it and don't move on to FSX. A GTX480 is a bit wasted on FS9, isn't it? You don't need to worry about frame rates on FS9 unless you have a slow system -- and with a GTX 480 I wouldn't have thought you would have. After all the first priority is the fast processor. No, it really isn't, all that stuff is only for FSX. Pete

Your install log show everything is okay. Do you have a problem? Is there anyone who can translate into English for you? Regards Pete

Why did you just go out and purchase it without running it first? It operates in its main role without any money. Why did you want to buy it anyway? Did you download and read what you were getting first? Are you posting in such a manner just for sympathy? I'm a pensioner too and I've only been able to carry on development and support because some folks do buy my software. Else it would have stopped with FS2002! It isn't a problem with FSUIPC. You either have a corrupted DLL.XML file, probably caused by some other add-on messing it up, or your FSX installation has problems (often caused by incorrectly applied updates or attempts at re-installing). I can't tell without more information. If you want help then say so and I'll try to help, but if you truly believe you've simply wasted your money and that's that, then there's really no more I can say, is there? :-( Pete

Wow! Lucky you! I'm thinking of upgrading from my GTX 285. Don't do anything like that. The Installer runs with enough privileges in any case -- all installers do. You should certainly not need to set any compatibility modes whatsoever nor run FS in administrator modes. Maybe you've been trying too many weird settings. It will run well straightforwardly. But take care not to put all of the sliders in FSX full right. You can easily overload even with a fast system. Mine is a watercooled i7-750 overclocked to 4.5 GHz and using 2000 MHz overclocked memory, and even that won't run FSX flat out. Do NOT work on frame rates. If you allow FSX to gallop away with huge frame rates you are more likely to run into trouble. Frame rates aren't as important as smoothness of simulation. I limit mine to 30 fps -- using an external frame rate limiter, not FSX's internal one. There are a lot of improvements you can make to FSX graphics and performance, especially with an i7 system and a GTX285 or 480 video card. Take a look at some of the threads on ASVSIM's FSX forum, especially those by Jesus Bojote. There's a pinned essay by him near or at the top which is very educational. Regards Pete

You've got a corrupted registry by the look of it. See: That's the parameter which tells everything (not just FSUIPC) where FSX is, but it contains this path: Seems like some other installer you've used has messed the registry entries up. FSUIPC4's installer can fix it for you. Didn't you follow the instructions to locate FSX.EXE as it would surely have told you? Another way is to check the Announcements in this Forum. In particular see the one entitled "Fix for FS installation registry problems" right at the top. Regards Pete

If any program changed the position at all, you would surely see it on screen! You would suddenly be in a different place! I don't know of any tool you could be using during normal flight which would do such a thing. Having the weather refreshing every 3-4 minutes is daft. The new download could try to supplant the previous one even before it is fully established! Use 15 or 30 minutes at shortest. The cloud popping phenomenon is mostly to do with graphics settings. There's a lot of things you can do about that -- see the AVSIM FSX Forums for lots of hints on FSX graphics improvements. Pete

You don't buy a specific version. 3.96 is well out of date -- the oldest supported version is 3.98. Please update. That was fixed a while back. Please always make sure you are up to date before asking for support. Review the Announcements at the top of this Forum from time to time. You will find them very helpful in these matters, especially the one on "Updates". Regards Pete

Hmmm. I'm glad, but it's rather strange that 4.60a didn't. I'll never know why because I'm not reverting the source now. Too many other things addedyet to be documented. Regards Pete

Well, it should work in 4.60a too as nothing in that area has been changed since then. Interim updates (DLL only) are almost always available in the Updates announcement above. But I have an even later one almost ready to upload. Try that first (this is the exact version I just tested with): http://fsuipc.simflight.com/beta/FSUIPC4609b.zip Well here as soon as you've loaded FSX and are "ready to fly", the INI file has been changed so all Buttons and Axis references have the letters you assigned. That's done for the current aircraft at the exact same time as the [JoyNames] section is updated with the numerical equivalents, which did happen in your case as you showed. This won't occur for any control devices not currently attached or seen, simply because it isn't able to associate the names/GUIDs unless the devices are readable. You can also simply go into the FSUIPC options, Axes or Buttons tabs and move an axis or press a button and see the letters used rather than numbers. Regards Pete

FSUIPC automatically changes those Buttons and Axis sections for you, but only when the sections are used (i.e. loaded into memory). Is it possible that you also have some aircraft-specific Axis and Button assignments and these are assigned to the aircraft loaded by default? Aircraft-specific or Profile sections will be automatically updated next time they are used -- i.e. when the aircraft assigned to them are loaded. If this is not the case, I need to know more, please. I just checked here, and it still works fine in the latest updates of FSUIPC3 and 4 (3.984 and 4.604), so, what version are you using? If not these could you try updating. If you still get the problem I will have to get you to do some extra logging so I can determine why it doesn't work on your system. Regards Pete

Why 6D00? You may clash with other uses. Please stick to the allocated User area -- 66C0 to 66FF. Straight ahead to where? Do you know how to send data to your hardware? If it is on a COM serial port you can use Lua to write a driver for it -- the Lua implementation in the current version of FSUIPC includes a serial port library. But you will need to know all about the protocols of your hardware and drive every aspect of it. Otherwise, if you have a driver which can read FSUIPC offsets, what is wrong with using it? What is any more "direct" without a great deal of extra work for you? Pete

I use Windows 7 64-bit on three separate systems with FSX and many add-ons, and I would say it is the most stable setup I've ever had for FS. If your experience is the opposite I can only think there's some problems with your installation, drivers or hardware. Regards Pete

Unless you use a third party instrumentation system such as Project Magenta, Sim-Avionics or Flight Deck software, there's no way to do that -- except i think there's some video driver that sends images over networks. I don't remember the name and I'm not sure how efficient that can be. FS's gauges are 100% dependent on graphics code inside FS. They don't have any graphics capabilities which can be transposed elsewhere. PM and the others provide only instrumentation and systems programming (A/P, Overhead and all sorts of subsystems), not the aircraft. you choose your own aircraft model. There's no suitable external instrumentation of systems programs which can properly handle "all the planes". That's not a realistic target. You are best off sticking to a single PC implementation. I've known of single PCs using 6 screens, two sets of three via two Matrox Triple-Heads To Go. Top three as one scenery window, the other three with undocked instruments. That can work quite well. the only 3D window is the wide top one over 3 screens, so there's no big impact on performance. Regards Pete Pete

The parking brake should be disengaged using the "." key or a control assigned to operate it. There is a facility in FSUIPC to auto-disengage parking brakes when you pressboth toe brakes to a certain (adjustable) pressure, but you have to assign in FSUIPC to use that, and it is only in a very recent version of FSUIPC. Reverse your toe brake axes as I suggested and calibrate them with a good null zone near the off position. Assign some button for parking brakes. Pete

You probably have the brakes reversed. See if the Brake go off when you press both toe brakes fully. If so, reverse them -- wherever you've assigned them (FS or FSUIPC) there will be a REV option. Pete

You can see if writing to it does anything. It may not. Some add-on L:vars are simply memories of a switch setting and changing them may change the switch without activating the needed system change. But try, by all means. You could either do it in Lua, using the facility to Write to L:Vars, or create L:var macros. See the Macros chapter in the FSUIPC Advanced User's guide -- the L:Var section is actually listed in the contents page for that document. Pete

Erhold on. Where does this "instrument panel" come from? WideFS is NOT FS. You cannot extract gauges from FS and magically place them into WideFS's Window. All FS gauges need most of FS supporting them to work. If you mean add-on gauge-supplying programs, like Project Magenta, then obviously they need the normal Wideclient installation, as I just explained, and that can't be run on the same PC as FS. The touch-sensitive screens I'm talking about are used for an array of rectangular buttons, colour codes, and several pages of them. I think you should download and read through the documentation for WideFS before you spend any money! If you would be happy with an overhead which is only an array of rectangular button areas, and similarly for an FMS, with no displays and so on, fine. But it certainly now sounds like you are seriously misunderstanding something here. Regards Pete

Yes. Set the "ClassInstance" parameter in the Wideclient.INI file to something like 1. On one of my Client PCs I have three copies of WideClient running -- one is 'normal', accepting applications and talking to FS normally, the other two are ClassInstance's 1 and 2 supporting two separate 7" touch screens, one for pilot the other co-pilot positions. Such an install of WideClient cannot support normal FSUIPC applications, of course, because this parameter changes the FS window name which such programs look for. They will still try to attach directly to FS itself or a normal install of WideClient. Regards Pete