Pete Dowson

Right. First thing, it is obvious that you have NOT changed the Explorer option to hide filetypes, because your FSUIPC4.INI file is shown as just "FSUIPC4", whereas its name is FSUIPC4.INI, and your FSUIPC4.LOG file, which you denied was there even though I told you with Windows hiding things it would just look like FSUIPC4 as a text file. Do you see it now? 7th file down!!! The FSUIPC Install Log is called FSUIPC Install.log, and those two WideServer files are also filetype .log. You are obviously very confused by all this, and I would very strongly advise you to (a) change the folder options in Explorer to not hide filetypes from you, and ( B) get help with FSGRW from folks that know it, i.e. their support! Pete

And what are the names of all the files? Pete

You are not looking correctly then, because FSUIPC always produces a log. There's no way it has ever run on any machine anywhere without making a log file. Show me a directory listing for the Modules folder. You can do this by using the Dir command in a DOS window (command <ENTER> in the Run edit place), do dir <path to FSX>\modules >modulesfiles.txt or just take a pic or the explorer window showing the Modules folder. Pete

I can't tell without the run-time log. The installer's log merely shows it installed okay. Pete

Since your other aircraft are okay, it is going to be a specific problem with just that one, and obviously not with FSUIPC or your hardware. Have you asked their support? Maybe it doesn't like the old FS98 type throttle controls (ThrottleN_set, rather than Axis_ThrottleN_Set) which have to be used when calibrating with a reverse part of the axis. I believe there are a few like that. If it operates okay without the Mapping to the 4 throttles (which will allow it to use standard FSX controls) then that is the reason, and you will have to find another way to apply reverse -- either a separate reverser lever, or using buttons to operate throttle decr controls (like pressing F2). Pete

Well, there are two things I have to say to that. The first is that it's mostly gobblydegook to me, (and therefore that it is FSGRW support you need to show it to), and the second is that this part: most certainly talks about some TCP protocol and sockets being used, and not connecting. Since connection to FSUIPC uses no such mechanism I believe you are looking in the wrong direction. Evidently FSGRW needs something else you have not provided. Have you not even yet bothered with the support for the very program you have problems with? It would seem to me to be the obvious first place to go rather than waste so much time here, don't you think? Pete

FSUIPC always makes a Log. I suspect you are simply not recognising it because you have Windows hiding filetypes from you. Please change that Windows option as described in the FSUIPC documentation. With Explorer hiding filetypes it will simply look like a Text file named FSUIPC4. Pete

None of my programs link multiple copies of FS. It sounds like you are talking about a WidevieW problem. WidevieW is nothing to do with FSUIPC or WideFS. I suggest you try their support forum. Pete

No, sorry, it seems I don't. You simply need to create a new account with your new email address so you can purchase an FSUIPC4 registration. That should be no problem. People do it all the time! Pete

If thee is no Log file, then FSUIPC is not running and has never run! There will be no INI file generated either. What files are there? It sounds either like you have not installed FSUIPC yet, or your installation failed. Pete

By "new" FSUIPC, do you mean FSUIPC4, used with FSX and P3D? If so, then, no, you must purchase a new key. I can't help you there. You have to do that through SimMarket. Pete

That line simply means that when you run in global weather mode (DWC), FSUIPC is able to obtain local airport weather directly from Active Sky when requested by applications such as Radar Contact. If that hadn't been implemented in Active Sky then when the weather is the same all over the world, as it is when using DWC, programs asking for weather at an airport, for ATIS or whatever, will get exactly the same weather as that at the aircraft. The facility was first implemented in ASE and is also in AS2012. It is nothing to do with smoothing or wind shifts. If you want to you can disable it -- look in the Advanced User's guide for the INI file parameter. Incidentally, I strongly recommend an upgrade to ASN. Its weather capabilities are way beyond what AS2012 achieved. Pete

Yes, at last, what? You have it sorted? Do i need to know that? Pete

You could try Paul Henty, in the SubForum above dealing with his .Net interface. I know he is very good with .Net VB. I don't know if VB6 is much different. Pete

It IS a string! An ASCII string with one byte per ASCII character, ending with a zero byte. The format is called "ASCIIZ". It is standard format in C, C++ and FS, but not in VB. How do you 'decode a string byte by byte'? Do you mean interpret the weather. converting METAR gobbledegook into English? I suggested checking that you are reading the offset data correctly by comparing what FSInterrogate, shows. That is the utility provided in the SDK to help you debug your code. you can also use FSUIPC's logging which gives extensive assistance, especially with ipcRead and ipcWrite logging, to see if your program is operating correctly. Pete

In your original message here you said the error report was An error occurred during communicating to your Simulator........ blablabla Maybe the "blablabla" bit explained what it was that the program didn't like? Why do you think part of the error report in unimportant? Have you asked FSGRW support at all? That seems like the obvious place to go with a problem in their program. They should be able to diagnose it for you. If you merely want me to check that your FSUIPC is working correctly (now) in P3Dv2.4 then please run P3d, then close it down and show me the FSUIPC4.LOG file contents from the P3D Modules folder. Pete

