Pete Dowson

Okay. Thanks. As i said in the other thread, I'm looking to see if I can fix it for the FSUIPC loader. If I can manage that I think it will fix other occasions. But it isn't easy. Got nowhere so far. But that's just Day 1. ;-) Pete

Which panel has a working gear warning cutoff button? I think you'll need to lose the default FS sound (find the wave and rename it), and play it yourself instead on the conditions you wish. You could do that via a Lua plug-in. Pete

Hmm. Very odd. I'm trying to find a work-around for the mouse look being clobbered when the FSUIPC Loader is used. I feel that if I can solve that then it may make it more robust against other things. Not got anywhere yet though. I can't really find out why the Loader makes any difference. Must be some sort of timing thing, but nailing it is difficult! Regards Pete

Okay. So the normal Axis controls are being intercepted okay, and processed. So, let's look at your assignments: [Axes.Level D 767] 0=0X,256,F,66387,0,0,0 Axis left brake set 1=0Y,256,F,66388,0,0,0 Axis right brake set 2=0Z,256,F,65764,0,0,0 Axis rudder set 3=1X,256,F,65763,0,0,0 Axis ailerons set 4=1Y,256,F,65762,0,0,0 Axis elevator set 5=1Z,256,F,65765,0,0,0 Axis throttle set Now all those are the exact same ones which assignment in FS provides. No difference at all. The calibration routines should receive them identically no matter which way you assign them. This raises another question, though. Why ARE you assigning axes in FSUIPC? You might as well assign in FS, as it would be more efficient in any case rather than have FSUIPC send these controls to FS and for FSUIPC thern to intercept them for calibration. Really assignment of axes to FS controls is either intended for those who want different assignments for different aircraft, or who prefer the greater efficiency of the "direct to calibration" assignments, which involves no messages going back and forth to FS nor interceptions. I'm afraid I'm still at a loss to understand how your system is somehow working whilst the calibration cannot intercept the axis controls only whilst originating in FSUIPC. It relies on a function of SimConnect to make this happen and I'm now wondering if there's been some small corruption somewhere in that area. However, rather than try any reinstalling in your setup with which you are otherwise quite happy, I'd suggest one of two things: Either reassign those controls to the direct equivalents, which involves unticking the current assignments, selecting "direct to calibration" mode just above, then reselecting in the drop downs. Or deassign all axes in FSUIPC and assign in FS instead. Calibration is still valid. You could do this quickly by simply deleting the [Axes ...] sections in the INI. Hmm. I wonder what happened a week ago or so? Pete

The only way there will be no "IN" values changing in the Calibration tab is if no axis values are arriving there to be calibrated. To test this simply enable the controllers again in FS and see. I suggest you show me the current state of your INI file and explain, step by step,what you are doing and where, exactly, you think you should see activity yet are not. Regards Pete

I know. The line is created by assigning the aircraft to that profile via the Options checkbox and selection. When you load a new aircraft (one without a Profile assigned), and click on "Profile Specific", you get a list of the profiles which exist, and an entry to create a new one. You must have simply selected the Cessna one unintentionally. Too quick with the mouse button perhaps? After deleting the line for this? So you've repeated the original mistake! No. If the Cessna profile is okay, just remove the line that Andy and I pointed out, the one assigning your FA18 to the Cessna profile. THEN load FS and load the FA18, and create a new profile with whatever name you like. Do NOT click on "Cessna" again! Regards Pete

I only just read this entry. There is no way a new aircraft (one with a different name) can ever be "automatically" added to a profile. It can only be done by user selection. Apart from the profile assigned, if any, to the current aircraft, none of the profile names are even known to FSUIPC until you use the selection facility in the options. I think I have to emphasise what has now been said at least twice. delete the line assigning the aircraft to the cessna profile. I'm afraid FSUIPC does not currently offer an option to do this via the Options tabs -- I thought it an infrequent need and resources better spent elsewhere. Regards, Pete

