Pete Dowson

The log file shows 4186 Client Application: "FLControl" (Id=3008) 4186 E:\Program Files\Flight Link\FLControl.exe 4186 Product="Flight Link Control Center" 4186 Company="Flight Link, Inc." 4917Program not accredited for use with this unregistered FSUIPC Just temporarily, could you not run this please so we can check things straight. Also see if there are any other add-in DLLs in the Modules folder apart from FSUIPC. If so, remove those too. If you aren't sure, insert the little BAT file from the attached ZIP into the Modules folder, then run it (double click it in Explorer). It will make a little file called Dir.txt. Show me that. That's the FSUIPC.INI file. It sounds as if you have got Windows set to hide file extensions from you. I do hate that, it means you really can't tell what's what so easily. Anyway, another thing you could try, though I don't hold out a lot of hope, is to change this line: MainMenu=&Modules to MainMenu=&Flights for example. This will tell FSUIPC to add its menu to the Flights menu instead of creating a Modules menu and adding it there. If there's something preventing the menus being changed in any case, this won't work either. But let's see ... It's late here now (3 am), so I'm off to bed. I will check this thread in the morning. Regards, Pete ListDir.zip

Ooops! :-) Pete

Oh, sorryyes, I see it here too. LSASS.EXE is running. I've no idea what it is for, but it isn't interfering with FS or anything else here. So that was a red herring, sorry. Back to square one I'm afraid. Somehow something is stopping things changing your FS's menu. So far in 4 years the only thing I've known to do that is WindowBlinds, so I'm stuck. Look in the FS Modules folder. Is there an FSUIPC.INI and FSUIPC.LOG file? Can you show them to me please? Regards, Pete

Good. Glad you got it sorted. That's normally a result of engaging the autopilot on the ground. Wait till you are airborne. If it isn't that, I don't know, sorry. Check that you don't have an axis assigned to the trim in the FS assignments, or calibrated in FSUIPC. Otherwise, maybe someone else can jump in? Regards, Pete

You can unlock things in the Enditall utility, it simply warns you it is at your own risk. I don't know killall. Or you can simply use the Task Manager -- press Ctrl-Alt-Del, find the LSA Shell process, select it and delete it. At the worst you will simply crash the system and have to re-boot. Anyway, what IS this "LSA Shell"? How did you install it? What does it do? You shouldn't simply try deleting things, it may make it worse, more difficult to uninstall because you can lose the uninstall script for it. You could go to Start menu-Control Panel-Add/Remove programs, and see if it is listed there so you can remove it. If it is installable it should be uninstallable. If not whoever designed it should be made to eat it or something. Please keep us informed. We need to know these sorts of things so we can warn others. Thanks, Pete P.S. In the case of WindowBlinds, you could tell it not to apply its workings to specific applications, so you'd tell it not to mess with FS. I don't know what your LSA Shell is doing, but check to see if it has similar options to avoid messing with selected programs.

The problem is caused by some third party gauges sending many controls ("Key Events") to FS (either via the PANELS interface for Gauges, or direct by SendMessage with WM_COMMANDs) many times per second. This defeats the timer used in FS for accelerations, making it wrongly think that the increment/decrement operation the user it trying to do is being repeated fast. The proper fix is to re-program those gauges to not do such unfriendly and performance damaging things. The ones I looked at are very wasteful. They keep sending the same events over and over and over, which accomplishes nothing but a performance hit and this acceleration difficulty. If you are writing such gauges then you can fix them yourself. Just don't send controls except when you actually want to control something. If you are using other people's gauges, then choose ones which don't exhibit such bad behaviour. All the default FS gauges work fine. The MS programmers don't do such bad things! :-) Regards, Pete

Actually it is the same in 3.00 through to and including 3.05. The "fix" to the problem which I put into 3.05 wasn't a complete fix, unfortunately. The symptoms here are certainly NOT that the weather clears -- there's no sign of that. But the Weather Theme reverts to User Defined, for sure. I don't know why your weather actually changes, but it must be related, somehow. Does the log show a "clear weather" at all at that time? Anyway, the culprit is the Wind Smoothing option. Turn that off and the problem goes away. That Technical page option for not changing FS's own weather manages to cope with everything else *except* that one. Duh! I'll fix this in the next release, but that won't be for at least a week, maybe two, unless something else really serious comes up. Sorry. Regards, Pete

Please send me all the details to petedowson@btconnect.com. Are you the author? If so, you can either have your users enter the Key manually, or, better, you can provide it automatically and invisibly in your program or in your Version Info data. I can send you full details. Pete

Thanks for telling us. It's nice to have some good news now and then! Pete

