Pete Dowson

Interim updates and other things are available here in the Support Forum, via the Download Links subforum. It is one of four useful resources at the top of this main Forum page. No thank you. Found it by date. I see that was due to the aircraft name being reported as null (""). There's no way FSUIPC can select profiles without the name. Did you go through the checks I advised in that thread? Is your aircraft name coming across as blank also? I see that thread ended without any resolution being posted by the originator. Yes, it is the same. There is no way possible for FSUIPC to operate Profiles without names for the aircraft being profiled. Sorry. There is something about those aircraft which is messing up how the aircraft name is supplied. If A2A can suggest anything I'd be glad to cooperate, but FSUIPC can only work with what it is given. Regards Pete

Two points here. First: most devices do not signal their position until it is changed. FSUIPC and FSX react to changes. So for non-toggling switches (i.e. those using discrete On / Off controls), all you need to do is sync the switches initially by turning them on/off or off/on. Second, if you've assigned to toggling functions, like most keypresses and many FS functions, then the command isn't differentiating between on and off. In this case the only way to synchronise is to change the FS switch on-screen to match the hardware position. In general it is always best to find distinct on/off functions. If there is no such FS control there is often a way to do it through FSUIPC offsets instead. I always make sure that I close everything down, to cold and dark, before saving flights i intend to reload. Then i know in advance that the cockpit switches will match the FS settings. You need to say how you assigned the switch. You are probably using either the 'Z' key, whch is a toggle of course, or the "AP MASTER" FS control. In such a case, sync by changing the on-screen switch. Not automatically. You'd have to waggle the switches. BUT you would need to only choose separate on/off assignments, not toggles. Toggle controls are really only suited to buttons, not switches -- FS was designed for joysticks with buttons. They never really helped much with switches. For the AP Master you can assign as follows: AP MASTER OFF: control Offset dword set , offset x7BC, parameter 0 AP MASTER ON: control Offset dword set , offset x7BC, parameter 1 You can do similar things for other values. The offsets needed are listed in the FSUIPC offsets lists, available in the FSUIPC SDK. Regards Pete

Hmm. Strange. Could you please try version 3.999y2, now downloadable from the Download Links subforum? I've made one small change. I can't see anything wrong here, at least withthat version. Both FS9 and FSX (and all previous versions as far as I know) perform auto-assignments to devices they think are "newly connected". Maybe they fall asleep or give sme signal indicating such. I've always recommended either assigning all axes in FS or all axes and buttons in FSUIPC, and in the latter case disabling FS controllers completely to stop auto-reassignment. Regards Pete

No, just make sure you don't have the same buttons assigned in both FSX and in FSUIPC, otherwise both assigned actions will be executed. Use the Buttons and Switches tab in FSUIPC options, exactly as documented. Regards Pete

Can you please define what you mean by "latest version"? Is that 4.859i, or something easrlier? I always need Version Numberrs, please, else it could mean anything. See Download Links subforum for versions. If you have the problem with any supported version (i.e 4.853 or later) I need to see the FSUIPC4.INI file. I can't find that, and I'm afraid the link you provided doesn't work for me. Sorry, I don't understand. What are these "tools"? This is now sounding like a problem with A2A's software/ Have you asked in their Support Forum? Please try with the latest FSUIPC4 (4.859i) and let me see the INI file. You can paste it's contents here. Regards Pete

Yes. It is a rare tming bug in SimConnect. Please see the thread in the FAQ subforum entitled "FSX fails to run after FSUIPC4 first installed". Regards Pete

Done. Version 4.859i, now downloadable from the Download Links subforum, allows you to calibrate Steering Set in FSUIPC. Regards Pete

Okay. I'm glad it worked out in the end. Regards Pete

Well, I've never got any to notice, and that's also what others said. It's the reason I worked so hard on that aspect. What are you showing there? Sorry, I don't get it. I don't see any fast turbulence wobbling or jumping. And the aircraft doing jiggles and ups/downs (FSUIPC's turbulence operates in all three dimensions). Maybe whatever you think is happening to you in that flight doesn't happen with airliners? Turbulence should affect airliners too. Maybe fS is simulating some force which I'm not stopping with wind control. You'd probably need to log the X Y Z accelerations and velocities to see what is going on. Certainly the ambient wind isn't changing (the Shift+Z shows ambient). You're on SP2, not Acceleration. Might be different I suppose. Regards Pete

I spent at least two weeks full-time developing and testing a realistic turbulence emulation specifically because the smoothing removed the effect in FSX, and the same was reported by everyone. I had experienced pilots check out my emulation. It was quite an effort. I can't understand how you see differently, unless there's some difference here between versions of FSX. But if that option is disabled the turbulence setting in the weather reports are zeroed, so FSUIPC is not asked to make turbulence. BTW FSUIPC deals both with wind layer and cloud layer turbulence. Except by setting Global mode and providing a GLOB Metar string through SimConnect or FSUIPC. Regards Pete

