Pete Dowson

In that case, since FSUIPC only ever sends the axis values through initially and then when they change, the initial "wake up" signals coming from your axes are wrong. There's really not much I can do about that. Either revert to FS assignments or make it part of the initial cockpit checks to operate each lever (this would be proper practice in any case). Er, that's not true. Why do you think this? The reverse settings and so on are done in the Joystick Calibrations, not in the Assignments--unless you are assigning dedicated reverser axes, which is a completely different thing. Folks have been using FSUIPC to calibrate FS-assigned axes, and apply reverse zones, since FS2000 days. The Axis Assignments facilities are quite recent and were really aimed at those who want to have different controls assigned to the same functions in different aircraft -- like a Yoke for Boeings, a Joystick for Airbuses and fighters, a G-stick for helicopters and so on. FS assignments can't offer automatic switching for different aircraft as FSUIPC can. But all the Calibration facilities are offered for all the main axes which can be assigned in FS. That's they way it has ben done for years. Pete

Which SDK is that in? 0310 and 0368 (?) are the only ones I know. Not sure about 0368 though. Maybe that's it? Does this SDK-mentioned one you found speed up and slow down? Maybe you have to take care of that adjustment yourself, reading the sim rate in 0C1A. What about pauses or menu accesses stopping time? [LATER] Okay, I've looked up the "ELAPSED_SECONDS" value -- it's a Gauge Token Variable. I could probably read it as such, but I wouldn't want to have to try reading it at very frequent intervals as such access is relatively expensive (performance-wise). Most of the fast stuff I do is by mapping directly into the actual value in FS's memory. If i can't find this easily it has to be by athis expensive set of function calls. So, please tell me more about this need and how you'd be using it so I can assess whether I can provide it adequately. BTW FSX, via Simconnect, offers" ABSOLUTE TIME", which doesn't sound like it's going to sped up and slow down like you ask. It is described as "Time, as referenced from 12:00 AM January 1, 0000". Pete

No way I know, as PMDG do not publish details of their offset usage and probably encrypt the data there in any case. They don't want folks to gain access into their software. Regards Pete

Assign those controls to what? They are not axis controls so you wouldn't normally assign them to throttle-type levers. The Mixture full lean, lean, enrich and full rich controls are those by default assigned to the Ctrl+Shft+F1 to F4 key combinations. They must surely work, but they are smooth axis control -- they operate in the same way as the 3 and 9 NumPad keys do throttle inc and dec controls. Where are you trying to assign them? Just look down the list of axis assignments you can make in FS's assignments dialogue. Theose controls are not listed there, you will find the correct mixture assignments there. Please be ore specific when asking questions like this. It is very difficult to guess exactly what you are talking about sufficiently to give an adequate reply. Pete

It really sounds as if there are either multiple assignments to the same FS control axes, with different calibrations, or something rather weird going on with whatever Windows drivers are installed for your joysticks. You said originally that you "have done the calibration through FSUIPC". Using FSUIPC's calibration doesn't change assignments or anything, it only modifies the values read by FS before being sent to the simulation engine. So really if it is only calibration, not assignment, you've performed in FSUIPC then it could not make the difference you describe at all. So, I suspect you have also tried actually assigning axes in FSUIPC, and have not disabled them all in FS, so you have two inputs working against each other. If you have made such assignments, try deleting the entire [Axes] section from the FSUIPC.INI file and instead doing it the normal way, assigning through FS. Regards Pete

Good! Thanks for the update! Pete

I don't know IVAP or IVAO I'm afraid, but I suspect that the versions they programmed for FSX use the new SimConnect facilities for writing the messages to the screen. These are not the types of messages the FSUIPC facility is designed to intercept. I'm not sure that I would be able to do such a thing, at least not without hacking into FSX whilst running IVAP software which I don't have. Surely their software includes options for you to adjust or switch the sorts of messages you want to see? If not, have you discussed your needs with the authors? Regards Pete

Yes, the FSUIPC INI file, and the FSUIPC KEY file, which contains your registration details. Nothing else. Pete

Check the mouse driver for that toothat's the only other cause I've heard of. Pete

Right. So the ATC window is hooking keypresses before FSUIPC can see them. That will be happening because presumably it inserts its hook when it appears and removes it when it closes, whereas FSUIPC does it when it starts up. Well, yes, 221 and 223 are i think related to opening and closing added Windows such as the ATC one so it is probably seeing those first too. I know it steals most of the NUMPAD ones (96-105). Regards Pete

Is this in full screen mode or Windowed mode? Have you tried both? If it is only in full screen mode it is most likely to be a video driver problem. There is nothing odd about FSUIPC's dialogue window, it is a standard Windows-implemented dialogue defined in its attached resources. It uses a library DLL called COMCTL32.DLL, and some video drivers notoriously replace this with psrtial implementations of their own devising. It isn't the module, which is 100% proper Windows Win32 API (being a 32-bit program like FS, not 64). Mentioning Vista64 does suggest that the problem lies in the video drivers, which are still not terribly stable for Vista64 as far as I know. Try earlier or later video drivers, or possibly just different settings. Regards Pete