Actually I only just noticed this message (it must have crossed with my reply to your first, so of course mine got stuck on the end of the thread: Aha! Correctionyes, doing EXACTLY what you say, I can get it to happen here too. Now that is VERY weird. There's nothing I know of in FSUIPC which should care whether you are on the ground or airborne, but evidently something is doing something. Sorry I doubted you. I'll investigate this and let you know. Please don't worry about it any more, I'll get to the bottom of it ... Regards, Pete

Hmmm. Why didn't you kill that as suggested? What is it in any case? Sorry I have never heard of it. But if it is fiddling with the operating system shell, much as WindowBlinds does, it is certainly a prime suspect. Please let us know what it is and whether it is the culprit! Regards, Pete

Even if it did, FSUIPC isn't doing anything with it that matters, unless you are running an external weather program. That mesage is only logging the fact that something called WEATHER.DLL's clear weather routine, that's all. The log extract you showed before is just the initialisation call, for the default loaded Flight. Regards, Pete

I think you just execute it and it tells you. It comes with some documentation. Sorry, I do not do such things. In fact I am off-line for a while now. It is Sunday evening, one of the few times I relax a little. Regards, Pete

No, you are misinterpreting something there. When you load a flight, FS itself clears the previous weather. FS logs this fact, as it needs to know when this happens so that it can reset any weather supplied from outside. It merely intercepts FS's own call to the "clear weather" routine in order to detect it. The only times FSUIPC actually clears the weather are 1) when you tell it to, via hotkey or button 2) when you start a weather program which changes the weather through the old FS98 weather interface (unless you tell FSUIPC not to in an FSUIPC INI parameter -- see the Advanced Users guide) 3) when a "New Weather" or "Advanced Weather" interface using program requests that the weather be cleared. Yes, it means EXACTLY what it says. Something (in this case loading a flight) cleared the weather, so FSUIPC clears down the external weather requests, if any, so that next time an external weather program changes something they'll be seen as changes. Regards, Pete

So what did you do different, this time? Maybe that's the clue? Well, maybe there are other programs too that do this. Windowblinds is the only one folks have told me about. Try closing down any other add-ons you have running. The utility "EndItAll" is good for that. It has got to be one of them. What's a "messenger" program? Is this contact not good enough. Sorry, I don't understand. Regards, Pete

I am sorry, I never heard of any such problem with FS before. Unless anyone else here can jump in and help, I think you need to get on to Microsoft support. Evidently you have something in your system which is interacting very oddly with FS. Sorry I cannot help from here. Please do let us know how you get on. You need FS to work before trying to use FSUIPC, or any other add-on really. Regards, Pete

The ALT key does not open the Modules menu, it merely displays the FS menu, from which you will be able to select the Modules menu by the letter "M" (or use the mouse). Do you not even see the FS menu, the one beginning "Flights ..."? If not you have a big FS problem. If you do, and there is no "Modules" menu near the end of the list, then either you have not installed FSUIPC.DLL in the FS Modules folder, or you are running something like WindowsBlinds which prevents anything altering FS's menus. The latter problem is addressed in the Announcements at the top of this forum, and in the latest FSUIPC documentation (3.05). Regards, Pete

Have you got DX9b? That may help, along with the latest video drivers. Good luck! Regards, Pete

Wow! How do you get such fantastic performance? What processor/video are you using on the FS PC? I'm lucky to get 20 fps (average much less) on my P4 2.4GHz! Time I upgraded again I think! Pete

Ulisses, If the displays which are "jerky" are the engine read-outs in the EICAS, not the PFD or ND displays, then I can probably offer some adjustable parameters to make those scan, in FSUIPC, faster or slower. Generally they do take a lower priority. It's a performance thing -- a lot of the engine values have to be derived by my code on every frame. for some of them, to avoid the overheads, I don't do it on every frame, but only perhpas 3 or 4 or 5 times a second. This is in order to provide maximum fluidity to the important stuff like the attitude indications - pitch, bank, heading -- airspeed, vertical speed, altitude, and so on. Check things out, see what it is you are really seeing, check the WideFS logs, and so on. Then write to me on petedowson@btconnect .com -- not before Monday, please, and maybe I'll get you a Beta to try with some parameters to set scan rates. Regards, Pete

Yes: don't use visibility smoothing, visibility maxima or graduated visibilty. And enable the option in the Technical page to change FS's own weather, so mucking up the selection of "weather themes". The only other changes are to support a few extra values in the IPC interface, and some additional facilities for those programs, like FSMeteo 6, which use the NWI. That's it. You can check the list of changes in the History document. Really, if there's some minute timing change somewhere in FSUIPC which has an effect on stutters and pauses in Project Magenta on client computers, and I cannot imagine what that could be, your system must have been on a knife edge, ready to fail in such a manner in any case. Are the WideFS logs reporting problems? Are the frame rates poor (use "F" in PM's PFD) -- the data update rates should in general, match FS's own frame rates? Is the frame rate limiter set 'wisely' in FS? What exactly are these symptoms of stutters and pausing? I find it very difficult to imagine anything I've done for many months having any affect on this in the first place. It just doesn't make any sense. Pete

There really is no difference FSUIPC could make that I know of, and the difference in WideServer 6.02 to 6.10 is only evident when and if you ever got lots of restarts logged in the Server Log file -- they just shouldn't occur any more. If you turn off all the new visibility options in FSUIPC 3.05 then there is no difference in what FSUIPC is doing either. They are actually off by default of course. Every time I make a release of new versions, I get many messages like this. And really they cannot be due to the changes I've made, so it is extremely odd. Yet it happens every time. :? I try to keep the actual number of changes down, to keep things predictable and understandable, and in the developments from 3.00 to 3.05 this has most certainly been the case. The most significant change has been the visibility things in 3.05, and apart from those there is nothing of significance to normal running performance. And WideFS has not changed significantly since before version 5.50. Strange. Pete

No. Once you are registered, you are registered for the life of FSUIPC version 3.xx. All you need to do when you download the 3.05 ZIP is copy the FSUIPC.DLL into your FS Modules folder. Do NOT delete any files and your Registration will stay intact. If you ever do want to re-register, just delete the FSUIPC.KEY file, but I can't imagine why you'd want to do that. Regards Pete

Please ask the folks at Project Magenta to help. I'm sure they can make some short-term arrangements for you. It isn't really an FSUIPC matter. there is no way FSUIPC can magically determine you are running a demonstration only. Regards, Pete