Jump to content
The simFlight Network Forums

guenseli

Moderators
  • Posts

    464
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by guenseli

  1. sorry, i mean to assign it via the FSUIPC dialog inside FSX. So when I press e.g. Button 5 I can assign it as switch button. Now I have to edit manually the ini (which is no problem at all) But more practical would be to get this feature without editing manually... Some kind of dialog which says: button 5 AND button 4 make this or this action Or is it already implemented and I haven't found it till now? I hope you can understand my poor english explainings ;-)
  2. Thank you for your fast reply. One question left: Couldn't it be a feature, that the user can define a switch button via the FSUIPC dialog? Just a question if it is possible for you to realize it...
  3. Thank you for answering and patience, Mr. Dowson! Now I have understood you correctly. Well explained! I haven't tried it out now, but I'm sure it will work, or course! I'd like to reassign my complete Joystick and get a little bit more organizastion into my FSUIPC.ini Can I add comments (for myself) between the lines in the ini? And can I rearrange the buttons-order? Have I to change the order-numbers or can I just move the lines were I want?
  4. Thanks for your reply... I think heres my english a little bit to bad. In short words: it is not possible to realize this switch button? Or please, if I do misunderstand you, can you code the two line here with the example of the views? "next sub view" at button 4 and "prev sub view" when I press button 5 AND button 4 Sorry for asking you again, but I really haven't you understand due to my bad english...
  5. Hello it's me again, I have a little problem. Want to assign a compound button. If I press button 4 then "next sub View" is the action. Now I want to have with button 5 AND button 4 the action "prev sub View" The same procedure I have done with the parking brake, button 5 and button 0 are parking brake. Just button 0 is "brakes". But with the combination button 5 and button 4 an combined the action isn't working. Other combinations are working as they should, e.g. Button 5 and 3 or buttons 4 and 3 But not buttons 5 and 4 I have copied here the part with the Button section. The entries are at position 59 (next sub view) and 78 (the compound which is not working. I have FSX and version 4.505. hopefully you can find a mistake...? thank you! [buttons] 1=PB,6,C66059,0 2=UB,6,C66060,0 3=PB,7,Cx06000D0C,x0008 4=UB,7,Cx0A000D0C,x0008 5=PB,8,C66056,0 6=UB,8,C66057,0 7=PB,9,Cx06000D0C,x0010 8=UB,9,Cx0A000D0C,x0010 9=PB,10,Cx06000D0C,x0002 10=UB,10,Cx0A000D0C,x0002 11=PB,11,Cx06000D0C,x0001 12=UB,11,Cx0A000D0C,x0001 14=RA,32,C65734,0 15=RA,36,C65735,0 16=RA,38,C65671,0 17=RA,34,C65672,0 18=PA,9,C66080,0 19=PA,8,C66079,0 20=PA,11,C65758,0 21=PA,10,C65759,0 22=RA,13,C66525,0 23=RA,12,C66524,0 24=RA,16,C65656,0 25=RA,17,C65655,0 26=PA,2,C65580,0 27=PA,1,C66224,0 32=RA,7,K113,8 33=RC,7,K113,8 34=PD,6,C66226,0 35=PA,3,C66506,225 36=PA,21,C66615,0 37=PA,19,C66616,0 38=PA,20,C66625,0 39=PA,22,C66626,0 41=RC,8,K114,8 42=PC,0,C66106,0 43=PC,2,C65729,0 44=PC,4,C65724,0 45=PC,1,C65799,0 46=PC,3,C66112,0 47=PC,5,C66375,0 48=PB,4,C66241,0 49=PB,5,C66293,0 50=PB,34,C66242,0 51=PB,0,C65930,0 52=PB,1,C65936,0 53=PB,2,C65942,0 54=PB,3,C65948,0 55=UB,0,C65932,0 56=UB,1,C65938,0 57=UB,2,C65944,0 58=UB,3,C65950,0 59=PA,4,C66153,0 60=PD,5,K82,11 61=PD,4,C65858,0 63=PA,6,K82,9 64=PD,2,C65894,0 65=CP(+A,24)(+A,6)A,17,C65879,0 66=RA,24,C65879,0 67=RA,26,C65880,0 68=RA,23,C65892,0 69=RA,25,C65893,0 70=PD,3,C65895,0 71=PD,7,K112,8 72=RA,0,C65588,0 ButtonRepeat=20,10 73=CP(+A,5)A,0,C65752,0 74=PA,19,C66064,0 75=UA,19,C66065,0 76=PA,14,C66064,0 77=UA,14,C66065,0 78=CP(+A,5)A,4,C66154,0 79=PA,15,C65564,0
  6. ok, thank you for your detailed response! So I will educate myself in switching OFF all lights when leaving the airplane ;-)
  7. Oh, here comes the next question: imagine I would enter a loaded flight and there are some switches ON, some OFF (because the pilot before me was careless.. :wink: ) On my hardware switch panel are all switches OFF. Now FSX (or FSUIPC) don't recognizes this situation, means the (hardware) switches are oFF while the FSX switches are ON. Is there a possibility that FSUIPC makes a query if the (hardware) switches are OFF or ON after loading the flight?
  8. BINGO!!! Man, I thoughted much more complicated as it is... I thought you were talking about Binary codes... 0011, 0100, 0101 and so on... :oops: Thank you again, Mr Dowson! Since I own FSUIPC I can solve so much "problems" or better wishes... The next "hurdle" would be a new interface next month. For birthday I get the MCP Combo from VR InSight. FSUIPC would be perfect for this, I think! If I ever come to Stoke-On-Trend I'll take a cup of tea with you or spend you a beer or what ever you prefer!
  9. WOW, thank you... I just have to ask again, because i'm too dumb to compute the bits... I managed to toggle the strobes with parameter x0010 But the rest of the light don't follow my logical thinking. I have to say, that my logic doesn't correspond with the real worl logics in the world the most of the time... Please can you give me an example for the BCN lights parameter. Maybe I manage it then to get the rest... don't tell me the rest, I'll try it myself! :wink: Just the BCN please
  10. I was afraid about it and feel a little bit guilty... Don't read in this forum after ten o'clock in the evening, make yourself a nice cup of tea and take a long sleep! FlightSim couldn't be so important that you have to sit over a "problem" all the night! :wink:
  11. Dear Mr. Dowson, I have a question aout the lights in FSX. For default there are the following lights available e.g. PANEL_LIGHTS_OFF PANEL_LIGHTS_ON PANEL_LIGHTS_SET PANEL_LIGHTS_TOGGLE same for PANEL_LIGHTS. But for the other lights (Beacon, Nav, etc) theres just the possibility to TOGGLE. Could it be realised in a way to get the other with OFF and ON, too? Backround is: if "modded" my old Logitech Extreme to a switch panel and there are the light switches. The switches are normal switches from an electro market, where you can see the switch position (don't know the english naming for this kind of switches). And its very comfortable with FSUIPC to assign LDG and PNL lights to ON and OF, that I can see the status with the switch position. With the other TOGGLE lights it isn't possible, because they can be ON, but the switch is in OFF position. Hope, you understand, what I mean... btw: How to handle PANEL_LIGHTS_SET? What have I to set here?
  12. Hello Mr Dowson, thank you very, very much! No need to apologize. You make a great work! Everything works now as it should with the new version! But one thing: Your posting times are about 1 o'clock and 4:46 am....? Do you have another timezone? If not, please care about your sleep! ;-)
  13. Hello Mr Dowson, in this seconds I send you my *.ini file - undemanded, but I hope thats ok... Would be too long to place it here. Since this evening FSUIPC forgets my Joystick every time I load a new airplane or FSX. I have several times assigned the axis again and again, but every time I start FSX new, my Axis are away. I have a Saitek X52 Pro, two(!) Saitek Throttle Quadrants and a Logitech Extrem 3D which is "modificated" as a switch panel I have deleted any entry in the controls - standard.XML regarding the joysticks. That worked perfectly the last weeks... Today I was updating to 4.436 I was flying an hour, also with different airplanes an from one moment to another my controls failed. I haven't made any changes to FSUIPC. Via System settings in Vista, everything is ok. And when I assign my Joysticks new, then they will work, too. But when I load another plane or restart FSX the Joysticks are unassigned... with the exception of the mixture lever which is one lever of the saitek throttle quadrant. I have updatet now to 4.437 but without any efford. I hope you can find sth in my *.ini file.... I'm totally scared....??? Thank you very much! Edit: all other joystick-buttons, switches, etc worj as they should. It is just with the axis Edit2: I forgot one important thing: clicking on "reload all assignment" at the axis page will let FSX crash to desktop. I have never tried this before, so I don't know if its happend before, too...
  14. Thank you Mr Dowson, I also profited from this thread very much! Thank you, thank you!
  15. Yes, a first short test shows that it is fixed! Thank you very much! Can't say how glad I'm about such precious support. Greetings from Berlin
  16. Hello again, With the CaptainSim C130 I have the problem, that the GPS isn't panel 3. So, following your advice I wanted to assign it via Panel_ID, whta worked with other addons perfect. But CS has following code: [Window16] size_mm=456,378 window_size=0.5 position=7 BACKGROUND_COLOR=0,0,0 VISIBLE=0 zorder=32 ident=GPS_PANEL gauge00=fs9gps!gps_500,0,0 You can see, that ident isnt a number, but called "GPS_PANEL" How can I assign it in this case? Thank you!
  17. Thank you very much for this! Great support!!! I will see forward whats coming next...
  18. ok, I have set you a mail with logfile and ini. Thank you very much!
  19. Hello, thanks for fast responding and patience, again. I have FSX with Acceleration Pack and latest FSUIPC Version 4.421. OS is VISTA 64 HP I try it to make it understandable: 1) I start FSX and select the PMDG 747 and start a flight and do nothing else 2) Now, when I press e.g. NUM3 there will pop up the Overheadpanel AND FMC (what I have choosen via panel-ID and assigned it to NUM3) Same if I press e.g. NUM8 it pop up Throttle AND Overhead (I have assigned Overhead via Panel_ID to NUM8) I think NUM3 Overhead and NUM8 Throttle are PMDG Standards?! 3) Then I open FSUIPC from FSX Menue and press "Reload all Keys" or "Reload all Buttons" (doesn't matter) 4) A little window opens and closes very, very fast. I can't read... 5) Now closing FSUIP dialog and now everything runs as it should: NUM3 brings up FMC only and NUM8 brings up Overhead only and so on. Aborting the flight, go to FSX main menue and load a new flight doesn't have the issue described above. Everything works normal. Quiting FSX and restart brings back the issue. I'd like to show you the logging sequence but even when I select the logging function the small, fast window comes up and everything is working as it should... Nevertheless here is the working logging: 204892 KEYDOWN: VK=99, Waiting=0, Repeat=N, Shifts=0 204908 FS Control Sent: Ctrl=66506, Param=25 204908 .. This key is programmed in FSUIPC4 'Keys' options 204939 *** EVENT: Cntrl= 66506 (0x000103ca), Param= 25 (0x00000019) PANEL_ID_TOGGLE 204939 KEYUP: VK=99, Waiting=0 204955 *** EVENT: Cntrl= 66147 (0x00010263), Param= 0 (0x00000000) VIEW_RESET 206187 KEYDOWN: VK=99, Waiting=0, Repeat=N, Shifts=0 206187 FS Control Sent: Ctrl=66506, Param=25 206187 .. This key is programmed in FSUIPC4 'Keys' options 206187 *** EVENT: Cntrl= 66506 (0x000103ca), Param= 25 (0x00000019) PANEL_ID_TOGGLE 206249 KEYUP: VK=99, Waiting=0 206249 *** EVENT: Cntrl= 66147 (0x00010263), Param= 0 (0x00000000) VIEW_RESET I hope to have my steps explained clearly enough. Now I await your advice... :wink:
  20. ok it will work so far with the direct panel_IDs But one little thing is confusing me. As I stated above i have assigned my panels to NUM keys via FSUIPC. With PMDG 747 I have assigned the PMDG panels also to the NUM keys with your hint with the Panels_ID. But this method is just working after I have pressed "button reload or Key reload" inside FSUIPC. Is that a normal behavoiur I have to do after loading an addon aircraft with a special profile? Or is there an other procedure I have to follow? I have read the hole manual, but due to language isses it could be, I haven't understood everything correctly...
  21. AAAAhhhh! Thats the key. Good idea :wink: I will try it out as soon as possible! Sounds promising! Thanks for the great support again and I will report how it works.
  22. Sorry for my late response. Yes I understand anything what you said before, please don't be angry with me :wink: I try to explain it again as I did before hopefully in a better way: 1) I have nothing changed in FSX standard assignement 2) Then I wanted to be able to assign all panels which are normally SHIFT+n to my NUM numbers. I did it via FSUIPC saying my e.g. NUM3 is panel_3 3) Then, I have some Addon Airplane which have other panel constellations, e.g. panel 3 isn't GPS as I'm used to it from FSX Standard planes. So, I have assigned for this planes "plane specific" that NUM3 is panel_n, this one which is the addons GPS 4) Now I come to my PMDG 747X where I have done much more tricks: the 747X don't have e.g. the Overhead panel assigned to a panel number, you have to programm a shortcut in PMDGs KeyConfigurator. So, for the 747 I have to assign "plane specific", that NUM8 e.g. is Ctrl+Shift+8 or whatever.... Thats why I have an keypress to be an other keypress. And I undestand, that it will be a little too much to want with one keypress that there 3 or 4 commands will be changed in one time.... Wit PDG I say it is maybe a special case. But pointing to 3) it will happen too, that I press NUM8 and will get the panel_8 but also the view direction will change to this, what is assigned in FSX Standard. It will happen not everytime and I haven't sorted it out now what is the reason for it, but maybe it will happen when frames below 15 fps. I think the FSUIPC module "translation" isn't fast enough at low frames. But I don't know, I have no clue from such things! So please be patient with me. I don't blame FSUIPC which I think is one of the greatest tools developed for FS! But I'm very curoius and manage mostly things to get on their edges :wink:
  23. Ah ok, now I understand some things better, I think "assigning NUM8 to send keypress 56+9 you are making it look as if you are pressing Shift 8" that was what I wanted to do. But I understand that could confuse FSUIPC. I have tried it because it was possible ;-) And overall it works some times - but some times not. So, when you say thats not the intention of the programm I will roll back and try another programming system Maybe a combination of programming FSX Keys and FSUIPC. But nevertheless, beside my user faults, FSUIPC is a really programm with a wide range of possibilities. Thanks for the great and fast support!
  24. wow, fast response, thank you.... so, why I'm not assigning keys in FS? Because I bought FSUIPC to initialize it one time and save it and everytim I have to reinstall FSX I have my keys saved. I know I can save my controls.xml too, but with FSUIPC I have much more options as you know. So here is a log file (I have changed my email and name for this thread) User Name="GXXXXX SXXXXX" User Addr="guenseli at XXXXX" FSUIPC4 Key is provided WIDEFS7 not user registered, or expired [Continuation log requested by user] Running inside FSX on Windows Vista (SimConnect Acc/SP2 Oct07) Module base=61000000 Wind smoothing fix is fully installed 6686718 System time = 17:14:16, FSX time = 12:33:26 (20:33Z) 6686718 LogOptions changed, now 40000000 00000001 6687311 FS Control Sent: Ctrl=65765, Param=-16384 6687311 FSUIPC Control Action: Ctrl=6, Param=16383 6688543 KEYDOWN: VK=99, Waiting=0, Repeat=N, Shifts=0 6688543 FSUIPC Control Action: Ctrl=1070, Param=2355 6688543 SendKeyToFS(00040033=[shft+3], KEYDOWN) ctr=0 6688543 Sending WM_KEYDOWN, Key=16 (Shift) (Scan code 42), Ctr=2 6688543 .. This key is programmed in FSUIPC4 'Keys' options 6688543 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1 6688543 .. Key not programmed -- passed on to FS 6688543 KEYUP: VK=16, Waiting=0 6688543 KEYUP: VK=34, Waiting=0 6688637 Sending WM_KEYDOWN, Key=51 (Scan code 4), Ctr=1 6688637 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1 6688637 .. Key not programmed -- passed on to FS 6688637 KEYDOWN: VK=51, Waiting=0, Repeat=N, Shifts=1 6688637 .. Key not programmed -- passed on to FS 6689557 SendKeyToFS(00040033=[shft+3], KEYUP) ctr=0 6689557 Sending WM_KEYUP, Key=51 (Scan code 4), Ctr=1 6689557 KEYUP: VK=51, Waiting=0 6689651 Sending WM_KEYUP, Key=16 (Shift) (Scan code 42), Ctr=1 6689651 KEYUP: VK=16, Waiting=0 6690135 KEYDOWN: VK=99, Waiting=0, Repeat=Y, Shifts=0 6690135 .. This key is programmed in FSUIPC4 'Keys' options 6690228 KEYUP: VK=99, Waiting=0 6695922 KEYDOWN: VK=104, Waiting=0, Repeat=Y, Shifts=0 6695922 .. This key is programmed in FSUIPC4 'Keys' options 6696016 KEYUP: VK=104, Waiting=0 6710836 KEYDOWN: VK=104, Waiting=0, Repeat=N, Shifts=0 6710836 FSUIPC Control Action: Ctrl=1070, Param=2360 6710836 SendKeyToFS(00040038=[shft+8], KEYDOWN) ctr=0 6710836 Sending WM_KEYDOWN, Key=16 (Shift) (Scan code 42), Ctr=2 6710836 .. This key is programmed in FSUIPC4 'Keys' options 6710851 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1 6710851 .. Key not programmed -- passed on to FS 6710945 Sending WM_KEYDOWN, Key=56 (Scan code 9), Ctr=1 6710945 KEYUP: VK=16, Waiting=0 6710945 KEYUP: VK=38, Waiting=0 6710945 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1 6710945 .. Key not programmed -- passed on to FS 6710945 KEYDOWN: VK=56, Waiting=0, Repeat=N, Shifts=1 6710945 .. Key not programmed -- passed on to FS 6711787 SendKeyToFS(00040038=[shft+8], KEYUP) ctr=0 6711787 Sending WM_KEYUP, Key=56 (Scan code 9), Ctr=1 6711787 KEYUP: VK=56, Waiting=0 6711881 Sending WM_KEYUP, Key=16 (Shift) (Scan code 42), Ctr=1 6711881 KEYUP: VK=16, Waiting=0 6720539 KEYDOWN: VK=104, Waiting=0, Repeat=Y, Shifts=0 6720539 .. This key is programmed in FSUIPC4 'Keys' options 6720648 KEYUP: VK=104, Waiting=0 6727044 KEYDOWN: VK=104, Waiting=0, Repeat=N, Shifts=0 6727044 FSUIPC Control Action: Ctrl=1070, Param=2360 6727044 SendKeyToFS(00040038=[shft+8], KEYDOWN) ctr=0 6727044 Sending WM_KEYDOWN, Key=16 (Shift) (Scan code 42), Ctr=2 6727044 .. This key is programmed in FSUIPC4 'Keys' options 6727044 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1 6727044 .. Key not programmed -- passed on to FS 6727138 Sending WM_KEYDOWN, Key=56 (Scan code 9), Ctr=1 6727138 KEYUP: VK=16, Waiting=0 6727138 KEYUP: VK=38, Waiting=0 6727138 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1 6727138 .. Key not programmed -- passed on to FS 6727138 KEYDOWN: VK=56, Waiting=0, Repeat=N, Shifts=1 6727138 .. Key not programmed -- passed on to FS 6727980 SendKeyToFS(00040038=[shft+8], KEYUP) ctr=0 6727980 Sending WM_KEYUP, Key=56 (Scan code 9), Ctr=1 6727980 KEYUP: VK=56, Waiting=0 6728074 Sending WM_KEYUP, Key=16 (Shift) (Scan code 42), Ctr=1 6728074 KEYUP: VK=16, Waiting=0 6949985 KEYDOWN: VK=104, Waiting=0, Repeat=Y, Shifts=0 6949985 .. This key is programmed in FSUIPC4 'Keys' options 6949985 KEYUP: VK=104, Waiting=0 6957567 KEYDOWN: VK=104, Waiting=0, Repeat=N, Shifts=0 6957567 FSUIPC Control Action: Ctrl=1070, Param=2360 6957567 SendKeyToFS(00040038=[shft+8], KEYDOWN) ctr=0 6957567 Sending WM_KEYDOWN, Key=16 (Shift) (Scan code 42), Ctr=2 6957567 .. This key is programmed in FSUIPC4 'Keys' options 6957567 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1 6957567 .. Key not programmed -- passed on to FS 6957661 Sending WM_KEYDOWN, Key=56 (Scan code 9), Ctr=1 6957661 KEYDOWN: VK=56, Waiting=0, Repeat=N, Shifts=1 6957661 .. Key not programmed -- passed on to FS 6957754 KEYUP: VK=16, Waiting=0 6957754 KEYUP: VK=38, Waiting=0 6958441 SendKeyToFS(00040038=[shft+8], KEYUP) ctr=0 6958441 Sending WM_KEYUP, Key=56 (Scan code 9), Ctr=1 6958441 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1 6958441 .. Key not programmed -- passed on to FS 6958441 KEYUP: VK=56, Waiting=0 6958534 Sending WM_KEYUP, Key=16 (Shift) (Scan code 42), Ctr=1 6958534 KEYUP: VK=16, Waiting=0 6959829 KEYDOWN: VK=104, Waiting=0, Repeat=Y, Shifts=0 6959829 .. This key is programmed in FSUIPC4 'Keys' options 6959907 KEYUP: VK=104, Waiting=0 6961498 KEYDOWN: VK=104, Waiting=0, Repeat=N, Shifts=0 6961514 FSUIPC Control Action: Ctrl=1070, Param=2360 6961514 SendKeyToFS(00040038=[shft+8], KEYDOWN) ctr=0 6961514 Sending WM_KEYDOWN, Key=16 (Shift) (Scan code 42), Ctr=2 6961514 .. This key is programmed in FSUIPC4 'Keys' options 6961514 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1 6961514 .. Key not programmed -- passed on to FS 6961592 Sending WM_KEYDOWN, Key=56 (Scan code 9), Ctr=1 6961592 KEYUP: VK=16, Waiting=0 6961592 KEYUP: VK=38, Waiting=0 6961607 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1 6961607 .. Key not programmed -- passed on to FS 6961607 KEYDOWN: VK=56, Waiting=0, Repeat=N, Shifts=1 6961607 .. Key not programmed -- passed on to FS 6962341 SendKeyToFS(00040038=[shft+8], KEYUP) ctr=0 6962341 Sending WM_KEYUP, Key=56 (Scan code 9), Ctr=1 6962356 KEYUP: VK=56, Waiting=0 6962434 Sending WM_KEYUP, Key=16 (Shift) (Scan code 42), Ctr=1 6962434 KEYUP: VK=16, Waiting=0 7015724 Sim stopped: average frame rate for last 328 secs = 11.9 fps [Log closed by user request, and continued in new file] 7027939 System time = 17:19:58, FSX time = 12:38:55 (20:38Z) 7027939 *** FSUIPC log file being closed Average frame rate for running time of 3384 secs = 14.9 fps Memory managed: 1537 Allocs, 1533 Freed ********* FSUIPC Log file closed *********** I have just pressed NUM8 Num 8 is panel_8 normally. For the PMDG 747 I have changed it Aircraft specific to bring up EICAS panel via a FSUIPC generated shortcut. What happend was , that view changed and EICAS showed up not reliable What I have done in FSUIPC is changed the key NUM8 to Keypress&release with Parameter 56+9 and no repeat. Maybe you can read out sth...
×
×
  • 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.