Pete Dowson

Please send the request by email == petedowson@btconnect.com -- and I'll look at it. But it won't be till early October now, at the earliest. Pete

You don't actually ask a question. But I assume you have found that those FS controls do not work on the PMDG 737NGX. There was no need for all those pictures, a few words would have sufficed. The assignments you've used would work on any normal add-on or default aircraft, but PMDG implement all of their own controls. There's a list provided in one of the files in their 737NG SDK folder, and you can assign them by number using the <custom control> selection in FSUIPC. Pete

Sorry, i don't know such a file. It isn't anything to do with FSUIPC. Pete

Why did you delete files being updating FSUIPC? There's never any need. FSUIPC updates simply replace programs and documentation. They never change your settings. Everything you've setup in FSUIPC4 is stored in the FSUIPC4.INI file, unlesx you are using Profiles and have selected the Files option, for separate Profile files. If you like, paste its contents in a message here and I'll try to find what you've set wrong. Pete

No, and there's no point. There has not been any change in FSUIPC's treatment of axis assignments and calibrations for many years. It is all standard DirectInput stuff. Ddn't you follow the link I gave? Pete

You can either have multiple small Lua plug-ins, one for each assignable function, and just assign those buttons appropriately, or you can have one larger Lua plug-in,loaded initially (perhaps by an [Auto] entry in the INI file), and have that do different things according to the PARAM value, the Parameter you provide when assigning a button or switch, In the former case you assign to "Lua name" in the second to "LuaValue name". Your choice. Whatever you find easier. I doubt there's much difference in performance or efficiency. Pete

You mean adding ".. \nMode=" .. mode" to the end, before the closing)? Why not show me the whole line? BTW with offset 66C0, are you sure it is an "SW" signed word (ie 2 bytes, or 16 bits?), with a range -65536 to +65535?. Usually, it is just used for a mode selection, a single unsigned byte (UB) is sufficient. That has a range of 0-255. BTW if you are still using the original code from the examples installed with FSUIPC, it would be a little more efficient these days to use the event system to make it run 20 times per second. To do this put function displayvals() at the beginning instead of the "while 1 do", remove the ipc.sleep(50) line, and add event.timer(50, "displayvals") at the end, after the 'end' line. Pete [LATER] Oops. Crossed with your "fixed" post.

Syntax, permitted instructions, and general language help is all provided on the Lua website, the one referenced in the Lua documents I provide (see below *). I cannot undertake to document the language itself, only the FSUIPC specific additions. However, if I understood what you wanted and what you've tried and failed with, maybe I could help more directly. For instance i've no idea what you mean by " it's quickly become apparent that that won't work with a button state". Pete * From the FSUIPC Lua documentation: What is “Lua”? It is a programming language. The best way to see and learn what it is all about is to visit this web page: http://www.lua.org/about.html

Yes! Found it! FS used to have an option. In fact its setting was reflected in an FSUIPC offset in FSUIPC3 (for FS2004 and earlier -- 0358 which to quote indicated "COM frequency settable in 25KHz increments if true (else 50KHz).". I am pretty sure that option doesn't exist any more, not for at least 10 years -- FSX and P3D defaults to the 25KHz increment. But maybe you are using an old version of FS and haven't found the option? I'm afraid I can't tell you where it is, probably either Aircraft - Realism, or Options - Settings - General. I have FSX, FSX-SE and P3D installed, but nothing older I'm afraid. But whatever you have, it certainly is not any restriction imposed by any of my software as you accuse. Pete

My software? It is FS, and I've never had any trouble whatsoever setting any desired radio frequency. "Try it"? Pardon? I use it all the time in my cockpit. It is used by many folks using hardware radio stacks linked to FS through my software, 117.17 set in the FS radios means 117.175. It has always worked perfectly. I don't know what problem you have, but it isn't what you are saying, or are you not explaining yourself well enough. For instance: What are you using to make these increments? FSUIPC doesn't do "increments", the INC /DEC facilities are FS controls, or KEY EVENTS. In fact all of the radio facilities are applied using FS controls -- as supported by SimConnect since FSX. Also, you seem to have something wrong. The COM frequency band is 118.000–136.975 MHz, in steps of 25 kH, which is .025MHz. If you are only seeing increments of 0.25 MHz then you'd only get 117.00, 117.25, 117.50, 117.75 etc. Plainly not true. Delving deeper, going back to your original message and reading it more carefully: Perhaps this is a problem with the add-on aircraft you are using? Have you tried checking with a default aircraft? If you are using INC/DEC assignments to FS controls, then "my software" is only the messenger. It simply sends the control on to FS. You could assign directly in FS. Have you tried? Or maybe it's an FS option. What version are you using? I seem to recall there was an option for enabling or disabling the 0.025 increments -- when FS first came out I think they were new. There are more new ones now, (" it is becoming common to further divide those channels into three (8.33 kHz channel spacing), potentially permitting 2,280 channels. " -- Wikipedia). Pete

FSX-SE build 62613 was not supported by FSUIPC 4.939e. The first FSUIPC version supporting 62613 was 4.939j, released on 1st April. Anyway, I'll do some checks here and maybe change the installer to try and deal with all the alternatives. it's quite a complex puzzle with so many different possibilities which have been reported. And things are different again if someone has attempted to uninstall FSX-MS before installing FSX-SE. It doesn't clear out all the references. BTW, I have both Registry paths for FSX-SE installation on my PC -- the DoveTailGames one and the Microsoft one. The DoveTailGames one was created by one of the DoveTail updates (don't actually know which). Maybe you missed one and they stopped doing it. Pete