Why? It has never used FSUIPC and FSUIPC is not mentioned at all anywhere in its description or documentation that I know of. Too many to list here. Check the links on the right-hand side of the main http://www.schiratti.com/dowson download page for some examples. Surely, instead of asking what will use FSUIPC you should be asking yourself what you want to use the second PC for? Seems odd to just want to run what will run rather than have some sort of purpose. WideFS you mean. It is a little misleading to think of it as "widescreen", which is merely a 16:9 display. It also leads to confusion with WidevieW which is a totally different program. By "nothing happens", you mean there is no Window made by the WideClient program? Nothing saying "waiting for connection" or something similar? Please check the WideClient.Log file on the client PC and the WideServer.Log file on the Server PC and show me those. They will tell you what is going on. I really cannot believe "nothing happens"! Regards Pete

Not initially. First, what add-ons, apart from FSUIPC4, have you installed? If you've only installed FSUIPC4 and nothing else, then simply look in the FSX "Modules" folder and make sure there's no nothing in there which includes the word "SimConnect" in its name. You'd need to do the same in the folders of any other add-ons you have installed. Don't delete them ll for now, just list them for me. First and easiest, though, please just show me the Install and FSUIPC4 logs from the FSX Modules folder, as already mentioned. Pete

Is FSUIPC4 installed and working okay -- you've accessed the GPS page in the dialogue and set everything correctly? Sorry, I've no idea. I've never got any GPS or PDA device to work. There are several older threads from folks who eventually got stuff working, but I don't recall anything specifically different between WinXP and Vista -- excepting of course that Vista currently seems to be a pig of an operating system, stopping you doing too many things or at least making them very difficult indeed. Regards Pete

No, it isn't. Thanks to Martin I've already verified that 9.3 no longer uses the MFC42.DLL library, which FStarRC hooks in order to extract the data from the print stream. It now uses MFC71.DLL instead. I'l be making a version of FStarRC which tries that DLL if MFC42 can't be hooked. This should allow a full log to be derived which will enable me to work out what else has changed. Stay tuned for a few days. I won't be able to deal with it will Wednesday or Thursday in any case. Regards Pete

I'm pretty sure the default ones (they can be user-assigned, therefore changed, of course) are listed somewhere in FS's Help. Have you checked? Pete

Ah, do you mean the FSUIPC hotkey trapping facility, offsets 3210 etc? Pete

These keypresses are picked up by YOUR program, you mean? you aren't sending them to FSUIPC or FSX? Er, traffic density changing in FSUIPC is an added FSUIPC control, not an FS keypress or control. I'm afraid I am now thoroughly confused about what it is you are doing and what you think is going wrong. It will if that vehicle is an AI aircraft. FSUIPC doesn't know anything about other vehicles, or road traffic either. If you mean something about keypresses not getting through when the ATC window is open, because it eats them, yes. If you mean can FS controls be sent for FS to action when the ATC window is open, yes they can, the ATC window has no effect on controls. Regards Pete

Hmm. Strange as that code is now the same as it was in FS9. I'll re-check it here. Pete

Do that in FS's assignments first. Test them and make sure they work before even looking at FSUIPC. Once the throttles are working normally in FS, go to FSUIPC, Joystick Calibrations, and find the page showing 4 throttles. Calibrate each ofg the two, one at a time, following the simple steps in the User guide. The "centre" is your idle. Assign the flaps in FS, then refer to the long explanatory section in the FSUIPC user guide for programming notches, if that's what you want. If you don't want notches then you don't need to do anything special. Those are all easy to assign in FS. What is the problem? If you have specific problems, state them. Regards Pete

Yes, I think that was the same bug which also caused this, as noted: It should be working now, in 4.208. Do you have evidence to think otherwise? Happy New Year Pete

Phew, that was quick! I'm still catching up today from my week off. Visitors and another day off tomorrow, so I'll not get to this till later in the week, or maybe next week. Okay? Happy New Year! Pete

SimConnect is the new Microsoft FS application interface for FSX and beyond, eventually supplanting FSUIPC for that purpose. FSUIPC's interfacing role is now mainly for interfacing older applications. Pete

I've really no idea. This will be a new problem for FSX . I suspect it's all down to what SimConnect does with the Events when I've sent them. It sounds like it isn't delivering them to all the places which should receive them. Please could you summarise these findings and send all the details to tell_fs@microsoft.com. I'll also try some experiments to verify your findings and report them direct. Unfortunately these sorts of bugs are very unlikely (i.e. 0% probability) to get fixed before FSXI, but they should be lodged now. If I can find a way of identifying these modes internally I might try finding alternative ways of sending the events -- like posting them to FS's window as I used to. Unfortuately I can't do that for all modes as some of the stuff then doesn't work (in FSX). Happy New Year Pete

I've never actually tested this, but I think FS's sensitivity and null zone settings only apply to axes assigned in FS. Certainly, If you assign in FSUIPC for direct calibration in FSUIPC they are irrelevant. Of course you shouldn't have the same axes assigned in both FS and FSUIPC, or you'll get conflicting actions when you use them. If you find that FS insists on re-assigning axes every time you reload it, even though you did delete all the assignments, you could try setting all the sensitivities to minimum (full left) -- they shouldn't interfere then. Regards Pete