I suspect that he did have 60 set once, and when changing it to 10 did not delete the excess. FSUIPC doesn't remember how many there were. You'll note theose after the 10 have a discontinuous timestamp. Regards Pete

But you've changed nothing? Which FSUIPC tab are you trying to assign a profile? According to the Log you only loaded the aircraft called "Flight Test Aircraft E1": 16224 Aircraft="Flight Test Aircraft E1" and this is already assigned to the "cessna152" profile, here: [Profile.cessna152] 1=C152II LIGHTBLUE G.F. 2=Flight Test Aircraft E1 3=C152II Calypso G.F. Therefore the checkbox for profiles SHOULD be ticked and grayed out for Axis assignments, though not for Buttons or Keys, because with those you can have both general and specific asssignments. You say you cannot assign the aircraft to a Profile, but that is precisely because it is already assigned, as pointed out already. I think you need to explain in more detail what it is you are concerned about, please, because it is certainly appearing as if you are misunderstanding things. If you want to assign this aircraft to a different Profile now you'll need to delete the line assigning it to an existing Profile, as andy suggested. Pete

I'm afraid I don't know how that can be. Could you re-post the INI file, as it is now, AND the Log file corresponding to this attempt. If I still cannot see how it can occur I will have to add some diagnostic logging code to get more information. Pete

I'm thinking this is another Windows8 problem, like the disappearing controllers. I'll need confirmation from the others in this thread. i.e. answers to this question: "Is this always only with Win 8? Does it happen during an actual session, or only on a restart?" If it is Win8 only, then I doubt I can fix it because it would mean a standard Windows API function is not working correctly. Win8 updates may be the only solution. There's nothing complicated about the mouselook. The only crucial part is the receipt of Mouse messages in subclassed window procedures. Why that would vary from one time to another I don't know, but so far no one has told me whether it's the same throughout a session, or can disappear during a session. If it's a loading time difference it may be some sort of subclass timing difference afftecting the order of things, in which case it may be related to the similar problem when using the FSUIPC Loader. When I have received sufficient information I'll investigate further. Regards Pete

Either assign the aircraft to the same profile, or, more flexibly, change the [General] parameter ShortAircraftNameOk=No to ShortAircraftNameOk=Substring and edit the name listed after 1= in your [Profile....] section to a short subset of the name which applies to all liveries. Regards Pete

You can only detect it by seeing the values change. Just read offset 0BE0 or 0BE4 every 100 mSecs, say, and if different, they're moving. If same, not moving. If you aren't able to do it for whatever interface you are using, you could have a little Lua plug-in doing this, setting or clearing a flag in a user offset such as 66C0. Regards Pete

Yes, it has. That is exactly right. What is the question please? If you don't see the mised actions, look here: [buttons.CT182T] 0=P0,8,K83,8 1=P0,0,C65564,0 2=R0,10,C65607,0 3=U0,10,K0,8 4=R0,11,C65615,0 5=U0,11,K0,8 6=R0,5,C65758,0 7=R0,4,C65759,0 8=R0,2,C66278,0 9=R0,3,C66279,0 10=P0,9,C66153,0 11=P0,7,K49,9 12=P0,6,K50,9 13=P0,1,C65752,0 See? Control for Press, Keypress for Release. Definitely mixed! It is perfectly legitimate, but it makes use of the dialogue impossible, you must edit the lines in the INI instead. Pete

