Pete Dowson

Of course! Though I'm not sure it'll cope with the numbers of programs you want to run, at least not without using some of the alternative Run options it offers.. Please do peruse the documentation sometime. It might prove useful! ;-) Pete

4.82 hasn't been supported for quite a while! Just run the installer. NEVER uninstall. Pete

There has been absolutely no change in version 4.90 over the previously supported version other than the removal of the codesign checking and signature. Regards Pete

When such programs are starting up they make their requests for the data they are going to be needing. At that time the requests are being sent through to fS. That's the only time because once the need for specific data items is recorded with the Server, it is sent automatically everytime it changes. It never needs to be requested again unless the connection is lost. So things are going to start up with something approaching a traffic jam, then smooth out. But I thought you said you were getting good flying for 10-15 minutes before things started clogging up, so I would have assumed you were long past the possibly clogging up phase. If it is to do with this phenomenon, then it might just be that the programs have rather short timeouts on their data requests, so fail and complain even though the initial data is going to be arriving soon. The way I get over a potential jam initially is use the Delay option between the Run commands in the WideClient.INI. file. For example, here's part of the [user] section in one of my WideClient.INIs: Run1=c:\WideClientOnly\wideclient3\wideclient.exe Delay1=3 Close1=Yes Run2=c:\WideClientOnly\wideclient2\wideclient.exe Delay2=3 Close2=Yes Run3=C:\pfdcopilotND\pfd.exe Delay3=3 Close3=Yes Run4=C:\pfdpilotND\pfd.exe Close4=Yes [/CODE] See the Delay's, separateing the loading of each application? Regards Pete

No, that is the FSUIPC.LOG, the normal run-time log. I need to see the log that the Installer produces. It is called FSUIPC Install.LOG. Yes, and that Window is headed "FSUIPC Installer: Found FS9.1", right? so it did install! Behind that window there's a larger one headed "Installer for FSUIPC" and it contains the log which you can look at and save. In that log it will tell you where it found FS9 and therefore where FSUIPC's updates will be installed! The Install log itself will be saved too, when you finish the installer, but you can read the log on screen too, before "OK" ing the message box. You must have two installations and are looking in the wrong place. The Installer installs into the correct one, the one pointed to by the Registry. If you've made another copy of FS9 without reinstalling it then the registry will be wrong, pointing to the original installation. If you want your copied installation to be the main one you should fix the registry so it points to it. There is a utility which will do that for you, here: http://www.flight1so...stry_Repair.exe Pete

Ok. Thanks for letting me know. I looked up VAFS and it seems to me that it should only be reading data, not interfering with controls. That is if it really is the "Virtual Airline Financial System" program? Pete

The prompt to find FSX only appears if your registry is corrupt or you've moved FSX without reinstalling -- FSUIPC, like many programs, uses the Registry to locate the FSX installation. Have you perhaps restored your Windows system to a point before FSX was installed? When you locate FSX.EXE in the Explorer style Wnidw, and actualy select it, the Installer should carry on. If it appears again you've not actually selected it. Maybe you should show me the Installerr log file rather than quote bits from it? You could also repair the registry first. This tool will do that for FS9 or FSX: http://www.flight1software.com/files/FS_Registry_Repair.exe Regards Pete

There's been no change whatsoever in 4.90 from the previously supported version (4.88) except for the removal of the code signature check. There is an option to NOT use the centre mouse button for mouse look, but that's been in for a couple of releases. You'll need to be more specific in what you've done and what you've changed. Incidentally, there's also a Mouse Move option which uses the wheel to MOVE back and forth. Sure you aren't confusing with that? Mouse LOOK doesn't move your eyepoint at all. Mouse MOVE can move your actual eyepoint in the cockpit back and forth with the wheel turning, and left and right with the wheel pushed to the sides* -- it doesn't use mouse movements at all. It sounds like you may be mixing up the two facilities. You CAN enable both and both will work fine in 4.90. I just did, here. * I suspect not all mice have side movements on the mouse wheel. Pete

Have you checked the calibrations? Also always test first with a default aircraft. Pete

Why? That's a very drastic measure and is seldom a good idea. Best to replace or clean your device, or check why your power supply is so varying. The filter facility was originally added for a guy in the Thai jungle with really bad power supplies! I've never seen it needed with any modern installation. Pete

Merely updating your version of FSUIPC changes absolutely none of your settings. You need to look elsewhere. Regards Pete

Well, there's no indication of any network problems in the log -- as i said, it records as performing well. The problem would be that there'e be 10-15 minutes of detailed logging (reams and reams) before there MIGHT possibly be something worth looking at. You'd need to look at it yourself, checking the times on the left 9they are in milliseconds since the time logged at the start) and just send a section. Even then, not knowing which program is reading what I'm unlikely to be able to tell -- it isn't as if there will be any errors, as if there were there'd be evidnce in the default log. If I had a program misbehaving like their's I'd log the problem in the program, as that knows what it wants and what is missing. Pete

