Pete Dowson

Yes, I know. But I don't understand why, that's why I asked why you did it! Don't try "pasting a file", paste the TEXT inside the file. You have to open it in a text editor first -- like Norepad. Try double clicking on the file to open it. Sorry, I just feel frustrated not being able to explain complete fundamentals. I really have no idea how anyone can even use FS without knowing al ittle about what files are and how to view them. Sorry. It is my failing. Maybe someone else who can think as a pure beginner can help. I've been involved with computers since 1963 and cannot work out how to explain things which are too obvious to me. It isn't your fault, but mine. As the User Guide tells you, just delete (or rename) the program, FSUIPC4.DLL. There's nothing else running. That's it, the whole FSUIPC. Pete

Paste "icons"? "cdm"? Sorry, you've lost me. To paste text into a message you select it from the editor you are viewing it in, select "copy" then place your mouse cursor in the message and select "paste". These are normal editing options. Have you never used an editor? Try right clicking your mouse. In the directory listing you've inexplicably entered by long-hand into your last message, these are the files I need to see: FSUIPC4 Install Text 5KB FSUIPC4 Text Doc 2KB You have Windows set to hide the real names from you. In fact "FSUIPC4 Install" is "FSUIPC4 Install.log" and "FSUIPC4" is "FSUIPC4.LOG". They are both normal text files which wil open in notepad or your selected editor if you double click them. But why did you post it? It is of no interest or relevance here. Regards Pete

Okay. That's good. Now I just need to see the Log files. I'm not sure why you appeared to post your SimMarket receipt details? Pete

The SimMarket page, which is where you pay for the Key, only gives a link to the download site. The version downloaded is updated from time to time, though Mr. Schiratti doesn't update the text very often. To check the version you are using, look at the Options in FSX, or look at the first line of the Log in the FSX Modules folder, or simply right-click on the FSUIPC4.DLL itself and look at the version number in its Properies. I assume you mean Add-Ons menu, FSUIPC? In that case you should know the version number, as it is displayed on the first tab. The FSX modules folder is the Modules folder inside your FSX installation. Assuming you let FSX install itself where it wanted to go, FSX will be in the Mcrosoft Games folder in Program Files. The first thing any FS user needs to know is where his FS is! If it wasn't Schiratti.com you went to first off, where on Earth was it? There's only the two places - Schiratti and, for latest updates, here in the Download Links subforum as I said. I'm afraid I cannot help further without information, and the best will be in the Log files I mentioned. Regards Pete

Hmmm. No real explanation for it then. I've no idea what can "malfunction" in RC to do what you say, and agreement between Shift+Z altitude and the altimeter when flying Flight Levels is certainly only correct when the QNH is 1013 (29.92"). Weird. Glad you sorted it though, but that's a rather drastic step to take -- it would cost me several days to get FSX back to where I had it! Regards Pete

Never mind. If it's important he'll be back. Best Regards Pete

Well, yes, it is extreme, but what a splendit result! Thanks for letting us know! Regards Pete

You are using an out of date version of FSUIPC. That was fixed a few releases ago shortly after it was first reported to me. The current version, 4.758 (installer), works fine. There's also a later update, 4,761, available in the Download Links subforum. I'm very surprised the ASE folks didn't tell you this on their forum. It only occurs when you are NOT using FSUIPC's wind smoothing, which option is the main reason most folks install and register FSUIPC for. That's why it went unnoticed for so long. Regards Pete

You seem to have tacked a quoted email (?) onto a Support Forum thread from last year dealing with a different subject. I've no idea what it is you mean by all that. Please stop and try to expain what your problem is, because the above makes no sense I'm afraid. What is the Version number of the FSUIPC4 you have? If it isn't a recent one (4.758 is the latest Installer and he latest update is 4.761 -- both available from the Download Links subforum). If you have a problem instlaling it or running it I need to see the log files. You will find an Install log and an FSUIPC4 log in the FSX Modules folder. Paste them into a message here along with a clear explanation of what your problem is. Close FSX down first. What does "2068" mean in this context? And, incidentally, why did you purchase FSUIPC -- what was your intended use when you purchased it? Why didn't you install it and check it was what you wanted first? Regards Pete

Actually you are running FSUIPC 4.703 which is about 10 m0nths old -- current is 4.758 or 4.761. But it wouldn't make any difference in this case. The fact that you are connecting successfully and using the connection certainly indicates that WideFS is working fine.The logs you supplied also confirm this. WideFS does not discriminate between its client applications. I suspect that both FSC and PlanG not only need to talk to FS via WideFS and FSUIPC, but also need access to some of the FS folders in order to obtasin information about airports, scenery and so forth. You'll need to refer to their documentation to find out how to set file sharing up adequately for them to work. WideFs is merely a network extension of the FSUIPC interface, it is not a filesharing system. You have to rely on Windows' file sharing facilities and correct netowrk paths. Please supply a complete FSUIPC4 log file too, with FSX closed beforehand, with any further queries. Regards Pete