Hmm. That's very strange. I specifically changed it to look for DoveTailGames because many folks were finding problems with the original method. Mind you, i did change it a long time ago -- version 4.939e was back in FSX-SE 62611 days, in February/March 2015. There have been many versions of FSUIPC4 since then as well an other versions of FSX-SE. How come you missed all those? Have been away for a few months? I am a little bemused on two counts: 1. Why, when the change to look for the DoveTailGames install details has been around for at least two FSX-SE releases (62613 and 62615) and many FSUIPC updates, has no one mentioned this problem before, and 2. Why hasn't your specific registry got this entry when the FSX-SE install creates it? Have you rolled back at some stage? I'll look to see what i can do to overcome these bewildering differences, but meanwhile, obviously, you can deal with your specific problem by simply copying the updated files from your FSX Modules folder to your FSX-SE Modules folder. Pete

All FS's radios, and most real world radios, only display 2 decimal digits. The .005 value is assumed. When you tune 119.17 it is assumed to be 117.175 as there is no 117.170 channel. The radios work in channels, not in continuous values. You are worried about something that isn't a problem. Pete

You can see from the picture of the slopes on screen. One way flattens the centre, making the controls less response near the centre, and sharpens the slopes to the extremes to compensate, so suiting folks who tend to over-control. The other makes the centre steeper, for faster response, and flattens the extremes to compensate. That way more suits fighter jets and stunt planes where you need rapid aircraft response. Pete

I suspect everyone just adjusts to their own taste. If the aircraft you fly are sophisticated add-on aircraft, like PMDG or Aerosoft, I'd leave all the main controls linear, i.e. FSUIPC's slope "0", because they should have already been dealt with correctly in the modelling. Just flatten it in the middle slightly if you find you overcontrol. Pete

Is this on the same PC as before you "started to move over", without reinstalling the throttle quadrant? If so just copy your FSX version of the FSUIPC4.INI file over to the P3D Modules folder so FSUIPC will be acting exactly the same. There is no difference between FSX and P3D in this regard. If it's a new install of the throttles, take a look at this FAQ subforum thread: http://forum.simflight.com/topic/79464-some-saitek-axes-only-provide-partial-movement/ Pete

You might notice that the last message before yours in nearly 3 years old ... I think you'll be lucky to get a response. Maybe you can find the author posting elsewhere more recently? Pete

It doesn't close. Just select Yes to allow FSUIPC to run. This is a well-known problem with FSX's SimConnect and is covered in FAQ threads. It occurs before FSUIPC is even loaded. It may have come up just then after running with the TEST version f because of the shut-down problem I mentioned. Please look out for a new release, 4.945, which will be ready to download later today. Pete

Nevertheless, the request to Windows for there deletion are being ussued and returning "success", see: 602656 Autosave started: next file entry 1 602656 Autosave: deleting "C:\Users\Desk-Rob\Documents\Flight Simulator X - Steam Edition Files\AutoSave Wed 142549" 602656 ... Autosave finished 1202156 Autosave started: next file entry 2 1202156 Autosave: deleting "C:\Users\Desk-Rob\Documents\Flight Simulator X - Steam Edition Files\AutoSave Wed 143548" 1202156 ... Autosave finished 1801656 Autosave started: next file entry 3 1801656 Autosave: deleting "C:\Users\Desk-Rob\Documents\Flight Simulator X - Steam Edition Files\AutoSave Wed 144548" 1801656 ... Autosave finished 2401156 Autosave started: next file entry 4 2401156 Autosave: deleting "C:\Users\Desk-Rob\Documents\Flight Simulator X - Steam Edition Files\AutoSave Wed 145547" 2401171 ... Autosave finished 3000656 Autosave started: next file entry 5 3000656 Autosave: deleting "C:\Users\Desk-Rob\Documents\Flight Simulator X - Steam Edition Files\AutoSave Wed 150547" 3000671 ... Autosave finished 3600156 Autosave started: next file entry 0 3600156 Autosave: deleting "C:\Users\Desk-Rob\Documents\Flight Simulator X - Steam Edition Files\AutoSave Wed 151546" 3600171 ... Autosave finished 4199656 Autosave started: next file entry 1 4199656 Autosave: deleting "C:\Users\Desk-Rob\Documents\Flight Simulator X - Steam Edition Files\AutoSave Fri 114540" 4199671 ... Autosave finished 4799156 Autosave started: next file entry 2 4799156 Autosave: deleting "C:\Users\Desk-Rob\Documents\Flight Simulator X - Steam Edition Files\AutoSave Fri 115539" 4799171 ... Autosave finished So, it most definitely is something up with either Win10, or your specific installation. Sorry, I can't really do more! Pete

