Pete Dowson

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

Assigning a button to just "Brakes" in FSUIPC is identical to assigning it to BRAKES in FS -- there's no advantage or difference. You'd want to set the "repeat" option, otherwise hold it down won't keep the brakes on. The "BRAKES" control is exactly the one used by the default "." keyboard assignment, but of course keys auto-repeat on the keyboard. Pete

I am having difficulty remembering any of that, but I think there was a whole world of difference between the ISA version and USB version -- with my code, at least. On ISA I used assembly code via my EPIC95.VXD. For the USB version I interface to RR's EPICIO.DLL. I'm afraid I don't even know where my documentation is for this stuff now. Your best bet really lies with the EPIC forum (is it still Ray's green side up?) or with RR or FlightLink. Regards Pete

No, because I have no information. If you want me to look, please get me a full log. Be sure to use the 2.00 version as appended earlier in this thread, and set "Log=Debug" in the FStarRC.INI file [settings] section. Then run a session including pronting the report. The FStarRC.Log file it produces will be quite big, but it should help me work out what to change -- you'd then have to test any changes for me. Send it ZIPPED to petedowson@btconnect.com. Regards Pete

FSNavigator is NOT an FSUIPC client application, but an FS DLL (i.e. a Module, like FSUIPC, which installs INTO FS itself). It is one of the main examples of add-ons which cannot possibly be run on any machine not running FS! FSCommander works fine through WideFS, but you must run WideClient on the client PC first. Pete

I'm not aware of any specific problems with this feature. But can you give me more details so I can check? Specifically: which messages, and what updates have you applied to FSX? Regards Pete

You have made an error then. Please show me the actual SimConnect.INI file you have made and tell me EXACTLY where you placed it. Regards Pete