Pete Dowson

Why? That should most certainly not be necessary. Okay, so it isn't what I thought it was. Sorry, it doesn't see other traffic but they all show with distance 000? That doesn't make sense. Which is it, no AI or all AI at 000? You didn't add the line I asked you to, so this log contains nothing more useful for me to check. As well as supplying a useful log, could you try using a different default start-up flight, one without a plan. We need to eliminate a problem in the flight or plan. Regards Pete

It's the oldest supported version. There are always interim updates in the Download Links subforum. The mouse macro facilities only work on gauges which are written using the Microsoft C/C++ gauges SDK. Unfortunately hardly any of the default Microsoft gauges are written that way. If a mouse macro cannot be made the display does not appear. It is the same as if you clicked on a position on the screen not even on a switch. The traps installed in the gauges cannot catch them when they don't go there. Additionally, for FSX, the traps won't work on the original version of FSX. They need SP1 or SP2/Acceleration installed. Regards Pete

Hmmm ... that's evidently a previously undiscovered effect! :???: You don't HAVE to set STICK_SENSITIVITY_MODE=0. What that does is make the joysticks behave like normal linear analogue inputs, which I think is far more controllable and predictable. The default mode uses some sort of time-based feature where the changes sort of "catch up" with your stick position. Calibration still works, it's just a little bit messier and less predictable. So I think the choice over what is more important to you has to be made. Try both and see. Of course you could assign in FSUIPC instead of in FS. Then the "stick sensitivity mode" is irrelevant. The problem then is that unless you disable controllers in FS it sometimes automatically re-assigns things even if you deliberately unassign them -- this happens for instance if the joystick is disconnected or powered off at any time when FS is loaded, as it then thinks it is new and does you a "favour". If you disable controllers in FS it disables the "mouse look" facility as well, which defeats the object. I'd never noticed the effect on "mouse look" because I don't have a mouse (or keyboard) in the cockpit. I use either TrackIR to look around (VFR flying in a light aircraft) or simple views (the usual 45 degree views, not panned) for airliner flying. I use Ezca to set the views precisely.(http://www.flight1.c...oduct=ezdockcam ) Regards Pete

I'm sure Paul will be able to help you with VB, but for Project Magenta I'm afraid ALL of the PM offsets are only used by PM. None of them are noticed by Flight Sim itself, and therefore do nothing without the relevant PM parts present. The "sysvar.txt" file does list some FS offsets which are used in the pmSystems logic of course. If you are using PM with the exception of PMsystems, then you would have to supply the simulation of the subsystems you want which PMsystems implements. And that includes the APU. PMsystems does not use the FSX APU (there was no FS9 simulation of an APU in any case). Regards Pete

Hmmm. Very strange. The log looks okay. Are you perhaps running FSX "as administrator" at all? If so you would also need to run all FSUIPC client programs "as administrator" too -- otherwise, because they are at different privilege levels widows blocks data sharing between them. Mind you, I would have thought that would stop the version number being seen, too. It's just another offset like the clock. Have you always had this problem? I see you are using the very latest version, 4.659. Didn't you install 4.60 or 4.638 using the Installer first? I'd like to know if this is something new just with this new update as there's just been a small change to prevent it stalling on initialisation during paused mode. Oh, I see WideFS is registered too. Are the programs you checked with running on a Client? In Windowed mode does the FSX title bar show WideFS as running ("waiting for clients" or "connected")? That frame rate looks pretty low: Is that typical of what you normally get? Is the Sim "Paused" at all? If so can you unpause it please. One more thing to try, to get more information. Can you edit the FSUIPC4.INI file and add "LogExtras=Yes" to the [General] section. Then load FSX run it for a few minutes at leasst as you just did, then close it and show me the Log again. [LATER] Okay. I think I've found the problem anyway. It was a change in 4.659 only. The fact that your start-up loaded a PLN file messed up an additional check I had put in to ensure a safe start-up. Sorry about that. Please try 4.661 now uploaded and ready. Regards Pete

Sounds like FSUIPC is not running correctly. Does it appear in the AddOns menu in FSX? Please close down FSX then find the FSUIPC4.LOG file (not the Install log) and paste a copy into a message here. Pete

Good. I am pleased you got it all sorted! Pete

