Pete Dowson

Okay, but now i need to repeat what I said before which I think you must have missed in trying to send me the same information again. Here, I'll repeat it all: You said in your original message: which is actually contradicted by the Log, here: Whenever it has said this it has always been true in the past. Far from being blocked, FSUIPC4 is running okay and creating its menu entry. This automatically results in an "Add-ons" menu item, the right-most in the standard menu. In your earlier (partial) log I see that you did go into the FSX menus in order to load a different flight: 842218 Sim stopped: average frame rate for last 709 secs = 19.0 fps 849312 Weather Mode now = Theme 849312 C:\Users\Jim\AppData\Roaming\Microsoft\FSX\Previous flight.FLT 882515 C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\Piper_J3Cub\Piper_J3Cub.AIR and also messed about in the Weather menu, changing modes: 1451437 Sim stopped: average frame rate for last 550 secs = 19.9 fps 5261000 Weather Mode now = Global 5263296 Weather Mode now = Custom so you certainly know where the menu is. Please just look to the right a bit for the Add-ons menu. Regards Pete

Ah. Completely different to what i reported to PMDG, then, which was an immediate rise to 512 and staying there. :-( Either way, these values are totally under PMDG control, they aren't FS readouts. Retry with no other FSUIPC clients running please, even remove WideServer from the INI file. If it is okay then we'll add them one by one. I doubt it. The other report said that the auto-start was the same. No axis input involved at all. I don't see how anything to do with throttles is related to starting. The throttle doesn't come into it. Have you reported these things to PMDG? I have no contact with them again at present. Timing of what? The values they use, it seems, are all theirs -- but they do calculate EPR, for instance, from FS's own N1 or N2. Those will be changing on each FS frame now, instead of less often. Did you try the other version (3.759) I attached above? It was the last one before I made some of these values available more often (for a smoother result on hardware gauges). The latter happened in 3.761. There was no 3.760 (I always have a non-zero 1/1000th digit for Betas). It is works okay in 3.759 I shall have to start on a process of elimination, to find out which values need to be "slowed down" again. Pete

Er, yes, is this relevant to anything? Incidentally, the FSUIPC4.LOG file you are showing still isn't "finished". you should close FSX down before getting the files! I'm curious as to why you've posted the same things again, plus the Install file. Did you read my last reply? And are you "James Brock" by any chance. Somehow you sent a message with the same log fragment attached to the Webmaster. Why? He was puzzled and just sent it to me. So now I've seen exactly the same partial file three times. Any reason? Pete

Not wanting to give up without more of a struggle, I've now uploaded 4.175 with a renewed attempt at getting wind smoothing working. I'm managed to reduce the stuttering, but i fear it may also be less effective. I won't be able to do a full flight test on it till later in the week, but please try it yourself and let me know. Regards Pete

Well, neither of these are complete files, and only the first fragment is a LOG file -- the other part you provided was part of the INI file (the one described as "configuration settings"), so I guess you must have double-clicked the wrong entries! You said in your original message: which is actually contradicted by the Log, here: 4093 FSUIPC Menu entry added Far from being blocked, FSUIPC4 is running okay and creating its menu entry. This automatically results in an "Add-ons" menu item, the right-most in the standard menu. I see later that you did go into the FSX menus in order to load a different flight: 842218 Sim stopped: average frame rate for last 709 secs = 19.0 fps 849312 Weather Mode now = Theme 849312 C:\Users\Jim\AppData\Roaming\Microsoft\FSX\Previous flight.FLT 882515 C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\Piper_J3Cub\Piper_J3Cub.AIR and also messed about in the Weather menu, changing modes: 1451437 Sim stopped: average frame rate for last 550 secs = 19.9 fps 5261000 Weather Mode now = Global 5263296 Weather Mode now = Custom so you certainly know where the menu is. Just look to the right a bit for the Add-ons menu. Please, if you show me a Log again, make it the complete Log. And the Install log should have a self-evident name (including the word "Install" as a clue!) so I cannot understand how you possibly missed it. Regards Pete

Okay. Try that Joyview program I sent above, please. That uses the same joystick interface as the Axis Assignments in FSUIPC3. Yes. The normal and long-standing way of calibrating FS's axes is to let FS read them, and ask FSUIPC to intercept the actual control values (aileron, elevator, etc) and "correct" them before they get to FS's simulation engine. You can have a mix of assignments in FS and FSUIPC as far as buttons are concerned -- just don't have any assigned in both if you don't want both actions to occur. Please just look at the User guide and skip the Axis Assignments section, which is an advanced and recently added capability mainly for very sophisticated actions, like auto-switching between helo and airliner and fighter controls, etc. Regards Pete

My PMDG contacts have been trying 3.763 for me with the 747 and cannot reproduce these problems, so this is likely to be quite a tough nut to crack. There's really no much FSUIPC involvement in any of the actions their code uses to start engines. Do you have any other FSUIPC client programs running at the same time? And when you say "and no EPR" do you mean no indication at all, or a constant value of 1.0? Regards Pete

I cannot find anything different about Engines 2-4 compared to Engine 1. According to my contact in PMDG the EGT read-out is from their code. The chap in PMDG cannot reproduce your problem, so we're a bit stuck in trying to understand this problem I'm afraid. You say "My guess is, some of the new features in the FSUIPC betas are conflicting with the custom PMDG 747 coding.", but the problem with that is -- there are no new features which have anything much to do with Engines, only this one: Which is basically just a change in timing. Anyway, I attach 3.759 -- this is the last I have before the above change (I no longer have 3.761 or 3.762, which only had changes to the Traffic Zapper anyway). Please try that ASAP and let me know. Oh, one more thing. When you say "and no EPR" do you mean no indication at all, or a constant value of 1.0? Pete FSUIPC3759.zip

Oh, right. Okay. So what range of values do you see in the FSUIPC axis assignments Tab. Do they move through the range, or jump from one extreme to the other? Ah .. it sounds like you somehow have the yoke set to a "digital" mode, like a Game Pad. Doesn't it show this behavious in the Game Controller (Windows) screen too? No. As I say, it sounds more like what you would get from one of the rockers on a gamepad, or a game pad joystick when set to "digital" instead of "analogue" mode. Strange. I've really no idea. All FSUIPC does here is read the axes directly instead of via FS. You didn't mention if it was FSUIPC3 or FSUIPC4 (for FSX) you are using, but FSUIPC4 uses the same system (DirectInput) as FS, whereas FSUIPC3 uses the old Windows API. What made you go direct to the total-FSUIPC rather than the easier (older, more established, less complicated) FSUIPC joystick calibrations of FS assignments method? If we are talking about FS2004 and FSUIPC3 here, it may be that the drivers for this yoke do not support the older Windows joystick interface very well. I attach a utility which uses the same interface -- you could check with that. If we are talking about FSX and FSUIPC4, then it is a real puzzle -- if it were acting like a digital pad via DirectInput it wouldn't be flyable through FS's assignments either. Regards Pete joyview.zip

Phew! Thank you! I was getting worried. What 4-engined prop are you using in FSX, BTW? I was going to have to ask you because I've not got one so couldn't properly test the prop pitch and mixture stuff, only in theory! ;-) Regards Pete

