Pete Dowson

It creates a new one, as does WideClient. WideClient saves one previous one (adding a '0' to the name), but not a stack. Pete

It shouldn't do. Sounds like it is cutting fuel or battery too, which it certainly should not. See what controls it is sending -- Event logging in the FSUIPC logging tab. Regards Pete

Good. It's unusual to have faults in those cards, but I'm pleased the fix was relatively easy in the end! Pete

Yes, but you have to do it by editing the INI file. You can have almost as many assignments to one button as you like. They are actioned in the order of the line numbers (the number on the left of the =). I didn't want to overcomplicate the assignments dialogue, which works fine for 99% of folks' needs. Once you add multiple assignments you can't edit that button in the dialogue -- it stops you so you can't mess it up. There are many things you can do with buttons in the INI file. Please see the Advanced User's guide. You can edit assignment sections in the INI whilst FS is running and simply use the "reload" button in the dialogue to get the changes actioned. Regards Pete

Well i assume they've implemented it like that so you can do it all ways. Many FS controls have "toggle", "on" and "off" variants, Oh, i keep making that mistake! Sorry. glad you sorted it anyway. I edited my original to fix the error in case anyone else copies it without reading further! Regards Pete

Hmm. Strange. I know your RC is running on the Server, but where it's at shouldn't make any difference at all. And your problem is nothing like the one i managed, with difficulty, to reproduce here. In my case RC was defintely making the weather requests but getting the wrong data. In your case there is absolutely no sign in the log of it ever making any specific requests whatsoever. Looking back at your first log it was the same, which was why one of the questions i posed then was whether the log was actually the one covering the period in which you asked for ATIS. Could you test again, please, but this time add these lines to the FSUIPC4.INI before loading FSX: They go in the [General] section: Debug=Please TestOptions=x2000 LogExtras=32 And on the AS2012 PC, in the Wideclient.INI, please change the Log= option in the [user] section to Log=ASE. Also, before starting RC, in the Logging tab, add these to the Monitor section on the right: offset 0371, type U8, hex offset CC04, type U32 offset CC08, type FLT64 offset CC10, type FLT64 Check "Normal Log" below., and OK out. Those offsets, the CCxx ones, are the ones used to request weather, so if those don't show the correct changes then it is definitely RC you need to look at. Can you tel me the actual RC build number, please. I assume it is version 4, but what is the number shown on its initial window? The log will be even bigger, so please ZIP it again. And include the WideClient.Log file from the Client PC. Thanks, Pete

Certainly the parameter needs to be 1 for Metres and 0 for feet. You'd either need to use a toggle switch or use the button flag to turn the button into a toggle. Using button flags to turn a momentary button into a toggle isn't "advanced programming2. It isn't actually "programing" at all, just paramter or configuration setting. Simply make the action conditional on the button's own flag, like this in the INI file CP(F+j,b)j,b,C69996,0 CP(F-j,b)j,b,C69996,1 where j = joystick number (0-15) and b = button number (0-31). It wouldn't be quite so asy if your button is on a wideFS client or is from a GoFlight device as the joystick number would not be in a valid flag range. Let me know. Pete

Depends what you mean by "communicate NGX". The offsets provide information -- read-outs -- for whatever purposes you may have. They are read-only, as it says To control NGX functions you use the events they list in the SDK. You can send events via offset 3110 if you wish to use offsets rather than assigned controls.. Regards Pete