Not a tutorial as such, but the logging and Lua plug-in I mentioned will find them for you, then putting together the macros you need is only a matter of following a format. There are plenty of other aircraft examples which should help you over in the User Contributions subform. Regards Pete ]

The mouse macro facility depends upon the aircraft gauges being written in C/C++ using the Microsoft gauge SDK for such. I don't know if that aircraft is old or new (or for FS9 or FSX?) but if it is quite a recent one then it is quite likely that it was not written in such a way and is therefore not amenable to mouse macro treatment. The alternative for many recent aircraft is the use of local gauge variables (L:Vars). There is an FSUIPC control you can assign to a button or key to list those for you, and a Lua plug-in provided amongst the examples to monitor them. Using L:Var macros is often a more successful way of finding a way of controlling the switches on gauges., especially those written using XML. But also do not overlook the standard built-in FS controls, which for standard types of gauges are still most often used. Just enable FSUIPC's event lgging, then operate the controls with the mouse and see what FS control is logged for it, if any. Regards Pete

Then that is very likely the problem. Unless, by sheer coincidence, the actual QNH is 1013.2, the Flight Level you should be flying is NOT the same as the true altitude. You need to set your altimeter to 1013.2 (29.92"), usually by pressing "STD" on the EFIS control panel when told to fly Flight Levels. This always needs doing when flying Flight Levels. Unfortunately very many American flight-simmers get so used to flying in the North American continent, where the Flight Levels begin at 18000', and FS assumes this when you press 'B', that they do not understand what goes wrong when flying elsewhere. I'm not saying that you are one such, but that does actually look like what is occurring in this case. You should then not be reading the same on your Altimeter as in the Shift+Z readout -- unless, of course, the QNH just happens to be 1013, which, from what you say, sounds not to be the case! Regards Pete

By "wrong" what do you mean? What are you comparing it with? Press Shift+Z to get your true altitude displayed by FSX at the top of the screen. That will be the "true" altitude, not necessarily the one shown on your altimeter. Were you actually instructed to fly an altitude, or a flight level? What is the current barometric pressure (QNH) and what is your altimeter set to? And where are you flying -- what is the local Transition Altitude? Without answers to these questions I'm afraid there's no way to answer your questions. No, and it won't make a difference in any case. The altitude cones direct from SimConnect. FSUIPC is only the interface and that's not changed in any relevant respect. Answer the questions above, then maybe things will be clearer. Oh, one other thing. Check that you haven't got FSX set to use Metres instead of Feet for altitudes. RC should be detecting this and therefore copied, but I've not checked that this is so. Regards Pete

This is all probably down to the fact that the Lua script is a script interpreted by an interpreter running in a thread which is being restricted in its processor usage so as not to affect FS unduly.. If you really do want consistency I think you would need to write a driver in a programming language and compile it as a separate process. You are probably just expecting too much from a general-purpose plug-in script system. I don't see why that can possibly matter, provided you can adjust values at a reasonably speed. You are trying to run a script which probably takes several milliseconds in any case to run at 100 times per second, and you are wanting FS to keep up with that too. If your FS frame rate is of the order of 200 fps then this might well be achievable -- provided you limited it to less to give enough time to other threads. If it is only achieving 20-40 then you are probably asking the impossible. I have several encoders being interpreted by Lua plug-ins and have no problem using them to make adjustments at normal rates, but I limit the frame rate on FS so that other threads and processes get enogh time. In the end, you judge by the readouts you are getting, not by counting the "clicks" from the encoder. Yes, of course, but you lose the assignment flexibility. And at 100 increments per second you'd probably over-control because the display would not keep up. A proper driver will always be more efficient than an interpreted plug-in. The plug-in system is merely a way of adding minor facilities to a system which would otherwise necessitate me continuously adding things to fSUIPC. It is designed for flexibility and to avoid FSUIPC getting more complicated all the time.. Yes, it seems so. Regards Pete

What was the hidden IP address? What is your Server's IP address? What did you end up putting into the WideClient.INI file as a result of all this research? I was advising you what to do based on partial information. If, as I believe from the partial IP address you provided, your router is providing the wrong IP address, then the way around it is EITHER to recongifure the router so it works correctly OR, probably easier, just tell WideClient the server IP address and Protocol you want to use. There's only about one or two paragraphs to read for that, and i pointed you exactly to them. Well, it's your choice, but if I were you I'd consider providing a little more information, and perhaps rather than reading upteen irrelevant things just following the advice provided? Pete

1. I moved your support question to the Support Forum. You posted in the FAQ subforum where it would have gone unnoticed for a while! 2. We have not yet got to March 2012, so I think maybe the date on your PC is wrong? Try setting it correctly and maybe it may register? 3. If not, then you are making an error entering one or more of the three fields. All three parts much be exactly correct -- name, email and Key. Use cut and paste. 4. The current installer is for 4.758, not 4.751. Regards Pete

I am sure this is a Saitek driver installation problem which can be resolved by a Registry hack, but i'm afraid I don't know the details and in any case I cannot support Saitek. They must support their own devices. I expect the solution is posted someplace on the Saitek support forum as it has been reported several times. Regards Pete

Waiting for a connection just means what it says, and not finding INITIAL.LUA is normal unless you really do have a plug-in to run as soon as WideClient is started, which is not usual. file sharing is completely irrelevant for WideFS connections as it doesn't use any shared files, it just talks over the working LAN. Why have you obliterated the most important part, the IP address? But a LAN IPaddress is local to your LAN, no use to anyone else at all. And most folks have the same set in any case. Is the obliterated address that of your Server? I don't think it is -- it is probably the address of your ISP. I could have checked it for you if you hadn't obliterated it. Here's an extract from a document talking about LAN addresses: As you see, NONE of these begin "115". I really don't think your Server has an IP address beginning 115, do you? The problem of routers not providing your Server address but that of your ISP has been experienced by a number of folks and is discussed in a well perused FAQ subforum thread entitled: WideFS Server names translating into incorrect IP addresses You could also have read the part of the WideFS user guide where it explains how to set your own IP address and protocol in the Wideclient INI file. It's in the section about configuring your network, and has a red emboldened subtitle imploring you to read it! Regards Pete

65588 is "BRAKES", and is the control used by the default '.' key. The parameter is irrelevant, it doesn't use one, not being an axis control. FSUIPC sends a BRAKES control when toe brakes are pressed sufficiently to put them over the threshold for Parking Brake release -- otherwise the brake axes do not have this effect. The threshold is an INI parameter (BrakeReleaseThreshold) defaulting to 75%, but it can be 0 to turn it off. However, this action is certainly not dependent on how fast you press, nor is it sent more than once so even if BRAKES did have an adverse effect it would immediately be cancelled out by the very next brake axis value. By "release" do you mean the brakes come off completely, ignoring the brake axes values? If so, why do you think brakes would release when a Brakes control is sent? If it only occurs with certain add-ons (unnamed for some odd reason), then you need to investigate those add-ons, don't you? I don't see how a BRAKES control will affect things one way or another. But if you think it is because of FSUIPC's action described above, just try with the threshold set to 0. Regards Pete

I'm not familiar with such technicalities, sorry. I'm just used to something which sets or clears a flag in the input from the Windows joystick interface. What, exactly, is "missing" virtual button presses? What is looking at them? If you mean FSUIPC is actually making virtual button presses faster than it is scanning them, then, if you want to catch them all (why?) you'd have to increase the button scanning rate -- an FSUIPC INI file parameter. But, generally, the rate is good enough for normal value increments and decrements and it then doesn't matter if some are missed. Are you counting the clicks or something? Without knowing what you mean by "it" I can't really answer, sorry. You can experiment with the button polling rate, rate I'm not sure what you are trying to achieve. Note that the event.timer method of calling the routine depends on Windows timer calls, which are not guaranteed to provide calls at exactly the intervals requested. It depends on the loading on the rest of the system. If the Lua threads were run at a higher priority then it would probably be more predictable, but at the cost of affecting FS performance, something I'm not willing to risk. If the device is connecting as Joystick #3 and that rotary is operating buttons 30 and 31, they would surely be seen. Of course. How not? If they are not showing up you'll need to adjust the time, or turn the knob faster, or reduce the polling time, or al three. No idea. Where are you seeing those? FSUIPC adds "vor1 obi inc fast", one of the additional FSUIPC controls listed in the Advanced User's guide. There are several added to make up for omissions in FS's supply of controls. REgards Pete

In that case, wouldn't it also run with XP compatibility mode selected in the right-clickpProperies-Compatibility options? Regards Pete

The those axes were already assign and calibrated when you created the profiles they would have inherited those settings unless you opted not to. If you have existing 'default' [Axes] and [JoystickCalibration] sections, and you want to use those non-profile specific settings for one or more of the profiles, just delete the Axes and JoystickCalibration sections completely for those profiles. Generally I would expect folks to have some button and key assignments different for each profile, but most aircraft using the same axis assignments and calibrations. Only in more esoteric situations, like using a joystick for fighters and a yoke otherwise, and maybe a G-stick for helos, would I really expect different axes assigned. Similarly for calibrations, though some aircraft might want different slopes or more or less aggressive action. That's answered in the manual just after the paragraphs I quoted earlier, thus: Regards Pete

Well 0C42 is clearly labelled Magenetic Variation, not a heading, 0C5C is the readout for a bearing TO VOR2, as also clearly described, and likewise 0C60 is the VOR2 radial you are on. Obviously none of those are settable, all being read-outs. The two course values are called OBS in FS ("Omni Bearing Selector"), NAV1's OBS being at offset 0C4E and NAV2's at 0C5E, the latter being right next to one of the wrong ones you picked! Regards Pete

Sorry, the only things I've ever heard are that folks don't fly PMDG with any turbulence, at least not of the type FSUIPC can simulate. You might want to try a weather program such as Active Sky, see if that gives you what you want. Alternatively, just experiment with FSUIPC parameter values between the two you've already tried. Maybe you'll find some values which don't upset the sensitive aircraft but which give you something you think is okay. Regards Pete