All my uploads are in the Download Links subforum here. The Schiratti links just point back here. If you look at the Updated Modules in the subforum it will be obvious. Pete

Ok. There doesn't look to be anything there which would be sending much data TO FS, it's all requiring just updates FROM FS. The two highest data SENDING applications are the PIOT and FO displays, which I suppose is what you'd expect if they want to be smooth: 1652862 Client 6508 requests: 102655 (Ave 64/sec), Data: 64500448 bytes (40489/sec), Average 628 bytes/Process 1652862 Client 2748 requests: 95753 (Ave 60/sec), Data: 59492959 bytes (37346/sec), Average 621 bytes/Process Well, there are no errors logged, but remember, I did say that UDP has no error detection. It can lose or corrpt blocks without any attempt to correct them and no notifications. HOWEVER, the WideFS protocol does check the lengths, sequence numbers and sumchecks on each received frame, so it should be okay in any case. I've been using UDP for ages and the only times I've ever had any problems (which is hardly ever) the log has been showing the errors, things like sequence errors and sum checks. There's lots of logging available, right down to all the data and every single exchange both with the programs and with the network, but if we enable that it will be many many megabytes, and honstly I wouldn't have time to pore through it even if you could get it to me. I think your first step must be to ask the JET45 folks what they think, What causes those symptoms in their programs? BTW didn't you ever try TCP protocol without that CWP program running? Pete

That looks perfect. But where's that "Jet45_CWP_Driver" program? You seem to be not running that now but several others not listed before! 46129 New Client Application: "interfaceIT" (Id=9484) 379035 New Client Application: "interfaceIT" (Id=9972) Was that 2 copies of "interfaceIT", or did you restart it after about 5 minutes? That's pretty impressive performance. What is your average FS frame rate? Interesting if most of those applications are instrumentation, not control, that the transmission of data TO FS is so much higher than reception from it. Why is that? Are those not just display instruments after all? Pete

Didn't the installation program for 3.999z2 report any problem? I can't help without any information. I'd need to see the Installer log file, please. Paste it here. And please actually descibe what you see when you run it! Pete

Well, I'm sure you can run AISmooth from someplace more, er... "sensible". Not sure about Linda though? Pete

Error 193 means that the program pointed to is not a valid program and can't be loaded. Not sure why you get that. Quotes don't seem to matter unless you want to add command line parameters. I never ever let FS install in its default folders like you. Nothing but trouble themn from 3rd party apps wanting write access to folders. So I don't have a folder path like yours. However, I tried this with a program which is in Program Files and has spaces: Run1=CLOSE,C:\Program Files (x86)\CE Remote Tools\5.01\bin\ccfilevw.exe and it ran fine. If it can't find a file it gives error 2 and if the path is not valid it gives error 267. So neither of those cases are true. Put, say AISmooth.exe someplace like that and see if that changes anything, because currently I'm afraid I don't have a clue. BTW you know you can use the EXE.XML file to run EXEs too? Only trouble that way is they don't close when you close FSX. Regards Pete

SimMarket could say how many of each they've sold registrations for, but many FSUIPC users are not puchasers. FSUIPC has no on-line link to upload usage information. In terms of actual add-on sales (not just of FSUIPC but all things FS-wise) I'm pretty sure FSX overtook FS9 a few years back. However, there is certainly a strong FS9 user base, and this saddens many developers because of the need to make two versions of things in order to cover a broad enough base. Regards Pete

I've now uploaded just the DLL itself in a ZIP in case anyone is really worried about the Installer. Pete

It's a rare timing bug in SimConnect. Please read the FAQ subforum thread on the subject: http://forum.simflight.com/topic/68382-fsx-fails-to-run-after-fsuipc4-first-installed/ Pete

It's never used as an email address. It could be a home address or a company registration. It's only part of the way used to tie the key to you uniquely. Name alone is often not sufficient. Pete

FSUIPC doesn't have a text line. They are all FS's. If you mean the normal text bar which is FS's (eg fir ATIS), and which can also be used by programs directly or via FSUIPC, then I'm pretty sure its location and state (docked or undocked, and shape) is saved when you save a flight. It's one of the "Window" sections in the saved FLT file I think. Have you tried? Pete

I've also now uploaded a ZIP containing only the DLL itself, no installer. If it is only a false pattern being found in the Installer then maybe the 3.999z2 DLL only will not trigger a response from NAV. Regards Pete

When you say "both" you mean both FSUIPC and WideFS? Between WideServer and its INI file? The INI file merely contains the settings. If you were using WideFS before there's no need to change your INI file. No, you showed only the WideServer and FSUIPC log files, both of which show everything is fine. What about the Client log, from the PC where you are running WideClient? There's always two (2) ends to a connection -- one on the FS PC and one on each client PC on the Network. Showing only the Server shows only one end, and that end is working fine. Pete