If you haven't deleted anything from your previous install, you simply run the later installer and that's it. No need to re-enter anything. It just updates the DLL and the documentation. That was a mess in their Registry, which a later updates of the FSUIPC4 installer fixed for them n any case. So many folks don't bother to first ceck for updates! :-(. There's been at least 5 full new Releases since then plus about 10 interim updates! FSX-SE and Prepar3D are both still being developed. FSUIPC4 has been continuously developed with regular updates now since 2006. The same applies to all the previous versions ever since FS98 days (1997)! Pete

Cost? In what, memory, performance? None that I can measure. Or do you mean money? Updates have always not only been free but pretty much compulsory, unless you don't want any support because I cannot support old versions! Sorry, I do not understand this part at all. Whoever says FSUIPC4 doesn't work with FSX-SE is using the wrong version of FSUIPC. What is this about a "path" and what "errors"? Pete

4.939t pre-dates the current version of FSX-SE -- it only knows up to 62613, and will not only warn you but it will not work correctly with 62615!. You always need to use the latest version. The current official release is 4.944a. Note that I have found that the interim test updates I've been supplying here (4.944d/e/f) sometimes cause Windows to report a crash after you close FSX-SE down. I've found the reason for that and it will be fixed in the next proper release, so please don't worry about that for now. If the results of the extra logging in 4.944f indicate something I can do to help the Autosave deletions, I'll fix that first anyway (but I don't hold out too much hope of that score at present I'm afraid). Pete

Yes. Unless you want to assign things differently for different aircraft types, there's nothing wrong with assigning everythnig in FS/P3D and still using Calibration in FSUIPC. In fact that was how it was always done -- assignments in FSUIPC were a later addition. It depends whether you want a reverse section of the lever. The single throttle assignment, on the first tab (with elevator, airleron and rudder) is the "generic all-engine" throttle, the one those with only a single throttle lever might use. But it has no reverse capability. The separate engine calibration section allows a reverse zone (optionally disabled by the top left NRZ option). Sorry, I don't know what you mean there. All FSUIPC's settings are stored in the FSUIPC4.INI file, which is a standard Windows-style configuration settings file. ALL of FSUIPC's files, including itself, are installed in the Modules subfolder in your FS/P3D installation. Just look there. Maybe you simply don't recognise it because you have left Windows Explorer to hide the proper filenames from you. Best to turn that optin off, as described in the FSUIPC user guide. Pete

Sorry, there is absolutely nothing in simply replacing the FSUIPC4.DLL with the one in that downloaded ZIP which can possibily be responsible for any of that. All that has changed is a little bit of extra logging when AutoSave occurs, that's it. All you needed to do was copy the DLL into the FSX modules folder. Also the current version of the FSUIPC4 Installer recognises all existing versions of both FSX and FSX-SE, so evidently you are trying to use an old version of the Installer! If you want help with FSUIPC or its Installer I always need more information -- paricularly the Log files it produced especially to help in such circumstances. Pete

For more logging, just to confirm what I thinkj, download FSUIPC4944f and copy that into the FS Modules folder. Then Edit the FSUIPC4.INI file and add these two lines into the [General] section: Debug=Please LogExtras=4 When you run this version with that logging you will get an entry in the Log showing that it is Autosaving, and confirming the file(s) to be deleted, like this: 512245 Autosave started: next file entry 8 512245 Autosave: deleting "C:\Users\Pete\Documents\Flight Simulator X Files\AutoSave Thu 195338" 512245 ... Autosave finished 541792 Autosave started: next file entry 9 541792 Autosave: deleting "C:\Users\Pete\Documents\Flight Simulator X Files\AutoSave Thu 195408" 541792 ... Autosave finished See what you get, please. Pete