Pete Dowson

It could be part of what is slowing things down. Check that you haven't got SimConnect logging enabled all the time -- it produces huge amounts of information. (It's enabled via a SimConnect.ini file in your "My Documents\Flight Simulator X files" folder). Regards Pete

Okay. Thanks. I'll check the button assignment processing. Pete

From your further email [PLEASE USE THE FORUM!] No. It shows WideServer is running okay and is waiting for WideClient. As I said above, I need to see the other logs, particularly the WideClient log which shows what is happening on the Client! I have a feeling you've not bothered to read the section in the WideFS User Guide about configuring your network, the part which it tells you in emboldened red that all users should read part of it! You are probably doing something like using Win7 or Vista on one PC and XP on the other, and haven't put them in the same workgroup. At this rate this exchange is going to go on for days and days. If you would kindly read what i post and supply the right information it would be a lot quicker and easier for both of us! Thank you. Pete

All of FSUIPC's offsets into FS are listed in the offsets lists supplied in the SDK. There are none specifically for any add-on aircraft because FSUIPC is basically an interface into fS, not into add-ons.. I'm afraid I can't help you as I don't know what add-on you are talking about, and I don't have an ATR anyway, and you don't even say what version of FS you are using. :-( All I can suggest is that you look through other folks' contributions in the User Contributions subforum to see if anyone else has found information of use to you. Regards Pete

You can't separate FS gauges from FS. They are part of FS. WideFS only extends the FSUIPC interface to other PCs, so it only supports external programs, separate programs, which use the FSUIPC interface to connect to FS. Perhaps you are confusing it with WidevieW, which links several PCs running FS. There are programs which provide packages of gauges which do run on separate PCs. -- Project Magenta is the one I use. There's also ProSim 737, SimAvionics and FSXpand, and others too. WideServer.DLL, the separate module which used to be used alongside FSUIPC3, is built into FSUIPC4 for efficiency. But it is still only enabled with a purchased registration (for WideFS7), just as WideFS6 was. Regards Pete

Something is causing SimConnect to stop sending data to FSUIPC for a period which exceeds its timeout. Once it happens it seems not to recover despite all the FSUIPC retries. This is logged here: 1689413 **** No SimConnect events or states being received! Re-connecting now ... **** 1689522 SimConnect_Open succeeded: waiting to check version okay 1689522 Running in "Microsoft Flight Simulator X", Version: 10.0.61472.0 (SimConnect: 10.0.61259.0) 1689522 Initialising SimConnect data requests now 1689522 FSUIPC Menu entry added 1689647 \\DESKTOP-PC\Users\System User\Documents\Flight Simulator X Files\AutoSave Sun 135943.FLT 1690193 System time = 02/12/2012 13:59:50, Simulator time = 17:26:43 (10:26Z) 1809050 **** No SimConnect events or states being received! Re-connecting now ... **** et cetera .... I don't know what is doing it. You could try stopping each SimConnect-using add-on in turn to check. You could also extend the FSUIPC timeout to see if that at least allows it to recover. That's this parameter in the INI file: SimConnectStallTime=1 That's 1 second, the default. Try a higher value. There is a problem, and this is only a possible work-around. Since SimConnect should be sending data to FSUIPC at the frame rate, to not receive any for a whole second is certainly wrong and unusual. Regards Pete

From your email: Just replacing the binary program files with the same binary program files cannot make any difference. Only deleting the FSUIPC.KEY file, the one containing your registratin data, could make a difference, and you'd need to re-register. Why didn't you just follow my instructions above? And what do the Logs show? There's an FSUIPC.LOG and a WideServer.Log in the FS Moodules folder, and an WideClient.LOG on your Client. They contain the information needed to resolve things! I really cannot help at all without information! Pete

You need to revoke your previous registration. So, run the Installer. When it gets to the Registration, select "both" and "Delete the registrations". THEN enter the new ones, for FSUIPC and confirm then WideFS and confirm. I think maybe you are choosing "enter new registrations", which, I admit, isn't quite as it could be. it currently allows you to enter a different email which doesn't take. I'll fix that. Originally you couldn't change the name and email without deleting. Something changed when i relaxed the rules on having tow emails the same. Sorry. Pete

You don't really need to write so often. As I said after I checked, it takes the value for around 10-12 seconds after, so your original 5 secs interval would be fine. Well, yes, for smoothing, but enabling smoothing also enables FSUIPC's wind effect simulation -- turbulence, gusts and varianvce -- unless these are disabled in that section of the options. If you never want such effects, even when the weather report demands them, then it is okay for you to have smoothing off. But I would think the effects would normally be needed -- unless you are going to simulate them yourself? Well, from the three stations it uses for interpolation -- which are not always the three closest. In some cases the triangles used are ridiculous. I don't know if this one was corrected in FSX, but in FS9 one of the triangles, surrounding Rotterdam, had two vertices in the Netherlands and the third in North Africa! That could give rise to some weird interpolations. However, that's a diversion. The main problem is a bug in FS where during interpolations it can, in certain circumstances, get the sign of a value completely wrong. This is just like having a 180 degree reversal in on of the components. It's a known bug in FS (Micxrosoft knew about it) but it was never actually located in the code and corrected. Thanks. I may have a play. Regards Pete

Not sure how you connect that with a need to update FSUIPC. You should keep FSUIPC up to date in any case. There's a log file produced by the Installer which will clarify what is happening. That is why it is produced. I have no idea otherwise. Please paste the Installer log from your FS Modules folder into a message here. Again, I cannot see any connection between your problems with FSUIPC and your CH yoke not working. FSUIPC is NOT a hardware driver. It is not and never has been necessary to use CH devices! A few weeks? Did you never look in the Log to see what was reported? Sorry, I need information to help. Regards Pete

Can you clarify, please? How are you running these? I'm not aware of any particular problems with spaces in the names, but maybe it's a peculiarity in only one area? Button assignment, macros, [Auto] sections, Lua calls in other Luas? Which? Regards Pete

Yes -- unless you assign to Offset functions, or the control parameter works on your aircraft. I'm a little puzzled why you say 'E'. Here, by default, E selects an Engine. You need Shift+E for doors. Have you changed that? For FSUIPC4 INI editing, all you need to do is understand that any button can have many lines of dfferent assignments, and each of these are executed in sequence. The E+1 etc combinations you mention work just as well with E pressed then 1 or whatever soon after. However, using keypresses is, in general, not good. You become dependent on the whims of the Windows keyboard buffers and so on. An in any case, in FS itself, they keys are looked up in the table which tells it which controls to send, and then it sends the controls. (The table is an XML file which is made from the FSX keyboard assinments you make, or default). You must see how inefficient that is? The Shift+E key actually converts to the Toggle aircraft exit control, and the 1-3 to the Select 1, Select 2 and Select 3 controls. To use this method, you'd assign to the Toggle Aircraft Exit control and add another line in the INI file for the Select N control on the same button. FSUIPC executes them in order of line number. Formats are given in the FSUIPC Advanced Users document, and you'll also find the list of FSX control in your FSUIPC Documents folder. The alternatives are: 1. Assign to the Toggle Aircraft Exit control with a parameter of 1, 2 or 3 respectively. This should work -- worth a try for sure -- but it may depend on the aircraft model. 2. Assign to Offset byte togglebits, with offset x3367 and parameter x1, x2 or x4 for doors 1,2 and 3 respectively. Regards Pete

You have obtained a new WideFS6 registration and entered it, but you entered your original WideFS6 registration email address instead of the one you were clearly told to in the notification from SimMarket: When you are dealing with computers you MUST take care to do things exactly. They are not really intelligent enough to understand that when you say one thing you really mean a different thing! Just run the Installer again and re-register with the correct details. Regards Pete

Well yes, and you'd be correct. Surely this line is a BIG clue? So, it seems it isn't registered correctly! If you are having trouble with registrations, ZIP up the FSUIPC.KEY file in the FS Modules folder and send it to me along with any records you have of the Order numbers. Send to petedowson@btconnect.com. I've just done another search on SimMarket for your orders with the long email address (davidwoolfstein@gmail.com) and can only find registrations for FSUIPC3 and FSUIPC4 now, no WideFS. BTW why do you mess around with font sizes. Makes it very awkward when replying! Regards Pete

Yes, so best not to take FS's MAC computation too seriously. I use the one computed by Project Magenta in its CDU. Regards Pete

I've no idea why you get different results on FS9. The rudder effect is limited to 10% of its default action whilst below 30 knots, just as in FSX. It sounds rather like you haven't assigned both the tiller and the rudder pedals "direct to calibration" and calibrated them. And did you remember to change the MaxSteerSpeed parameter to -60 in the relevant calibration section? Regards Pete

I don't know where you get the formats you are suggesting here from. What's the "6,"? Do you mean 6=? One button assignment line can only include one control or one keypress. If you want the same button to do several things, they must be all on separate lines. They will be executed in order of the line number (the number before the =). Or alternatively you can construct a macro with the multiple entries invoked by one button assignment line. That's more efficient. However, for manipulating FS Menus you need to realise that once a menu dialogue opens, FSUIPC isn't running anymore and cannot interpret more data or send more keypresses. FS's dialogues are like most other dialogues (including FSUIPC's own) -- they are "modal" which means all else stops whilst you deal with them. If you send a sequence of keystrokes then some, maybe all if you are lucky, enter the keyboard buffer -- but not necessarily enough to carry over into the dialogue in order to accomplish what you want to do. The only sure way is to program your button to invoke a Lua plug-in to do the job. Plug-ins can work because they are running in a separate thread and are still operating when FS is in a dialogue. Exaples of using plug-ins to operate FS dialogues are provided in the ZIP file in your FSUIPC Documents folder. Check the ones called "Fuel737.lua" and "Payload737.lua". These are good examples. Regards Pete