Several points there. That "calibration" is not in FSX at all. FSX merely sends you to the Control Panel applet which does it for you. That calibration would apply to the input which FSUIPC would get in any case, it is done at driver level. Second, the Saitek quadrant is surely not the Yoke? Third, the Saitek quadrant has no range past what you call a "detent". When you pull back far enough.to the part at the front after the mini detent it operates a button, not any lower axis values. This is why everyone I know of uses the button programmed to "throttle decr" to engage reverse, as I keep telling you. If you really want a reverse range you'll have to give up part of the main lever movement. Yes, it would do if things were working correctly on your system. FSUIPC uses standard Windows DirectInput facilities for reading joystick axes and buttons and it has worked fine over all these last 10 and more years. There's no other way for me to implement it, and it works correctly for 99.99% users, at least. I'm sorry, but I don't know how to help you solve this problem which apparently is just one of the many problems folks have with Win8 and Saitek incompatibility. Well, I don't think you need to remedy anything, merely program reverse the way it is intended for Saitek Quadrants. Anyway, what do you actually mean by "no success"? Do you mean you assigned the throttles in FSX but don't then see them operating in FSUIPC's Joystick Calibration tab, on the throttles page? If that is what you do mean then you most certainly have a serious problem with SimConnect, because all that tab does is use SimConnect to intercept the actual assigned FS controls and allow you to calibrate the final values before sending them on to FS's simulation engine. If your SimConnect system is trashed you need to repair or reinstall FSX I'm afraid. Pete

Have you actually sent a read request first? It's the same as reading weather through the NWI, but just that you can get the string instead of having to decode the binary array data. And try using FSInterrogage to monitor the offset. I'm not able to check your code, it is in VB I assume? I don't know it. Pete

You don't need anything to do with WideFS for ASN. For ASN you have to have Simconnect configured for network access. ASN doesn't use FSUIPC or WideFS and WideFS doesn't use Simconnect. Ah, that explains it. I only have the free AVG. Pete

ASN and WideFS have absolutely nothing in common. I think you must have a lot of other things going on there, something is obviously badly wrong, but it certainly doesn't look anything to do with WideFS. I've no idea what you had in your FSX.CFG to make FSX crash, but there certainly is nothing in there which relates to ASN or WideFS in any case. The only thing likely there is that the default flight is bad, or the aircraft or the weather loaded with it. I'm afraid I cannot support ASN as it is not my product and uses nothing I've written. If the network is getting blocked or messed up by just trying to use two separate programs using entirely different ports then your Network setup needs sorting out. I suspect having two routers connected is making things bad as they'll both want to do things. You should make the second router an access point only, NOT a router. It'll be in the configuration somewhere. You must certainly not have more than one box trying to assign IP addresses. Pete

If they are FS controls, as you say, they most certainly ARE listed in the FSUIPC assignments drop down. You are simply not finding them! FSUIPC uses the names of the controls as defined in FSX's own "CONTROLS.DLL" and which FSX itself uses when recording your assignments in its XML files. The "names" of the controls in FSX assignments are not really their names, but translated descriptions, and vary according to language version. The actual names do not vary. If you can't find them by looking through the list, try searching for some of the key words. Or just enable Event logging in FSUIPC, operate the controls by key or mouse, and look in the Log to see their real names. FSUIPC's control list is actually a superset of those shown in FSX's assignments. It has all of those plus a lot more which aren't even supported by FSX's dialogues. Pete [LATER] I did a simple search for "Static" and immediately found "TOGGLE ALTERNATE STATIC". Similarly searching for "feather" finds "TOGGLE AUTOFEATHER ARM", and "Sync" finds "TOGGLE PROPELLER SYNC". I get the feeling you didn't really look very hard! :-(

Yes, just assign to the Axis Mixture Set control. When calibrated full rich is full forward and full lean is full back, Pete

Where do you calibrate in FSX? There is no calibration there! FSX relies solely on good calibration by the driver or by Windows' Game Controllers. If you can assign in FSX then you certainly should be able to in FSUIPC as it uses exactly the same interface -- but it can only identify devices to which Windows assigns a joystick number in the range 0-15. Unless you actually have more than 16 joystick type devices attached it should certainly be so assigned. Maybe the Registry entries for your device are incorrect -- try uninstalling them and thir driver in Windows' device manager, then re-booting. Also, you do NOT have to assign axes in FSUIPC in order to Calibrate in FSUIPC. The FSUIPC calibration is NOT axis calibration, but FSX control calibration. In other words it works on the control value inside FS, not on the input from the axis.

Only that possibly the loading, compiling and execution of such a complex script is sometimes taking longer than the interval between changes in the axis values. There are two things you can probably do about that. One is to compile the script (FSUIPC can load pre-compiled scripts as well as text ones). I think the compiler is called LUAC and should be available on the Lua website. the other is to increase the Delta on the axis assignments so it isn't called so frequently. An alternative, requiring a little change to the script, would be to make the script resident (loaded by an [Auto] parameter), and have it process the ipcPARAM on a polled basis -- i.e using a timer event. Then assign the axes to LuaValue instead of direct to the Lua script itself. I must admit i'm surprised cowl flap controls requite such a complex script! Pete

Are you Valentin Hernandez, email vhernandezpal@telefonica.net? If so I can get your FSUIPC3 key, as purchased in FS2006. Is that what you want? If so write to me at petedowson@btconnect.com. Pete