I am not a "sir", just Pete will do. I won't be telling you anything about software "internals". They are private. :-) You must mean "usage" or "externals", the stuff which is documented for you to use. That reads as if you want an external controller to have its switch changed when you change the switch in the aircraft panel on screen. I assume you really mean not to "capture" the switch changing on screen, but to operate the screen switch from a real one, or at least do the same job as it does? If you mean can you program a switch on your hardware to operate the aircraft instead of using the switches on screen, then that depends on how the aircraft is coded and what provisions they have made. There are several distinct possibilities: First, check if the switches just use normal FS controls. If there's no sufficient documentation with the aircraft, try using FSUIPC's logging -- enable Event logging, operate the switrch, and see if it has used an GS control. If so, assign your hardware switch to that control. Second, check the aircraft documentation to see if they've provided a way of operating the switch without a mouse. Many aircraft allow you to assign key presses. If so, assign jkeypresses and program your hardware switches to send those. Third, if the aircraft gauges you want to operate were written in C/C++ using the standard Microsoft FS panel SDK, there's a good chance FSUIPC's "mouse macro" facilities might work. Try those. They are documented in the FSUIPC User Guide. Fourth, if the aircraft uses named local panel variables (L:Vars), and if the gauges are written in XML this is more likely, you might be able to program the switches using macros containing L:Var writes. To find out about a panels L:vars use the Lua plug-in for listing and monitoring L:Vars, provided as an example in the FSUIPC package. Finally, if none of the above, you would probably have to resort to using something like Luciano Napolitano's "Key2Mouse" program to program a key press to move and press the mouse buttons for you, then program your switches in FSUIPC to send the keystrokes. Examples of user's applying some of these things can be found in the User Contributions sub-forum. You can use aircraft specific no matter what else you do. Although better these days to set up Profiles instead. Best to read up more about them, then, look at other folks' examples, and use the Lua plug-in to find the variables you need. I can answer specific questions but I cannot undertake a tutorial here -- that's what documentation is for, in the first instance. I see no one, as yet, has entered a User Contribution for the VRS Superbug, so when you succeed it would be nice if you posted your solutions there. Regards Pete

Sorry, what does "resetting the config file on the Clients" entail? I've never heard of such a thing. The Wideclient.INI file has no need of user interference. And neither WideFS nor FSUIPC has anything whatsoever to do with the Internet, so I really don't understand why your Internet timeouts affect WideFS? No. Won't it locate the Server by name? And in order to stop the IP address changing, simply define a fixed IP address on the Server PC instead of letting the router assign them. It is recommended to do this in any case as it saves having Windows continually polling for IP addresses. All your PCs should have fixed IP addresses defined by you, not assigned by the router. Pete

Good. It was a missing line in the code. Odd no one discovered it before. Regards Pete

Okay. In that case please try 4.658, get it from this link FSUIPC 4.658. Let me know if that changes it.. I'm off-line now for a few hours. Pete

Do you see the PENDING request logged AFTER the first ACTIVATE? THAT's the question I asked and which you never answer!!! I think FSX never has completely zero dynamics unless you change to GLOBAL mode, new in FSX. That's what global mode was for -- non-dynamic training weather. Anything called "spare" means "unused" or "reserved". When will you answer my question? I will investigate here when I know the answer -- but it will not be till tomorrow now as I have to go out. An answer would be appreciated please! Regards Pete

Yes, it works? What does 'end of "NW_SET_PENDING" weather data for all airport.' mean? My question was:"Is there an NW_ACTIVATE further down the log? If so, aren't there any NW_SET_PENDING's logged thereafter?", and you answer "yes", so you are saying it is okay after all? Your log shows okay: If you want to. I'm not sure what your problem is at present as you haven't explained. If there is a problem then please describe it. What is it you want to do which doesn't appear to be working correctly? Is it simply a misunderstanding or any actual operational difficulty? Regards Pete

Why post to the FAQ subforum? Support is done here, in the main Forum. You are lucky I spotted your message at all. You are making a mistake then in part of the three fields. And are you sure you purchased an FSUIPC3 key and you are installing FSUIPC3 in FS9 or earlier? I do not see anyone with the name "Constantine" purchasing anything of mine recently. Is that a code name? I can't check if you hide your name. Don't post Keys here, but some clue would help. Pete