I assume you've claibrated them in Windows first? If not, that's your first step. Then check the Sensitivity and Null sliders in FS -- the sensitivity should be at maximum (full right) and the null zone full left. That should give you a "normal" FS response. For more control, calibrate in FSUIPC: follow the instructions in the FSUIPC User Guide, step by step. Regards Pete

If you have two throttles assigned, and map them as you say, AND you have a 3 or 4 engine aircraft loaded, then, in FSUIPC, you will only use the calibration sections for throttles 1 and 2. Ignore 3 and 4. I've made just those assignments here, and the throttles are operating the correct levers in FSX. They work fine, no matter whether I assign in FSX itself, or assign to FS controls (Axis throttle1 set and axis throtte2 set) in FSUIPC's Axis assignments, or even if I assign direct to FSUIPC in the axis assignments. The only odd-looking thing in that in at least one of those modes the Calibration screen may show the throttle 4 responding, and in the FS-assigned mode both the Throttle1 and 2 calibration IN/OUT values change when you move the throttle 1 lever (but #2 shows the calibrated values IN and OUT). None of this matters -- use the calibrations as normal. On your other reports: what does "can not be set" actually mean, please? I don't understand. Nothing at all in this area. Please review the list of changes posted in the "FSX Downloads" Announcement. The entry which refers to the fix you say worked is #9/ That's not been changed at all since then. I need more information, please. I cannot make anything go wrong here. Regards Pete

No, unfortunately I can't. I will need someone in PMDG to tell me what variable they are using which isn't looking right. As far as I am aware I've made no changes which should do anything like what you observe. I'll ask PMDG to look at this thread and let me know what may be amiss. Regards Pete

Sorry, what is this a list of? Where is this related to FSUIPC, please? I don't understand anything you are saying, I'm afraid. What is CTRL_G supposed to do, where? Could you refer to the things you are asking FSUIPC to do? What are you assigning and what to, and where (which Tab). What is the name of the thing you are assigning to? Et cetera. Do you mean the 0-9 keys on the keyboard, or are you referring to some FS controls? If you mean the FS controls "ATC Menu 0" to "ATC Menu 9", then you should know that all FSUIPC does is send them to FS. If FS is ignoring them, then FSUIPC can do nothing. I expect they aren't programmed in FSX any more -- there are a few strange things which occur when the ATC menu is displayed, like the keyboard elevator/aileron controls don't work either. I think Microsoft have programmed the ATC menu differently and are scanning the keyboard instead of processing controls. You may need to change your button assignments to send the 0-9 keypresses instead. Unfortunately it is quite common for controls listed in the Table in The FS CONTROLS.DLL to be left in, listed, even when the code for them is no longer there. Also, sometimes new ones are added but they run out of time and don't actually code them, though that certainly isn't the case here. Regards Pete

Oh dear. :cry: :roll: :cry: :roll: I said file TYPE "Log". I also said they were ordinary text files. You have your Explorer set in its stupidly annoying mode where it hides the file types for types it thinks it "knows"! You are reading descriptions, not filenames! Two of those files, no doubt the two text files, are type LOG! The "FSUIPC4 configurations settings" file is type INI. You'll need to understand that too, one day. Just double click on the text files!! Pete

As I said, they will be in the FSX Modules folder. That's a folder inside your FSX folder with the name "Modules". They are files of filetype LOG, and will be ordinary text files which will open with Notepad or any other editor. Just cut and paste their contents into a message here. If SimConnect is blocked then many add-ons cannot work. Pete

No, because more information is needed. Does it produce a Log (in the Modules folder of FSX)? Does it show an installation window with details? And the "error reporting tool" message has ways of getting lots more information -- I need some of that. Please take a closer look at it. But first and foremost I need the version. If it isn't the current one (4.16) go get that first please. Pete

They sound the same as the one I fixed. what's the difference? No. Can I see the Calibration and Axes sections of your INI file please? Pete

Yes, it works identically. I use it, with Radar Contact, all the time. FSUIPC4 does not intercept and re-direct FSX's own texts. I thought you said you used Radar Contact? It works with that and any external program providing messages. Regards Pete

The errors in the Event viewer are in no way related. They are "standard" errors reported by Windows every time you either Install FSUIPC4 or run FSX with FSUIPC4 installed, and they occur during initialisation. Please see the many other threads about this, or in particular this one: viewtopic.php?f=54&t=64737 CTDs when doing thinks like switching views tend to relate to video driver issues. See if it happens in Windowed mode. Try newer or older drivers. Try changing some of the video settings. Regards Pete

Show me the two Log files from the FSX Modules folder -- both the Install log, which shows the progress of the installation, and the FSUIPC4 log which will tell us what is wrong. It does sound like a normal SimConnect blockage, probably by your firewall, but the log s will tell us more. Regards Pete

Doesn't this completely depend on how the Airbus is implemented by the add-on aircraft maker? Or are you only concerned with the (rather poor, I've been told) implementation of the Airbus in FSX? From other support inquiries over the last few years I was under the impression that the specific throttle "detente" positions to which you refer were implemented in add-ons like those from PSS by specific keystrokes or controls, not by detente ranges on the throttle. If this is the case then the facility to calibrate such detentes is already most certainly present in FSUIPC -- it is handled by the assignment capabilities on the right-hand side of the Axis Assignments tab. I'd like to know a lot more first, as it is not a trivial job -- probably a week or two's sold programming and testing. I also suspect that it would still be easy enough to do it via the Axis Assignments facilities. You can program specific axis input ranges (your detentes, with a little leeway each side) to send the appropriate "Axis Throttle Set" controls with the parameter required to select the correct position in the FS aircraft implementation. In fact, the Flaps detentes could have been done this way too -- it is just that the latter facility was added long before I provided the more generalised axis assignments capabilities. Take a closer look. I'm sure you are missing something you can do already. Regards Pete

Sorry, could you explain in more detail what you mean? FSUIPC itself does not offer specific ATC facilities. Regards Pete

Not really, I don't know it. Not the FSUIPC Log. Show me the FSUIPC log, please. The complete log -- i.e. run FS, get the error, close FS, show me the FSUIPC Log file from the Modules folder. Well, 3.74 is not supported, it is too old. The oldest currently supported version is 3.75, as listed in the Announcements above. However, that won't be the reason. Try removing, temporarily, the FSUIPC.KEY file from the Modules folder, to make it appear unregistered. If it then works you have something wrong with your Key. If it is still the same the most likely causes are either (a) the DLL file is corrupt, causing the Signing check to fail, or (b) the codesigning root for GlobalSign is not installed on your PC. Checking the log should help determine which, though you can also right-click on the DLL itself, select Properties-Signature and see if it is correctly signed. For more details on codesigning and fixes, read the current documentation or the first few paragraphs in the "Other Downloads" Announcement above. Regards Pete

Possibly, though McAfee was one of the programs which caused problems with SimConnect in the early days. Maybe the re-install got that sorted. Glad it's all working for you now. Good flying! Regards Pete