I don't see anything there which would cause such a problem, though it is perhaps a little worrying, presuming that you have Controllers disabled in FS, that you only have axes assigned for the one aircraft only in the one livery. You have no default assignments, which is very ununsual. If you load a different aircraft you'd have no controls until you assigned them. This is even odder when you see that you do have default calibrations even though there are no assignments which could be calibrated that way. I would strongly recommend some tidy up and a little more flexibility adding, as follows: In [General] change ShortAircraftNameOk=No to ShortAircraftNameOk=Substring and delete these strange lines -- I don't know how they arose at all! !1=DeleteVehiclesForAES !1=Wheel values: 25 sets of 8 FLOAT32 values starting at offset 0xA000 !2=Braking values: 25 sets of 4 FLOAT32 values starting at offset 0xA400 Then change the Profile definition so it applies to all the Level D 767s: [Profile.Level D 767] 1=Level D Simulations B767 Add a copy of the 767 axes section with the title [Axes] so that you have some default axis assignments, thus: [Axes] 0=0X,256,F,66387,0,0,0 1=0Y,256,F,66388,0,0,0 2=0Z,256,F,65764,0,0,0 3=1X,256,F,65763,0,0,0 4=1Y,256,F,65762,0,0,0 5=1Z,256,F,65765,0,0,0 Regards Pete

What needs explaining? The only relevant part to scaling the input value to get values more suited to what you want are these: *-0.01,+327 which simply says "multiply by -0.01" then "add 327". i.e. it changes the sign, making positive negative or vice versa, then divides by 100 (same as multiplying by .01 = 1/100th) before adding 327. You'd need to experiment really. I'm not totally sure without experimenting myself, but I think the value for 5x needs to be 320 and 0.25x is 16, so you want the minimum axis value converting to 16 and the max to 320. If the values run from -16383 to +16383 you'd need something like: *.0092779,+168 the first number being 304 / 32766 to get the full ranfe -16383 to +16383 to be -152 to +152, and the +168 adjusts this to +16 to +320, as required. As before, you can reverse this is you wish by using *-.0092779,+168 Pete

Are you wanting to write a program to do this? What language? You could consider using a Lua plug-in. That'd be quite simple. Pete

How did you change over from aircraft specific to Profiles? It looks like you have got the INI file settings in a mess. But I can't help unless you showw me the INI file. Please do NOT include almost unreadable pictures of part of the file, just paste the entire content into your message! Pete

No, in this version the Aircraft name is being seen: so it should now easily be possible to assign it to a new profile if you wish. Pete

Okay. But try also FSUIPC's Event logging and operate the switch and see what numbers it uses. It is probably related to the parameter value. What about EVT_OH_LIGHTS_L_ENGINE_START EVT_OH_LIGHTS_R_ENGINE_START I think those are the starter controls. Maybe parameters 0-3, or some others based on the MOUSE_FLAGs? Pete

The log really tells me nothing about how you've assigned things, so I have no idea. The INI file is more relevant. The calibration tab merely receives values either direct from FSUIPC assignments or from FSX itself. In either case, if the axes are calibrated and it never sees them it wouldn't pass them on, so nothing would work. BTW this doesn't look good: Something is stalling FSX so much that SimConnect can't send data to FSUIPC for a significant period. Maybe this is related? where, in the timeframe of the log, were you trying to use the Calibration tab? What about the next load of FS? Nothing speciifcally I know of, expecially if the axes are assigned in FSUIPC "direct to calibration". If assigned to FS controls, in FS or in FSUIPC, then the calibration depends upong intercepting controls via Simconnect, and if you are getting SimConnect stalling i suppose all sorts of weird things might result. Regards Pete

Sorry, but the offsets for the NGX are not writable. I assume you must mean control number, not offset? When you assign a button, key or switch, in the assignment drop down you can select <custom control> (at the top of the list) and enter the control number (range 65536-131070), as derived from that .h file. Pete

Please try 3.999y5, now available in the Download Links subforum. Pete

And the log with the problem aircraft being loded? Version 4.827 is well out of date now and unsupported. A lot of changes have occurred to improve the Profile system. Please update. The earliest supported is 4.853, and there's an 4.859m available in Download Links subforum. Looking at the INI file you seem to have two similarly named but different 747 profile names set up: [Profile.74710] 1=PMDG 747-8i Air France and [Profile.747 10] 1=747 10 with axes assigned, no buttons, in the latter: [Axes.747 10] and buttons assigned, no axes, in the former: [buttons.74710] Regards Pete