Pete Dowson

Average frame rate for running time of 5325 secs = 20.2 fps So FSX is running at 20 fps, and the applications on that client are getting at least that same frame rate each, excpet one: 2712078 **************** Individual client application activity **************** 2712078 Client 2168 requests: 49241 (Ave 20/sec), Data: 210572768 bytes (86018/sec), Average 4276 bytes/Process 2712078 Client 284 requests: 51697 (Ave 21/sec), Data: 220773822 bytes (90185/sec), Average 4270 bytes/Process 2712078 Client 3708 requests: 51803 (Ave 21/sec), Data: 221176910 bytes (90350/sec), Average 4269 bytes/Process 2712078 Client 2740 requests: 50525 (Ave 20/sec), Data: 211858476 bytes (86543/sec), Average 4193 bytes/Process 2712078 Client 2172 requests: 54819 (Ave 22/sec), Data: 96251110 bytes (39318/sec), Average 1755 bytes/Process 2712078 Client 3704 requests: 18896 (Ave 7/sec), Data: 69899779 bytes (28553/sec), Average 3699 bytes/Process The only exception is pmSystems, which is probably okay as that only needs to deal with overhead changes: 406 New Client Application: "pmsystems" (Id=3704) The only worry is the loading on that Client: 2712078 Max receive buffer = 1602, Max send depth = 26, Send frames lost = 5 You forgot to send the Server log, which would show its performance, but on the whole it certainly looks as if WideFS and FSUIPC are performing very well on a system which is struggkling with rather too much load. 20 fps is okay, but not exactly good. I also think you are rather overloading that Client with 4 copies of PPM's PFD! Why on Earth are you doing that? With F6 expanded mode you could have all 5 displays -- Pilot and copilot PFD and ND and the EICAS all from one copy. When I used to run several copies of PFD on one PC I got awful stuttering, especially in climbs, turns and descents. The problem I think is PM's use of OpenGL instead of DirectX. OpenGL is no where near as fast these days. Regards Pete

Fixed in 4.863, which you can get from the Download Links subforum. It was as I thought, but worse. In FSUIPC3 it would change between .0 and .5 every 5-7 seconds. Because of a re-use of the counter it was using for something else, in FSUIPC4 it was changing it every 100 mSecs or less! Not enough time to get the signal confirmed! In 4.863 it does it at 5 second intervals, roughly. Regards Pete

again, another log, another one unfinished. Please NEVER post logs without first closing the relevant programs! I already told you "With all those logs unfinished there's no useful information.!!!! Why are you sending this in any case? Last post you said "antill now work good"!? You are confusing matters. The logs are unfinished and otherwise show things are okay, with reasonable performance as far as I can see with limited data. Your FSUIPC log shows an average FS frame rate of only 18 fps but one of your Client PCs was getting serviced by WideFS at 15 fps, which is about what I'd expect in such circumstances. Please PLEASE stop posting incomplete logs. They are not useful. Pete

With all those logs unfinished there's no useful information. Pete

Any reason you are using TCP protocol? UDP is usually more efficient. I use it here with 6 PCs and Project Magenta and it is all very smooth. If using TCP is slowing things down then it will be due to lots of retries. UDP doesn't have error correction, so it needs a reliable network. This entry in your log is worrying too: 377179 **** ERROR! Sumcheck or length fails on received block (skt=9544), len=628 (time=5575680) 377179 **** (N.B. Previous block was only partial) That implies something not behaving quite so well on your Network. However, your performance figures don't look really bad: What is your average FSX frame rate? Maybe you should show me the FSUIPC4 log file to. Unfortunately the WideClient log files you showed were not complete -- it looks like you did not close the WideClients first. The performance figures for those are loast, they'd be at the end. Pete

You need to be on the current version for support. Download and Install 3.999z and try again. Pete

Hmm. It depends on recognising the ADF signal strength. Maybe, because in FSX I'm using Simconnect (which is asynchronous), it is taking longer to get that feedback and FSUIPC is not hovering on the frequences long enough. I doubt that the facility has been used since FSUIPC1 or FSUIPC2 days! It was original designed to suit hardware ADF devices made in the US which had no .5 facilkity because north American NDBs are all whole numbers. Sounds like that Carenado aircraft is only designed for you in North America? You probably need the export model! ;-) I'll check and get back to you. Pete

I always need VERSION NUMBERS please! You don't even mention whether it is FSUIPC3 or FSUIPC4, FSX or ESP or P3D or FS98 or FS2000 or FS2002 or FS2004!??? It sounds like you've made other changes apart from simply installing FSUIPC and WideFS. Check the WideServer and WideClient log files. That's what they are for, to tell you waht is going on! And what are the version numbers for the previous releases you are using? Note that the way WideFS works has not changed in any way affecting communications or performance for about 7 years! If you cannot figure out what the Logs are telling you, paste them into a message here. Include your INI files too please. And next time PLEASE give VERSION numbers. That's what they are for, so I can tell what you are using properly! Regards Pete

