Jump to content
The simFlight Network Forums

soldano

Members
  • Content Count

    85
  • Joined

  • Last visited

Community Reputation

0 Neutral

About soldano

  • Rank
    Advanced Member
  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 am using both a VR Insight M Panel and a Saitek Pro Flight Switch panel, and both word OK.- Regards Jorge
  5. 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
  6. If you referr to your post #23, yes, you did it indeed, but lately today, and after maltreating me in you former mails.- And by the way, the "corrected" lines at that post, work only partially as the movements doesnt match.-
  7. 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
  8. 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
  9. 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
  10. 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
  11. Thanks Andydigital I wait for Pete response.- Regards Jorge
  12. 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
  13. 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
  14. 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
×
×
  • 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.