Pete Dowson

You've not tried Radar Contact, then, because that uses no synthesised voices. All of them are recorded by a band of volunteers, they are all human. I also use IYP, which does use speech synthesis, and I agree with you regarding the default speech engine voices and many of the cheaper ones, but the more expensive ones (25-40 UKP each) are very good indeed. I wouldn't spend that much for ATC voices because you need too many different ones, but for IYP acting as a copilot you only need the one. I actually bought two -- a UK male and a UK female, and sometiimes switch. Regards Pete

Okay, that's good. You must have actually run wideclient.exe then - it doesn't run itself (unless you put it into Windows' "start up" folder! ;-) No need. If it connects it is working. That part is nothing to do with WideFS. The program is asking for the path to your FS installation so that it can read files. You need to meet those sorts of requirements by sharing folders and giving the correct network paths to the program. I can't help with that, it is an FS Commander problem. I'm pretty certainly it must be covered in the FSC manual, but if not you need to go to FSC support. Sorry, but I don't know the program. Regards Pete

This is all only true in North America, of course. the rest of the world uses various Transition Altitudes when climbing and Transition Levels when descending, ranging from 3000 feet or so to, yes, 18,000 (though not many that high as far as I know).. No, sorry, there is no way FSUIPC or anything else can come between the built-in faulty ATC and the built in weather system. The solution most folks use for the poor FS ATC is to use thrid party applications, such as Radar Contact (good for IFR) and VoxATC (good for VFR). These also have the benefit of understanding that there's a world outside of North America. ;-) Regards Pete

I don't think it is there normally, so you would have had to add it. Instead of assigning the throttles "direct to FSUIPC calibration", please assign them to the FS controls, "axis throttle1 set" and "axis throttle2 set". The 'direct to calibration' method bypasses FS and I think the PMDG needs to see them. I hadn't realised you were doing that. Is that with the "sync pos" method of calibration, because you only mentioned 40-50% business in that context I think? I'll check the numbers here in any case. Regards Pete

Either of the two ways you've discovered would work. The one using virtual buttons gives you more flexibility in that you can assign the buttons as you like, and change them more easily, or assign then differently for different aircraft (using profiles). Pete

I don't know what "it" is in that statement. Link what? Why not just assign the buttons to whatever you want them to do, in FSUIPC's button assignments Tab? That's the whole reason for setting the buttons, surely? I don't understand how this relates to your original question on invoking a macro by using offset 0D70. Have you changed subjects? Regards Pete

I don't know HIDMacros, but your previous effort wouldn't work because you were using a very old version of FSUIPC which didn't have the facilty you were trying. So what's he problem now? Pete

All your settings are in the INI file. Reinstalling FSUIPC won't do anything, unless you take the opportunity to update. If you want to start afresh with settings, just rename the INI file. Well we can do some logging but just logging everything without knowing precisely what we are doing will just generate heaps of data with no way of analysing it. I need to know more about what the problem really is first, and that includes showing the INI file section with the sync pos settings which you said didn't work and stopped one axis going to idle (as I asked earlier). Regards Pete

Sounds like you have some assigned as either Profile or Aircraft specific, and those obviously won't load when flying with a different aircraft. Just check what you are doing. the current aircraft or profile for assignments is displayed in the title bar in the relevant assignment tabs. Pete

4.30? That is VERY old!, well over 3 years!!! That facility wasn't even in that version! I can't support anything older than 4.80! Pete

There's a Japanese language site, otherwise you can buy it packaged with Project Magenta when you buy a system from them. There's no other way. Regards Pete

Try version 3.999e, now available. I added the same mouse code to the two hooked child windows as well as the main one. I've also put a small improvement in to make it easier to get out of a "stuck right button" situation, which can happen if you use the feature on a part of the screen which induces a pop-up menu on right button press. This is a problem because I then don't see the button up (all messages are diverted to the popup menu). After you've dealt with the popup, or escaped from it, I cancel the swap on the next left button press (provided of course that you've not re-selected the swap action). That improvement is also in 4.804, so you'll need to update. Regards Pete

The only thing wrong with what you have is the automatic axis assignments to the profile. That should be optional. There's really no reason to start again each time. Anyway, 4.804 is up, now. http://fsuipc.simflight.com/beta/FSUIPC4804.zip I'm just updating the announcement. Regards Pete