The doors offset only actually gives the door state. When you write to it, FSUIPC sees this and sends the FS control for the door on your behalf. Almost all switch and control offsets work like this -- FSUIPC converting your action into the correct FS control, so there is nothing stopping you using the control directly, either by assignment or via offset 3110. Use the jetway control. TOGGLE JETWAY. This is what the default assignment in FSX translates Ctrl+J into. Pete

Unfortunately, by definition, there's no valid screen position outside FSX when it is run in full screen mode, and as that is likely the normal way for most folks, I can't see how it can be resolved. If someone would like to see if there's a good parking place for the mouse on a full screen display, I'll try moving it there (recording first it's original position of course, so i can put it back then the control is pressed again). Pete

You need to state the version number of the Makerunways program you are using. And you can check for yourself exactly what is it doing by looking in Runways.txt which is a comprehensive log of all of the airport data files it examined and the results it got. Check that you are looking at the correct Scenery.CFG file. If it gets no add-ons whatseover it sounds like the default copy. Pete

After first installation FSX will always ask if you want to run the program, and trust it. After that it will not ask again. An INI file is generated when it first runs, it isn't installed. And if it has ever run there will bre a log file too, FSUIPC4.LOG. Why did you install the Loader? This is only needed in exceptional circumstances and the Installation guide tells you when to try it. Did you not read the one short document included in the downloaded ZIP advising you what to do? Please remove the loader and re-run the Installer. If you've purchased a registration code then registration is done as part of the installation process. Please do read the installing and registering document in the ZIP it isn't very long and won't take much of your time, really! What is "NOT found"? Is that your comment? I think you've omitted a lot of the Install Log which preceded the part you posted. Why? Okay. there's one really BIG problem you have, straight off. You have the base version of FSX installed -- the original one from September 2005 -- yet you've installed the SP1 and SP2/Acceration versions of SimConnect. These are NOT compatible with the original version of FSX. You need to install SP1 and SP2 updates to FSX, or, if you own it, Acceleration. Regards Pete

FSUIPC's installer makes sure that is installed -- and you'd not have either FSUIPC nor a server running if that were wrong. Wideclient can go anywhewre you like on the client PC. Replacing the same DLL and EXE with an exact copy of the same DLL and EXE will make absolutely no change at all. It isn;t anything to do with either. It is your Windows networking. I've never used any firewalls on my netwrok and have never had any problems, but every time i've seen reports like yours it has turned out to be a firewall. There is one other slim possibility, that you have something else installed using the same Port as WideFs and taking it first. You could try changing the Port numbers in FSUIPC4.INI and WideClient.INI. They must match each other. The registration details are in text form in the FSUIPC4.KEY file in your FSX modules folder. As advised in the user guide, you should have made a backup of that long ago! SimConnect.xml has nothing to do with it. Regards Pete

Sorry, I've no idea what FSX is doing. But the slow down is evidently nothing to do with the images of cockpit panels and mouse cursors. I've never noticed any slowdown whatsoever in frame rates when the mouse pointer is over any panels, but then I don't use any third party add-on panels at all. There's absolutely nothing else i know of in Windows that can help here, it must be solely down to the way those panels are coded. Don't the makers have anything to say about it? I susepct it could be cured by better panel coding. What if the new control also moved the mouse pointer, say to top left of the FS window? I could probably do that -- but it might cause some confusion when it re-appeared, unless on the next click I replaced it where it was? Does moving the mouse off the panels make the frame rate speed up? Obviously if you have the mouse pointer visible you are using the mouse, so wouldn't it be just as easy to move it away when done rather than press a button to remove the cursor? Regards Pete

Okay, done. Please get 4.862 from the Download Links subforum. Note that if FSX/P3D has also hidden the cursor, you still have to move the mouse to get it back. I've no way of overriding FSX/P3D's hiding method. Pete

Have you prrogrammed them to operate? FSUIPC's built in facilities for assigning buttons and switches to functions applies equally to all normal joystick devices and Go Flight modules, but FSUIPC doesn't handle displays and indicators by itself. It never has. How can it, they are too varied in implementation, and there is no pre-defined method of dealing with displays for all devices in Windows or even for GoFlight. There are two ways of handling GoFlight displays and indicators. The old way was with a program called GFDisplay. But much better now are the facilities for programming them build into the Lua plug-in system. There's a GFD (GoFlight Devices) library for both reading switches and writing to indicators and displays. There's an example Lua in the Lua ZIP installed in your FSUIPC Documents folder. Regards Pete

These are the meanings of those entries. They are records of changes to the FSX weather mode: Weather Mode now = Theme "Theme" is the setting of weather according to one of the listed themes in FSX's weather setting menu. Programs use the Clear Weather theme to clear previous weather in preparation for setting their own. Weather Mode now = Custom "Custom" is the mode which gets set automatically when a program starts setting specific WX station weather. Weather programs not using Global mode set the weather from METARs this way. Weather Mode now = Global "Global" is where one set of weather is sent for FSX to apply globally -- i.e. all over the world. This is used by weather programs for greater control as it avoids some of the bugs in the FSX weather engine which are due to interpolation between WX stations. I don't know Opus, but I use ActiveSky 2012. Ever since ASE, Active Sky has had a Global mode ("DWC" they used to call it -- Direct Weather Control or Direct Wind Control). It works so well that it is defaulted in AS2012. Maybe Opus does the same. However, you seem to be getting an odd cycle in modes: 2589913 Weather Mode now = Custom 2590054 Weather Mode now = Theme 2590054 Weather Mode now = Custom 2590756 Weather Mode now = Global 22 seconds gap 2813775 Weather Mode now = Custom 2813931 Weather Mode now = Theme 2813931 Weather Mode now = Custom 2815756 Weather Mode now = Global 12 seconds gap 2935206 Weather Mode now = Custom 2935284 Weather Mode now = Theme 2935362 Weather Mode now = Custom 2935752 Weather Mode now = Global 12 seconds gap 3056824 Weather Mode now = Custom 3056934 Weather Mode now = Theme 3056996 Weather Mode now = Custom 3060834 Weather Mode now = Global 12 seconds gap 3178365 Weather Mode now = Custom 3178443 Weather Mode now = Theme 3178505 Weather Mode now = Custom 3186758 Weather Mode now = Global 7 seconds gap 3193653 Weather Mode now = Custom 3193778 Weather Mode now = Theme 3193856 Weather Mode now = Custom 3195837 Weather Mode now = Global 36 seconds gap 3559163 Weather Mode now = Custom 3559272 Weather Mode now = Theme 3559319 Weather Mode now = Custom 3560817 Weather Mode now = Global 33 seconds gap 3893005 Weather Mode now = Custom 3893114 Weather Mode now = Theme 3893177 Weather Mode now = Custom 3896032 Weather Mode now = Global 33 seconds gap 4227861 Weather Mode now = Custom 4227939 Weather Mode now = Theme 4228002 Weather Mode now = Custom 4230966 Weather Mode now = Global 36 seconds gap 4266394 Weather Mode now = Custom 4266518 Weather Mode now = Theme 4266581 Weather Mode now = Custom 4271011 Weather Mode now = Global et cetera Not exactly regular, but regular enough to appear to be deliberate. Do these cycles roughly correspond to your stuttering and flicker? If not it might not be related. If so, could these intervals be realted to the update rate from your Opus weather settings? If it is deliberately updating weather with these mode changes then it certainly isn't good. Check that you don't have FSUIPC set to update FSX weather too, as that could interfere. You can use the stuff in the Wind Smoothing box, but avoid everything else. Also check that you haven't actually got more than one program trying to control the weather. Regards Pete

Exactly. That's the one. Press it then and see. Pressure variation you mean? FSUIPC does have QNH smoothing, and I see you have it enabled and set to the default of 1mb over 5 seconds: That should work in FS9 (I never got it working in FSX unfortunately). Maybe you need to try a different period? Pete

Looks okay, but then most things are just your options, as you might wish. I'm not really sure what you expected me to make of it, but just as a test you could switch off all FSUIPC's weather actions, using the button on the first tab. Make a copy of the INI first so you can reset everything they was you have it. To be honest I seem to remember that the flickering weather in FS9 was just one of the many reasons I changed completely over to FSX as soon as I could! Not sure about panels though. I don't have any panels visible at all, but i can't see how weather updates can flicker a 2D panel. Seems more likely to be a video driver problem, maybe related to weather flicker (cloud popping etc). Regards Pete

x10880 = 67712. They are the same. One is in hexadecimal, the other decimal. FS uses hex encoding for the frequencies, but parameters are normally in decimal as that's what most folks understand. Internally all Windows buttons number from 0 upwards, but again lots of folks don't understand counting from 0 so their "simple" user interfaces add 1. You should be able to subtract 1 to convert back without any pain? Pete

This is exactly what you'd get if there's a firewall stopping the requests from the Client reaching the Server. The latter is simply not receving anything. Check for no firewall blocks at either end. If you must run firewalls then allow FSX.EXE through on the Server and wideclient on the client. Regards Pete

No, sorry. I've tried in the past to generate oil leaks and so on, to no avail. If you were controlling your own complete cockpit you'd program you own systems to allow all sorts of things lie this, and just manipulate other factors in the FS simulation to generate the end effect. This is what completely separate systems do like Project Magents pmSystems, SimAvionics and ProSim -- possibly also some add-on aircraft like those by PMDG. But the internal systems of FS itself aren't complete and not very manipulatable. Regards Pete

Normally you'd actually ADJUST the radio to a chosen frequency. It' unusual to directly set a specific frequency, but you cand do it by simple assignment (in FSUIPC options NOT the INI) to "Nav1 radio set" with an appropriate parameter. The parameter would be x10880 for 108.80. Pete

The PMDG offsets are just those provided by PMDG, mapped directly into FSUIPC memory. There is absolutely no processing nor interference. You get whatever PMDG give you. Regards Pete

The "current" versions being what? FSUIPC 3.999z or FSUIPC 4.861? Version numbers always required. I don't even know if you mean FSUIPC3 or 4. Not using the installer? Just paste the Log into a message. But the Client is only half the story. I'd need to see the WideServer log file also! There are two ends to a network connection. Pete