Pete Dowson

I've checked here, and checked the code. It's a P3Dv4 bug. FSUIPC can't really do it wrong, as it simply asks for "AI Traffic Assigned Runway", receives a character string result, and supplies that, as is. I'm reporting it to L-M now and hope it will get fixed by the next release. Pete

FSUIPC has nothing to do with how those programs choose to operate. I didn't even know they gave AI such instruction. TrafficLook (one of the free demo programs available in the Download Links subforum here) will show the data Radar Contact gets and uses. See if that shows the runways assigned to AI correctly. if not it is likely to be a bug in P3Dv4 which will need to be reported so it gets fixed in an update. The way FSUIPC5 gets the information from SimConnect is no different than itwas for FSUIPC4 and P3Dv3. However, I can re-check that. I'll see if I can make time to check this myself tomorrow. Bedtime for me here, now. Pete

Since I don't understand how you have the problem, i'm not likely to be able to make it work for you in any future release. Did you try what I suggested? Did you even check the permissions? I need you to help me help you! One thing always advised is NEVER install any version of FS or P3D in the Program Files folders. Select your own folder. I always use a folder simply called "Prepar3d v4", and usually on another disk, not even on C. But I have tested my install on a brand new Windows 10 PC, letting it install in its default path, and, though the Permissions on the Prepar3D folder itself stops file writing, the installer does successfully change those permissions for the Modules folder. So, if you cannot do as I advised above, there are two other things you can try: 1. Mark Prepar3D.exe to "run as administator" itself. Do this by right-clicking it and selecting Compatibility. 2. Totally uninstall Prepar3D and re-install is in a different folder of your own choosing, away from Windows. Pete

Yes, it's the same as before. The application interface which RC uses doesn't need a registered FSUIPC. Pete

Your copy of FSUIPC is out of date then! Try 5.112, the currently supported version. It will still not be like it was in FSX and P3D3, because the facilities just don't exist in P3D4, and I'm not hacking into code as I used to. But the revised window you'll see is better. It won't be entitled "Radar Contact" because the facility to change the title does not exist! With either type of display, your "Green bar" or the better one in 5.112, you can always move them and resize them to suit. FSUIPC will try to remember the new sizes and positions, but if you change your P3D window, say from full screen to windowed or vice versa, the overlaid windows will not be in the right position. Pete

If you are using FSUIPC you don't need any Saitek software. And it wouldn't explain the lack of a Log and INI file in the Modules folder. They are ALWAYS written, from your very first runwith FSUIPC. Pete

Well, it's really weird, so interesting from that perspective. The extra logging only makes it log exactly what it is doing and what the result is, it certainly doesn't change what it does. Maybe just slowing it down helped, but then why would it work without the logging too? I think something else changed which fixed it. Thanks but, no, I don't need the files now it works. I am short of time this week -- on holiday from Wednesday eve till mid-September. This will be THE main holiday of the year, over 3 weeks! So all sorts of horrible things are bound to happen! Pete

FSUIPC5 always saves the FSUIPC5.LOG and FSUIPC5.INI files in your Modules folder. There would also be an FSUIPC5.JoyScan.csv file. All three are written to the Modules folder, nowhere else. If they are not getting written then there is certainly somethng wrong on your system. I've not heard of anyone having such an odd problem. Check the permissions set on that folkder, as follows: Start Explorer by right-click and "run as ... administrator". Right click on the Modules folder, Select 'Properties' Select the Security tab. Among the list of "Group or User Names" there should be "Everyone". If not you need to add it manually -- see later. Select Everyone. In the "Permissions for Everyone" list, all entries should be ticked. If not, tick them. Click OK and you are done. If there is no 'Everyone' listed, just add it as follows: Click the Edit button, then Add. Type Everyone in the edit bix where the cursor is, then OK. Proceed above as when Everyone is present in the list. Now this is all precisely what the FSUIPC5 Installer does, so if it doesn't work manually either, you have a problem. maybe your system is set up to prvent you doing things, even as Administrator. are you signing in as a Guest, or as Administrator / Owner? Pete

Well, I have actually found a little bug which could cause the symptoms you saw originally, so I will be releasing an interim update in any case. within the next day or two. I found it be comparing that area of FSUIPC code with the same part in FSUIPC4, and saw a difference which didn't make sense (and wasn't related to the conversion to 64-bit). Pete

In the [General] section: Debug=Please LogExtras=x200000 Pete

If you say "No" to that, is the correct Profile among those on offer for you to choose from? What happens if you do? Pete

Just looked at your HidScanner log. The Satek X-52 shows 39 buttons altogether, so 7 of those won't be directly assignable in FSUIPC. But they won't be in any case, whether the Saitek software was installed correctly or not. The log file and the JoyScan file both suggest something was wrong. If after doing what i suggest above, things work (i.e. P3D loads) and you find you need to use those extra 7 buttons, then you could try installing the Saitek software. Maybe by removing everything properly the problem will be cleared. I know aa lot of folks do have the Saitek drivers for later models (I assume later? X-55, X-56) installed okay without the crash you are getting, so I still think it's something worng with your installation. Pete

How many buttons does it have? FSUIPC handles the standard HID 32 buttons. I know some very recent devices have uo to 64, though. I expect P3D will support the others, but take care to avoid ocnflicts if you assign in both. Yes, but "uninstall software and remove devices" should be "uninstall software uninstall devices in Device manager, including drivers in device manger, then re-boot so that Windows supports them with the standard USB HID drivers." Pete

That link works okay. The JoyScan file indicates a device with Vendor ID 06A3 and Product ID 0762. But it appears not to be a usable HID device. The crash is not actually occurring in FSUIPC at all. I suspect it is the drivers you have installed. Try what I suggested. Pete

