Pete Dowson

A key for what? I don't issue any keys, by the way, so I can't help in any case. But if you are going to try to get one from, say, your account at SimMarket (survey the Announcements above to see why*), it will certainly help you to work out what you need a key for. I doubt you'll ever get a replacement, just a reminder of the one you forgot. Pete * Look for "READ THIS IF YOU LOSE YOUR FSUIPC or WIDEFS keys"

But why are you holding down a key for Spoiler A whilst operating SbyRdr B ? I would like to understand the need for multiple unrelated simultaneous keypresses. It doesn't seem logical to me. Pete

I've never changed anything in the way the PLN files are created. I never use PLN files myself. Did they ever work with FS2004? What differences are there to those produced by FS itself? Nothing was attached. Perhaps you should paste it in? But it won't help unless I have a good FS2004 plan to compare it with. Let me see. Here is a simple short plan I created recently (it uses FSX data, mind, but it should certainly still load okay): [flightplan] title=FStarRC: EHAM to EBBR description=Schiphol to Brussels National at FL199. Generated by FliteStar via FStarRC (c) Pete Dowson type=IFR cruising_altitude=19900 departure_name=Schiphol departure_id=EHAM, N52* 19.00', E4* 45.08', +000000.00 destination_name=Brussels National destination_id=EBBR, N50* 54.01', E4* 29.01', +000184.00 waypoint.0=EHAM, A, N52* 19.00', E4* 45.08', +000000.00, waypoint.1=268TO, I, N52* 19.00', E4* 44.06', +000500.00, waypoint.2=EH056, I, N52* 19.08', E4* 39.00', +002900.00, waypoint.3=EH032, I, N52* 15.08', E4* 35.03', +006000.00, waypoint.4=EH075, I, N52* 9.04', E4* 45.04', +012100.00, waypoint.5=LEKKO, I, N51* 55.05', E4* 46.00', +019900.00, waypoint.6=Xrstr, I, N51* 34.01', E4* 29.72', +019900.00, waypoint.7=WOODY, I, N51* 24.03', E4* 22.00', +019900.00, waypoint.8=D026H, I, N51* 17.05', E4* 16.08', +008300.00, waypoint.9=ANT, V, N51* 11.04', E4* 28.04', +004900.00, waypoint.10=EBBR, A, N50* 54.01', E4* 29.01', +000184.00, Try that. It loads into FS2004 fine here. It was created using the latest RWS file and FStarRC, but the RWS file is from FSX, that's the only difference. Maybe you have some non-standard Locale differences, maybe commas for decimal points or something? Check against the above, which works fine here. [LATER] You update crossed with my first posting of this. I tried your plan here and you are right, it does not load. But i've no idea why. It looks the same in all essentials as the one I show above, yet mine loads and yours doesn't. Sorry, I haven't a clue why. Can you see any differences (other than names, positions etc)? The format is identical. [LATER STILL] Ah! Waypoint number 9 is missing in yours. How does that happen? If you edit the numbers to make them sequential, it loads fine. None of the plans I've generated have a missing line. In order to find out why you have one such i need to know exactly how you did it. Regards Pete

Okay, then it was a typo in the original file. I'll fix it on next release. Er, what sorts of keys are these? FSUIPC doesn't combinational sequences of keys other than using shifts with keys, and then the shifts must be pressed first, naturally -- the graphic or action key must be pressed last whilst the shifts are held. The shifts supported by FSUIPC are: Shift, Ctrl, Alt (the normal ones as in Windows), plus extra ones to give a greater variety: Tab, Windows and Menu. If you mean you are trying to use "press" and "release" of keyboard keys for different things, and sometimes in combination, then FSUIPC is completely dependent upon Windows ability to decode those events. Normal keyboards are built using matrices and many combinations of key presses don't have the results you might expect. Maybe some specific examples of what you are trying to do will help me understand. What are these "A" and "T" doing, for instance? Maybe you should tell me exactly what you are actually trying to do. You must be using some huge keyboard emulating circuit or something I assume? I've not been asked so many questions on Key programming in the 10 years they've been available. The recent "no repeats" option was the first change for many years. Pete