That's not a version number! ;-). It will be 6.9 something I expect. "FS98" is a version of FS which first appeared in 1997 and upon which the whole FSUIPC offset interface is based. There is a limit on the filename length which can be used . The Lua facility was built into the existing Macro facilities in FSUIPC and uses the same tables. There's a limit of 16 characters. The name is truncated in the [LuaFiles] section in the INI file and in the drop-down list on screen, but the other characters are thereby lost so the file cannot be loaded. Just take care to make sure the name in the drop down does actually match your filename. I think I will change the way the list is built so that invalid names are never listed and therefore cannot be assigned -- it'ds never caused a notified problem till now. Spaces are okay, no trouble. It is only the length restriction. I thought this was clearly documented but I must admit I can't see it explicitly anywhere for Lua files, only for Macro files. Apologies. This omission will be corrected in the next Lua package update. Regards Pete

WideClient didn't even see the Broadcast as it did in the originalLog you showed, so what have you changed? Broadcasts are not sent until FS is "ready to fly", and won't get to PCs on a different WorkGroup. You've changed something to make it worse. I note that you only ran WideClient for a few seconds before closing it down! Sometimes it takes a lot longer, depending on your Network and what else is going on in both PCs. You tried to start a program on the Client too, which means WideClient was doing a lot of other things already, yet you still closed it within seconds! Pete

Er, sorry, I'm confused. 1. WideFS does not load FS9 or FSX 2. The WideClient icon is a globe in yellow and blue, nothing like either FS icon. 3. The actual icon used for shortcuts doesn't affect what they do, only what they look like. Where are you writing that line? What does it have to do with WideClient? There's no such parameter used in Wideclient. Please check the documentation. Perhaps you mean "Run1=..."? What do you mean "write something in Wide Client software to FSX on my other computer"? WideClient does not run on a computer running FS. And if you want it to run programs on another computer, install those programs onthat computer. Regards Pete

No, sorry. It's just the 3Gb memory usable to FS (including its own code etcetera) getting used up and fragmented. Sometimes saving a flight will tidy it up and either free some or at least defragment it so larger contiguous space is available. What is actually using it would be very difficult to determine. you can't tell by just looking at it -- it is just binary data. The only way would be to try to hook into the memory allocation API in Windows and log where the cals come from. And that isn't nice because the actual part responsible could be several layers back, so it needs a stack dump each time to find the originator. All this would slow everything down too much and create many megabytes of data which may not even help in any case. The only way is by trial and error using a process of elimination. Maybe it's only one specific scenery add-on? Maybe some specific AI? Or weather -- maybe using 4096 clouds is just too much? If you have a registered install of FSUIPC then you could try enabling the AutoSave. Having a flight regularly saved might help. At least some folks report so. Regards Pete

No, that's not true. Your writing to the offset is exactly the same if you wrote at 1 msec intervals or 10 mSec intervals. The value simply gets sotred in the offset. Whatever values are in the offset at the time FSUIPC wuld normally apply smoothing checks are applied instead of the intended smoothing value. The simulation of the three effects occurs as normal, should the weather setting demand them. I've seen it. You can check it yourself by using a wind layer which has turbulance, variance or gusts. No, that's the whole point. The whole reason I went to a lot of trouble simulating the effects was precisely because by overwriting the wind values between the WEATHER DLL and the SIM1 simulation engine, none of FS's effect were getting through. I had to add the effects myself else you wouldn't get them. The same will occur with this direct control via the offsets, because it is exactly the same as my smoothing -- even more so with the changes i did to make them work more effectively. If you've seen turbulence whilst controling th winds it will be FSUIPC adding it. Yuo can check that easily by inhibiting it or turning off smoothing. Yes. using global mode like ActiveSky achoeves the same because all the stations are then set identically. You don't like FSUIPC's? You can change them a bit with the parameters provided you know. No options checked = no weather modified. Correct. That includes smoothing disabled mind. You still have that diagnostic logging enabled? Yes, each time there's a pass through the code which sets the smoothing values, the ranges for turbulence, should it be needed, are recomputed. Since your setting of the wind offsets follows the same path, the same computations are made. but the turbulence won't be simulated with the smoothing switched off -- that's part of another routine. I could never get that working satisfactorily at all. The code is there but disabled. You can re-enable most of it by setting PatchVisibilityValues=Yes in the [General] section of the INI file. If you try it let me know how you get on! Regards Pete

The numbers on the left are the number of milliseconds sibce FSUIPC started. There's no more information here about your memory. When it is below 300 mb free you'll get this warning. It is re-checked every 10 seconds, as the times show. Fixing OOMs is by reducing FS sliders or using less detailed, less complex scenery and aircraft. Regards Pete