Hi, I've spent a few hours today puzzling over this problem. I couldn't reproduce it on either of my normal test configurations, i.e. (a ) FSX + AS2012 on the Server, RC on the Client, or (b ) RC + AS2012 on the Client , FSX on the Server. But i could get it to happen reasonably consistently with this configuration: (c ) RC on Client1, ASE on Client 2, FSX on Server. There should be no difference between (b ) and (c ) because WideClient talks to FSUIPC on the Server about this stuff, not direct to the requesting program (RC). The only real difference here is timing. My Client 1 is quite a slow PC, whilst Client 2 is fast. So, I looked for a cause of a timing problem -- one thread doing something to nullify the result of another. And I think i found one. I have it working consistently now in configuration ©. So, please test it on your system for me. Download 4.824 test version FSUIPC4824_test . Use this with the weather logging still enabled and send me the zipped log if it still doesn't work. If it does work, try again without the weather logging (because logging changes times too). The relevant log entries with weather logging enabled should be like this: When RC asks for the weather you should find something like this in the Log: 382983 Request received to decode ASE METAR ... 382983 Weather Received (ASE Read): "???? 181236Z 06714KT&D457OG 02609KT&A914NG 05416KT&A1829OG 05715KT&A2743NG 05009KT&A3658NG 04309KT&A5486NG 04106KT&A7315NG 33113KT&A9144NG 32115KT&A10363NG 32815KT&A11887NG 33008KT&A13411NG 31108KT&A14935NG 55KM&B-2000&D4000 2CU021&CU000FNVN000N 7CU025&CU000FLVN000L 7CI270&CI000FNVN000N 08/04 03/M09&A914 M01/M13&A1829 M03/M15&A2743 M13/M25&A3658 M29/M41&A5486 M43/M55&A7315 M45/M57&A9144 M43/M55&A10363 M44/M56&A11887 M45/M57&A13411 M49/M61&A14935 Q0979" 382983 WX Received (null), WX request type 3, Lat=53.3472, Lon=-2.2834[/CODE] or, for an ICAO-specific request: [CODE] 378053 Request received to decode ASE METAR ... 378053 Weather Received (ASE Read): "???? 181236Z 06714KT&D457OG 02609KT&A914NG 05416KT&A1829OG 05715KT&A2743NG 05009KT&A3658NG 04309KT&A5486NG 04106KT&A7315NG 33113KT&A9144NG 32115KT&A10363NG 32815KT&A11887NG 33008KT&A13411NG 31108KT&A14935NG 55KM&B-2000&D4000 2CU021&CU000FNVN000N 7CU025&CU000FLVN000L 7CI270&CI000FNVN000N 08/04 03/M09&A914 M01/M13&A1829 M03/M15&A2743 M13/M25&A3658 M29/M41&A5486 M43/M55&A7315 M45/M57&A9144 M43/M55&A10363 M44/M56&A11887 M45/M57&A13411 M49/M61&A14935 Q0979" 378053 WX Received (null), WX request type 3, ICAO=EGCC [/CODE] That's for ASE/AS2012 on a Client PC, not on the FSX PC. If it is on the FSX PC the logging is slightly different. For example, for a Lat/Lon interpolated weather request: [CODE] 1125454 Weather requested from ASE for Lat 53.7716, Lon -3.0286 1125672 WX Received, WX request type 3, Lat=53.7716, Lon=-3.0286 1125672 Weather received from ASE: "???? 180831Z 06013KT&D457OG 07523KT&A914MG 06821KT&A1829NG 06620KT&A2743MG 06310KT&A3658NG 05103KT&A5486NG 20202KT&A7315NG 33613KT&A9144NG 33212KT&A10363NG 32413KT&A11887NG 33311KT&A13411NG 34906KT&A14935NG 46KM&B-2000&D4000 3CU019&CU000FNVN000N 2CI260&CI000FNVN000N 07/04 05/M07&A914 M01/M13&A1829 M04/M16&A2743 M15/M27&A3658 M30/M42&A5486 M43/M55&A7315 M45/M57&A9144 M43/M55&A10363 M43/M55&A11887 M44/M56&A13411 M50/M62&A14935 Q0981"[/CODE] The difference arises from the different sources -- the former case is derived from WideServer's posting into FSUIPC, the latter is with FSUIPC reading direct from ASE/AS2012. Good luck! Regards Pete

So why do you think you have to reinstall FSX as well? As it clearly says, you Place the "Install FSUIPC4.exe" program onto your desktop, or into a temporary folder, and right click on it, selecting "run as ... Administrator". Why do you find that unclear? How have you managed to install it before? Regards, Pete

