Pete Dowson

Where do you see these values? If those are the "OUT" values then you have not calibrated that left brake axis. Pete

Yes, of course. So why did you disable it? I don't understand. When I said to try disabling the other DLLs, in order to find which one is reacting with FSUIPC, you insttead just disabled FSUIPC. It makes no sense! Pete

I'm afraid FSUIPC knows nothing about inserting traffic, and neither do I. In FS9 and before I think this was done using the Multiplayer interface as published by MS, with an SDK I think. It might be the same in FSX/P3D, but equally it might be done via SimConnect facilities. The only association FSUIPC has ever had with muliplayer traffic has been a facility to inject the details of that traffic into its TCAS tables so that they would be shown on cockpit ND's in TCAS modes. Those facilities still exist. Pete

Of course not, because you Disabled FSUIPC. That's fine if you don't want to use it, but I don't see the point of doing that in the current context as it tells us nothing. Pete

I don't think there is any way for 64-bit apps to share memory with 32-bit apps. When you think about it you'll understand why. Pete

Sorry, apart from a very few dedicated functions, FSUIPC has never been a mouse-assignment program. Maybe it can be handled using the Mouse library in the Lua plug-in programming facilities. But doesn't Logitech provide a way to assign them to keystrokes or something? Pete

If I could reproduce the problem, I could possibly help. All I can tell from the information you have and we can get is that a call to the sound part of DirectX (DirectSound), part of Windows, is crashing on yours and some other systems, but not on either of mine. And the code performing the calls in FSUIPC, on behalf of FSRAAS, is the same code that has been doing this now for many years. Maybe the FSRAAS programmers can help. Note that i have FSRAAS because I too used to use it all the time. Nowadays I use a payware produce for RAAS which I think performs better and which is more complete. http://www.fs2crew.com/cart/products/FS2Crew%3A-RAAS-Professional.html Regards Pete