The log shows no connection in the few seconds you allowed WideClient to run. It hasn't even received the broadcast from the Server yet before you started "istation". What are you doing? You need to have FS running and Wideserver ready, waiting for clients, as before. Did you check or remove your firewalls? Pete

A power-dependent turning tendency is almost always due to over-high "realism" settings causing torque or propwash effects to hit the tailplane, though that certainly shouldn't happen with a 737. I would guess more at an engine thrust mis-balance. Did you delete the old assignments? Possibly a disconnected old assignment still has a driver feeding in bad values. Try using FSUIPC's axis logging to see if spurious incorrect values are occurring. Mind you, nothing to do with axis assignments (except throttles perhaps) should really make veering power dependent. That's more suggestive of a strong crosswind, needing opposite aileron and a little rudder correction. For the axis assgnments, please check, or show me, the entries in your FSUIPC INI file. I'd need to see the Joy letter section and the axes sections. For all else I think you need to check elsewhere, but do try using the logging. Regards Pete

Actually thst's the correct WideClient log. Thank you. If this information is correct: 219 Trying TCP/IP host "David" port 8002 ... 219 ... Okay, IP Address = 192.168.0.100 which it looks to be, then the problem is this: 1233 Error on client pre-Connection Select() [Error=10061] Connection refused which probably means that your Server PC has a firewall block on either all programs accessing it, or just this one. It could possibly be a firewall block on the Client, so I'd check both if I were you. In general, if you have a fireewall operating on your internet Router, as most folks do, it isn't so necessary to have it also on each PC, and it does make networking a bit of a chore. I've got 12 computers in my Network and if i had the firewalls all running I'd be up the wall myself! ;-) If you want to leave the firewall enabled you'll need to allow the program "WideClient.exe" through to the Server and the program "FS9.EXE" through to the Client. Regards Pete

And I am spending a lot of time trying to help you, to no avail because you do not seem to read what I say. This is the first bit of useful information. So you have something else wrong, which is why I need to see both logs. No, you did not! You just sent me an FSUIPC log and two WideServer logs, both of which show the same as the last, and still no Wideclient log file from your Client PC! There are TWO ends to a PC network link between two computers. The server end, where FS runs, is okay. It is broadcasting its service but the Client is either not connected or not running or is unable to see the broadcasts. The Client log would either confirm this or show what the problem might be. Also, if you did, as you say, read the first few paragraphs in the network configuring part of the WideFS User Guide, you would see that as an alternative to relying on the Broadcast you can explicitly give the Server's name or IP address. I think you are very confused here. In order to get the Server working, as it certainly is now, with your incorrect registration, merely deleting the FSUIPC DLL and the WideServer DLL would not have mad a jot of difference. When you deleted those you must also have deleted the FSUIPC KEY file, which allowed it to re-register from scratch. However, as i pointed out, the "delete" rather than "enter new" option woould also have done the same thing. The instructions I was referring to were to use Delete Registrations. Instead of that you deleted the DLLs and re-ran the Installer, and evidently the KEY file as well. This is why it DID then work, so daying it still did not sort out the problem is just plain wrong. It did sort out your registration problem! You now have a different problem, one on the network, and you still haven't provided the Log file for me to assist with that. I am continuing to try to help to the best of my ability, but I really must ask yet again that you read more carefully so you can begin to help me help you. There is nothing hard or complicated here. I ask to see a file, you show it to me, I tell you what might be wrong and how to fix it. You and I might both find it quicker if you pasted the file contents into messages here rather that coninuing to use emails, which were only for the confidential registration data. Regards Pete

I've tested this here, both for button and key assignment, including assignment to buttons on WideFS client PCs, and I cannot make it go wrong with spaces in the name. I'm wondering now if you have an older version of FSUIPC4 installed. Could you please confirm you are using at least 4.853, and if not update. If so, download the very latest from the Download Links subforum and try that. Regards Pete

Well, in that case it must have been something else and the update to WideClient a mere coincidence. Unless of ocurse the older one was corrupted in some way. Regards Pete

I think you must mean allowing the Steering Tiller calibration to operate on the FSX steering set control just as it does on FSUIPC's own steering tiller control. FSUIPC's axis assignment already allows assignment to the FSX steering set control -- it's in the FS controls dropdown. Alternatively I could have an option in the FSUIPC4.INI file for the FSUIPC steering tiller assignment to use the FS control instead of its own method, as used before FSX. I'll think about the best way. It's on my list. Regards Pete

I assume you mean WideClient in the laptop. FSUIPC doesn't run outside of FS. The WideClient in the laptop must have been very old because there's been no incompatibility in versions for several years! The improvements have been in other areas altogether, like the Lua plug-in capabilities. Anyway, glad you resolved it. Regards Pete

Well the console shouldn't be that harmful but it will slow things down a bit. It's caused by the "console=yes" line in the file above. But best for now simply to delete or rename the SmConnect.ini file. Regards Pete