FSUIPC offsets reflect provisions in FS itself, not in add-ons which implement additional subsystems, unless they use FSUIPC themselves. Additionally, many switches and buttons are only represented by controls or events sent to the sim, not by offsets which are primarily designed for reading data out of the sim, not specifically controlling switches. Googling finds this brief description: "AC electrical power is normally developed in the Lear Jet by two ll5 volt, LL00 cycle static inverters". So, how does your add-on aircraft implemet the switches? Are they just cosmetic, to make it look good, or do they actualy do something? If they are tied to anything in FS itself, they most likely are the generators. Does the aircraft have switches for those too, or possibly the inverters ARE the generators for this particular aircraft? Doesn't the add-on's documentation reveal anything? Doesn't it allow you to assign buttons or keypresses, or are those switches mouse-only? Enable event logging in FSUIPC and see what is logged when you operate them. If mouse-only, see if mouse macros will work. If not investigate the L:Vars for ths aircraft -- that might offer a way too. Regards Pete

The mode switch is simply a multi-position switch which is sending button numbers 8, 9 and 10 to indicate the different positions. You can either assign those button numbers as usual, or use conditional programming to make them select other functions on the other buttons. Conditional programming is covered in the Advance User's manual for FSUIPC. There might be some examples already available from other users. Everyone does their own thing, though, so you may or may not find something that suits you. But do a search, and do check the User Contributions subforum. Also there's a program called LINDA which might help -- see the pinned thread at the top of this Forum. Regards Pete

It can't be anything to do with aircraft types. I received the log and examined it, and I can't find any trace of RC ever asking for the weather for any specific location. There are only three possibilities I can think of here: 1. Maybe the log doesn't include the period where you asked for the ATIS. is that possible? It starts at 19:14 on the 17th, and ends at 19:46, just 32 minutes later, and the whole thing seems to take place at or around EGKK -- at least that was still the nearest WX station 10 minutes before the end as well as at the start. At what point did you ask for Cardiff ATIS? And did you expect to get an ATIS for a station well out of ATIS transmission range? I'm not sure what RC does about that. 2. Maybe my normal "weather logging" doesn't include the RC weather requests. I'm not sure how that could arise -- it certainly always has here. I shall double-check this within the next couple of days or so. I'm sorry I can't do it immediately but my system, the one with AS2012 and RC, is out of action at present during a little rebuild. 3. Maybe RC isn't actually asking for the weather after all, and simply reading the weather which FSUIPC is reading and making available all the time. Why that should happen I don't know, but i should be able to find out when I embark upon resolving #2 one way or the other. If you don't hear from me by the end of the week, add a reminder here. Regards Pete

I've moved this to the Support Forum as it appears to be a request for Support, not a list of Download Links, into which subforum it was posted. It is availble in the same place it always was, the Schiratti "Dowson" page, and also in the "Updated Modules" thread in the "Download Links" subforum here -- the very place you posted to. In fact your message was originally right next to it, so how could you possibly miss it? All the search engines i've tried take you directly to the standard place, the Schiratti site, as the very first choice. Additionally, further down the lists of references found there's often the Download Links subforum here. How can you miss them all? If you've ever used FSUIPC before then it's always found in the same place you got it from -- the Schiratti page has been there now for 14 years and has featured it all that time. Not only that but there are links in its documentation and on the purchase pages in SimMarket. How did you find you way here and miss all the easy stuff? Pete

Good! Thanks for confirming. Pete

Odd, then, that they have the correct FSUIPC offset listed in one of their configuratin files. Oh, well. ... Pete

Oh, I didn't know that! Sorry. I only do it when my post is still the last in the thread. Pete

Really? I didn't think those programs used FSUIPC at all? No. I don't see how anything can prevent buttons coming through the Direct Input interface except from some driver or other. Are you sure you have no Saitek software running? In that case it is most certainly a driver for your hardware which is intercepting and interpreting the buttons itself, and only leaving a small set for user programming. Regards Pete