Not vexed, confused rather. ... and is the aircraft as bad in either case? If so this proves it is something wrong with the aircraft. If it is only playing up since you registered then delete your FSUIPC4 INI file as I suggested so that you can be sure FSUIPC is not interfering by way of bad user settings for the joysticks. The real test as to whether FSUIPC is doing anything untoward is by using the default aircraft, as FSUIPC only deals with things inside FS, those used by default aircraft. If an add-on adds anything extra then FSUIPC doesn't have anything really to do with it except as an access portal to FS's data should that add-on need it. Of course FSX-specific add-ons have the option of using FSX facilities directly and therefore usually don't need FSUIPC at all. Regards Pete

FSUIPC doesn't do anything at all regarding any flight controls, joysticks, etc, in an unregistered copy. None of the bad behaviour can possibly be due to FSUIPC itself. Perhaps the aircraft is using FSUIPC and does something different (wrongly, it sounds like) when it is installed compared to when it isn't? I don't know this DA F70.100, so I've no idea what it does, but there is absolutely nothing in FSUIPC which knows anything about graphical effects like surfaces moving. You need to ask DA support, then. No, you are wrong. Try a default aircraft. Does that fly okay with FSUIPC installed and your controls in use? FSUIPC is an INTERFACE to FS for applications. It can be used well by those applications or used badly. If your DA add-on aircraft is using it badly, then it is at fault and you need to talk to DA about getting it fixed. FSUIPC is also a collection of User-oriented facilities, but those are only available when you register, so none of those can in any way be involved. Er, hold on! You said you were using it unregistered, so what's changed between the paragraphs above this, and your new statement? This is the first time you mentioned FSX too! Delete your FSUIPC4.INI file, which contains all of the FSUIPC4 configuration settings, from the FSX Modules folder. This will undo any horrible mess you might have made is messing about in FSUIPC's joystick facilities. Regards Pete

No idea, sorry. Does it work without the extra 1? Have you tried making your own macro for it? I only supplied the Macro files as (I hoped) working examples. I'm pretty sure i checked each one but maybe I forgot to use that one. I don't have the PMDG 737 aircraft panels installed as a rule, and i am a bit tied up at present, unable to install and check immediately. If it works without the '1' let me know please and I'll change the example. Really? That's odd. It seems to work here. Are you pressing "confirm"? I'll do some experiments, but it will be later in the week. [LATER] Okay, I've reproduced the problem and fixed in in FSUIPC4, so it will be the same in FSUIPC3. I'll sort it out tomorrow, probably. Look out for an update. If the Macro is in error all I can do at present is fix my copy (delete the '1'?) and include it when i upload the updated FSUIPC3. Regards Pete

I suspect the stutter will be related to the nature of the asynchronous interface used, the Windows messaging system, so it will vary from system to system depending on performance and workload. Good. Thanks for confirming. Regards Pete

Thanks for the example. I have reproduced that and found the bug. Sorry about that. I am building versions 3.823 and 4.304 now and will upload them later today. Please watch for updates in the Downloads announcements. [LATER] Okay, the updated versions are now available. Regards Pete

No, "0" isn't replaced by "&H". The "&H" part just says "the following number is in in hexadecimal" -- the same as the prefix "0x" in C/C++. Preceding 0's in a hexadecimal number mean EXACTLY the same as preceding 0's in a decimal number, or a number in any radix -- absolutely nothing, just zero! The offset 0231 is the same as 231 and 0000000000231. The number of 0's at the beginning are completely irrelevant. Same as decimal 0000001 is the same as .... 1, no larger, no smaller! They can begin with 1, 2, 3 or 000001, 000000002, 03, whatever you like. The only thing to be aware of is the peculiarity of Microsoft VB to change any hexadecimal number larger than 7FFF into one starting FFFF... ("sign extension"). For instance, it changes &H8100 into &HFFFF8100. Why? No idea -- it is bad programming or bad design or a bug. It even changes &H00008100 into &HFFFF8100 ! Apparently, to stop it doing such stupid things you should add another & at the end. Thus: &H8100& which does actually compile as &H00008100 ! Pete

