Pete Dowson

But the email attached to the account IS the one you just said works okay!! vhernandezpal@orange.es. I told you that above. There is NO account in SimMarket with the email associated with your FSUIPC3 key!! This is where you are going wrong all the time, and you are not reading my replies!! They do not send passwords, they do not have access to your password, it is private to you. You must always make sure you use one which you will not forget! Anyway, I have managed to get them to change your password to an easy one and I have sent you an email -- to vhernandezpal@orange.es, which is the one associated with your account AND the one you said was working !!! Regards Pete

You are misunderstanding. Offsets hold data, sometimes input data sometimes output data. They are no "events". Events are actions, and initiated by controls with a control number and a parameter. Controls are assigned. You CAN send controls via offsets -- see offset 3110. The names and control numbers you saw in the log relate to the controls/events you need to use. FSUIPC sends some controls via SmConnect, and some directly to FS's wnindow. It varies according to function. It varies enormously. Add-on writers implement things which aren't, in their opinion, simulated properly or at all in FS. For those aspects, SimConnect doesn't help because it is just an interface into the simulator which they are programming around because of those shortfalls. Do you see? Maybe, underneath, the add-on code does use built-in FS actions, but being effectively made part of FS (loaded as one of its gauges, for example) it doesn't need always to use controls as such. Mouse macros in FSUIPC only operate on Gauges which are written in C/C++ to strict rules laid down in one of Microsoft's SDKs. Even most of FS's default aircraft don't supportthem. More and more aircraft these days use Local Variables instead. This is especially true of XML gauges. Pete

Okay, more information. It seems that is actually the one which you used when you purchased the FSUIPC3 key. You can still use it to buy FSUIPC4. It is not locked, you just need to log into that account. You only have the one account and it has been the same one now for at least the 8 years since you purchased FSUIPC3! Pete

Maybe, maybe not. At least it looks like you have most of the controls you need there then. The loop which happens every second is probably just to make sure certain things are set certain ways, and will be automnomous in any case so you can ignore that. A lot of these add-ons seems to waste a lot of processing that way when they only need to check if it has changed first. On the part where you say That looks like something internal to their code. I can only suggest you investigate the possibility of use local panel variables, or mouse macros. One or the other might just possibly be useful (not both). If neither then I'm afraid I've no idea. Are you getting any help from the add-=on makers? They'd really know all this better than someone like myself who knows little about any add-on aircraft. All i can do is point to the tools available. Pete

If you give me your current email address I will ask them if they can clear the account so you can start again, but first please do make sure your email is actually receiving messages okay. Send yourself one, as a check. After tomorrow I am away until November 26th. Pete

Oh dear. Why not just paste it like you did with the Install log? [LATER] Oh, I see. You've enabled a load of logging? Why on Earth have you done that? If you didn't think a log was produced, what was the point of enabling logging options? Anyway it shows FSUIPC is working just fine. Now, don't you think it is about time you went and sought the help you really need, i.e. with FSGRW? Pete

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