Okay. And the log confirms that: 47 FLT UNC path = "\\GRF-MAIN\Users\John Fail\Documents\Prepar3D Files\" 62 FS UNC path = "\\GRF-MAIN\Prepar3D\" 2948 \\GRF-MAIN\Users\John Fail\Documents\Prepar3D Files\Cessna 310 At Williams Field Mesa Arizona KIWA Runway 30R Ready For Takeoff.FLT 2948 \\GRF-MAIN\Prepar3D\SimObjects\Airplanes\310Q\c310q.AIR[/CODE] Those are the 4 paths which any application interfacing to FSUIPC, even through WideClient, can read using that connection. Maybe, maybe not. I really don't think all that many programs use shared folders. I'm pretty sure Radar Contact does not. If IYP does I'd be surprised, and I don't know what it is using then for? Maybe to read the current flight plan from the "FLT UNC Path" logged above? I'm afraid I will have to hand you back to IYP support. I really don't know what it is looking for, now why it cannot get what it wants using the paths presented to it via the interface. Send the FSUIPC log to IYP -- that will be useful to them I expect. BTW I loooked up error 9004. It appears to be related to a database enquiry. The wording of the error description is: Regards Pete

Get a full FSUIPC4 log with Weather logging enabled, for a session which includes the request which RC will be making to get the weather for ATIS. It will be a large file, so ZIP it up and send it attached to an email to petedowson@btconnect.com. Mention your false name here else I won't be able to relate it. Pete

Doesn't matter whether you select hex or not. the numbers 0 - 5 are the same in decimal and hex! Pete

No. There is no way I can keep adding hardware drivers for every company that cannot be bothered to provide their own software. You must complain to cpFlight if they cannot make hardware which works with FS. What simulator are they providing it for if not FS? I do not support Saitek etc. I support standard Windows-compatible joysticks. Saitek etc make windows-compatible joysticks. What have Axes got to do with an Autobrake switch? Nothing in your log relates to anything useful at all. If you want to see what switches do, you must log buttons, not axes. So. What is that supposed to do? Seems like it is configured to use offset 2F80 which is correct for the FS Autobrake, doesn't it? So you have no problem! Check by Monitoring 2F80 as a U8 on the right-hand side of the Logging tab in FSUIPC. Check the FS window option below the list so you can see it in real time on screen. I don't understand what you want from me. It seems you need to get your cpFlight hardware supported by cpFlight. Don't they help? Pete

All versions of AS2012 and all supported and recent versions of FSUIPC4 support AS2012 weather reading in DWC mode. If you are not using AS2012's DWC mode then it isn't relevant as ASwill be writing localised weather in any case. FSUIPC does not communicate with AS2012 over a network. You must have WideClient running on the same PC as AS2012 is AS2012 is not on the FSX PC. It is WideClient which sends the weather data to FSUIPC. the current version of Wideclient is 6.961 (see the Download Links subforum), but the facility works with WideClient 6.94 in any case. You can see what weather is being requested and supplied if you enable Weather Logging. There is nothing directly realted to AS2012 -- all the facilities are labelled as if it were ASE, because it was originally incorporated for use with ASE, and didn't change for AS2012. Regards Pete

Same place as you got 4.80. 4.80 isn't available any more. 4.823 is the one available from the Schiratti site and the Download Links subforum here. (The Schiratti site isn't mine, so the words there do not get updated very often, but the links are to the same files as here). Just SP2 (or Acceleration if you purchased it). Pete

FSUIPC can only see the same buttons as FS. So, does FS see the other buttons? It sounds like you have some other software which is handling those buttons and preventing them coming through as normal Jpoystick buttons. The Direct Input interface in Windows used by both FSUIPC4 and FSX actually gets all 32 possible button indications in one 32-bit word, so it is not possible for it to only get a subset if the device and its driver are allowing them through. BTW the current version of FSUIPC4 is 4.823. Regards Pete