Several things here: First, you have no condition on the first two actionsd, so even if you had button C,19 pressed the relevant line 1 or 2 would still activate. You need - conditions on those so they don't activate when the button is pressed. Second, there is no 'P' after the () condition -- the P occurs before the condition, exactly where you have the first P. Third, I don't know which is your Joystick 0 -- you deleted the joyletter section entries defining the numbers. Try using A instead. So: 1=CR(-C,19)A,2,K81,10 2=CR(-C,19)A,3,K81,11 3=CP(+C,19)A,2,K84,8 4=CP(+C,19)A,3,K82,8 Regards Pete

Hmmm. Probably to do with the spaces and the two sets of "". I'm not sure the "" help with the parameter. I would very strongly suggest installing IvAp to a decent top-level folder, like C:\Ivap, then use: Run1=C:\Ivap\ivap_dllhost.exe C:\IvAp\ivap_fsx.dll FSUIPC only looks at the Run commands during initialisation. Regards Pete

Okay. I've done some tests of my own, with wind smoothing enabled too and the effects allowed (turbulence, variance, gusts). The direct wind offsets still work okay and even the effects still occur, just using the forced direction and speed as the new "centre". Furthermore I've added the wind smoothing calls to the path originally only used for direct wind changes, and, whilst i can't swear that this will remove your "circling" nuisance (which I can't reproduce in any case). at least it has the same chance as the direct wind setting. It certainly doesn't seem to do any harm at all. So, please replace 4.859f with FSUIPC 4.859g test and do any further testing with that. I'll be using it in flights over the weekend and if I don't see anything untoward I'll make it more generally available, so let me know please. Regards Pete

