Pete Dowson

You should probably select Axis throttle set instead. The Throttle set controls are the original FS98 controls which have a reverse zone. it is possible that the Airbus doesn't like those. If you assigned in the sim itself it would be the Axis throttle set controls. Pete

This is explained in the installation guide provided in the ZIP you downloaded for FSUIPC7. Please do read that! Pete

You don't "add it". Unlike previous versions of FSUIPC, version 7 is an "EXE" -- a free standing program. You can run it and MSFS independently. If MSFS is running, FSUIPC7 will connect to it. There is an (optional) short cut provided. and put on your desktop. to start both FSUIPC7 and MSFS. If that isn't working then that's another matter. You'll need to provide more details so that John can work out why. But you don't need to use it -- you can start MSFS and when it is up and running, run FSUIPC7. Or vice versa. I think John is working on a way for MSFS to be started and automatically load and run FSUIPC7, but would be an enhancement planned for a new release. Pete

Sorry, what are you wanting FSUIPC to do with this card? Are you talking about WideFS connecting to a networked PC? WideFS doesn't work with tablets, only Windows PCs. Is "fsradiopanel" some add-on which uses FSUIPC? If it's a tablet App and wishes to talk to FSUIPC it should come supplied with some sort of server program which you run on the PC. Configuring the link would be a matter of parameters in the App I would think. FSUIPC doesn't support links from tablets directly. Pete

Just for clarification, those numbers are not "offsets", but control or event numbers, as listed in the supplied controls lists. "Offsets" are addresses of slots containing data for programs to read and write. They are not controls, though when written some do invoke controls. Pete

Yes, sounds reasonablye. You can then only be 10 secs late detecting TOD. In fact, assuming a speed of, say, 500 knots cruise, you could use 100 seconds and still only be about 1.5 nm late at max (less than 1 nm on average). Sorry, you've lost me there. i didn't understand any of that. 😞 Pete

Yes, there should be a neutral zone, when the engine is idling. You use the central zone calibration to set its size and position on your particular throttle controls. You need to calibrate to make it easy and certain to set idle properly and with stability. Pete

In the case of the "ask" substitute, you' wouldn't want to delay the supply of the reply and the termination of the plug-in. So check at the sort of period you would allow for the reply to be entered, whether long or short. And terminate as soon as done so it can be invoked again if needed rather than wait for the expiry of the time allowed. In your new one i assume you'll want to check for the arrival at TOD more often than 5 minutes or you could be 5 minutes late in detecting it. I don't know of any specific limit on the timer -- it is using a facility in Windows Looking at that it says: so the max timer works out at 2,147,483 seconds, or nearly 25 days. Pete

Yes, that is the correct way to do it. But surely you will have just one profile for all Twin-Engine-GA aircraft -- except for those needing specific treatment such as any from PMDG or FSL. I don't understand the problem. It surely must be the actual value being fed to the aircraft controls which matters in terms of calibrating -- you calibrate to suit the aircraft type. They are all different. Using the same aileron/elevator calibration for a fighter or stunt aircraft as for a light trainer would not be right. "Maintain"? How often do you change calibrations once you get them right? Sorry, either I am still misunderstanding your problem or you are misunderstanding what FSUIPC calibration is about -- i.e. allowing you to get the best results with each aircraft. Perhaps you are making separate profiles for every individual aircraft. I would advise thinking more in terms of aircraft types and grouping them into fewer profiles accordingly. Also please note that the calibration facilities in FSUIPC work on controls assigned in the Sim. The ability to assign axes in FSUIPC was added not only for access to more axis controls than offered in the sim's UI, but also so that different aircraft could use different controls (eg joystick for Airbus, Yoke for Boeing). Pete

Weather file corruptions are the most usual cause of weird crashes in different places. Try setting NoWeatherAtAll=Yes in the [General] section of FSUIPC4.INI. That stops it asking for weather data from SimConnect and so doesn't force SimConnect to read the bad data. If that seems to fix it, remove that added parameter and instead find and delete your wxstationlist.bin file in your FSX AppData folder, and all of the saved .wx files in your FSX Documents folder. The bin file wil be regenerated next time you run FSX, and .wx files are created each time you save a flight. If that doesn't help, then I'm sorry but I can't really help. I think yo will need to do a process of elimination. Start by removing that RecorderFSX.DLL. Although you weren't using it at the time those tow crashes in it certainly occurred when it was doing something. Incidentally, the FSX log file you provided doesn't show anything -- FSUIPC closed down tidily when SimConnect called it to say FSX was closing (tidily). No crash. Pete

You should be able to do that with FSUIPC's normal calibration facilities. Those are its main calibration points. Pete

You'd have to process the Shift key as well to decide whether it is upper or lower case. Check the definition of event.key. You'll see you can specify which shift keys you are wanting, and the value of the Shift settings is supplied to your function. Pete

That's pretty realistic with real-life aircraft too. Maybe they line up better when brand new, but they don't stay that way. FSUIPC doesn't calibrate axes, but axis controls. It's the value being used in the Sim which is adjusted. Pete