Checking the code I see that in FSX only there's a special change which treats the very first "NW_SET_PENDING" as an "NW_SET". It should change after the first NW_ACTIVATE. I don't now remember why this was necessary -- something to do with how the weather system works in SimConnect. The weather setting code hasn't been changed for nearly 5 years now and I am afraid I don't remember the technicalities. Is there an NW_ACTIVATE further down the log? If so, aren't there any NW_SET_PENDING's logged thereafter? I think the idea is to set the complete weather normally initially, rather than delay it, but then do the delayed implementation subsequently, whilst the user is actively flying. Mind you, a lot of the value of the PENDING/ACTIVATE system is lost in SimConnect because of its delayed morphng mechanism in any case. In FS9 FSUIPC was actualy overwriting the current weather settings. In FSX the timing is all controlled by SimConnect. It is most out of FSUIPC's control. Regards Pete

It is not differently coded in FSX. What is the problem? Pete

Have you assigned a flaps axis in FS at all, because, as this shows, you most certainly haven't assigned one in FSUIPC: [Axes] 0=0X,256,D,1,0,0,0 =Aileron 1=0Y,256,D,2,0,0,0 =Elevator 2=0U,256,D,5,0,0,0 =Prop pitch 3=0V,256,D,6,0,0,0 =Mixture 4=2R,256 5=2R,B,-10922,14720,65595,0,65603,0 =These two are assigned by range to the FLAPS UP and FLAPS DOWN buttons. You also appear to have no Throttle assigned. If you assign to the Flaps up and Flaps down buttons (same as keypresses), they are not calibratable because they are not axis inputs, as I keep telling you. if you don't assign an axis to an axis control is doesn't operate like an axis control and you cannot calibrate it. Why didn't you read my last reply? There's no gear axis either, but an entry like your Flaps entry would actually make more sense for the gear because there is actually no gear axis control -- only gear up and gear down. On your other message I'm afraid I cannot support the CH Control Manager, you need to talk to CH about that. On the flaps, I don't want to hear any more from you whatsoever until you assign the flaps lever to the flaps -- on the LEFT hand side of the assignments, just as you obviously have done already for Aileron, Elevator, Proppitch and Mixture! [Why on Earth are you going daft with the flaps instead of treating it like the other axes? It makes no sense and I don't want to have ot repeat all this again]. :roll:: :roll:: :roll: Pete

Right ... Sorry, you've lost me. What does that mean in this context? And what do YOU think is the "latest version of FSUIPC"? Folks have come here and said exactly that and been found later to have been using 12-18 months old versions! I ALWAYS need you to quote actual version numbers! That's the only thing which makes sense! Since you know the mouse macros work, and folks have already posted them for the MD11, what is your question now? Regards Pete

Not you, then? You do not need to buy it to use VRInsight devices! VRInsight are an approved and licensed FSUIPC user (unlike Saitek, I might add!). Where are you reading such rubbish? WideServer's CODE is included in FSUIPC4, for FSX, to make it more efficient. But WideFS, the product, remains a separate licensable program. You do not "order" the sofftware from SimMarket, nor receive it from them. SimMarket only provide registration keys. you can install FSUIPC and use it weithout ever visiting SimMarket. What information do you expect? Did you select the option for a combined FSUIPC + WideFS price? If not, you don't get it. I don't have a website. No. You buy WideFS7 for FSX or WideFS6 for FS9 and before. nothing to do with WideClient. wihich you can get and install on any number of clients, free. It is the WideServer which has to be registered. Are you using FS9? If so it should work fine. WideFS6 is clearly defined as being for FS9 and before. If the key is rejected by the installer you are making a mistake somewhere. Maybe you are spelling your name incorrectly? That is the most common error. Regards Pete

Yes, the SDK badly needs updating. That is your correct reference rather than FSInterrogate though -- that is more out of date and wrong in some places. All changes since then are listed in the changes list -- the FSUIPC4 History document for changes up to the current official release (4.60) and the list in the Download Links - Updated Modules thread for interim updates since then. The SDK will be updated from those last two sources in due course. Major updates of both FSUIPCs and WideFS are due soon. It's the documentation which slows me down! ;-) Regards Pete

As I said (see "The SDK contains your reference documentation"), it is part of the FSUIPC SDK, the same place as where FSInterrogate comes from. The SDK is not automatically installed on everyone's system, as it contains far too much stuff aimed at developers and folks doing their own thing, not of interest to the majority. Where did you get FSInterrogate if not from the FSUIPC SDK? As far as I'm aware that's the only place! Why are you using it instead of the documentation? The SDK is available on the same main download site as FSUIPC and WideFS, i.e. http://www.schiratti.com/dowson . Pete

