Jolun Posted April 10, 2017 Report Posted April 10, 2017 (edited) Hi, I have problem to set the elevator trim for my PMDG737 NGX (It works perfect for PMDG 777 & 747 V3). I use FSUIPC 4 (latest version 4.964 pay ware). I'm running a P3D V3.4 latest version. Under Button + Switches I have put in: offset sword decrement, x0BC0 -50/16383 and checked Control to repeat..... offset sword increment, x0BC0 50/16383 and checked Control to repeat..... I did it the same way for PMDG 777 and 747 and it works just fine. For the 737 does not work the trim is not moving when I press the trim buttons. I have the engines running and hydraulics on (NGX Default panel state). When I open FSUIPC the line for decrement looks like this "14=R2,10,Cx42000BC0,x3FFFFFCE -{offset sword decrement, offset 0BC0 (Decr=65486, Limit=16383)}-". I changed the ini file with the correct "wordings" see first bullet. Next time I start the sim the wrong values are back. I have FSLB's A320, PMDG, 737, 777 and 747 installed. I also have Active Sky 2016 installed and lot of scenery's. I'm running Win 10 x64 I would appreciate some help to understand how to solve my problem. Best regards Jonas Lundgren FSUIPC4.ini FSUIPC4.log Edited April 10, 2017 by Jolun
Thomas Richter Posted April 10, 2017 Report Posted April 10, 2017 Hi, Quote I use FSUIPC 4 (latest version 4.964 pay ware). Latest is FSUIPC4965 Offset 0xBC0 range is 16383 (Trim Up) to -16383 (Trim DN), so you need to use instead offset sword decrement, x0BC0 50/-16383 and checked Control to repeat..... offset sword increment, x0BC0 50/16383 and checked Control to repeat..... That will show up in FSUIPC4.ini as (here) 1=R0,5,Cx43000BC0,xC1800032 -{offset sdword decrement, offset 0BC0 (Decr=50, Limit=-16383)}- 2=R0,3,Cx33000BC0,x3E800032 -{offset sdword increment, offset 0BC0 (Incr=50, Limit=16383)}- The -50 value you used to decrease would actually increase and because it is not signed value it gives the extreme high positive value. As the function already is defined as decrease there is no need to use a negative value BUT the max negative limit. Thomas
Jolun Posted April 11, 2017 Author Report Posted April 11, 2017 Ok thánks for the replay. But I don't understand way the sim or the add-on automatically change the value 50 to 65486 in the decrement statement? Best regards Jonas
Thomas Richter Posted April 11, 2017 Report Posted April 11, 2017 Hi, as I already said: Quote The -50 value you used to decrease would actually increase and because it is not signed value it gives the extreme high positive value. As the function already is defined as decrease there is no need to use a negative value BUT the max negative limit. Thomas
Pete Dowson Posted April 11, 2017 Report Posted April 11, 2017 3 hours ago, Jolun said: But I don't understand way the sim or the add-on automatically change the value 50 to 65486 in the decrement statement? It changes nothing. As an unsigned number -50 IS 65486. Inside the computer where numbers are represented by binary bits, they are indistinguishable. How a collection of bits is used depends purely on how you define them to be used -- code or data, signed, unsigned, floating point, etc. It's all in the definition, and that parameter is defined to be unsigned, as documented. Pete
Jolun Posted April 11, 2017 Author Report Posted April 11, 2017 Ok, now I have updated to 4.965 and followed your instruction (...decrement 50/-16383). No more change 65486, as expectedFSUIPC4.ini. But the trim wheel does not move at all. I have unchecked the box telling the sim to handle the controls = FSUIPC handles all flight controls. It still works for the 747. It seams to be isolated to the PMDG 737NGX. I notice that before decrement is sdword and in other cases it is only sword? What to do? Jonas
Thomas Richter Posted April 11, 2017 Report Posted April 11, 2017 Hi, the trim changes correct also for PMDG B737NGX. The Trim wheels are not moving because it seems that PMDG doesn't read the actual trim value via SimConnect back but only the trim controls like Key input. I checked the Trim function here with B737NGX. For the other PMDG products it might be different. Thomas
Jolun Posted April 11, 2017 Author Report Posted April 11, 2017 Ok then I try to implement some keys for this. Thanks for the answer. Jonas
Pete Dowson Posted April 11, 2017 Report Posted April 11, 2017 40 minutes ago, Jolun said: Ok then I try to implement some keys for this. If you really want to use controls for trim, checkout all the PMDG-supplied "custom controls" listed towards the end of the ".h" document included in the SDK folder of your PMDG 737NGX folder. You can assign to such controls in FSUIPC by using the <custom control> assignment and entering the number computed from that document. Pete
Jolun Posted April 11, 2017 Author Report Posted April 11, 2017 If I delete the ini file then I can let the sim control the trim (new one is built on start). This works But if I use my "old" ini file and delete 737 trim settings (and clean all seeings in the sim except for trim). It does not work. If I go with a new ini file can I copy all a/c specific settings( except the one for 737) in to the new ini and hope it will work? or do I have to do it from scratch? Jonas
Jolun Posted April 11, 2017 Author Report Posted April 11, 2017 You don't have to answer this it looks like I only have to delete the 737 specific parts in the "old" ini file and then rebuild the 737 settings. Jonas
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now