Pete Dowson

There's no change in the Profile system. You have something wrong. Show me your FSUIPC INI file.

No!! Why exit FSX? Just load a different aircraft! You seem to be suffering from quite a few misunderstandings. You could ALWAYS change aircraft in all versions of FS without restarting! You can create your generic settings by loading any aircraft with no profile assigned. Then, when you create a new profile you are offered the option to include the generic settings or not, as you wish. Why not read the User guide (again?) Pete

Once you assign a Profile for an aircraft, that's it -- it is the Profile for that aircraft. What do you expect, to have multiple profiles for the same aircraft? Where's the sense in that? Load a different aircraft, one without a profile, and create one for it ... and so on. Anything else makes no sense. Do you mean "delete" profile, not exit? i.e. delete all the assignments made for that profile? I have thought of doing that -- currently it is only by deleting the profile sections in the INI file. But, as I said above, if you have a profile assigned to the current aircraft you cannot use another profile for that aircraft. It makes no sense. How is FSUIPC expected to choose the correct profile for each aircraft automatically if there are multiple ones assigned? You evidently don't understand the purpose of profiles! Anyway, why are you changing the subject of this profile. What about the X-55? That was why I gave you an FSUIPC update! I'm still waiting for the result, please! Pete

This is just an error on termination. There's no reason there for it to be refused loading next time. In any case I've now made another improvement. Try this version: FSUIPC4969b.zip Pete

Please run Windows Event Viewer (run it from the Start menu) and find, in the Application logs, the most recent Crash Data for FSX. You should be able to view it and copy it. Show me that, please. And also any log or part log produced. That is ALWAYs required. 4.969a loads fine here. The differences to 4.969 are miniscule. Pete

Here: FSUIPC4969a.zip Just copy the DLL into the Modulesfolder. Pete

You need to ZIP files for upload, as I said. Please see my previous message and let me know how it goes with the interim update. Pete

Yes, I understand that. But the prupose of adding those lines was to get more logging in the LOG file. Try ZIPping the file first. Being all text it will compress really well. I have an interim update for 4.969 which I'm testing at present. I don't know if it will fix your problem (i could do with the log for that), but I'll give you a link to it anyway, soon, so you can try it. The number of variations I've seen in how these X-55 units can register themselves wrongly is infuriating. Those (and the similar X-56's) have caused no end of problems over the last few weeks. PEte

What is the meaning of the "FSUIPC.ini debug x200000 files? They are merely the settings. The point of adding those Debug lines is to get the log with all the details in. You supplied the Install log, which only shows that you installed FSUIPC, but you omitted the crucial FSUIPC4.LOG file itself! Pete

It's a pity PMDG don't simply freeze the aircraft operations themselves rather than the whole sim. Perhaps they haven't found a way. Mind you, you'd still get pauses whilst flying. Maybe they should just make memory copies rather than create files. Pete

I didn't expect it to change anything, but the log would be more appropriate. It shows: which means the sim was frozen for so long that SimConnect stopped sending data to FSUIPC. The reason is that you are using a complex PMDG aircraft and you've enabled AutoSave in FSUIPC. You'll need to disable that. The PMDG aircraft are designed to save every detail of their state whenever they see a flight being saved. They actually freeze the whole Sim whilst they do this. It is that which causes the SimConnect disconnection. (They could simply freeze the aircraft and let the rest carry on, but they don't, which is a shame). There is a parameter in FSUIPC which controls how long FSUIPC will tolerate between data updates. You could increase that but I think not by enough. Anyway, even if this stopped FSUIPC getting the data, you'd experience long pauses every time a flight is autosaved, ruining your enjoyment. So disable Autosave (it does default off), and just do a manual autosave before any critical operation. Pete

Yes, about 99% of the informstion is populated by requests made to Simconnect, which then provides updates and they change. There are a number of add-on aircraft which have their own subsystems as the authors decided that the FS/P3D implementation doesn't do the job they need. PMDG, FSLabs, A2A and some of the Aerosoft implementations (the advanced Airbus) are this way. Some sub-systems are partly or moslty done in a standard way, others not at all. Pete