You seem to misunderstand. The KEYCODES are not ASCII character codes, they are numbers representing the physical key. The numbers 96-105 ARE the ASCII codes for a-j. If you try to display them as characters that is what you will see! You need ot convert them in your program if you want the characters 0-9. For exactly the same reason! The KEYCODES for the A-Z keys (and they are marked like that) are 65-90, which are the ASCII codes for A-Z, not a-z. Please read my previous explanation again. You persist in thinking that Keycodes are ASCII character codes when they are not. Check for yourself -- compare an ASCII table (on the Internet, probably wikipedia) with the Keycode list I referred you to. Pete

This is my sig on another Foum: Win10: 2004 build 19041.685 Processor: I9 9900KS at 5.5GHz Mobo: Maximus XI Extreme Z390 Memory: 32Gb at 3900 MHz. GPU: RTX 24Gb Titan Displays: 2 x 2160p projectors at 30Hz onto 200 FOV curved screen P3D5 set with 2 windows using ViewGroups Don't ask how much that lot cost! But compared to the cockpit, originally bought from PFC some 20 years ago, with all the money lavished on that with updates and upgrades over the years, the PC system (and its external Koolance cooling system) was minor. I use AIG's free stuff, excellent. I've installed all airlines. Total data size about 41 Gb! If I don't limit it I get 500 or more around London some times of the day. i have to get it down to 160 or so with the limiter in FSUIPC. Wow! A practical man! I can do electrics but for anything else, forget it. It's a good job I was good at programming (supposed to be retired now, but i still dabble). Well, yes, at present. For something like my setup I don't think MSFS will be good enough this year -- for airliner flying. It already makes a good VFR sim though (I have it on a different PC with a single screen), albeit pretty unreliable. Pete

Well it is for me, mainly because it's performance is so good in comparison. But I am using one P3D5 PC with two projectors to give me a 210 degree FOV on a curved screen. With P3D4 and before each additional scenery Window created reduced the frame rate by up to 50%, making it very difficult to achieve flyable performance in dense areas like London Heathrow without having reduced settings a little or no AI traffic. In P3Dv5 I not only get good frame rates, but I'm able to use Orbx True Earth GB and a reasonable amount of traffic. That's quite a difference. In your case it sounds better to stick to P3D4. Pete

Really? How was that done? How long has such a bug been there? In FSUIPC4 and 5 too? PEte

FSUIPC uses normal Windows facilities to recognise key presses, and all keyboards look the same through Windows. So the answer is yes, but the keys will be the same. You might be able to open it as a HID using the HID facilities in the Lua plug-in com library. Then it would be a matter of decoding the input you might get. I've never tried reading a keyboard directly like that. Pete

I'll just add a correction to that. FSUIPC never deletes settings without you re-programming them. The usual problem is not using Joy Letters for joystick numbering so that FSUIPC can follow devices when their Windows assignments changes, usually because of a major windows update or unplugging the USB devices and re-connecting them into a different socket. Pete

There are lots of example Lua plug-ins provided -- take a look. And the Lua functions I mentioned are all described in the Lua library document. Pete

The name is FSUIPC4.DLL, not FSUIPIC. And if installed in FSX it will be in the Modules folder withing the FSX folder. If you want us to help you use FSUIPC to make assignments to your hardware, you need to just describe what you are trying to do and what is not working. I've no idea what you mean by "so many bugs". Do you mean mechanical or electrical faults with the hardware? If so then that should be Honeycomb support or your supplier. Pete

No difference in FSUIPC or SimConnect's flight saving, so it must either be to do with how the PMDG code operates in P3D5, or the fact that P3D5 is very different to P3D4 is terms or graphics, performance and so on. Most folks using PMDG aircraft in FSX, P3D1-3 and P3D4 have found that the flight saving actions they do causes stutters every time. You were lucky not seeing these in P3D4. If we could do something about it, believe me, we would. but there's not much we can do to improve what is basically just a single call to SimConnect requesting the flight be saved. What then occurs is that P3D saves its files (fxml, wx) and notifies other programs that this is being done. The PMDG code sees this and freezes its systems code whilst collecting all the data for its own saved files. May be PMDG could improve this by just making a complete copy in memory and invoking a separate thread to save it whilst allowing the simulation to continue. But they are unlikely to consider the effort worthwhile. Pete

It's an MSFS crash, not FSUIPC (which closed tidily because MSFS stopped running). Your session ran successfully for over 8 hours though. So I would say reducing SimConnect loading by not requesting AI data improved things significantly. Don't forget to retrieve the Windows crash data for MSFS from Ecvent Viewer and include it in your crash report on Zendesk. Pete

Very neat. Not sure what you think John 'had to do', but the values returned are correct and are the KEYCODES, as documented, not the ASCII code for the graphic characters. Please see the table in the Advanced Users guide, pages 17-18. You will see that the A-Z keys are 65-90 and the numerals on the NumPad are, indeed, 96-105. Key codes are used to represent every key on the keyboard which couldn't be done sticking to the standard ASCII encoding. Pete

Only in that FSUIPC6 is being developed with improvements and new facilities, whilst FSUIPC5 will cease updates altogether soon (if not already -- I think it was perhaps at the end of 2010). So, if you are happy and aren't planning to update your P3D4 to the far superior P3D5, then stay with FSUIPC5, by all means. Pete