Pete Dowson

Why? Are they private, secret matters? I only do tech support here on the Forum. Pete

My copy of as_btrsrp.dll, which is in use (as I use ASN) is also version 1.0.0.12, dated 5th October 2014 (i.e. quite recently updated), and is both copyright HiFi Technologies and digitally signed by them. So mine is certainly the official one installed with ASN and updated from time to time when you load ASN. However, it is never in any of the FSX folders, but it is normally loaded by having an entry in the DLL.XML file, the same way as FSUIPC4 is loaded, the entry there called "as_connect" which should be last in the DLL.XML file. I don't know how it got into your FSX folder, but it most certainly should not be there, and in fact if you aren't an ASN user I don't understand how you even came to have it? Do you have any programs by HiFi Technologies? Pete

Doesn't it say who it's by, no copyright or anything? Pete

Would that be the same as on iceBlue77's CS overhead? Can you help him at all? I realise it must be difficult from memory of my overhead! Pete

Hmm. I wonder how that got there? As far as I know that's purely to do with Active Sky. Can you check it's Properties (right-click on it), see if it tells you who made it and what version it is? Then try renaming it, eg to as_btstrp.dlx, and running FSX again. Pete

As far as I can see, the lines logged "ASN active function link set" can only occur if there's a modules called "as_btstrp.dll" running, and even then only if that has a function in it called "isActive". Could you do a search on your system to see if there's a file "as_btstrp.dll" there, please? Pete

I cannot really support other folks' programs and that's really nothing to do with FSUIPC or WideFS. Have you tried the RC forum over on AVSIM? All I can tell you is that error 76 is "Path Not Found" (I only found that by Googling), so I would guess you have your Flights on your FS PC in a folder not known to or not accessible to RC on the Client. You probably need to share that folder. Pete

Aha. This is the same problem someone else got. It turned out to be some sort of corruption, because when he reinstalled FSX it worked fine. However, before we resort to anything so drastic, let me see if we can nail it down more exactly, because corruption in one case leading to a crash in an oddity, but when it happens exactly the same to two folks there's something specific going on. I'll get back to you after I've thought it through. Maybe I'll need to add more logging to pinpoint it. You don't have ASN installed at all do you? Or did you? Pete

After doing what, exactly? Can you please download FSUIPC4937c and test with that. If it still fails at least it will give me data relating to the current code state. Pete

But look at the assignment you made: 1=0Y,B,0,0,65762,0 That is most certainly NOT an assignment made on the left hand side of the Axes tab! It is an assignment on the right-hand side, in the "range" setting options, and with the range still left at 0-0. The "B" means "in both directions" (it could be a U for Up or D for Down only). But with no real range (0-0 isn't much room!), nothing can happen. Why are you still persisting in using a part of the assignments tab which has very specialised applications none of which you need? PLEASE please please read the user guide and do what I said, only assign axes on the left side of the tab -- the place where you can make up to 4 assignments. I 'm not going to keep repeating mysef like this. I've never known anyone to be so persistent in not doing what is advised. If you cannot distinguish between left and right I suggest you simply assign your axes in FSX. You can still calibrate in FSUIPC if you wish. The assignments facilities in FSUIPC are more extensive but they aren't necessary for calibration. Pete

Sorry, I don't know, and I'm not in a position to take a look at present. With my poor eyesight I leave all that stuff to my good friend Thomas, but he lives a long way away and isn't due to visit till December earliest. I know that with some of the stuff on that overhead we simply gave up and re-wired it through some Leo Bodnar boards instead. We also replaced the Duct Pressure and Cabin Pressure gauges with proper dual-needle ones from Flight Illusion. I think you need a friend like Thomas who is good with hardware! I am just very lucky in that department. Pete

That looks like a problem in SimConnect with a corrupt weather file. These are binary files and not subject to any checks by Simconnect, so when FSUIPC asks SimConnect to supply weather data you get a crash from the bad data structures. You can prove it is this one way or the other by changing WeatherReadFactor in the [General] section of the FSUIPC4.INI file (in the FSX Modules folder) to WeatherReadFactor=0 This will stop FSUIPC trying to read or write any weather at all. The way to fix the problem is to delete the offending weather files -- the .WX files in your Documents|Flight Simulator X Files folder, and the WXStationList.bin file in the same folder as your FSX.CFG file. Pete

Well, two joystick devices have most certainly been detected: [JoyNames] AutoAssignLetters=No 0=Saitek Pro Flight Cessna Yoke 0.GUID={9C4F3DE0-D14E-11E3-8003-444553540000} 1=Saitek Pro Flight Cessna Rudder Pedals 1.GUID={9C7B56F0-D14E-11E3-800A-444553540000} Furthermore, you do seem to have actual made an assignment to one of them, though a rather odd one, a right-hand side "range" assignment with a range 0 to 0, not making any sense. I suggest you delete those two lines: [Axes] PollInterval=10 RangeRepeatRate=10 0=0Y,32 1=0Y,B,0,0,65694,0 This is AFTER you deleted the INI, so it is all a result of what you just did. you say but how could you "set elevator axis" if, as you say, FSUIPC doesn't detect any axes? The strange range assignment you've set is for the control "Elevator Set". Why? That's a most unusual control to choose -- the regular one is Axis elevator set, or better normally to assign direct to FSUIPC calibration. And in ay case, your assignment won't work because you've said only to send the Elevator Set control when the axis value goes from 0 to 0! I think you sre trying to do things you don't understand. Why not use the normal easy assignments? Even better, why not actually try reading at least some of the FSUIPC user guide? That's there to help you, you know! Pete

You didn't find "Auto throttle to GA"? Pete

No, sorry. You might be able to trace the wiring. With a couple of the BOBs I just used a hot soldering iron to remake all the joints in case one or more was dry. That fixed the problems I had. Pete

FSUIPC supports up to 32 buttons on any of up to 15 joysticks, so #35 will not be seen. Sorry. And as for being "all too complicated", it is surely as easy as flying complex aircraft and using complex controls, and the fact that up to 32 buttons are supported is also fairly clearly stated. FSUIPC's Lua plug-in library for COM and HID devices will be able to read any number of buttons, but it would mean writing a small plug-in program for it. Pete

I'm a programmer, I wrote my own. All of the hardware in my cockpit is handled by my own software. I don't like other uncontrolled (i.e. not in my control) software handling any of it. Since I program it I can adjust it to suit me exactly! ;-) Regards Pete