When you have both rudder and tiller assigned in FSUIPC the rudder control is used by both. FSUIPC uses the tiller input on the ground from 0 to 60 knots GS, and the rudder input in the air and on the ground above 60 knots. The effect of the two inputs is gradually changed between the two between 0 and 60. This is to simulate reality, and is fully documented in the FSUIPC documentation. I suspect you are trying to test the rudders on the ground and not whilst moving fast enough for rudder to be effective. If you don't want this action then you could try assigning your tiller to the FSX steering axis control instead, which I think uses the nose wheel instead of the rudder. This control is new to FSX -- the FSUIPC facility dates from earlier versions of FS. Also, the rudder assignment is this: 2=0Z,1139,D,3,0,0,0 The 1139 value has been set by YOU, in the Assignments tab. It is the "Delta", the value which defines the change seen in the axis before any movement is accepted. The default is 256 as you see in the others, and generally that is enough for all standard devices -- it gives 128 discrete values, which approximates the real resolution of most commercial axes. Try changing it in the file. Yes, of course double assignment causes conflicts and odd behaviour, as I think I said in my previous reply. You need to delete the assignment you don't want. Why do you have double assignments in any case? If you had dual controls then you'd have double assignments to aileron and elevator too, but you haven't. The double throttle assignments are actually, on looking again, for the Left and Right brakes (number 7 left brake, 8=right brake). You don't have any FSUIPC assignments for throttles at all. So I'm now thinking you have the controllers also enabled in FSX -- that will most certainly give rise to worse conflicts than having double assignments in FSUIPC! You must choose one or the other! :-( What's the need for that "as a customer" business? Am I not helping? Why do you feel the need to make insinuations or threats? I always try to help where I can ... even for those who are not "customers". FSUIPC has been around now for 16 years and was free for most of that time. I've helped FS users in general virtually full time for the whole period, only charging for some aspects of FSUIPC use when my other sourcces of income dried up. Pete

I really don't think there's any point. The problem is somewhere deep in DirectSound, or in the sound drivers themselves. And FSRaas20.exe works perfectly well here on two different Win7 PCs, as I think I previously reported. That's with the current FSUIPC of course, but the sound facilities in FSUIPC haven't changed since around FS2002 days. Pete

You really do need to describe the problem in a little more detail than implying they "don't work"! In what way don't they work? No action at all? Wrong action? Jerky movement? Random movement?One thing strikes me directly from your B777 axes section, the part I've kept above. You have double axis assignments to the steering tiller (0S and 0T) and also to both throttles 1 and 2 (1U, 1V and 1Z, 1R). Generally that is NOT a good idea! They can interfere with each other. BTW, people often come here saying they are old. I'm not sure why. Is it meant to be an excuse for something? I am over 71, so also an "old senior citizen" but I can't use that as an excuse. Well not yet, in any case. Maybe I'll become feeble or get dementia, but then would I be flying my sim? :-) Pete

The problem is still there. FSIPC is detecting the ASN DLL and obtaining the address in it of a function. The only difference here is that I tested the pointer it returned to see if was valid before trying to use it, and logged the error insterad of using it. That's the later line saying "ASN active function renoved". However, the line "ASN Running? Smoothing is by ASN" following is odd, so maybe I didn't catch all cases. The pointer which was obtained was from a modules called AS_BSTRP.DLL (I think I got that right -- I'm doing this from memory). I doubt if it is FSUIPC causing the Stackhask error, but I'm afraid I can't contine investigation now till Friday as I'm not back home till then (I'm typing this on my iPad). There's certainly something in your system which appears to respond to FSUIPC's requests to interface with ASN. Sorry about the delay till I can check further at this end, but meanwhile maybe you could try a process of elimination of the DLLs you do have enabled. In the DLL.XML file you showed earlier you can prevent each loading by changing the line: <Disabled>False</Disabled> to <Disabled>True</Disabled> Pete

I'm afraid I don't fully understand. What exactly is it you want FSUIPC to report for you, what is it supposed to "count"? Do you mean every single WRITE access to any of the weather values through any of the methods available (there are several)? You do realise, I hope, that in FSX FSUIPC uses SimConnect completely for weather setting, so if you are looking at the latter you already have it covered, though I'm not sure exactly what you'd do to monitor settings made to the Weather via SimConnect either. FSUIPC can't actually determine if or when weather is injected directly by FSX, whether from its server or by user in the menus. Changes to the weather are occurring all the time in any case. Pete

Actually it is a commonly reported problem specifically with the Saitek quadrant, and is caused by a bad setting in the Registry which defines some axes as "digital" (meaning "on or off"). I would have though Saitek would have fixed their install package by now. I don't recall the specific details, but you'll certainly find the answers somewhere over in the Saitek support forum. Pete

Or try FSUIPC4937c.zip, in which I've changed 3F02 so it increments even if the same flight is reloaded. Pete

Right. I can't see anything there which might cause this crash. I'm puzzled. I've added a little more logging to version 4.937c to try and at least eliminate the reason I thought was the cause. Please download it from this link: FSUIPC4937c.zip, and try again. Whether it crashes or not I'd still like to see the log please. If it does crash please get the crash data again for me as it may be different. Thanks Pete

Sorry, but if just getting an add-on up to date crashes your FS you have something seriously messed up in FS. Maybe you should repair that first? There is no way any FSUIPC offset relates to anything specifically inside the 737NGX except for the specially mapped data which PMDG nicely provided. Pete

The documented FSUIPC offsets for FSX are for the FSX values. The PMDG 737NGX does not use much of the inbuilt FSX data, but does its own thing. With the fully update 737NGX there's a facility to provide their data -- please see their SDK documentation. When enabled correctly in PMDG's setup (INI?) the values you need are in extra offsets documented in a separate document in your FSUIPC documents folder. Pete

Put " around the complete paths. Otherwise the spaces terninate the paremeter. It's a standard Windoes thing. Pete

FSUIPC depends on SimConnect telling it. I don't think I get notifications of reloads, only new loads. but I'll check ... Pete

Quite possible. Have you tried other aircraft? Pete

Most folks use my freeware program "Makerunways" to create data bases generated from your installed scenery. There are standard libraries for file access, and searching depends on whether you choose a text-based database or a faster binary one. You need to know something about programming. I'm afraid I cannot tech Lua. I bought the printed books on the language and still need to refer to them. Or you can get all the help and information you need at the Lua website, link in the documentation I supply, or just Google it. Pete

It's the Chapter called "Button Programming". There's a section on "Sequences, combinations and mixtures". The format for controls is given, and the control numbers are listed in the document List of FSX Cpntrp;ds/ Pete

I'm not really responsible for either Cockpitsonic hardware support nor Project Magenta support. But I do use a Cockpitsonic overhead, much altered since first delivery, and not using their driver because of the changes. however, here goes: It should be writing to 5611 for Engine 2 -- 0=GND, 1=OFF, 2=CONT, 3=FLIGHT. For Engine 1, the offset is 5610, with the same values. I would guess that there is a connection problem to the switch. Try making sure all the cables in that area are firmly seated. I found that unplugging them and plugging them in again sometimes helps make better contact. Also I found that the workmanship on some of those little "BOBs" (break out boards) leaves something to be desired, with dry joints and incorrect wiring on several in mine. I was disappointed with the standard, and eventually replaced some parts, rewired others and resoldered several of the BOB connection boards. I replaced the Duct Pressure and Cabin Pressurisation gauges with proper dual-needle Flight Illusion ones. (Actually a friend of mine did all the work, as my eyesight leaves a lot to be desired these days). If you cannot find the problem I suggest you contact Cockpitsonic support, see if they will respond. don't they have a place in Canada? Mine came from Germany, but via a UK dealer who doesn't deal with them any more. Good luck! Pete

Is that it? Did FSX crash? There are no closing lines. If FSX was still running you really need to close it then check the log. But if it froze after that last log line, then there's nothing going wrong which FSUIPC detected. Sometimes an overload will show as SimConnect disconnections, but that it's happening. The average frame rate was a reasonably healthy but not wonderful 16.9 the last time FSUIPC logged anything. So, it looks like you have another problem causing the freeze. Pete

No,FSUIPC cannot cause your FS to freeze. It is the other way round -- FS freezing causes FSUIPC to stop servicing applications. Check the FSUIPC log file, see if it is reporting problems. Show it top me if you wish. Pete