Pete Dowson

[quote name="Luca Zappala I know the Crossfeed toggle one does work' date=' but I don't know what it is used for. Could you enlight me? [/quote] I think it may vary according to aircraft implementation, but if you look at the fuel selector switches on those cockpits with them showing, you'll see that crossfeed left-to-right will feed both engines from left tank, and vice versa. Usually left tank feeds left engine, right tank feeds right engine. I assume you'd use crossfeed to correct an imbalance, or to keep balance when one engine is out. Regards, Pete

Okay, Got it. Thanks. I don't understand this. If you cannot post new topics, how did you start this topic? I've not seen anyone with so restricted an access. Please write to the SimFlight forum folks and see what the problem is. I am writing separately about the FS2004 problem, with more questions. It is a puzzle. Regards, Pete

These "settings" are the input values which are of no interest at all to me, they are very specific to your hardware! What I need to know is what values FS wants to set "flight" and "ground" idle. From what you've said before I'm assuming GROUND idle should be the "real" idle, i.e 0, as you said you can taxi at flight idle. If Flight Idle were 0 then you'd get no thrust, and I assume ground idle would have to be negative -- hence your "engine problems"? If you have calibrated it so that Flight Idle gives you zero (the "centre" in FSUIPC), then I am now thinking that you have calibrated it wrong, and this is the problem. You surely need to calibrate so that the GROUND idle gives the zero!? I can easily use a simple joystick, calibrated for flaps through FSUIPC, to reliably select all 9 positions on the default 737. The flaps calibration facility does not, at present, provide any notches, however. All that is happening is that the increment is used to make the output value jump from one FS-notch to the next. You have to mark off your "detentes" to suit FS, not the other way round -- calibrate in FSUIPC to suit existing notches. I will certainly provide that method in the module I have planned -- I have already done something similar for the PFC quadrant with notched flaps. Regards, Pete

I've reproduced this now, under Win98SE. It is related to the automatic restart, so for now please set SyncInit=No, and AutoRestartTime=0 as I suggested. I am trying to track down the reason for the problem, but so far it looks like the sort of thread and comms restart I am attempting is not possible on Win98. It works fine, 100%, on Windows XP. I may just have to make it automatically omit those facilities on Win98. Regards, Pete

Ah, that is an entirely different matter. Obviously if FSUIPC is not running then no programs which access it will find it, and similarly it cannot produce a LOG file! What does FS say when you attempt to load it with FSUIPC installed? I've not heard of any similar problem with FSUIPC installed before. What errors? How are these reported? What has this to do with FSUIPC? These are all standard main parts of FS. If you did delete FSUI.DLL, which is part of FS and nothing to do with FSUIPC, then you will get many errors!! But nothing like that will stop FS loading. If FS isn't loading, what is happening instead? Do you mean you click on FS's icon and NOTHING happens, or what? I'm afraid I simply cannot picture what you are saying. Regards, Pete

[quote name="roger.wielgus Of course. It is just too bad ( for me) that this value does not match the setting on the quad. When I pull the lever back to flight Idle' date=' the generated values of my pots are simply to close to the ground Idle and the engines do not like that. [/quote] But I still don't understand, and you aren't telling me :cry: What ARE the values? Use FSUIPC's Logging -- monitor the throttle values (right-hand page, offsets 088C (Engine 1) and 0924 (Engine 2), as signed 16-bit values (S16). If the values are too close to be differentiated on your throttle lever then maybe it is some poor design on the part of the FS panel maker, and I don't understand that either. What is meant by "the engines don't like that"? What sort of complaints do they make? Well, one day, possibly, if you can explain it a bit more, please. I keep asking for specifics but don't get them. :o Regards, Pete

No, sorry. I've got no access at all to do with any scenery, whether dynamic or static. Maybe someone in Lago knows how to do those things, but I always thought scenery of all types had to be pre-compiled into a BGL and indexed by FS during the loading sequence. In FS2004 you can't even add new scenery and get it to appear as you used to, you have to close FS down and restart it. Regards, Pete

I don't know the program at all, so I have no idea if it is compatible with FS2004. I would, however, assume the author knows what he is talking about. He has not contacted me for an access key or any other details. If it is freeware then it is entitled to free access to FSUIPC, otherwise you would need to purchase a user key for FSUIPC. Regards, Pete

There's a correction from Lee Swordy, the author. Here is a quote from him: "For those of you who downloaded AFCAD2, you may find it is not self-registering with FSUIPC. This is because the program was misnamed. It should have been named AFCAD.exe but was instead named AFCAD2.exe. I have corrected the name and uploaded AFCAD204.zip again, but for those who have already downloaded, if you have the AFCAD2.exe version then rename it to AFCAD.exe. Otherwise, the uploads are identical. Sorry for the inconvenience, Lee Swordy" Okay? Regards, Pete

I checked this, and it is not exactly as you say. If you don't program any of the yoke buttons in FSUIPC, they are all programmable in PFC. If you program any one of the buttons in FSUIPC, then you have to program them all in FSUIPC. I'll fix it this week. It is similar to the other problems (with the lights and a set of 4 jetliner console switches) which I'd fixed in 1.71 -- see the History. I hadn't realised it also applied to the yoke. It must have been like that since 1.62 -- was your previous version 1.61 or earlier, then? Regards, Pete

When you say "run the FSUIPC.DLL", how are you "running" it? It runs only when you load FS, it cannot run on its own. The error "Not correct FSUIPC installation" is not one from FSUIPC, so it must be from something else. What are you running which tries to use FSUIPC? That is part of FS's own "User Interface". It is nothing whatsoever to do with FSUIPC. I am not surprised. Many things cannot work whjen you remove parts of FS like that! Please leave it alone. What version of FSUIPC have you installed? The current version is 3.11. Please show me the FSUIPC.LOG file, which you will find in the Modules folder too. Same for TrafficLook and WeatherSet -- check their versions numbers by right-clicking on the files, selecting Properties and Version. It sounds like you are using old (pre-FSUIPC 3) versions of those utilities rather than the ones which are supplied with FSUIPC version 3, in the ZIP. Regards, Pete

Sorry, none at all at present. :( Can you try changing some of the recently introduced options, as a process of elimination? For example, in the [Connection] section of the PFC.INI file try: SyncInit=No AutoRestartTime=0 You could also enter the PFC "Test" page and see if you get the crash when operating the axes then. This could separate the area of code. Additionally, on that test page enable the Also, as you are running Win98 the DrWatson dump would likely tell me everything I need to know, so could you check the section "If FS crashes ..." in the FSUIPC User Guide and get me a DrWatson -- ZIP it and send it to me at petedowson@btconnect.com. Please also include your FSUIPC.INI file and your PFC.INI file. Thanks, Pete

But which Idle is the FS idle? They cannot both be zero if there's no additional control being used! So how does FS differentiate between the two idles? I keep asking the same question in different ways but not yet getting a usable answer I'm afraid. :cry: It sounds as if your "flight idle" is in fact just a specific throttle setting ABOVE zero, else you wouldn't be able to use it to taxi? Isn't this measurable on some dial similar to N1 or N2 or EPR or RPM or something? Regards, Pete

Not simulating the pilot closing down at the end of his trip, then? just some cheat? Why not do as I've always done -- create a Flight with everything switched off and load that when I want to start off with everything switched off? After all, for many complex add-on panels this may be the only way, as they have many private subsystems which are not part of FS itself and therefore not accessible to FSUIPC. Regards, Pete

Does it say "you can attach files"in small print at bottom right of the Forum? If so, when you compose a message, at the bottpm there should be a button you can press to attach files. However, there is a low limit on size. If one of your files is a JPG it may be too big. In case of problem you can email it to me at petedowson@btconnect.com. Regards, Pete

Another thing which may be worth trying, if you are using an nVidia-based video card -- the latest drivers (52.16) are said to fix some (not all) black screen problems, and are faster too, so worth a try for sure. Regards, Pete

You would really do this by switching everything off, switch by switch. Simulating all that with one switch or button seems a bit odd. Why would that be needed? Pete

It will do. I was not suggesting that it would report zero frames or anything. but normally I'd expect it to be changing all the time when the simulation is running, and frozen when it isn't. So you need to check for changes. I'll look at other things tomorrow, not had time this weekend. Regards, Pete

There doesn't appear to be an attached Zip file for me to look at, but black screen type crashes are a known hazard with FS204 (and other programs using DirectX9, it seems). I cannot hold out much hope, but I'd like to see the Log please. The access violation it is trapping certainly sounds very odd. Regards, Pete

The reasons will be best found by checking the WideServer and WideClient.Log files. These will be found in the same folder as WideServer and WideClient, respectively. This tells me nothing useful, I'm afraid. It is best to ask PM questions at the PM support place. But show me the Log files which I can understand and we'll take it from there. By the way, please always use the latest versions -- FSUIPC is 3.11 and WideFS is 6.101. Regards, Pete

Ah, but I don't! :wink: What is the difference in terms of throttle value between "flight" and "ground" idles? They cannot both be zero, else how is the difference seen? Are you sure the difference is not a button press or switch instead of a throttle value? Regards, Pete

These are simply "centre" positions, just like those necessarily provided for Aileron, Elevator, Rudder, et cetera. Centre values are always 0 so there's no ambiguity, no problem. But how can I have two different types of zero? And there are no "stops" or "detentes" in FSUIPC at present, that is the problem. There are only Maximum/Centre/Minimum. I can apply those to any axis, that is not a problem. The maximum, centre, minimum values are self-evident and determinable. What is the value of a "flight idle" compared to a "ground idle"? They cannot both be zero I assume? So which one is zero, and then what is the other? Without knowing these things I can do nothing. And at present I do not want to start extending the current FSUIPC facilities by adding a new feature for "stops" or "detentes" when the time would be more beneficially be spent doing things more generally and in a less error-prone way. The stuff in FSUIPC has really been stretched further than was originally intended in any case and I fear to stretch it further may break it in too many places and cost much more time to then fix, for much less return. Regards, Pete

Do you know precisely how I can do this? I can understand full forward = 16384. Full reverse = -16384 * percentage reverse available (defined in AIR file or CFG), and idle = 0, but where do these other values get defined? How would I know what values to set for "flight Idle" relative to "Ground Idle"?, or "Min Prop" relative to "Startup/feather"? Aren't these very specific to the individual implementation by the aircraft maker? How do I find out? In any case it is too big a job to change the current axis facilities in FSUIPC. I do have on my list a big project to undertake which will certainly include such facilities, assuming I can understand them. It will probably be a separate optional module which works with FSUIPC and replace the Joystick pages therein. It will assign the axes too -- bypassing FS's facilities altogether, and so allowing full calibration and detailed "stops" (detentes), response curves, and maybe even button-mapping from specific axis positions. I will try to make this compatible with the current facilities, and therefore may still use the FSUIPC.INI file values where applicable, but add many new parameters. Unfortunately, trying to make time to fit this in is proving more difficult than I had hoped, so I don't see it being done this side of Christmas. I shall try to make space by denying some of the many other requests for a while. Regards, Pete

No, sorry. I really hoped that developers would be kind enough to purchase a full FSUIPC key. After all I do not make any charges for all the work I do on the SDK nor for the support I offer (though the FSUIPC user documentation does actually imply that support is for registered users only). If you have a personal FSUIPC key then you do not need keys for anything else. To simply test your own application's access key you can temporarily remove the FSUIPC.KEY file. Regards, Pete

I don't know them. Are they merely the EFIS displays? See FSUIPC offsets 0E5A to 0E68. All that stuff used to work with FS2000 but it's never been verified with FS2002 or FS2004. Let me know please. Regards, Pete