Can you please state the actual version number, as everyone says that and it isn't always the latest when i get more information. Why go to that trouble and then go and install Saitek drivers? Unless you need ot use them for other programs, you really don't need them with FSUIPC and are the cause of many problems. To remove them now, including their low level bits, you'd need to not only uninstall them in Programs & Features but also in the Windows device manager. Uninstall the devices their AND elect to remove the drivers when the option presents itself. I'm afraid the link doesn't work. Pete

I don't know iFly737NG.dll-. Was that installed BEFORE you installed FSUIPC? If so that probably explains the problem. FSUIPC sets read/write permissions on the Modules folder when it creates that folder, but later, when just installing over an older version it simply places its files, not setting permissions. I might look to see if I can change that, but i'm not sure if it is possible. So, try this: Rename the Modules folder to something different, like "OldModules". You'll probably need to run Explorer "as administrator" too, to allow you to do this. THEN run the 5.112 installer again, so it creates a new Modules folder with the correct permissions, and after this, copy over that iFly file (assuming you still need it). Finally you should go into Folder Options in Exploer, and change the option which lets Windows hid "known" filetypes from you! The Istall file in your list above should show as "FSUIPC5 Install.log". Okay? Your Installer Log is fine. In future you should never install any version of FS or P3D in "Program Files". I know it is default, but you can change it. The whole of Program files is protected from you, the user and owner of the PC, to stop you changing your own files! It is part of the madness of modern Windows versions, and it gets worse not better. :-( Pete

Not sure I can advise really until you try writing it. But just some comments: 1. I define a Variable and write it on Systemstart to 14000 for Example. In Lua you don't have to pre--define variables. Just set it, like x = 14000 2. I Write this Variable permanent to a Free Offset Don't use what you think might be "free offsets", only User Offsets, 66C0-66FF. For variables only needed to be retained for other or later Lua plug-ins, it would be better to use Lua globals (via ipc.set and ipc.get functions). 4. I write in the Script the 6 logics (each Encoder direction) like... " If Button 1 is pressed for Increase Hundrets Part" then Variable + 100 " ( With a overrun logic on Frequency Limit if needed.) Take care here. I think that radio frequencies have to be written in BCD (="Binary coded decimal"). Like 11432 would be 0x11432, not the decimal number. If you are writing the values direct to the offsets in FSUIPC for the radio frequencies (which would be easier than using the FS Controls), then please heed the notes for those offsets in the Offsets Status List (in yourFSUIPC Documents folder). They aren't a straight copy. NAV and COM drop the 1 from 1xx.xx and just have xxxx. ADF frequecies are in two parts with the y digits in yxxx.y in a separate offset. Using the FS controls the values are NOT always in the units displayed on the radios, but kHz or something different. 5. I Finaly need a Logic for the Swap Button ( Again a selv defined Joystickbutton or Offset) like... READ FSX ADF1 ACTIVE and save it temporary to a new variable Then Write current Standby Variable to the Original FSX Active Offset AND Write Temporary saved Variable to our ADF Standby Variable. Using the offsets for Use and Standby (where supported) that's not as complicated. Where standby is not supported you'd need tostore it yourself, in a User Offset, or in a Lua Glonal variable. Pete

Open the Log in an editor, like Notepad, select the whole text, top to bottom, and copy. Then click the <> symbol just above the edit area. You can then paste in the contents of the log. But first, please, my questions, which I'll repeat as you continually seem to not read my replies: Did you run the Installer by right-clicking and selecting "run as" ... "Administrator", as instructed? What files are there in the P3D4 Modules folder? Pete

I do not have a web site! This Forum is my only place, and updates, interim versions, and lots of other useful things are here. Take a look in the Download Links subforum! The link SimMarket gives actaully points to the files here. Enrico Schiratti maintains a web page called the "dowson" page, but it isn't mine and the links there also come here. I have no control over anywhere but here. Pete

Did you run the Installer by right-clicking and selecting "run as" ... "Administrator", as instructed? What files are there in the P3D4 Modules folder? Please show me the Install log. Pete

Oh dear. As I said earlier, please download and install 5.112!! And be sure to run the installer "as administrator ". 5.112 was released specifically to deal with this problem, which is why I asked to to install it in the first place. Pete

You said that before. And I asked for the version number of FSUIPC5. You still have not told me! Pete

Sorry, I did miss that part of your original post. Which Sim is this with? ADF2 swap was a bug which I reported to L-M and I'm fairly sure was fixed in the latest versions of PeD. Have you tried those? ADF1 STBY SET and ADF2 STBY SET were added to P3D . They also added AFD1 PRIMARY SET and ADF2 PRIMARY SET to complete the set in a tidy fashion. FSX and before did not have full ADF2 support. I'm afraid I cannot help with those. Pete

The INI file, which I would need to see, as well as a log showing the aircraft name at least, was not attached! Please ZIP files if you intend to attach. If you select Axis assignments for an aircraft already assigned to a Profile, you cannot check or uncheck "Profile specific" as it will already be checked. So i assume you mean that it behaves as if the aircraft has not been assigned to a profile yet? There is no "new Profile dialogue". There's a dialogue allowing you to assign the aircraft to an existing Profile OR create a new one. Perhaps some more information would help me understand, like name of aircraft being assigned to, as well, of course, as the INI file containing the Profile assignments. This thread was solely about the old system, without Profiles. It is the wrong thread for a Profiles problem. Pete

I assume you are talking about FSUIPC? You don't actually say! Which version of FSUIPC? If not 5.112 please download it and install. Pete