Oh dear. :-( How do you tell for ANY program? 1. The version number is displayed clearly in the main About tab in the FSUIPC Options in the SIM. 2. The version number is clearly stated by the Installer when you installed it. 3. The version number i shown in the first line of the FSUIPC5.LOG file in you P3D Modules folder. 4. The version number is shown in the "UpdatedBy" parameter in your settings file, FSUIPC5.INI 5. The version number, as for any prtogram, is shown in the Properties of rthe DLL itself, when you right-cick on it. 6. The version number is shown in the Updates document supplied, or in its absece in the Gistory document installed alongside all the other documentation and goodies you were told to read by the Installation document. Same place as you got the original, or, for better choices and lots of other goodies, the obscurely named (?) "Download Links" subforum above. In fact that is where asll the links point to in any case. SimMarket only sell the registration keys, they don't supply the program. They provide a link back to the Download Links subforum here which hosts all my files. Pete

It's definitely okay here, in the currently supported version 5.103. It reads well in FSInterrogate and using the Monitor in FSUIPC's logging tab. Check yourself. FSInterrogate is provided for things like this. Here's an illustrative extract from my FSUIPC5 log with 0BB4 monitored in FSUIPC Logging: 238479 Monitor IPC:0BB4 (S16) = 1027 238494 SimRead: 0BB4="ELEVATOR DEFLECTION PCT" FLT64: 6.26886082863 238978 Monitor IPC:0BB4 (S16) = 1284 238978 SimRead: 0BB4="ELEVATOR DEFLECTION PCT" FLT64: 7.83683873683 241162 Monitor IPC:0BB4 (S16) = 1541 241162 SimRead: 0BB4="ELEVATOR DEFLECTION PCT" FLT64: 9.40482524299 243424 Monitor IPC:0BB4 (S16) = 1798 243424 SimRead: 0BB4="ELEVATOR DEFLECTION PCT" FLT64: 10.97281841 243751 Monitor IPC:0BB4 (S16) = 2058 243751 SimRead: 0BB4="ELEVATOR DEFLECTION PCT" FLT64: 12.561212578 Well, obviously, if it is only with the one aircraft, not with any defaults, then it is a problems with that aircraft. Maybe it needs something else sorted in the system to free the elevator, or maybe they don't use the default elevator simulation but their own. The FSUIPC offsets reflect what the sim does, and cannot always be relied on for aircraft which do their own thing. Pete

Please ALWAYS use the Support Forum, not one of the Subforums, when requesting help. First please make sure you are using version 5.103, the currently supported version. Then, as always for Support Requests, the FSUIPC5.LOG file is needed. That will show what is going on. Close P3D4 down before retrieving the Log file (it'll be in the P3D4 Modules folder). Pete

I'll have to look along the wrole path of the execution from my code to that level, and add a log at every part. That isn't a quick job. if only I could reproduce it, it would be a lot easier (and quicker). It must be something happening in the Lua code itself. The pathname certainly leaves my code intact, as you have shown. Also, seeing as it is so rare (for me, very; for you, somewhat), it must be some sort of timing interaction with other Lua parts. The separate threads really can't interfere (except via shared Globals) as they are effectively all in their own spaces with their own stacks. I might not have time for this for a day or two, but I do want to see it solved, so do your work-around if you must but please allow it to be tracked still when I add more logging. Pete

Sorry. I was only trying to help improve LINDA by pointing out misleading messages. I won't bother further. Pete

Warning? You mean the one telling me the Logging is off? I thought that was useful. It's the part that tells me I can turn it on in LINDA Setup which is misleading, as it isn't in LINDA Setup but the dropdown from the Console -- except for Developers, or do all users run in "Developer Mode"? Pete

That is out of date and not supported. Please update to 4.969. Please do this: Add these two lines to the [General] section of FSUIPC5.INI: Debug=Please LogExtras=x200000 Then run P3D4. Check that your devices are still not seen in FSUIPC then close P3D4. Show me these files, all from the P3D4 Modules folder. You might need to ZIP them to make them small enough if you intend to attach: FSUIPC5.LOG FSUIPC5.INI FSUIPC5.JoyScan.csv Pete

Sorry, but the main logging does clearly say: 175142 LUA.1: LINDA:: [START] WARNING - All LUA logging switched off !!! 175142 LUA.1: LINDA:: [START] Go to Setup LINDA to switch on (if required) So naturally I expected it to be in LINDA Setup! Pete

Dropbox? Do you mean the three arrows? (I would never have recognised that as a dropbox button!). What about the "Ready to go, Captain" message. When and where is that supposed to happen? [LATER] Oh, only in the Verbose Log. Shouldn't it be a normal message, on the FS screen, or is that the LINDA READY message? Seems they ought to be swapped? Pete

Using CTRL+ALT+R, as you stated? Please also see previous message which overlapped with yours. Pete

I'm not getting those lines. I see LINDA reporting: 175126 LUA.1: LINDA:: [START] Loading System Configuration files 175142 LUA.1: LINDA:: [START] WARNING - All LUA logging switched off !!! 175142 LUA.1: LINDA:: [START] Go to Setup LINDA to switch on (if required) And I've gone to LINDA.exe's "Settings" but see no option for extra logging? Additionally, as I asked before, when and where am I supposed to see the "Ready to go captain" message? Because I've not seen it yet. Maybe it isn't running properly here? I do get "LINDA READY" though. Please also see previous message. Pete

Yes, but why would I want to restart LINDA in FS without FS running? Makes no sense to me still, sorry. Well, I might indeed have to release an interim update without first fixing this*, but I don't like leaving it. It needs tracking down. I've made a test version which should log the actual argument and the Windows error number returned at the actual place where the file is opened. Lua code uses a C/C++ run-time library function (fopen) rather than the CreateFile Windows API function I always use, so there's another layer of code involved, but that shouldn't matter. I'll provide the test version via email if you don't mind. Please send me an email i can respond to. Pete * The need for an Interim release is mainly to get the Goflight facilities properly tested by others. Goflight have now supplied me with a GFDev64.dll which works well, and I've tested it thoroughly here, but only with RP48, T8 and P8 units, the only ones I have left.

Sorry, how does FSUIPC load LINDA with no flight simulator running? I don't get the question. Please see my previous messge, which seems to have overlapped with yours. Pete