I can understand possibly re-installing the Level D 767, but from all the reports I've read, re-installing FSX is likely to induce many more problems than it solves. Does that include the Windows "WinSxS" folders containing SimConnect versions? You don't need to remember it. As it says on screen, there is a file, the Install Log, which tells all. You've messed up SimConnect, which seems to often happen when you try to reinstall FSX. The way to fix it ("repair SimConnect") is described in the "FSX Help" announcement above. Regards Pete

I think the way to make that work is to assign the "Press" action it to "Throttle decr" with repeat enabled, and "Throttle cut" on release (or the individual engine versions of these two controls). This is not sure-fire knowledge though, it is only a hazy recollection. Regards Pete

Okay, so I should be able to reproduce it. Thanks, Actually all i needed was the Keys section -- i.e. this bit: So, now I need to know which of these keys I should be testing to reproduce the result you get. Don't you remember, I did ask You seem to miss half of what i say and ask each time, so this is getting to be really hard work! i am not going to embark on experiments to reproduce the problem until I can do exactly what you are doing, so I need for you to TELL me. See? I cannot see your PC from here, I cannot guess exactly what you do, this is why I ask the questions. I have to repeat the same questions over and over because you seem not to read them. Incidentally, I note that you already have one key programmed for Macro actions on both press and release. This one: 6=N77,8,M1:165,0,M1:164,0 That appears to be for an ordinary "M" key press (i.e unadorned by Shift, Control etc). Regards Pete

I hope you mean 3.82, not 3.20! Please first try 3.822 which you can obtain from the Other Downloads announcement above. Yes, but I understood what you were saying in your first message!!! What i said last time, which you appear not to have read at all was this (I have highlighted the parts asking you to do something): The point here is that I want to test it here and to make sure I do EXACTLY the same as you I need the EXACT information I asked for. I don't ask these things for nothing! Regards Pete

A Window which is Maximised! i.e. Windowed mode (the normal window display where you see other programs on the Windows desktop), but with FS maximised (press the maximise button, top right in the Title bar, next to the "X" button for termination. To change between Windowed and Full Screen modes, press ALT+ENTER. Here the only disadvantage of using Max'd Window more is that you have a title bar at the top. My frame rates are the same as in full screen mode. But take care to make sure the Windows Task Bar is hidden -- set its properties to "Auto-Hide" and untick the "Locked" and "On top" options. The Task Bar properties can be accessed by right-clicking on the Windows Start button, selecting Properties then TaskBar. Regards Pete

Yes, the Install log looks fine and shows FSUIPC4 is installed correctly. But that isn't what I asked. I said: Maybe you could go and find the correct answers, then we might get somewhere? Do you also confirm that this "IFly 747" uses FSUIPC, and that it is compatible with FSX? A lot of panels designed for FS9 won't work in FSX, or only work in DX9 mode. Are you using DX9 or DX10 with FSX? Regards Pete

Okay, so it sounds as if it isn't using any protocol I know about. Message formats? You mean PFC's Proprietary protocol? I don't think I'm allowed to publish that -- you'd need to apply to PFC and probably sign a non-disclosure agreement. If it isn't set to Elite protocol, then it must be some protocol I've never heard of, used before I ever heard of PFC or saw its products. Sorry, you do need to discuss it with PFC. I really cannot support disused protocols. Regards Pete

By "new FSUIPC", which do you mean, please? Always state version numbers, they are easy enough to find. Please show me the [Keys] section of your FSUIPC INI file and tell me exactly what additional action you are trying to assign to which key, and I will try it here. -- but if you are not using the very latest FSUIPC version (3.822 or 4.303 at present, see Downloads announcements above) please try that to make sure it is still a problem. I hate looking for problems I've already fixed! Regards Pete

That's much better -- at least you don't have the dual axis types both being used. The fact that there's an initial "8192" (calibrated from 0 I assume) being sent is now most certainly due to a zero reading being sent either by your joystick or by its driver. So that's really as much as FSUIPC can do for you. Why you don't see the same in FS9 is odd -- but maybe you should do all this in FS9 and compare logs (though, sadly, I don't have exactly the same logging there). Maybe it is occurring in FS9 but has no noticeable effect because it occurs before FS9 is "ready to fly" -- in FSX these operations are not actually started until that stage, so you may be observing a spurious reading from the driver/joystick which has always been there. For the PMDG? So now it is impossible to see if anything in the PMDG code is responsible, or contributing. Don't you ever use other aircraft? Results from a default aircraft would have been far more relevant and interesting. Why not simply make that section THE default [Axes] section, so you can use it with all aircraft? By the way, I did say I fixed the problem setting the logging options in 4.302, and now 4.303 is released, but I see you are still using 4.301 (not that it would make any difference here). I don't think there's much else I can do for you as the cause certainly looks external to FSUIPC. I cannot make any of my "cheap" joysticks/gamepads (that I keep around just for such testing) do the same -- they use default Windows drivers. Regards Pete

