Jump to content
The simFlight Network Forums

soldano

Members
  • Posts

    85
  • Joined

  • Last visited

Posts posted by soldano

  1. I must be doing something wrong, as when I try the fix I am having problems.-

    This is my inicial setting which works OK:

    [JoyNames]

    AutoAssignLetters=No

    0=CH PRO PEDALS USB

    0.GUID={D5C7D590-2C2D-11E2-8003-444553540000}

    1=CH THROTTLE QUADRANT

    1.GUID={D5C7D590-2C2D-11E2-8004-444553540000}

    2=CH FLIGHT SIM YOKE USB

    2.GUID={D5C7D590-2C2D-11E2-8005-444553540000}

    This is what I set:

    [JoyNames]

    AutoAssignLetters=Yes

    A=CH PRO PEDALS USB

    A.GUID={D5C7D590-2C2D-11E2-8003-444553540000}

    B=CH THROTTLE QUADRANT

    B.GUID={D5C7D590-2C2D-11E2-8004-444553540000}

    C=CH FLIGHT SIM YOKE USB

    C.GUID={D5C7D590-2C2D-11E2-8005-444553540000}

    This is the result after running FSX, and now both the Yoke and the Quadrant have their IDs changed and doesnt work

    [JoyNames]

    AutoAssignLetters=Yes

    A=CH PRO PEDALS USB

    A.GUID={D5C7D590-2C2D-11E2-8003-444553540000}

    B=CH THROTTLE QUADRANT

    B.GUID={D5C7D590-2C2D-11E2-8004-444553540000}

    C=CH FLIGHT SIM YOKE USB

    C.GUID={D5C7D590-2C2D-11E2-8005-444553540000}

    0=CH PRO PEDALS USB

    0.GUID={D5C7D590-2C2D-11E2-8003-444553540000}

    1=CH THROTTLE QUADRANT

    1.GUID={D5C7D590-2C2D-11E2-8004-444553540000}

    2=CH FLIGHT SIM YOKE USB

    2.GUID={D5C7D590-2C2D-11E2-8005-444553540000}

    What I am doing wrong ?

    Thanks

  2. Thanks Pete for your quick reply

    I have 3 devices: CH yoke: ID #0, CH Quadrant: ID #1, and CH Pedals: ID #2.- The problem happened when I reinstalled a Hotas Cougar, with the CH Quadrant unplugged, from then, the Quadrant was assigned as ID # 3, and so all my settings for that device were gone.-

    I tried the solution suggested at the manual, assigning letters or numbers to the devices and setting "AutoAssign letters=Yes" , but no way, the Quadrant was always designed at the 3rd place in the list regardless of the letter or number assigned at the FSUIPC4.ini.-

    So it seems that option works only when configuring the devices for the first time.-

    As I didnt want to configure the Quadrant again, the solution came when I restored Windows to the status before the Cougar was installed, then the Quadrant retrieved its original ID, and all is OK now.-

    My question is: Now that all works OK, if I modify the Joynames section as suggested in the manual, should I be safe from a future similar problem ?

    Thanks again

  3. Sometimes when I unplug a device, I found that its ID has changed in the FSUIPC axes configure window, so I must reconfigure all its axes, which is most annoying.- I happens in spite of re-plugging the device in the same USB socket.-

    I think it is Windows which assigns a new ID when detecting some change.- Is there a way to manually reassign the former joystick ID ?

    I use Win 7 64 and have controls disabled within FSX

    Thanks

  4. I don't know how GoFlight modules work.

    But as long as you can assign a button in FSUIPC to your hardware you can use LUAs or Macros.

    Guenseli

    I could program almost all the functions of my GoFlight Module using the Lua files you kindly posted, but couldnt do it with the Mode and Range knobs,as there are only increasing and decreasing parameters for both.- The mode knob has 4 positions and the range knob has 7, all of them are recognized with diferent button numbers at FSUIPC.-

    Pete Dowson said that, as they are written, your Lua files doesnt work for that functions in the GF Efis.- He posted: "I suspect that's because the Lua program you are calling looks to be quite long and has to be loaded, compiled and executed for each line in the INI. A shorter one with just the entries you want might do the job, but I doubt it. In the end the only sane way would be to program the sequences themselves properly in a Lua plug-in. Maybe an appeal to the original Lua programmer for the one you are using might elicit results"

    Maybe you have the patience to do that, and share it with us.-

    Thanks

    Jorge

  5. Not a "dumb" but someone who evidently hasn't the patience to read all of the words and instead just ploughs ahead regardless.

    I know. I pointed out that, though Andy posted macros for you, you thought they were INI file lines.

    I explained things to you, I enumerated solutions, and you simply ignored half of what i said. Patience has limits. I'm simply not going to continue repeating and expanding on things if you can't be bothered to use a little more time and effort, and read things properly.

    I thought, as I said, that this must be down to lack of English, but from your latest tirade this is evidently not the correct diagnosis. :-(

    I'm sorry, but I'm not responding any more in this thread. It has taken enough hours of my life without any reward for either of us as it is. My 'corrected' lines from Andy's post, included in one of my replies, should make it work for you. If not, please seek help elsewhere.

    Pete

    Nothing of what you said changes the fact that you said: "If I thought he could handle Lua file editing I'd have explained a much more efficient way of accomplishing the whole thing", you clearly knew from the beginning that my knowledge was basic, and you didnt.-

    Jorge

  6. Yes, but he didn't put your macro code into a Macro file for reference in his INI file, he put your macros into the [buttons.Jets] section of his INI file where they'll be rejected as invalidly formatted lines. Macros go in macro files.

    I don't think he'd know either way as it isn't his Lua at all, it's one he got from the User Contributions subforum. If I thought he could handle Lua file editing I'd have explained a much more efficient way of accomplishing the whole thing in any case. I was going to follow through with such, as I hinted at right at the start, but since he understands hardly anything I write, or possibly simply doesn't read much of it, it really would be pointless. I hope he can find someone who can speak his language.

    Regards

    Pete

    I am really upset, because although with limitations, I do understand English enough to realize that you did knew I couldnt handle Lua file editing when you answered me in your post #5: "Not in any "INI". Save the Lua plug-in from that thread I pointed you too, into the FS modules folder, with a name like "PMDG747.lua", then load up FS, go to FSUIPC button assignments, and assign to "Lua PMDG747" with the parameter needed as listed in that program, or even in the thread itself.", to my post #4 which said: "Thanks Pete and Prokopiu for your replies, but my limited knowledge makes me only able to use basic FSUIPC configuration options.- How can I implement what you said in my ini ?".-.-

    Your explanation, for which I was grateful, was at that moment enough clear for me,even not knowing anything about Lua programming, and made me able to configure all the functions of the EFIS with the exception of the Mode and Range knobs.-

    That situation motivated my post #9: "Thanks Pete And how can I program the Mode and Range rotaries, provided that the Guenseli's list, included only increase and decrease parameters for both ? (16 to 19) Regards Jorge" , which you answered with your posts #10 and #12, which in my opinion were'nt enough clear to somebody with a limited knowledge as yo knew I was.-

    Then came your post #16 in which instead of giving me a solution, you nearly treated me as dumb.-

    Then came Andydigital who, with good will, kindly attempted to give me a solution.- I was confused about it and as it included line numbers in sequence with my ini buttons section, I didnt treated as a macro, and so pasted at the ini, which was not at all illogical, as Andydigital in a certain way recognized when he asked you "isn't my button macro above calling parameters in his Lua script?"

    But the most offensive and unjustified of all came with your post #25, which is quoted, and in which you said, beside some other things which I better forget about: "If I thought he could handle Lua file editing I'd have explained a much more efficient way of accomplishing the whole thing".- You were quite aware of the limited extense of my knowledge, why didnt you explained from the beggining that "more efficient way accomplishing the whole thing" ?.-

    Up to the moment, every time I asked you for support, I got it quickly, eficiently and in good terms, so I dont know what happened this time with you.-

    Regards

    Jorge

  7. Using Pete's efficient method you should be doing this;

    APP - - - 17 17 17

    VOR - - - + 17 17 17 16

    MAP + + + - 16 16 16 17

    PLN + + + 16 16 16

    Which translates to;

    30=APP
    30.1=P170,16,CL1:R,17
    30.2=P170,16,CL1:R,17
    30.3=P170,16,CL1:R,17
    
    31=VOR
    31.1=P170,17,CL1:R,17
    31.2=P170,17,CL1:R,17
    31.3=P170,17,CL1:R,17
    31.4=P170,17,CL1:R,16
    
    32=MAP
    32.1=P170,18,CL1:R,16
    32.2=P170,18,CL1:R,16
    32.3=P170,18,CL1:R,16
    32.4=P170,18,CL1:R,17
    
    33=PLN
    33.1=P170,19,CL1:R,16
    33.2=P170,19,CL1:R,16
    33.3=P170,19,CL1:R,16
    
    

    There I did it for you, its the last time I will though :wink:

    Thanks Andydigital.-

    I cut and paste the lines you kindly sent, but no way, it doesnt work.-

    The relevant lines of the ini looks like this now:

    [LuaFiles]

    1=PDMG747

    [buttons.Jets]

    0=P170,4,CL1:R,3

    1=P170,3,CL1:R,4

    2=P170,13,CL1:R,7

    3=P170,15,CL1:R,23

    4=P170,12,CL1:R,8

    5=P170,28,CL1:R,10

    6=P170,14,CL1:R,24

    7=P170,30,CL1:R,20

    8=P170,31,CL1:R,21

    9=P170,2,CL1:R,5

    14=P170,9,K88,14

    15=P170,8,K87,14

    20=P170,1,CL1:R,6

    21=P170,29,CL1:R,10

    22=P170,11,K90,14

    23=P170,10,K89,14

    28=P170,6,CL1:R,2

    30=APP

    30.1=P170,16,CL1:R,17

    30.2=P170,16,CL1:R,17

    30.3=P170,16,CL1:R,17

    31=VOR

    31.1=P170,17,CL1:R,17

    31.2=P170,17,CL1:R,17

    31.3=P170,17,CL1:R,17

    31.4=P170,17,CL1:R,16

    32=MAP

    32.1=P170,18,CL1:R,16

    32.2=P170,18,CL1:R,16

    32.3=P170,18,CL1:R,16

    32.4=P170,18,CL1:R,17

    33=PLN

    33.1=P170,19,CL1:R,16

    33.2=P170,19,CL1:R,16

    33.3=P170,19,CL1:R,16

    Also I tried re-arranging the line numbers in sequence, also deleting the APP, VOR, MAP and PLN reference lines, but no way.-

    Regards

    Jorge

  8. Perhaps my English understanding is dificult,as it is not my language, or maybe you didnt explain it clearly, or something is missing.-

    Of course I also guessed the same about having all 4 buttons doing the same thing, but you said exactly: "So make two more copies of that line, with increasing line numbers. Now that same switch selection will do 3 decrements" , as I asumed you referred to the first line created: "30=P170,18,CL1:R,17" I made 2 copies changing only the line numbers,leaving the decrement parameter, what else could I understand ?.- Also: "So make two more copies with increasing line numbers, and change the last number on those two lines from 17 to 16 (the parameter for increase).", I did it so, and again, what else could it be understood about it ?.- Although my programming capabilities are null, I really think I am not so dumb, so something is missing at your explanation.- Maybe the button numbers have to be changed in each line, but the sequence is not clear to me.-

    Regards

    Jorge

  9. How do you work out there should be 5 lines for each? You aren't reading what is being written here!!!

    Yes, that's correct. Once a button is programmed with multiple entries in the INI file you cannot change it in the Options screen.

    Yes, and look how wrong they are:

    30=P170,18,CL1:R,17

    31=P170,18,CL1:R,17

    32=P170,18,CL1:R,17

    33=P170,18,CL1:R,16

    34=P170,18,CL1:R,16

    35=P170,17,CL1:R,17

    36=P170,17,CL1:R,17

    37=P170,17,CL1:R,17

    38=P170,17,CL1:R,16

    39=P170,17,CL1:R,16

    40=P170,16,CL1:R,17

    41=P170,16,CL1:R,17

    42=P170,16,CL1:R,17

    43=P170,16,CL1:R,16

    44=P170,16,CL1:R,16

    45=P170,19,CL1:R,17

    46=P170,19,CL1:R,17

    47=P170,19,CL1:R,17

    48=P170,19,CL1:R,16

    49=P170,19,CL1:R,16

    You have all 4 buttons doing EXACTLY the same thing. How on Earth can they make different selections if they all do the same thing? You are not reading what I've been saying at all! :-(

    You have programmed every one to do 3 decrements (so going to "APP"), then 2 increments (so going to "MAP"). Don't you see that? Please THINK about what you are doing!

    Regards

    Pete

  10. Presuming your go flight mode dial is set out APP VOR MAP PLN, to get to each setting you need to do this with the ND decrease and increase functions in macros in the FSUIPC.ini;

    APP = -3 (dec) + 0 (i.e. leave out the increase) assign this to Go Flight EFIS Button 16

    VOR = -3 (dec) + 1 (inc) assign this to Go Flight EFIS Button 17

    MAP = -3 (dec) + 2 (inc) assign this to Go Flight EFIS Button 18

    PLN = -3 (dec) + 3 (inc) assign this to Go Flight EFIS Button 19

    EDIT: You beat me to it Pete, lol. Also my version isn't as efficient.

    Thanks Andydigital

    I wait for Pete response.-

    Regards

    Jorge

  11. Er ... you cannot do what I suggested by simple assignments in FSUIPC. You have to either create a new Lua plugin, (or add to the one you have already) or edit the assignments in your FSUIPC INI file.

    Evidently.

    Let's try it by editing the INI file.

    Assign the button number you get by turning TO the "MAP" position "parameter 17 (decrease)". Remember the joy/button numbers.

    Press OK.

    Load the INI file into an editor like NotePad.

    Find the [buttons] section, and then, within it, a line starting off

    n=Pj,b ....

    where n is simply a line number and j,b are the joy/button numbers.

    Now, this does one "decrement". You need 3 of those. So make two more copies of that line, with increasing line numbers. Now that same switch selection will do 3 decrements -- placing the switch in the left most (APP) position no matter where is was before. This part will apply to all of the other positions too.

    To get to "MAP" from there we need two Increments. So make two more copies with increasing line numbers, and change the last number on those two lines from

    17 to 16 (the parameter for increase).

    Now selecting "MAP" will do 5 operations -- 3 decrements and two increments, so reaching the correct position!

    Okay? Do you understand now? Just apply this logic to all 4 positions.

    Note that there will be shorter ways for some positions. Representing incr by + and decr by - you could do it most efficiently like this:

    APP - - -

    VOR - - - +

    MAP + + + -

    PLN + + +

    So, a maximum of 4 operations listed for any of the 4 switch positions.

    Note that this method is not very efficient and may appear slow. To speed it up you would need to make a new Lua plug-in to handle the switch instead. Try it first, though, till you understand what is going on. It isn't hard to understand, not really, it is just doing what it says, turning the knob to one extreme then back again. Then, if it isn't very satisfactory, we can look at constructing a Lua plug-in.

    Regards

    Pete

    Pete

    I did what you said, beggining by assigning to Map (button 18) the parameter 17 of LUA PDMG747, which created in the ini the line: 30=P170,18,CL1:R,17.-

    I followed then your instructions copying and modifying the line so I created 5 lines for each function, but it doesnt work, also I could see that in the FSUIPC buttons box, switching buttons 16 to 19 shows them grayed out with parameter 17 set.-

    All the other GF Efis device functions work OK.-

    I configurated all as jets profile specific.-

    The relevant lines of my ini are:

    [LuaFiles]

    1=PDMG747

    [buttons.Jets]

    0=P170,4,CL1:R,3

    1=P170,3,CL1:R,4

    2=P170,13,CL1:R,7

    3=P170,15,CL1:R,23

    4=P170,12,CL1:R,8

    5=P170,28,CL1:R,10

    6=P170,14,CL1:R,24

    7=P170,30,CL1:R,20

    8=P170,31,CL1:R,21

    9=P170,2,CL1:R,5

    14=P170,9,K88,14

    15=P170,8,K87,14

    20=P170,1,CL1:R,6

    21=P170,29,CL1:R,10

    22=P170,11,K90,14

    23=P170,10,K89,14

    28=P170,6,CL1:R,2

    30=P170,18,CL1:R,17

    31=P170,18,CL1:R,17

    32=P170,18,CL1:R,17

    33=P170,18,CL1:R,16

    34=P170,18,CL1:R,16

    35=P170,17,CL1:R,17

    36=P170,17,CL1:R,17

    37=P170,17,CL1:R,17

    38=P170,17,CL1:R,16

    39=P170,17,CL1:R,16

    40=P170,16,CL1:R,17

    41=P170,16,CL1:R,17

    42=P170,16,CL1:R,17

    43=P170,16,CL1:R,16

    44=P170,16,CL1:R,16

    45=P170,19,CL1:R,17

    46=P170,19,CL1:R,17

    47=P170,19,CL1:R,17

    48=P170,19,CL1:R,16

    49=P170,19,CL1:R,16

    I remember you that the button numbers of the Mode knob positions are from left to right: VOR: 17, MAP: 18, PLN: 19, and App: 16.-

    Thanks for you patience

    Jorge

  12. If there are only increments and decrements then you have to use them to reach the position you want -- in other words n increments to get from position x to x+n, and so on. You'd either need to synchronise things by hand (i.e. mouse clicks) to start with, and keep track of the position thereafter in the program, or always do enough "decrements" first to be sure it gets to the left-most position so you can count from there.

    Basically, taking the latter method as being easier, if a switch has, say, 4 position, 0-3, like a 737 EFIS mode switch, always start with:

    send decrement

    send decrement

    send decrement

    Now you know you are at position 0

    If you want 1, send one increment, 2 send two, 3 send three. See?

    You can do those things in FSUIPC macros or, in a Lua plug-in, your choice. If the controls you need to send can only be done by the Lua "ipc.control" facility then you can only do it in a Lua plug-in.

    Regards

    Pete

    Pete

    In my case the lua parameters for ND Mode are: increase = 16, decrease = 17.-

    My GF EFIS mode knob has 4 positions, from left to right: App, Vor, Map and Pln; its switching is recognized by FSUIPC as buttons 16, 17, 18, and 19.-

    So

    a) I turn right both panel and device knobs matching at the Pln position.

    B) Turn GF knob left to Map (Fsuipc shows button 18) select LUA747PDMG and assign parameter 17 (decrease).-

    c) Turn GF knob left to Vor (Fsuipc shows button 17) select LUA747PDMG and assign parameter 17 (decrease).-

    d) Turn GF knob left to App (Fsuipc shows button 16) select LUA747PDMG and assign parameter 17 (decrease).-

    e) Make a test returning GF knob to Pln, and then turning again left to Map, to Vor and to App, it works OK as the panel knob replicates the GF device movements, so both panel and GF device knobs are now at App.-

    f) Turn GF knob right from App to Vor (Fsuipc shows button 17) select LUA747PDMG and parameter 17 shows already set, as it happens for the subsequent positions, so if I try to select parameter 16 (increase), I must replace all the former settings, which makes the work return to the beginning.-

    So the results are that I am able to switch the mode knob only one way, and with the condition that the panel knob should be previously set by mouse at the first position.-

    Maybe there is something I dont understand at your explanation.-

    Thanks

    Jorge

  13. I did what Pete said, and it worked with most functions.-

    I have problems with:

    The left and right VOR decrease, it only works in increase mode, so the left and right ADF selection is not available.-

    Cannot manage to configure the mode and range rotaries as there are only increase and decrease parameters available.-

    I mapped the Baro knob pressing mode to Std, and although the animation can be seen, it doesnt change the mode at the gauge.-

    I noticed that at the FSUIPC button assignements box list, besides the LUA PDMG747 entry, also appears the following ones: LUAClear, LUAdebug, LUAKill, LUASet, LUAToggle and LUAValue all related to the PDMG747, what are them for ?.-

    Also I couldnt found a Baro increase/decrease parameter which is useful to map at the upper right rotary knob, instead of an IN/HPA switch.-

    Thanks

  14. I managed to configure my GoFlight Efis with the GF software to work with my PDMG B 747, using its own keymapping list.- The result was that all EFIS functions worked surprisingly well for a time at first, now I dont know why, but it fails to work and couldnt fix it.-

    So I tried configuring it with FSUIPC, using again the keymapping list provided with that addon aircraft.-

    I entered the "buttons/switches" box and noticed that the device is recognized as 170 and all its functions send diferent numbers.- I checked "select for keypress",selected my jets profile and assigned all the key combinations I could, the result was that some functions work OK, and some others dont.-

    I couldnt map the mode and range rotaries, for which the keymapping list has no puntual positions, but increase and decrease options.-

    Also all 7 lower buttons doesnt work.-

    I send the relevant part of my ini:

    [buttons.Jets]

    0=P170,16,K96,14

    1=P170,17,K96,14

    2=P170,18,K96,14

    3=P170,19,K96,14

    4=P170,14,K98,14

    5=P170,9,K88,14

    6=P170,8,K87,14

    7=P170,11,K90,14

    8=P170,10,K89,14

    9=P170,20,K99,14

    10=P170,21,K99,14

    11=P170,22,K99,14

    12=P170,23,K99,14

    13=P170,24,K99,14

    14=P170,25,K99,14

    15=P170,4,K104,14

    16=P170,3,K105,14

    17=P170,2,K109,14

    18=P170,1,K187,14

    19=P170,0,K220,14

    20=P170,15,K84,14

    21=P170,12,K86,14

    22=P170,13,K85,14

    23=P170,28,K82,14

    24=P170,29,K83,14

    25=P170,30,K78,14

    26=P170,31,K79,14

    Also the relevant part of the PDMG B747 keymapping list:

    [EFIS Captain]

    Press MINS=Ctrl+Tab+M

    Increase MINS=Ctrl+Tab+N

    Decrease MINS=Ctrl+Tab+O

    Reset MINS=Ctrl+Tab+P

    Press BARO=Ctrl+Tab+Q

    Increase BARO=Ctrl+Tab+R

    Decrease BARO=Ctrl+Tab+S

    Press BARO STD=Ctrl+Tab+T

    Press FPV=Ctrl+Tab+U

    Press MTRS=Ctrl+Tab+V

    Increase NAVL=Ctrl+Tab+W

    Decrease NAVL=Ctrl+Tab+X

    Increase NAVR=Ctrl+Tab+Y

    Decrease NAVR=Ctrl+Tab+Z

    Increase NDMODE=Ctrl+Tab+Num_0

    Decrease NDMODE=Ctrl+Tab+Num_1

    Press NDMODE CTR=Ctrl+Tab+Num_2

    Increase NDRANGE=Ctrl+Tab+Num_3

    Decrease NDRANGE=Ctrl+Tab+Num_4

    Press NDRANGE TFC=Ctrl+Tab+Num_5

    Press WXR=Ctrl+Tab+Num_6

    Press STA=Ctrl+Tab+Num_7

    Press WPT=Ctrl+Tab+Num_8

    Press ARPT=Ctrl+Tab+Num_9

    Press DATA=Ctrl+Tab+-

    Press POS=Ctrl+Tab+=

    Press TERR=Ctrl+Tab+\

    Need some help for my problem

    Thanks

    Jorge

  15. I really wanted you to do the comparison, not I. I already listed all the areas that have any relevance.

    Okay. That shouldn't affect the Profile-specific aircraft, but it will affect aircraft not assigned to a Profile.

    Er, wait a minute. This is new. you explicitly said it was the LevelD B 737. so i've been looking in the wrong place all this time?

    Which settings do you want, the Jets profile ones or the 767 specific ones? If you want the latter just remove the 767 name in the [Profile.Jets] section. If you want it to abide by the Jets profile, delete all the sections with the 767 in the name.

    Until you've done this and tested it there's no point in continuing.

    Regards

    Pete

    [/quote

    ]

    Pete

    Sorry about the confusion about the 737, it was a silly mistake.-

    I deleted the last Level D B767 profile and calibration section, reassigned axis of the throttle and reversers only, and calibrated them, and now it works OK.-

    I didnt delete yet the B767 line at the jets profile, so it seems both profiles coexist without problems.- The new lines look like this:

    [Profile.Level D Simulations B767-300ER]

    1=Level D Simulations B767-300ER

    [Axes.Level D Simulations B767-300ER]

    0=0X,256,D,7,40,0,0

    1=0Y,256,D,8,0,0,0

    2=0Z,256,D,3,40,0,0

    3=1X,256,D,9,0,0,0

    4=1Y,256,D,10,0,0,0

    5=1R,256,D,42,0,0,0

    6=1V,256,D,41,0,0,0

    7=2X,256,D,1,38,0,0

    8=2Y,256,D,2,39,0,0

    9=2Z,256,D,4,0,0,0

    10=2U,256,D,6,0,0,0

    11=2V,256,D,5,0,0,0

    12=2P,0,F,66416,0,0,0

    Thanks

  16. So, a comparison of the two INI files would prove very helpful, would it not? A much easier way to diagnose the problem than trying to work out which bits of the INI you supplied applies to that aircraft?

    Isolating just those lines rleevant to Throttle axis assignments and calibrations, you have:

    1=CH THROTTLE QUADRANT

    1.GUID={631A6290-C9A3-11DF-8002-444553540000}

    So the Throttle is joystick #1.

    2=CH FLIGHT SIM YOKE USB

    2.GUID={631A89A0-C9A3-11DF-8003-444553540000}

    Doesn't the yoke also have a throttle mounted on it? I seem to remember, aeons ago, my CH yoke having one, on top.

    [Axes]

    3=1X,256,D,9,0,0,0

    4=1Y,256,D,10,0,0,0

    5=1R,256,D,42,0,0,0

    6=1V,256,D,41,0,0,0

    Those are Throttle 1 and 2 and Reversers 1 and 2.

    [JoystickCalibration]

    Throttle=-16384,16383

    Throttle1=-16253,-10532,512,14208

    Throttle2=-16384,-8842,512,15232

    Seems okay except you have the default throttle calibrated too? Best press "Reset" on that.

    [Profile.Jets]

    1=PMDG

    2=FeelThere Boeing

    3=Learjet 45

    4=Level D Simulations B767-300ER

    5=Commercial Level

    6=Boeing 737-800

    7=Boeing 747-400

    8=Bombardier CRJ 700

    9=CS 727-200

    10=CS 727-100

    11=Captain Sim 757-200

    11=CS 767-300

    12=Boeing 777-223ER

    13=CS 767-300

    14=CS 767 Captain AWACS

    15=MS-760_AAF

    16=LSH MD-82

    17=Super 80 Professional

    18=Eaglesoft Citation

    19=PIC Citation X

    20=jf_A320-211 CFM56

    21=jf_A320-232_IAE

    22=Airbus A321

    23=A330-200

    24=Feelthere A340-300 Airbus

    25=Feelthere A340-600 Airbus

    26=CS_B707-300

    27=Concorde

    28=Embraer 175

    29=Embraer 195

    You have a ***LOT*** of aircraft categorised in your "Jets" profile! And these are all fine with the throttles? Which here will your LevelD B 737 match to? Or have you not assigned it to a Profile? We'd need to know to understand which calibration is appropriate.

    Also, you appear to have "Level D Simulations B767-300ER" listed as a Jets profile aircraft whilst also having a separate Profile for it too:

    [Profile.Level D Simulations B767-300ER]

    1=Level D Simulations B767-300ER

    [JoystickCalibration.Level D Simulations B767-300ER]

    [buttons.Level D Simulations B767-300ER]

    To be honest, I'm not sure which of the two assignments will take priority in such a case.

    However, carrying on:

    [Axes.Jets]

    3=1X,256,D,9,0,0,0

    4=1Y,256,D,10,0,0,0

    5=1Z,256,D,11,0,0,0

    6=1R,256,D,43,44,0,0

    7=1U,256,D,12,0,0,0

    8=1V,256,D,41,42,0,0

    That's the Jets profile 4 throttles and 4 reversers.

    [JoystickCalibration.Jets]

    Throttle=-16384,16383

    Throttle1=-16384,-512,512,14208/32

    Throttle2=-16253,-512,512,15360/32

    Throttle3=-16384,-512,512,14720/32

    SyncSlopeThrottle3=26/26,33/33,44/47,62/66,85/86,104/104,127/128

    Throttle4=-16384,-512,512,14848/32

    Reverser1=-16384,14848

    Reverser2=-16384,14848

    Reverser3=-16384,14208

    Reverser4=-16384,14208

    SyncSlopeThrottle4=26/33,30/47,53/66,81/86,109/104,127/128

    SlopeLeftBrake=15

    SlopeRightBrake=15

    You appear to have the default throttle calibrated too. Best to "Reset" that.

    Not sure why you sre Synching throttles 3 and 4 but not 2. Is it because they are behaving very differently?

    Anyway, there's nothing i can see here which would mess up only ONE "Jets" profile aircraft and not the others, assunming your 737 fits as one of those listed.

    Looks like a comparison with your older but working INI is necessary.

    Regards

    Pete

    Thanks Pete for your quick reply

    I am on work now, so I will send the older ini tonight.-

    For now I can say:

    The CH Flightsim Yoke has indeed its own throttle which works in my case only as a general setting with aircraft not included in special profiles.-

    All aircraft included in my jets profile are fine with the throttles.-

    The "Level D.Simulations B767-300ER" (which is efectively the problematic aircraft)is included in the original jet profiles, and in a second one with its own calibration lines.- I think it is so because after including in the ini all the related to Go Flight EFIS, as steveo38 gently sent to me, the throttle wasnt working and had to calibrate it again.-

    As I noticed that also, I tried deleting both the redundant profile and calibrating lines, but no way, the problem continued.-

  17. I have just spent some time and sorted this out for you. Change the line numbers 42 through to 56 with the following:

    42=P170,16,CM2:2,0

    43=P170,16,CM2:2,0

    44=P170,16,CM2:2,0

    45=P170,16,CM2:2,0

    46=P170,16,CM2:2,0

    //47=P170,16,CM2:2,0

    //48=P170,16,CM2:2,0

    49=P170,17,CM2:2,0

    50=P170,17,CM2:2,0

    51=P170,17,CM2:2,0

    52=P170,17,CM2:2,0

    53=P170,17,CM2:2,0

    54=P170,17,CM2:1,0

    //55=P170,17,CM2:2,0

    //56=P170,17,CM2:2,0

    Yes, that how I have configured it since I use FS2Crew alot. You can change lines 139,140,143,144 to assign something else to it if you wish.

    No, I dont fly those planes.

    My GoFlight EFIS works OK with the LevelD B 737, but now I have problems with throttles, when I takeoff manually, they perform erratically, sometimes going to minimuns, and sometimes one lever stays at maximun while the other goes to minimun.- I have no problems with other aircraft, and as I saved a backup of my former .ini, I replaced it and the problems dissapeared, so obviously the issue is due to the modifications made in it.- I have my controls disabled in FSX, and FSUIPC managing them, I am using CH quadrant, pedals and yoke in Windows 7 64.-

    Any opinion will be welcome

    Thanks

    This is the contents of my .ini

    [General]

    UpdatedByVersion=4645

    History=5DB1GX85PGSC9UH671UFB

    TCASid=Flight

    TCASrange=40

    AxisCalibration=No

    DirectAxesToCalibs=No

    ShowMultilineWindow=Yes

    SuppressSingleline=No

    SuppressMultilineFS=No

    AxisIntercepts=No

    DontResetAxes=No

    WeatherReadFactor=2

    WeatherRewriteSeconds=1

    CustomWeatherModify=No

    SimConnectStallTime=1

    MouseWheelTrim=No

    MouseWheelTrimSpeed=1

    JoystickTimeout=15

    FixControlAccel=Yes

    FixMachSpeedBug=No

    VisibilityOptions=No

    OneCloudLayer=No

    CloudTurbulence=No

    CloudIcing=No

    GenerateCirrus=Yes

    SuppressCloudTurbulence=No

    MaxIce=-4

    MinIce=-4

    UpperWindGusts=No

    SuppressWindTurbulence=No

    SuppressWindVariance=No

    WindTurbulence=Yes

    TurbulenceRate=1.0,5.0

    TurbulenceDivisor=20,20,40,40

    SuppressAllGusts=No

    MaxSurfaceWind=0

    WindLimitLevel=200

    WindDiscardLevel=400

    WindAjustAltitude=No

    WindAjustAltitudeBy=2000

    SmoothBySimTime=No

    WindSmoothing=No

    WindSmoothness=2

    WindSmoothAirborneOnly=Yes

    PressureSmoothness=0

    TemperatureSmoothness=0

    DisconnTrimForAP=No

    ZeroElevForAPAlt=No

    ThrottleSyncAll=No

    WhiteMessages=No

    ShowPMcontrols=No

    SpoilerIncrement=512

    MagicBattery=No

    RudderSpikeRemoval=No

    ElevatorSpikeRemoval=No

    AileronSpikeRemoval=No

    ReversedElevatorTrim=No

    ClockSync=No

    ClockSyncMins=5

    ClearWeatherDynamics=No

    OwnWeatherChanges=No

    TimeForSelect=4

    LoadFlightMenu=No

    LoadPlanMenu=No

    PauseAfterCrash=No

    BrakeReleaseThreshold=75

    SaveDataWithFlights=No

    ZapSound=firework

    ShortAircraftNameOk=Substring

    UseProfiles=Yes

    Console=No

    PollGFTQ6=Yes

    BlankDisplays=No

    GetNearestAirports=No

    LuaRerunDelay=66

    [JoyNames]

    AutoAssignLetters=No

    0=CH PRO PEDALS USB

    0.GUID={631A6290-C9A3-11DF-8001-444553540000}

    1=CH THROTTLE QUADRANT

    1.GUID={631A6290-C9A3-11DF-8002-444553540000}

    2=CH FLIGHT SIM YOKE USB

    2.GUID={631A89A0-C9A3-11DF-8003-444553540000}

    [WideServer]

    WideFSenabled=Yes

    [buttons]

    ButtonRepeat=20,10

    1=P1,0,K54,8

    2=P1,1,K55,8

    3=P1,4,K52,9

    4=P1,5,K90,8

    5=P1,7,K191,9

    6=P1,8,K82,9

    7=P1,9,K90,8

    8=P1,10,K117,8

    9=P1,11,K118,8

    10=P2,4,K121,8

    11=P2,5,K120,8

    12=P2,7,K122,8

    13=R2,10,K36,8

    14=R2,11,K35,8

    15=R2,8,K13,9

    16=R2,9,K8,9

    17=P2,1,K190,10

    18=R2,3,K135,10

    19=R2,2,K45,10

    [AutoSave]

    AutoSaveEnabled=No

    [GPSout]

    GPSoutEnabled=No

    Port=COM0

    Speed=4800

    Interval=2000

    PosTo6Decimal=No

    Sentences=

    [GPSout2]

    GPSoutEnabled=No

    Port=<none set>

    Speed=4800

    Interval=2000

    PosTo6Decimal=No

    Sentences=

    [Axes]

    0=0X,256,D,7,40,0,0

    1=0Y,256,D,8,0,0,0

    2=0Z,256,D,3,40,0,0

    3=1X,256,D,9,0,0,0

    4=1Y,256,D,10,0,0,0

    5=1R,256,D,42,0,0,0

    6=1V,256,D,41,0,0,0

    7=2X,256,D,1,38,0,0

    8=2Y,256,D,2,39,0,0

    9=2Z,256,D,4,0,0,0

    10=2U,256,D,6,0,0,0

    11=2V,256,D,5,0,0,0

    12=2P,0,F,66416,0,0,0

    [JoystickCalibration]

    AllowSuppressForPFCquad=Yes

    ExcludeThrottleSet=Yes

    ExcludeMixtureSet=Yes

    ExcludePropPitchSet=Yes

    SepRevsJetsOnly=No

    ApplyHeloTrim=No

    UseAxisControlsForNRZ=No

    FlapsSetControl=0

    FlapDetents=No

    ReverserControl=66292

    Reverser1Control=66422

    Reverser2Control=66425

    Reverser3Control=66428

    Reverser4Control=66431

    MaxThrottleForReverser=256

    AileronTrimControl=66731

    RudderTrimControl=66732

    CowlFlaps1Control=66162

    CowlFlaps2Control=66163

    CowlFlaps3Control=66164

    CowlFlaps4Control=66165

    SteeringTillerControl=0

    MaxSteerSpeed=60

    Aileron=-16253,-520,-520,15744

    Elevator=-15213,-1430,-1430,16128

    Rudder=-16384,0,0,16256

    Throttle=-16384,16383

    PropPitch=-16384,16383

    Mixture=-16253,16383

    LeftBrake=-16384,15616/16

    RightBrake=-16253,16383/16

    Reverser1=-16384,14848

    Reverser2=-16384,14848

    Reverser3=-16384,14208

    Reverser4=-16384,14208

    Spoilers=-16380,16380/16

    SyncSlopeThrottle3=26/26

    PropPitch1=-16384,-16384,0,14720

    PropPitch2=-16384,-16384,512,16383

    Throttle1=-16253,-10532,512,14208

    Throttle2=-16384,-8842,512,15232

    Throttle3=-16384,-512,512,14720

    Throttle4=-16384,-512,512,16383

    [Profile.Jets]

    1=PMDG

    2=FeelThere Boeing

    3=Learjet 45

    4=Level D Simulations B767-300ER

    5=Commercial Level

    6=Boeing 737-800

    7=Boeing 747-400

    8=Bombardier CRJ 700

    9=CS 727-200

    10=CS 727-100

    11=Captain Sim 757-200

    11=CS 767-300

    12=Boeing 777-223ER

    13=CS 767-300

    14=CS 767 Captain AWACS

    15=MS-760_AAF

    16=LSH MD-82

    17=Super 80 Professional

    18=Eaglesoft Citation

    19=PIC Citation X

    20=jf_A320-211 CFM56

    21=jf_A320-232_IAE

    22=Airbus A321

    23=A330-200

    24=Feelthere A340-300 Airbus

    25=Feelthere A340-600 Airbus

    26=CS_B707-300

    27=Concorde

    28=Embraer 175

    29=Embraer 195

    [Axes.Jets]

    0=0X,256,D,7,0,0,0

    1=0Y,256,D,8,0,0,0

    2=0Z,256,D,3,40,0,0

    3=1X,256,D,9,0,0,0

    4=1Y,256,D,10,0,0,0

    5=1Z,256,D,11,0,0,0

    6=1R,256,D,43,44,0,0

    7=1U,256,D,12,0,0,0

    8=1V,256,D,41,42,0,0

    9=2X,256,D,1,38,0,0

    10=2Y,256,D,2,39,0,0

    11=2U,256,D,22,0,0,0

    12=2P,0,F,66416,0,0,0

    [Profile.Prop Twin]

    1=FSD Panther

    2=RealAir Beech Duke

    3=Beech Baron

    4=PA-34 SENECA II

    5=FSD Navajo Flair

    6=Douglas DC-3

    7=RealAir Beech Duke

    8=IA-35 Huanquero

    9=Piper PA-44 Seminole

    10=Navajo

    11=Eaglesoft Piper TC

    [Axes.Prop Twin]

    0=0X,256,D,7,40,0,0

    1=0Y,256,D,8,0,0,0

    2=0Z,256,D,3,40,0,0

    3=1X,256,D,9,0,0,0

    4=1Y,256,D,10,0,0,0

    5=1Z,256,D,17,0,0,0

    6=1R,256,D,14,0,0,0

    7=1U,256,D,18,0,0,0

    8=1V,256,D,13,0,0,0

    9=2X,256,D,1,38,0,0

    10=2Y,256,D,2,39,0,0

    11=2Z,256,D,4,0,0,0

    12=2U,256,D,6,0,0,0

    13=2V,256,D,5,0,0,0

    14=2P,0,F,66416,0,0,0

    [Profile.Turboprop BAE]

    1=PMDG J-41

    [Axes.Turboprop BAE]

    0=0X,256,D,7,40,0,0

    1=0Y,256,D,8,0,0,0

    2=0Z,256,D,3,40,0,0

    3=1X,256,D,9,0,0,0

    4=1Y,256,D,10,0,0,0

    5=1R,256,D,18,0,0,0

    6=1V,256,D,17,0,0,0

    7=2X,256,D,1,38,0,0

    8=2Y,256,D,2,39,0,0

    9=2Z,256,D,4,0,0,0

    10=2U,256,D,6,0,0,0

    11=2V,256,D,5,0,0,0

    12=2P,0,F,66416,0,0,0

    [JoystickCalibration.Turboprop BAE]

    AllowSuppressForPFCquad=Yes

    ExcludeThrottleSet=Yes

    ExcludeMixtureSet=Yes

    ExcludePropPitchSet=Yes

    SepRevsJetsOnly=No

    ApplyHeloTrim=No

    FlapsSetControl=0

    FlapDetents=No

    ReverserControl=66292

    Reverser1Control=66422

    Reverser2Control=66425

    Reverser3Control=66428

    Reverser4Control=66431

    MaxThrottleForReverser=256

    AileronTrimControl=66731

    RudderTrimControl=66732

    CowlFlaps1Control=66162

    CowlFlaps2Control=66163

    CowlFlaps3Control=66164

    CowlFlaps4Control=66165

    SteeringTillerControl=0

    MaxSteerSpeed=60

    Aileron=-16253,-520,-520,15744

    Elevator=-15213,-1430,-1430,16128

    Rudder=-16384,-130,-130,16128

    Throttle=-16384,16383

    PropPitch=-16384,16383

    Mixture=-16253,16383

    LeftBrake=-16384,15616/16

    RightBrake=-16253,16383/16

    Throttle1=-16384,-11963,512,14208

    Throttle2=-16384,-8582,512,15232

    Throttle3=-16384,-512,512,14720

    Throttle4=-16384,-512,512,16383

    PropPitch1=-16384,-16384,-16384,14848

    PropPitch2=-16384,-16384,-16384,14208

    Spoilers=-16380,16380/16

    Reverser1=-16384,14848

    Reverser2=-16384,14848

    Reverser3=-16384,14208

    Reverser4=-16384,14208

    UseAxisControlsForNRZ=No

    SlopeRudder=15

    [Profile.Turboprop Cheyenne]

    1=Piper PA31T

    2=Piper PA31T1

    3=Piper PA31T2

    4=de Havilland Canadian Twin Otter

    [Axes.Turboprop Cheyenne]

    0=0X,256,D,7,40,0,0

    1=0Y,256,D,8,0,0,0

    2=0Z,256,D,3,40,0,0

    3=1X,256,D,9,0,0,0

    4=1Y,256,D,10,0,0,0

    5=1Z,256,D,17,0,0,0

    6=1R,256,D,14,0,0,0

    7=1U,256,D,18,0,0,0

    8=1V,256,D,13,0,0,0

    9=2X,256,D,1,38,0,0

    10=2Y,256,D,2,39,0,0

    11=2Z,256,D,4,0,0,0

    12=2U,256,D,6,0,0,0

    13=2V,256,D,5,0,0,0

    14=2P,0,F,66416,0,0,0

    [JoystickCalibration.Turboprop Cheyenne]

    AllowSuppressForPFCquad=Yes

    ExcludeThrottleSet=Yes

    ExcludeMixtureSet=Yes

    ExcludePropPitchSet=Yes

    SepRevsJetsOnly=No

    ApplyHeloTrim=No

    FlapsSetControl=0

    FlapDetents=No

    ReverserControl=66292

    Reverser1Control=66422

    Reverser2Control=66425

    Reverser3Control=66428

    Reverser4Control=66431

    MaxThrottleForReverser=256

    AileronTrimControl=66731

    RudderTrimControl=66732

    CowlFlaps1Control=66162

    CowlFlaps2Control=66163

    CowlFlaps3Control=66164

    CowlFlaps4Control=66165

    SteeringTillerControl=0

    MaxSteerSpeed=60

    Aileron=-16253,-520,-520,15744

    Elevator=-15213,-1430,-1430,16128

    Rudder=-16384,0,0,16256

    Throttle=-16384,16383

    PropPitch=-16384,16383

    Mixture=-16253,16383

    LeftBrake=-16384,15616/16

    RightBrake=-16253,16383/16

    Throttle1=-16384,-11703,-512,14208

    Throttle2=-16384,-11312,-512,15232

    Throttle3=-16384,-512,512,14720

    Throttle4=-16384,-512,512,16383

    Mixture1=-16384,8192,8192,14976/32

    Mixture2=-16384,8192,8192,14208/32

    PropPitch1=-16384,-16384,-16384,14720

    PropPitch2=-16384,-16384,-16384,14976

    Spoilers=-16380,16380/16

    Reverser1=-16384,14848

    Reverser2=-16384,14848

    Reverser3=-16384,14208

    Reverser4=-16384,14208

    UseAxisControlsForNRZ=No

    [MacroFiles]

    1=747 OHD

    2=LVLD767

    3=APchart

    [JoystickCalibration.Jets]

    AllowSuppressForPFCquad=Yes

    ExcludeThrottleSet=Yes

    ExcludeMixtureSet=Yes

    ExcludePropPitchSet=Yes

    SepRevsJetsOnly=No

    ApplyHeloTrim=No

    UseAxisControlsForNRZ=No

    FlapsSetControl=0

    FlapDetents=No

    ReverserControl=66292

    Reverser1Control=66422

    Reverser2Control=66425

    Reverser3Control=66428

    Reverser4Control=66431

    MaxThrottleForReverser=256

    AileronTrimControl=66731

    RudderTrimControl=66732

    CowlFlaps1Control=66162

    CowlFlaps2Control=66163

    CowlFlaps3Control=66164

    CowlFlaps4Control=66165

    SteeringTillerControl=0

    MaxSteerSpeed=60

    Aileron=-16253,-520,-520,15744

    Elevator=-15213,-1430,-1430,16128

    Rudder=-16384,0,0,16256

    Throttle=-16384,16383

    PropPitch=-16384,16383

    Mixture=-16253,16383

    LeftBrake=-16384,15616/16

    RightBrake=-16253,16383/16

    Throttle1=-16384,-512,512,14208/32

    Throttle2=-16253,-512,512,15360/32

    Throttle3=-16384,-512,512,14720/32

    SyncSlopeThrottle3=26/26,33/33,44/47,62/66,85/86,104/104,127/128

    Throttle4=-16384,-512,512,14848/32

    PropPitch1=-16384,-16384,0,14720

    PropPitch2=-16384,-16384,512,16383

    Spoilers=-16380,16380/16

    Reverser1=-16384,14848

    Reverser2=-16384,14848

    Reverser3=-16384,14208

    Reverser4=-16384,14208

    SyncSlopeThrottle4=26/33,30/47,53/66,81/86,109/104,127/128

    SlopeLeftBrake=15

    SlopeRightBrake=15

    [JoystickCalibration.Prop Twin]

    AllowSuppressForPFCquad=Yes

    ExcludeThrottleSet=Yes

    ExcludeMixtureSet=Yes

    ExcludePropPitchSet=Yes

    SepRevsJetsOnly=No

    ApplyHeloTrim=No

    UseAxisControlsForNRZ=No

    FlapsSetControl=0

    FlapDetents=No

    ReverserControl=66292

    Reverser1Control=66422

    Reverser2Control=66425

    Reverser3Control=66428

    Reverser4Control=66431

    MaxThrottleForReverser=256

    AileronTrimControl=66731

    RudderTrimControl=66732

    CowlFlaps1Control=66162

    CowlFlaps2Control=66163

    CowlFlaps3Control=66164

    CowlFlaps4Control=66165

    SteeringTillerControl=0

    MaxSteerSpeed=60

    Aileron=-16253,-520,-520,15744

    Elevator=-14043,-260,-260,16256

    Rudder=-16384,0,0,16256

    Throttle=-16384,16383

    PropPitch=-16384,16383

    Mixture=-16253,16383

    LeftBrake=-16384,15616/16

    RightBrake=-16253,16383/16

    Throttle1=-16384,-512,512,14208/40

    Throttle2=-16384,-512,512,15360/40

    SyncSlopeThrottle2=26/26

    Throttle3=-16384,-512,512,14720/32

    SyncSlopeThrottle3=26/26

    Throttle4=-16384,-512,512,16383/32

    PropPitch1=-16384,-16384,0,14720

    PropPitch2=-16384,-16384,512,16383

    Spoilers=-16380,16380/16

    Reverser1=-16384,14848

    Reverser2=-16384,14848

    Reverser3=-16384,14208

    Reverser4=-16384,14208

    [Profile.Turboprop ATR]

    1=Flight 1 ATR 72-500

    [Axes.Turboprop ATR]

    0=0X,256,D,7,40,0,0

    1=0Y,256,D,8,0,0,0

    2=0Z,256,D,3,40,0,0

    3=1X,256,D,9,0,0,0

    4=1Y,256,D,10,0,0,0

    5=1Z,256,D,17,0,0,0

    6=1R,256,F,14,0,0,0

    7=1U,256,D,18,0,0,0

    8=1V,256,D,13,0,0,0

    9=2X,256,D,1,38,0,0

    10=2Y,256,D,2,39,0,0

    11=2Z,256,D,4,0,0,0

    12=2U,256,D,6,0,0,0

    13=2V,256,D,5,0,0,0

    14=2P,0,F,66416,0,0,0

    [sounds]

    Path=E:\FS10\Sound\

    Device1=Controlador primario de sonido

    Device2=Altavoces (SoundMAX Integrated Digital HD Audio)

    Device3=Interfaz SPDIF (SoundMAX Integrated Digital HD Audio)

    [Window.Radar Contact]

    Docked=242, 2813, 3548, 30

    [buttons.Level D Simulations B767-300ER]

    7=P170,21,CM2:5,0

    8=P170,21,CM2:5,0

    9=P170,21,CM2:5,0

    10=P170,21,CM2:5,0

    11=P170,21,CM2:5,0

    12=P170,21,CM2:4,0

    13=P170,20,CM2:5,0

    14=P170,20,CM2:5,0

    15=P170,20,CM2:5,0

    16=P170,20,CM2:5,0

    17=P170,20,CM2:5,0

    18=P170,22,CM2:5,0

    19=P170,22,CM2:5,0

    20=P170,22,CM2:5,0

    21=P170,22,CM2:5,0

    22=P170,22,CM2:5,0

    23=P170,22,CM2:4,0

    24=P170,22,CM2:4,0

    25=P170,23,CM2:5,0

    26=P170,23,CM2:5,0

    27=P170,23,CM2:5,0

    28=P170,23,CM2:5,0

    29=P170,23,CM2:5,0

    30=P170,23,CM2:4,0

    31=P170,23,CM2:4,0

    32=P170,23,CM2:4,0

    33=P170,24,CM2:5,0

    34=P170,24,CM2:5,0

    35=P170,24,CM2:5,0

    36=P170,24,CM2:5,0

    37=P170,24,CM2:5,0

    38=P170,24,CM2:4,0

    39=P170,24,CM2:4,0

    40=P170,24,CM2:4,0

    41=P170,24,CM2:4,0

    42=P170,16,CM2:2,0

    43=P170,16,CM2:2,0

    44=P170,16,CM2:2,0

    45=P170,16,CM2:2,0

    46=P170,16,CM2:2,0

    //47=P170,16,CM2:2,0

    //48=P170,16,CM2:2,0

    49=P170,17,CM2:2,0

    50=P170,17,CM2:2,0

    51=P170,17,CM2:2,0

    52=P170,17,CM2:2,0

    53=P170,17,CM2:2,0

    54=P170,17,CM2:1,0

    //55=P170,17,CM2:2,0

    //56=P170,17,CM2:2,0

    57=P170,18,CM2:1,0

    58=P170,18,CM2:1,0

    59=P170,18,CM2:1,0

    60=P170,18,CM2:1,0

    61=P170,18,CM2:1,0

    62=P170,18,CM2:2,0

    63=P170,19,CM2:1,0

    64=P170,19,CM2:1,0

    65=P170,19,CM2:1,0

    66=P170,19,CM2:1,0

    67=P170,19,CM2:1,0

    68=P170,9,CM2:6,0

    69=P170,8,CM2:6,0

    70=P170,11,CM2:7,0

    71=P170,10,CM2:7,0

    //72=P170,28,CM2:10,0

    //73=P170,29,CM2:11,0

    //74=P170,30,CM2:8,0

    //75=P170,31,CM2:9,0

    74=P170,1,CM2:56,0

    76=P170,5,CM2:12,0

    77=P170,4,CM2:15,0

    78=P170,3,CM2:13,0

    79=P170,2,CM2:14,0

    81=P174,10,CM2:17,0

    82=P174,9,CM2:18,0

    83=P174,11,CM2:19,0

    84=P174,8,CM2:20,0

    95=P174,0,CM2:33,0

    //96=P170,14,CM2:3,0

    98=P170,13,CM2:34,0

    99=P170,12,CM2:35,0

    100=P170,25,CM2:5,0

    101=P170,25,CM2:5,0

    102=P170,25,CM2:5,0

    103=P170,25,CM2:5,0

    104=P170,25,CM2:5,0

    105=P170,25,CM2:4,0

    106=P170,25,CM2:4,0

    107=P170,25,CM2:4,0

    108=P170,25,CM2:4,0

    109=P170,25,CM2:4,0

    112=P101,7,CM2:41,0

    113=P109,5,CM2:37,0

    114=U109,5,CM2:39,0

    118=P101,9,CM2:43,0

    120=P170,0,CM2:54,0

    121=P1,6,K54,9

    122=P1,5,K55,9

    123=P1,4,K53,9

    124=P101,15,CM2:41,0

    125=P170,15,C1005,43535

    126=CP(F+170,15)170,28,CM2:49,0

    127=CP(F+170,15)170,29,CM2:50,0

    128=CP(F-170,15)170,28,CM2:10,0

    129=CP(F-170,15)170,29,CM2:11,0

    130=CU(F+170,15)170,28,CM2:49,0

    131=CU(F+170,15)170,29,CM2:50,0

    132=CU(F-170,15)170,28,CM2:10,0

    133=CU(F-170,15)170,29,CM2:11,0

    134=P170,6,CM2:16,0

    //135=U170,31,CM2:9,0

    //136=U170,30,CM2:8,0

    137=P173,0,CM2:3,0

    138=P170,14,C1005,43535

    139=CP(F+170,14)170,30,CM2:51,0

    140=CP(F+170,14)170,31,CM2:52,0

    141=CP(F-170,14)170,30,CM2:8,0

    142=CP(F-170,14)170,31,CM2:9,0

    143=CU(F+170,14)170,30,CM2:51,0

    144=CU(F+170,14)170,31,CM2:52,0

    145=CU(F-170,14)170,30,CM2:8,0

    146=CU(F-170,14)170,31,CM2:9,0

    151=P0,18,K53,9

    152=P0,19,K54,9

    153=P0,16,CM2:45,0

    155=P165,2,CM2:53,0

    156=P165,1,CM2:3,0

    163=P0,14,K87,11

    167=P158,14,CL23:R,0

    168=U158,14,CL23:K,0

    169=P0,15,K75,11

    170=R169,1,C66635,0

    171=U169,1,C65967,0

    172=R169,2,C66636,0

    173=U169,2,C65972,0

    174=P0,17,C65876,0

    [Profile.Level D Simulations B767-300ER]

    1=Level D Simulations B767-300ER

    [JoystickCalibration.Level D Simulations B767-300ER]

    AllowSuppressForPFCquad=Yes

    ExcludeThrottleSet=Yes

    ExcludeMixtureSet=Yes

    ExcludePropPitchSet=Yes

    SepRevsJetsOnly=No

    ApplyHeloTrim=No

    UseAxisControlsForNRZ=No

    FlapsSetControl=0

    FlapDetents=No

    ReverserControl=66292

    Reverser1Control=66422

    Reverser2Control=66425

    Reverser3Control=66428

    Reverser4Control=66431

    MaxThrottleForReverser=256

    AileronTrimControl=66731

    RudderTrimControl=66732

    CowlFlaps1Control=66162

    CowlFlaps2Control=66163

    CowlFlaps3Control=66164

    CowlFlaps4Control=66165

    SteeringTillerControl=0

    MaxSteerSpeed=60

    Aileron=-16253,-520,-520,15744

    Elevator=-15213,-1430,-1430,16128

    Rudder=-16384,0,0,16256

    Throttle=-16384,16383

    PropPitch=-16384,16383

    Mixture=-16253,16383

    LeftBrake=-16384,15616/16

    RightBrake=-16253,16383/16

    Throttle1=-16253,-512,512,14336/32

    Throttle2=-16384,-512,512,15360/32

    Throttle3=-16384,-512,512,14720/32

    SyncSlopeThrottle3=26/26

    Throttle4=-16384,-512,512,16383/32

    PropPitch1=-16384,-16384,0,14720

    PropPitch2=-16384,-16384,512,16383

    Spoilers=-16380,16380/16

    Reverser1=-16384,14848

    Reverser2=-16384,14208

    Reverser3=-16384,14208

    Reverser4=-16384,14208

  18. Hi,

    I assume that you have the Aerosoft (boxed?) version. You will get the discount from them. Go to their page and look for FS Commander 9, then go to the Service Page where it is explained in detail how to proceed to get the discount.

    Note that the boxed version of 9.0 will only be available after Nov. 22

    Note also that you get the discount from SimMarket, if you previously bought from SimMarket; you get the discount from Aerosoft if you previously bought from Aerosoft. General principle: each one supports only its own customers, because only these are on record.

    Regards

    Sascha

    I purchased FSC X from PC √°viator Inc, and I cannot find FSC 9 in its store yet.- May I expect them to sell it and make the discount ?

    Thanks

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.