Is this a new bug in P3D's SimConnect? Have you checked the actual SimConnect METAR strings which are being sent to SimConnect, because all the NWI does is make FSUIPC build those strings. I'm pretty certain it's always been okay with FSX and SP2/Acceleration versions of SimConnect. In FS2004, for which the NWI was devised, it was only possible to have one visibility layer. Trying to use more never worked. Therefore the original design was for one layer. The additions was done in such a way as to not break existing programs. And yes, the layers all count. I suspect the Global weather facility in SimConnect only allows one layer still. The global setting is really only used as the initial default for weather stations not yet set up. Check the METAR string being sent. It sounds like some odd changes in the SimConnect weather interface have been introduced. Please just double-check using the string versions -- you can get those by FSUIPC's logging or SimConnect logging. If P3D have changed these things I suggest you might want to look at sending the METAR strings yourself rather than use the NWI. I'd hoped folks would have moved on by now from that system devised in 2003 to match the binary hacked interface into FS2004. You can send the strings via FSUIPC if you'd prefer not to use SimConnect directly. Hmm. Sounds like quite a few of the bugs in FSX's weather facilities have been carried over into P3D and maybe even made worse. Of course FSUIPC has no control over "artefacts" I'm afraid. Pete

Ah, right. My error then. I'll try to remember that! ;-) Pete

Oops. It IS 32! I was looking at an old printed version of the manuals -- I am too mean to keep printing new editions! Sorry. It used to be 8 -- it was changed in version 4.80, a couple of years ago! So, assuming you aren't using a pretty old version (check that first please), something else is wrong. I notice here: AlsoManage8=PMDG\PMDG 777X\PanelState\*.FLT.0.rte (for examples), that although there are spaces in the complete pathname, it still works without the " ". So maybe you don't need those " " around lines 9 and 10 after all. Can you try without? (Sorry I'm hypothesising in these matters -- all this code is so old (as am I) that I can't recall it all, and delving into it sometimes takes longer than simply trying things). Pete

As most certainly documented, there are only 8 AlsoManage entries supported. Up till now that's always been plenty. I could see if that's easy to extend and if so, do so. "Next=" just keeps track of where, in your cycle of 10 saves, the next one to be replaced goes. You can see line 1= has the latest time, line 2 the earliest, so it is next to be removed and re-used. Pete

Sorry, I am confused. I'm not in a position to check VB code as I don't know VB and especially not VB.Net -- maybe Paul Henty can help there. But are you saying the all the true AI aircraft give you correct and changing COM frequencies but MP aircraft do not? Actually I wasn't even aware that SimConnect supplied FSUIPC with data on MP aircraft. In FS9 there was no way -- the MP aircraft only got into FSUIPC's TCAS tables thanks to programs like AIBridge injecting the data directly. If SimConnect is actually supplying MP data, then FSUIPC is unaware of any differences -- they are all treated alike, so if the COM frequency appears to remain fixed at one value I fear it must be a SimConnect problem. I'm afraid I know nothing about MP at all and have never used anything which supplied any. Regards Pete

If that's the path, yes it should work fine. But usually there's no "-" character in "Flight Simulator X Files", just a space instead. Why not try it? Pete

Exactly as documented in the FSUIPC Advanced User's document (the section listed in the contents entitled AUTOSAVE: INI-file only options) just specify the full path in the AlsoManage parameter. If it contains spaces remember to enclose the whole parameter in " " Pete

There is nothing related to axes that can be done is FSX without using FSUIPC that cannot be done in FSUIPC instead. So you need to explain that statement please. There are several methods of assigning axes and certainly lots of calibration options. Joystick Calibration can be done in FSUIPC no matter how or where you assign, in FSX or in FSUIPC. And joystick calibration can be made Profile or aircraft specific, as you wish. If you are really talking about assignment, and not calibration (the two are separate), then I would certainly not advise any assignments in FS if you are assigning any in FSUIPC. You will get into trouble that way. Pete