I don't know, sorry -- I don't have anything to do with that side. You'll have to raise a "problem ticket", with SimMarket. Pete

If you are testing the spoiler lever on the ground, DON'T! With FS, as you operate the spoiler lever it naturally passes through the "ARM" position (detente). If you are on the ground at the time, FS sees the ARM and the fact you are on the ground, and deploys 100% spoilers automatically (as if you'd just landed). Getting them back down is then difficult until you spool up again (e.g. as if for a Go around), as you've found. the same thing can be seen if you use the mouse to drag the spooler lever on the Quadrant gauge in your FS panel. Regards Pete

I use a 9800GTX on one PC and a 9800GX2 on another. The newest nVidia drivers I've got, 177.79, are actually very good, performance-wise (much less stutters in DX10 mode than even using 177.70), but I have had three occasions this wee where FSX has "crashed" into a black screen with on way out. This wasn't when going into a menu item, just with FSX sitting there, parked at an airport, one occasion flying. I've taken to using maximised windowed mode (same frame rates) for now. Regards Pete

Sorry, I know of no change whatsoever in the PFC protocols I support which would make it "not recognise" any PFC digital control system set in PFC digitaL protocol mode. The protocol has been substantially extended over the last three years, but not in any way made incompatible. What version of my driver did it EVER work with? Are you sure it is one of the series of PFC systems which are supported by their digital protocol? Are you sure it isn't one of those systems with dual PFC/Elite protocols built in, and is switched to Elite? (I think they had a protocol switch behind the throttle quadrant). Are you sure it is operating at the serial line speed set in the driver? You may need to visit PFC's forums for more help -- www.flypfc.com. Regards Pete

If you are assigning axes in FSUIPC, there are only two "ways" -- (1) assign to an FS control. That routes it back to FS, and then FSUIPC calibration is optional. This method is less efficient, but gives you the complete range of FS axis-type controls to choose from. Or (2) assign "Direct to FSUIPC", which bypasses FS altogether, going direct to the calibration section. Using that you MUST calibrate in FSUIPC, or you won't get any results. This way is more efficient, but you are then limited to the axes FSUIPC can calibrate for you. Provided they cover all you want, it is the best way. I'm pretty sure it does say most of this in the documentation some place, too. Regards Pete

A "black screen" isn't a CTD. CTD means "crash to desktop", which means FS simply disappears without trace, leaving no window, no message, and you are dumped back on the Windows desktop. Surely your Windows desktop isn't all black? If you do really mean a black screen, then it sounds exactly like a fairly well known video driver problem. Try switching FS to windowed mode first. If it then works you have a video driver problem. See about updating your drivers. Regards Pete