Have you tried without this "CH Control Manager"? Certainly FSUIPC doesn't need it, and there may be conflicts for all I know. Have you tried the CH Hangar at all? http://www.ch-hangar.com/ . Well, please start again -- clear the detentes, because your current detente #1 (the centre pair of values) runs from 1 to 16380 as far as I can read on that graphic. That removes any possible scope for calibration. Press the Reset button and start again. And this happens on all axes, all axis assignments? Where are you assigning the flaps lever, and to what control? In an earlier message you stated: which still makes no sense to me, because an axis is an axis which is an axis! Your odd reference to "landing gear and flaps" in the same sentence as "up and down values" is of concern, because there is NO landing gear axis, but there IS a flaps axis, which is what you should be using. You cannot calibrate landing gear up and down controls, nor any "inc" and "dec" controls. You can only calibrate genuine axis controls, as it is only they which provide any parameter (other than 0) to be calibrated! Therefore I think you are misunderstanding "flaps".and are not even assigning to a flaps axis at all! Why not show me your FSUIPC4.INI file (paste it into a message) so I can see what sort of mess you have made. I'm sure it is all something you are completely confused about. Regards Pete

Sorry, for Vista and Windows 7 I have no idea how to fix a broken Simconnect system. I deliberately broke the one on my development system so I could research methods of fixing it, with a view to maybe producing a utility which could do the repair. But after many many hours without getting anywhere at all, I gave up. The Windows side-by-side library system is the most evilly complex web of inter-connected GUIDs and other unfathomable things that I found it impenetrable. I can't even find a programmatic way to do it on WinXP, though the "delete folders and run repair" method seems to work better on that system. Looking at the internals they are completely different on XP compared to Vista and 7. Some facilities are missing in the original compared to SP1 and SP2 and a lot of programs insist on SP1 at least. However, if you have FSX itself updated to SP1 or SP2/Acceleration, there can be complications in any case with having a broken related SimConnect, things which again I don't understand. In the latest incremental updates to FSUIPC4 i actually link more directly to SimConnect -- I do this primarily to get over my broken development installation, as otherwise I think it's definitely a Windows-and-everything reinstall job. I can't run other SimConnect utilities on it still, but I don't need to. I've still got a separate and fully working flight PC. So, for FSUIPC only you could try downloading the latest FSUIPC4 increment from the Download Links subforum. This won't help with other SimConnect programs though. No, it doesn't. It only requires at LEAST the base version. It far prefers SP1, or better SP2, and offers more with those. They are also far more efficient as they use direct connection rather than TCP/IP for internal modules, and pipes instead of TCP/IP for local external ones. Most current Simconnect add-ons need SP1 at least as far as I know. I don't know how your bad install arose, but I can't offer any chance of repairing it without a windows re-install I'm afraid. When you install FSX, make sure you run it between each part of the install process. That appears to be very important. i.e. Base version -- run it -- reboot -- SP1 -- run it -- reboot -- SP2 or Acceleration -- run it. Only then start installing add-ons. Regards Pete

What version of FSUIPC4? I need to know the version number. There was an error until recent versions, as listed here in the interim update change list: Otherwise they work okay on the default 738. I'm not surprised. Offset 0E60 is not used in FSUIPC4. THe EFIS range is controlled via offset 0E00. As clearly documented, 04F8 belongs to Project Magenta. If you aren't using PM software it will naturally have no effect. Its "address"? What the "address" of a switch? Sorry, you've lost me there. That is because those so-called "EFIS" offsets refer to the viual approach system which was implemented in older editions of FS -- the hoops you fly through. Microsoft called that "EFIS". It is not at all related the the ND, and as you would see if you referred to the correct document (the FSUIPC4 Offsets Status PDF) those offsets certainly don't apply to FSX. Please use the offset documentation supplied, then you'd save yourself a lot of bother and time. The data in FSInterrogate is NOT intended to be used as a reference. it is a utility, with data entered by users, and not up to date. The SDK contains your reference documentation, updated for interim versions by the changes list supplied in the Download Links subforum. Regards Pete

No, sorry. You need to go to SuperBug support. I'm afraid I cannot support other folks' products. I have enough with my own! ;-) Regards Pete