-
Posts
38,265 -
Joined
-
Days Won
170
Content Type
Profiles
Forums
Events
Gallery
Downloads
Everything posted by Pete Dowson
-
PFC Throttle Qaudrant and Wilco A380 V2
Pete Dowson replied to phil mitchell's topic in FSUIPC Support Pete Dowson Modules
Yes. Airbuses are different. They don't have direct throttle control, but "fly-by-wire". The throttle merely sets different thrust modes. I suspect that, in order to implement this properly, Wilco have intercepted the regualr FS throttle controls and re-interpreting them accordingly. The PFC driver doesn't send the standard throttle controls, but operates the FS throttles directly, so bypassing Wilco's intercept. The only way around this is to assign the throttles in FSUIPC instead. In the quadrant section of the PFC driver disable the throttle (make a user configuration with your other levers, but no throttles enabled), then go into FSUIPC's axis assignments, move the throttles and assign them to the regular FS controls -- Axis Throttle1 Set - Axis Throttle 4 set. Then the Airbus should see them. Regards Pete -
Problem with button assignment
Pete Dowson replied to 3greens's topic in FSUIPC Support Pete Dowson Modules
"Z" is, by default, assigned to the FS control 'AP Master", to which of course you can also assign a joystick button in FS itself. If that is what is doing it then, as always, assigning to the control directly, in FSUIPC, is more efficient and often more effective. However, if I assigned that key press to my button, FSUIPC does recognise the input and saves the assignment but then nothing happens. I have tried both "momentary" and "hold down": same result. I must be missing something obvious... Two things wrong there: 1. With the button repeating whilst held, as you have set in the general button assignments, the AP control will be repeatedly sent, alternately turning the A/P off and on. You certainly don't want that! 2. You have the same button re-assigned specifically for the aircraft named "B737-700 Easy Jet - Stairs", so with that aircraft the assignment to 'Z' will be overruled. For that aircraft the same button will send control 65791, which is "AUTOPILOT OFF". If that is the aircraft you are testing it with, then it sounds like PMDG have re-used 'Z' for their Autopilot control, but are ignoring the FS controls. In that case you'd need to change your aircraft-specific assignment for that button to send Z too, or instead. If it isn't the aircraft you are testing it on, then something else is wrong. Enable Button logging in the Logging tab of FSUIPC and re-test, then paste the resulting FSUIPC.LOG text into a message here. Regards Pete -
Oddities from my TQ
Pete Dowson replied to richard hutchinson's topic in FSUIPC Support Pete Dowson Modules
I'm afraid you'll need to provide more information than that. For instance, are you using FSUIPC? If so, which version (the actual number)? Are you assigning in FSUIPC? If so how, exactly, and to which specific controls? And do you also have assignments in FSX, or are all controllers disabled there? Regards Pete -
Writing to an offset
Pete Dowson replied to Steve Johnson's topic in FSUIPC Support Pete Dowson Modules
Yes, FSUIPC can write to L:vars. This is by macros, and is described in the section called Gauge local variable access (L:vars), by macro in the FSUIPC4 Advanced User's document -- it is actually listed in the contents. Lua plug-ins can both read and write L:vars -- see the Lua library documentation (the ipc.readLvar and ipc.writeLvar functions). So, yes, they can be used to communicate between an XML gauge and FSUIPC4. Other Lua functions are supported for L:vars too. These are used in the example Lua plugin provded to log L:vars on screen. Regards Pete -
Registration Code Not Working
Pete Dowson replied to kevchris's topic in FSUIPC Support Pete Dowson Modules
Yes. FSUIPC4 is not FSUIPC3. It's a completely different version, not an update. You need to purchase a different registration. Pete -
Problem installing FSUIPC FS9
Pete Dowson replied to Alias's topic in FSUIPC Support Pete Dowson Modules
Oh dear. The details you sent me are for FSUIPC4, and clearly say so. You cannot use your FSUIPC4 key for FSUIPC3! Pete -
Writing to an offset
Pete Dowson replied to Steve Johnson's topic in FSUIPC Support Pete Dowson Modules
Not that I know of. They are worlds apart. How can FS even understand that FSUIPC accepts Lua plug-ins? If your XML can send a keypress to the main FS window, then you could program that keypress to execute a Lua file. But of course there's no need to have a Lua file then --- there's an Offset control assignable in FSUIPC which can write 1 to 66C0 in any case. I'm really not understanding why your XML is processing a button press in any case. Why not program the button in FSUIPC in the first place? It can write your Lvar (e.g. via Lua) and set 66C0. What is the custom XML gauge for? Regards Pete -
Problem installing FSUIPC FS9
Pete Dowson replied to Alias's topic in FSUIPC Support Pete Dowson Modules
Have you run the FSUIPC 3.98 installer? The registration should be performed there, as described in the Installation documentation provided, NOT in FSUIPC Options with FS running. That is the old method, and to do that you need to take special precautions (also described, but only in the User Guide which gets installed).. Please re-run the Installer and register there. Then tell me what happened. Sorry, I don't understand what you are saying. if you still get a problem Registering in the installer, as documented, please send me an email with all the three parts of the Registration and I will try it here. As there's been no change at all in any of that part of the program I cannot understand why there's any problem, but I can check. Email to petedowson@btconnect.com . Regards Pete -
GoFlight EFIS -FSUIPC
Pete Dowson replied to wolkenschieber's topic in FSUIPC Support Pete Dowson Modules
You are evidently NOT placing it into the correct folder. Are you sure you do not have more than one FSX installation? In the Modules folder you are talking about, it there an FSUIPC4.LOG and FSUIPC4.INI with a recent date and time (of your last FS session)? If not, you are looking in the wrong folder! Maybe you have some security setting such that you can't access the right folder? Just in case, try starting Windows Explorer by right-clicking it and selecting "Run as administrator". Then look or copy again. Also be aware that you cannot change FSUIPC4.DLL whilst FSX is running. Maybe you are thinking you've copied the file in but it failed because of that? No one else has ever reported any problem with installing updates like this. It has always just been a simple matter of overwriting the old version! Pete -
Writing to an offset
Pete Dowson replied to Steve Johnson's topic in FSUIPC Support Pete Dowson Modules
XML file? I assume you mean Lua? If so that should work fine. You must have something else wrong. Show me the complete file. did you check the log to see if there were errors listed for the Lua program? Enable button logging as well as your 66C0 monitoring and show me the resulting log, please. If you are really talking about an XML gauge, then I'm afraid you are mixing up the FSUIPC plug-in Lua facilities with FS's XML facilities. They aren't the same things. FSUIPC doesn't understand XML and FS doesn't understand Lua. Pete -
Do the throttle levers actually give you those values? It is most unusual, because even the best joysticks don't give full range, even digital ones. That's why calibration is needed, to map whatever values come from the joystick to the full range (-16384 to +16383) accepted by FS. In any case, even if your joysdtick is giving such unusual 'ideal' values, you should allow a little leeway at either end to account for variations -- readings can vary due to temperature, humidity, voltage and ... dirt. The is why the calibration steps numbered in the FSUIPC User Guide include parts which tell you to how to do the whole thing. I don't know a lot about Airbuses, but don't they only use the throttle levers to set thrust "modes", not to actually control the thrust? If you have everything working with other aircraft, then I think, for that particular add-on, you need help from someone who knows the aircraft. Maybe it needs specific keypress combinations sent for the different modes? You can assign controls to be sent by FSUIPC at different points along the throttle axis -- this is done on the right-hand side of the FSUIPC axis assignment tab. Regards Pete
-
Problem installing FSUIPC FS9
Pete Dowson replied to Alias's topic in FSUIPC Support Pete Dowson Modules
Whoops! No! Sorry! Part way through replying I switched to FSX mode! :neutral: No, 3.98 is fine. Just make sure your entries for Registration are all exactly correct, not just the code itself. The correct email is the one at tele2.it. I'm editing my original reply too to avoid confusing other readers! Regards Pete -
Wanting to have a flaps lever, small problem
Pete Dowson replied to Thralni's topic in FSUIPC Support Pete Dowson Modules
Really? I don't know how that is possible unless somehow you axis is giving larger input values at each end compared to the middle. Note that, for flaps (and spoilers too, in fact), you usually want to REVerse the axis, so that flaps up (and spoilers down) are at the full forward position, as on the aircraft, not full back as with throttle levers. If you want this, be sure to select REVerse before calibrating. With FS assignment you can select reverse in the FS assignments dialogue. If calibrating in FSUIPC you can use the checkbox there. Just don't reverse it in both places (obviously?) and calibrate after reversing, not before, or the numbers will be wrong. Look at the FSUIPC calibration. What are the numbers, both IN and OUT, shown in FSUIPC for each of those three positions? And one intermediate position both ways? And what numbers do you have showing below the Min and Max 'SET' buttons? I'd like to see some actual information, please. If you actually calibrated the Flaps 0 position of the lever by pressing the minimum "Set" button when the lever was there, then when you again place the lever there, the OUT value should show 0 no matter what the IN value. That's the whole point of calibration -- to get the desired input values from whatever range of external values your device (or its driver, rather) generates. But it will not (cannot) handle an axis which has a "parabolic response curve"! For FSUIPC calibration, it is the FSUIPC User Manual. Where else? There's a chapter in it about calibration and that contains numbered steps to follow. Regards Pete -
Problem installing FSUIPC FS9
Pete Dowson replied to Alias's topic in FSUIPC Support Pete Dowson Modules
The registration codes for FSUIPC3 have never changed. But the signature check has because the old signature expired. Make sure you installed 3.98 so that the signature is valid.. The registration needs your name, email and code all EXACTLY as when purchased. It doesn't matter if you changed your email address since, you enter the original. If any of those three things are wrong, the code will be rejected. If you are being told it is invalid, you are entering something wrong in one of those three fields. If the symptom is that it is accepted, but then FSUIPC doesn't work, check that you did install 3.98, and that the system date on your PC is correct. Regards Pete [This is an EDITED reply] -
flap settings carando bonanza
Pete Dowson replied to wpkm's topic in FSUIPC Support Pete Dowson Modules
FSUIPC can't change the defined postions for an aircraft. However, I think you can, perhaps quite easily. I'm reasonably sure that the flap positions are defined in the AIRCRAFT.CFG file, so you may be able to insert the 10 position there. What that will do to the on-screen graphic is another matter, though hopefully it should stop somewhere between 0 and 15. If you need help on this I'm not the right person. You want to ask in an Aircraft design forum, maybe in AVSIM. Shouldn't you write to Carenado and ask them to fix the aircraft anyway? I thought they prided themselves on their fidelity? Regards Pete -
FSX APPCRASH Fault Module FSUIPC4.dll_unloaded
Pete Dowson replied to idahosur's topic in FSUIPC Support Pete Dowson Modules
I get that too, some of the time. In my case it is mostly something to do with Ultimate Traffic 2. I think that in the various threads of FSX there are some which continue for a while to cross-refer to objects or memory which get freed earlier during the shutdown process. I think these are, in particular, related to SimConnect use -- and FSUIPC, Ultimate Traffic, ASE and many others (external to FSX like UT2, ASE, and internal like FSUIPC) are heavy SimConnect users. I suspect that the more SimConnect users there are the more chance of the crash on termination. Sometimes it just hangs (no windows, just "exists" in the background, invisibly except in the Process list), and has to be thrown off with Task Manager. It doesn't happen to me with only FSUIPC installed. If i stop UT2 and several other SimConnect programs running, everything is always okay. I am sure this is a SimConnect bug, and I know of no fix -- and it will never get fixed now. Luckily it only happens when you are closing FS in any case, so it is of no real consequence --- excepting that if you made changes to the FSX settings, they may not be saved. Unlike FSUIPC, settings in FSX are not saved until termination. I tend to make changes directly to my FSX.CFG file these days in any case, as there are some non-standard entries in there which get reset if you use the FSX settings dialogues. This is what happens with bugs which are intermittent (as they are in my case). It is very timing dependent. Your new machine is just executing the different threads in different times. It may even be using more cores. Could be anything like that. Regards Pete -
Wanting to have a flaps lever, small problem
Pete Dowson replied to Thralni's topic in FSUIPC Support Pete Dowson Modules
FSUIPC can only calibrate aircraft controls assigned to do something. You must assign your axis first. Why try to run before you can even toddle? Try doing things in FS itslef, first. Assign the flaps lever in FS, check that it works. THEN, maybe, try using FSUIPC to get specific positions calibrated, or other desired results. FSUIPC cannot work magic, it cannot read your mind! Assignment of axes, like button and key presses, is a subject which you need to deal with in FS first. If you don't understand it in FS you've no chance in anything more sophisticated. So try FS first, eh? Your second message (though labelled "EDIT" it was actually a separate post!): If you cannot understand how to do things in FS I'm afraid FSUIPC is not for you. It doesn't make FS easier, it makes it more flexible and more powerful in what you can do. That's the last thing you want to get involved in. I suggest you first take several steps back and read some of the Microsoft Help for FS. Maybe ask questions over in the FS Forum. All that is sorted, eventually, by calibration. I think you may be getting ahead of yourself, but if you calibrated the lowest value from your axis as the minimum, that would equate it to -16383 and therefore to flaps 0, of course, and similarly calibrating the maximum would take care of full or maximum flaps. That IS what calibration means -- matching the input values from your axes to the desired range within FS. If that is truly beyond you, which I don't believe for one minute, then I'm afraid I can't really help. I can't explain it any simpler really. Try just following the numbered calibration steps in the User Guide. It surely can't hurt to try using the documentation now and then? ;-) Incidentally, I'm really rather loathe to assist Saitek is doing support which they should really do in any case. They are not my 'flavour of the month' -- or even of the year. I am even thinking of removing support from FSUIPC for their devices. Pete -
Not a lot, because the WideServer one was from a run where it was working. Obviously I'd need to see the log when it didn't, else there's little point. This is why there's no useful information in the logs. Incidentally, the WideClient log is incomplete and shows no connection. it seems to be for a completely different time to the WideServer log. Okay. Thanks. Regards Pete
-
GoFlight EFIS -FSUIPC
Pete Dowson replied to wolkenschieber's topic in FSUIPC Support Pete Dowson Modules
Okay, found it. It was a bug in FSUIPC4. I don't know how long it's been there, but quite a long time. Odd no one's spotted it and reported it before. So, thanks ... It is fixed in FSUIPC 4.634, now downloadable via the Download Links subforum as before. Please do make sure you are putting the update in the right place, though! Regards Pete -
It may well be the cause off odd messages on screen, but I am at a loss to think how it could be preventing the WideServer part of FSUIPC4 from starting. That should start up a few seconds after you are ready to fly --- not straightway, but after not too many seconds. In the Menu bar! So, Traffic X is adding things to the Menu? Again I don't see any way that relates to WideServer. No. Best to paste their contents into your message. You can enclose them with "code" parentheses to keep their format intact and make longer files scrollable. The "code" button is the one like <>. Not sure what the file attachment rules are here, but be sure you ARE talking about the WideServer.log and WideClient.log files. They are simple text files in any case, so just use Notepad or similar to view them, select all and paste. It might be a good idea to include the FSUIPC4.log file too, please. Could you possibly use a darker colour for your quoted test -- pale pink is difficult to read? Or, better, use the quotation parentheses (select the text and use the button which looks like a comic's speech bubble). Regards Pete
-
Auto Throttle Problems
Pete Dowson replied to kunibert81's topic in FSUIPC Support Pete Dowson Modules
So that's what should happen. The A/T controls the throttle when engaged -- you don't. Another add-on? Your throttle should be left alone, doing nothing when you have autothrottle enabled. Why are you trying to use it with A/T engaged? Just leave it alone. I think you need to explain what it is you are doing and what you think the throttle lever should be doing when you have A/T engaged. Your original report included this statement: which implied that you were expecting to use the lever to set different Airbus thrust modes. You might be able to do that, but it probably needs special programming, depending on the add-on. FSX's Airbus doesn't really simulate the thrust modes as far as I know. Except for specially programmed Airbus add-ons, you don't use your throttle lever in A/T modes. Pete -
GoFlight EFIS -FSUIPC
Pete Dowson replied to wolkenschieber's topic in FSUIPC Support Pete Dowson Modules
Strange. It certainly worked originally. I'll check it here. The internal commands are different for the two aircraft, but FSUIPC sends both. Starting picture? Do you mean the "About" tab in FSUIPC4 Options? If that still says 4.60a, then that is what you have in your FSX Modules folder. 4.633 will display 4.633 and the date 14th November 2010. The Log file will also bear that number, and there will be an entry in the FSUIPC4.INI file saying "UpdatedByVersion=4633". Use windows Explorer, go to the FSX Modules folder, and right-clcik on FSUIPC4.DLL. Select Properties-Version. That'll confirm what I am sayting. Perhaps you have two FSX installations and copied to the wrong one? Perhaps you forgot to Unzip the DLL from the ZIP file you downloaded? Pete -
Auto Throttle Problems
Pete Dowson replied to kunibert81's topic in FSUIPC Support Pete Dowson Modules
Test with a default aircraft like the FSX 737-800. If it is okay with those, then it is working. Add-on Airbus implementations tend to use different controls to set the different throttle modes. Check their documentation. They might need keypress combinations to set the different modes. You can assign keypresses and other controls to areas of your throttle axes, using the right-hand side of the FSUIPC assignment tab. Another consideration is this: normally, with FS aircraft, the throttle lever is disconnected when using autothrottle -- airbus throttle modes need special treatment. Maybe you are assigning the throttles in FSUIPC for "Direct to FSUIPC calibration", and not to the FS controls? If you do that you are likely to bypass the code in the add-on Airbus which uses the throttle position to determine the thrust mode. Use the other assignment mode for such aircraft. Regards Pete -
Downloadproblem, WideClient 6.833
Pete Dowson replied to Bakern's topic in FSUIPC Support Pete Dowson Modules
Ah. This time it failed as follows, still reporting your mailbox full but also preventing it for a second reason: Seems you or your ISP has set a high level of protection which disallows all files which look like programs (in this case an EXE). I'll try renaming it and resending. After unzipping you'll need to rename it back to WideClient.exe. Pete -
flap settings carando bonanza
Pete Dowson replied to wpkm's topic in FSUIPC Support Pete Dowson Modules
If you are using Flaps INCR and Flaps DECR controls, there is no way you can miss any of the flap positions. You must be hitting the button twice to miss one. Assigning in FSUIPC is exactly the same as assigning in FS for all FS controls, and the Flap inc/dec controls are the ones assigned by default, in FS, to your F7 and F6 keys, respectively. If those work, the exact same controls send from button assignments must also work unless the button is bouncing and sending two or more such controls. Pete