Not really a bug, as it was never an advertised facility -- it's actually documented as "not working". It was only your report suggesting it "nearly worked" which prompted me to question why. The fact that it was nearly working was something of a surprise I suppose. But then, back in the day, I was still hoping Microsoft would fix the facility so I didn't really test that fiddle code fully. I was concentating only on the smoothing. Seems not many folks before you had actually tried using it, or had and not pursued it at all. The "fix" involved adding the processing of the directly written wind values to the path used for smoothing, so that it operates just as often and on the same weather to Sim calls. I'm wondering now how it would work with wind smoothing enabled. The values are written after the smoothed values, but there could be conflicts. Maybe you could enable the smoothing and see what happens? Well, I'm not sure how this helps with clouds, and since it is using the same paths as the wind smoothing I wouldn't expect it to be completely free of those 'circling' defects. Though if it does really turn out to be so, let me know because maybe I can back-process the smoothing action into the older paths for the direct wind control. Mind you, I've rarely seen any 'circling' with smoothing enabled. They seem very rare. Maybe you are confusing the wind variance simulation with a smoothing defect? The variance effect can be disabled using the checkbox. Regards Pete

I don't. Blame FS then, or its modelling. The value is read from SimConnect varable "CG PERCENT" defined in the SDK as "Longitudinal CG position as a percent of reference chord". The description in the offsets list was provided by others. I don't understand that stuff. I think it was also called CG_PERCENT in FS9 BTW) Pete

It's a problem with the PMDG aircraft -- and, as far as I was aware, a well known one at that. Their aircraft save states and reload states in their own sets of files, using their own Save and Reload menu entries. Those are either not saved by the standard flight save call into FS, or are not reloaded when the flight reload call is done -- or quite probably both. You need, I think to either save using their facility, or reload using their facility (as well as reloading the RC files), or even both. You say: but my guess is that this is completely the wrong way around. Reload the RC files first, then the flight in FS. I don't use any PMDG aircraft so I cannot help further I'm afraid. If you can't figure it out I suggest you post in the PMDG forums. FSUIPC and Radar Contact cannot help with such things in any way at all, and they most certainly are not the cause! BTW I never actually use the RC save/reload options either. With a complete cockpit driven via six other client PCs and lots of different modules such as Project Magenta, it would be almost impossible to continue a flight from part way through -- in fact quicker usually to start the flight again from scratch! Regards Pete

Could you please download FSUIPC 4.859f test and test this with your method? I've added the wind setting to other palaces. Maybe this will overcome your detected omissions? Let me know, please. Pete

One correction to my earlier reply: your interval of 5 seconds should be okay -- or at least setting 50 mSecs doesn't make any difference. I keep the written value and keep applying it for a timeout period of up to 10 seconds or so. Pete