Why are you repeating yourself? No, you had NOT! You assigned the buttons BEFORE clicking the Profile Specific checkbox, so those buttons are in the generic assignments, applied to all aircraft. with buttons and keys you can switch back and forth as you like, changing the generic or specific assignments, because they all apply -- except that the same button or key assigned specifically overrides one assigned generically. No buttons assigned because you assigned none. As I've explained before, and the axes were wrongly profile assigned because of a bug I've just fixed here and will be okay in 4.804 as soon as i can get around to uploading it! Of course they can! And for buttons and keys, both apply, with Profile ones taking precedence on duplicates. I've said all this before! With axes and calibrations, for the reasons i explained already, only the profile ones apply if both are present. Yes, of course it is valid, but your axes probably won't work in any aircraft, profile or not, because you've assigned them all "Direct to FSUIPC Calibration" but haven't (yet?) calibrated any of them. Pete

Not sure quoted out of context like that, but they are related to FSUIPC Offset controls. The encodings for all of the FSUIPC offset controls are detailed in the Advanced User's guide (in the "additional FS controls added by FSUIPC" section). The one starting x51 is listed there as "Offset Byte Cyclic Increment". The parameter of x00030001 would indicate an increment of 1 and a limit of 3. You can assign to these controls in the normal assignments tab. They are listed by name. If you need the decoding, use the list in the document. Yes, on the Logging tab, right-hand side. Put the offset in the monitoring list (you can monitor up to 4 places at the same time), select the type of value (eg U8 for unsigned 8-bit value), the select an option below -- display for on-screen in real time, or log, for logging, or both. These facilities are described in the documentation too. Regards Pete

Best to see if one of the regularly updated offsets are changing. Usually a timer is best. Offset 0310, for example. You'need to check whether it changed since you last read it. Regards Pete

I've moved this from the Download Links subforum, as it is not providing any download links and is actually a Support question. Please use the Support Forum for support. Thank you. Sorry, is that a question for me? Sorry, I'm lost. Which facility are you calling "mouseview"? The FSX mouse look, the FSUIPC mouse look, or the FSUIPC mouse move? I've not documented a "mouseview" and am unsure what you mean here. There's nothing in FSUIPC to make a cross appear. That's the FSX mouse look. It sounds like you are using FSX's "toggle mouse look", which would conflict with FSUIPC's mouselook. I don't know what you mean by "the rightbutton menu is checked". Sorry, I really have no idea what you are doing or expecting. Does your mouse have a middle button? If so, try simply enabling Mouse Look in FSUIPC's Miscellaneous tab, then, in virtual cockpit mode, hold the middle button down and drag the mouse around. That's "mouse look". You can assign controls to buttons or keys to do it too -- I'd recomment assigning "mouselook on" to press, and "mouselook off" to release, with no repeats, for best usability. Mouse look isn't a new facility in this version of FSUIPC. It previously operated only using the FSX toggle control, but that always resets the position first. That method still works, but don't use both. Regards Pete

I'm just abut to try to test the way you have listed, but before I do that the first question is: Why do you expect there to be any Profile Specific buttons in the INI when you didn't assign any? All the assignments are in the generic section, which applies to all aircraft. Assignments made Profile Specific are just the extra ones or overrides for the psecific profile, yet, according ytoy your sequence ofg actions you never actually made any such assignments. That's why there's no Profile specific buttons section. You have something else going on there, then. Detection of joysticks is nothing at all to do with profiles and hasn't been changed in years. If that sort of thing persists we'll need to investigate it separately. As documented, is sets the button repeat and delay to repeat timings. See the Advanced Users guide. That is the standard default setting. I'm starting to get the feeling that much of what you are reporting an a problem is in fact a result of a misunderstanding of how Profiles work. Generic (non-profile specific) assignments to buttons and keys apply to ALL aircraft unless explicitly overridden by Profile-specific assignments. You only need to assign the differences, not reassign everything. All of the more generally applicable buttons or keys will therefore be easy to do. Axis assignment and joystick calibration is different. It would be wrong to apply generic settings to specific aircraft if those settings are not overridden, because axes, unlike keys and buttons, are effectively always active. You wouldnt want a yoke used in a helicopter if you had a profile specific G-stick assigned for it instead, because the yoke could interfere quite easily. Anyway, the only problem I've found is that if you select Profile specific for Buttons, Keys or Calibrations, it automatically selects Profiles for Axis assignments as well, with a copy of your generic assignmnents. This happened to you, and it is wrong -- they should be individually selectable (not to different Profiles, but whether they are specific or not). I'll fix that now. Everything else works fine here. Regards Pete

I'll check all this when I get back. I'm out all morning. The events above aren't actually the same as those you described earlier. Regards Pete

You shouldn't need to do that. Here it works by simply holding the button down -- the PMDG NGX keeps updating the dials until the button is released! On a touchscreen I assumed you'd simply keep the dial "touched". I don't see any point in such an option when it holds whilst the button is pressed in any case. I'm afraid I don't have any FS9 aaircraft which uses this sort of facility, but it might happen if the aircraft uses a child window not the main FS window. I don't hook child windows in FSUIPC3 because there was never any need to. I'll check into that, but without the aircraft it isn't going to be easy -- or just a lot more code to intercept all the needed windows. I was going to say earlier that I'd rather only add new facilities to FSUIPC4, looking more to the current and future sims, rather than encourage folks even more to stay on FS9 (for which I'd originally ceased development several years ago, after al it is now over eight years old!), but I added it there too because the code was so simple. Regards Pete

There wouldn't be any interaction unless the Duke is using some FS control for its fuel switches which you've reassigned in FSUIPC. That doesn't seem likely. I assume you mean 'grab and turn' using the mouse? The only similar problem I've ever seen is with the MCP knobs in the PMDG 737NGX, which won't work properly if the Cowl Flaps 1 axis is calibrated in FSUIPC. For some odd reason, that control is used in the NGX to operate those knobs! Your calibrations don't seem to include anything likely to be re-used by the aircraft for anything different: Elevator=-16223,0,0,16383 Throttle1=-16380,-512,512,16380 Aileron=-16384,0,0,16383 Rudder=-16384,0,0,16383 Throttle=-16384,16383 PropPitch=-16384,16383 Mixture=-16384,16383 LeftBrake=-16384,16383/16 RightBrake=-16384,16383/16 Though you seem to have both the generic all-engine throttle calibrated as well aas the separate Engine 1 throttle. You should really only use one or the other. If you want two separate axes for the same job, assign them the same way, or make the two ways specific to different profiles. Also, most of those calibration values appear to be default values, except oddly the one extreme of the elevator. You need to consider following the calibration steps and leaving small dead zones at either ends. To see if the fuel switches are using some odd control which may conflict, enable both Event logging options (two checkmarks) in the Logging tab, then try the switches, and see what it reported in the Log. Regards Pete

Fixed now. Regards Pete

I've tried all sorts of ways to make this happen, and I can't. no matter what I do, everything works as it should. Could you do this for me, please: First make a copy of your INI file so far, in case you do manage to mess it up. Then reproduce the problem you describe above, but write down every little step you take to do it. I will need to do it in exactly the same way here. Let me know, please. BTW, I have found out what you mean about reconnecting to a different USB socket. I'm working on that now. That can't be a new problem. [LATER] Okay, that latter problem, it's a Windows thing. I couldn't get FSUIPC to see the device at all after moving it to a different USB port. Deleting that section in the INI doesn't help. That's irrelevant i think. Only closing FSX and reloading it will get it back OR simply reconnecting it on the original USB socket. The DirectInput routine reports an "access denied" error. I think moving the device gets it into a confused state, only resolving when that process (FSX in this case) is closed and restarted. This is actually a lot more than FSX can do -- FSX only ever scans devices when it initialises. If you connect one later it won't see it, unlike FSUIPC, and if you unplug one, that's it. It loses it until you restart. I think FSUIPC's treatment is far superior! ;-) I just need the step-by-step account of your Profile problem, now. As I said, I've tried all sorts of things and cannot break it, so far. Regards Pete

That's weird. I haven't got that to go wrong here. but I'll try with your settings . You don't get a section created until there's a reason -- i.e. in this case, after you actually calibrate one of the axes. If you move to a different USB socket then the joystick ID number will change, so all the assignments made before won't apply. If you want the flexibility of being able to move things around you need to use Joy Letters instead of the numbers. Then FSUIPC can keep track. I'm trying to figure out what you are seeing, but it is getting late here and I'm not sure I can do it so soon. It might need to wait till tomorrow now and I'm out in the morning. Regards Pete ..

No, I didn't say that. You can but they have to be two separate assignments, on two lines. Regards Pete