guenseli Posted January 17, 2009 Report Share Posted January 17, 2009 Hello, I hope I can explain my problem with FSUIPC and FSX clearly enough.... I have managed to assign the numpad keys in a way that they are linked to the panels... e.g. NUM1 shows panel1, NUM2 shows panel2.... no big thing so far. Normally the NUM keys linked to some view actions. So my problem is, that sometimes when I press a NUM Key the panel AND the standardview set shows up. Of course I don't want it to do that. I switch then some times to FSUIPC window, check the settings, can't find sth wrong, switch back and after some times the issue is gone. I know that a solution could be to delete the standard FSX kexs, but this issue above is just an example. I have this failure also with other key settings. Is it a kind of failed initialisation of FSUIPC? What could I do? btw I'm running Vista64 and FSX Acceleration! Link to comment Share on other sites More sharing options...
Pete Dowson Posted January 17, 2009 Report Share Posted January 17, 2009 I hope I can explain my problem with FSUIPC and FSX clearly enough.... I have managed to assign the numpad keys in a way that they are linked to the panels... e.g. NUM1 shows panel1, NUM2 shows panel2.... no big thing so far. Why are you using FSUIPC for such keypresses? FSX itself can surely handle such things. What FS controls are you assigning? So my problem is, that sometimes when I press a NUM Key the panel AND the standardview set shows up. Of course I don't want it to do that. I switch then some times to FSUIPC window, check the settings, can't find sth wrong, switch back and after some times the issue is gone. Are you sure NUM lock isn't getting changed? Those keys are different depending on the numlock setting. I know that a solution could be to delete the standard FSX kexs, but this issue above is just an example. For keypresses, if FSUIPC intercepts them FS doesn't see them, so unassigning keys in FS is irrelevant. They aren't like buttons. I have this failure also with other key settings. Such as? I think you need to be more specific, show me the [Keys] sections of your FSUIPC4.INI file. Also try Button/Key logging (FSUIPC Logging tab) and check the logging for yourself to see what is happening. Is it a kind of failed initialisation of FSUIPC? No, not any problem I know of. Are you perhaps assigning keys to be aircraft specific then changing aircraft? BTW please always make sure you are using the latest version, just in case things have changed. Latest is 4.418 (in updates above), with 4.419 due later today. Regards Pete Link to comment Share on other sites More sharing options...
guenseli Posted January 17, 2009 Author Report Share Posted January 17, 2009 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... Link to comment Share on other sites More sharing options...
Pete Dowson Posted January 17, 2009 Report Share Posted January 17, 2009 So here is a log file (I have changed my email and name for this thread) ... I have just pressed NUM8 Erthe log shows lots and lots of keypresses. Do you expect me to understand what you've done from just the one line "I have just pressed NUM8"? It does not relate. Please, from the moment you start logging till you stop, list every single keypress. What I have done in FSUIPC is changed the key NUM8 to Keypress&release with Parameter 56+9 and no repeat. Erwhat? OUCH! I think you'd better show my the Keys sections, as I asked. Or delete it all and start again. By assigning NUM8 to send keypress 56+9 you are making it look as if you are pressing Shift 8. Why? It makes no sense to use FSUIPC to convert one keypress into another. I've no idea what that would make happen, but it won't be nice -- the whole sequencing will get totally confused with keypresses and releases from you getting entwined with those from FSUIPC. The control facility to send keypresses which you are misusing was to allow Buttons to be used to send keypresses to those Add-Ons which do not recognise controls. FS itself actually recognises FS controls! Wonderful, no? USE THEM please. Never ever program FSUIPC to send keystrokes when there are perfectly good controls to be used. All that happens is that FS will look up the keystroke and convert it to a control which you could have used in the first place! Don't you see that? To find out what controls to use, if you don't know which ones, enable Event logging in FSUIPC, operate FS in the way which uses the control you want, then look it up in the Log. The name in the log is the one you'd use in the Assignments drop-down. For the panel selections the controls are (obscurely?) named "PANEL n" where "n" is the number -- so Panel 8 for your 8. Try it and see! There's also a list of all FSX controls installed in your FSX Modules folder, sorted numerically and alphabetically, so for the less obscurely named ones you should find them quite easily. Oh, incidentally, in FSX windowed more you can enable a console window for FSUIPC's logging and see the results of your actions in real time, on screen. There's a checkbox for this option in the Logging options tab. Regards Pete Link to comment Share on other sites More sharing options...
guenseli Posted January 17, 2009 Author Report Share Posted January 17, 2009 Ah ok, now I understand some things better, I think By assigning NUM8 to send keypress 56+9 you are making it look as if you are pressing Shift 8. Why? It makes no sense to use FSUIPC to convert one keypress into another. I've no idea what that would make happen, but it won't be nice -- the whole sequencing will get totally confused with keypresses and releases from you getting entwined with those from FSUIPC. "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! Link to comment Share on other sites More sharing options...
Pete Dowson Posted January 17, 2009 Report Share Posted January 17, 2009 "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. It's not specifically FSUIPC which is confused, it's the whole keyboard messaging system. When you press a key messages are send. FSUIPC translates those into "pretend" keypresses, so more messages get sent. FSUIPC and FS are looking for these messages and trying to deal with them. You are effectively setting up a little loop. The start of the converted sequence (DOWN DOWN UP UP) overlaps with the DOWN and UP of your "real" keypress. You can see what a mess that can create. So, when you say thats not the intention of the programm I will roll back and try another programming systemMaybe a combination of programming FSX Keys and FSUIPC. No!Why?You are making it complicated when it is so so simple!!! Simply assign your keys directly, in FSUIPC, to the controls you want FS to obey. What on Earth is the point in programming a key to press a key to translate into a control? Don't you see that is daft? For example, assign your NUM8 key to the Panel 8 control, instead of to the FSUIPC "press and release key" control, and it will be fine. They are both in the same dropdown list in FSUIPC, so what is the problem? You don't have to look far!! You'll be assigning keys in FSUIPC just like FS itself assigns them. What is really the problem here? Didn't you understand anything I said before? Please explain why you are ignoring my suggestions. Why do you only want a complicated solution rather than the obvious simple one? :( :( :( :?: Regards Pete Link to comment Share on other sites More sharing options...
guenseli Posted January 19, 2009 Author Report Share Posted January 19, 2009 What is really the problem here? Didn't you understand anything I said before? Please explain why you are ignoring my suggestions. Why do you only want a complicated solution rather than the obvious simple one? Sorry for my late response. Yes I understand anything what you said before, please don't be angry with me :wink: What on Earth is the point in programming a key to press a key to translate into a control? Don't you see that is daft? 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: Link to comment Share on other sites More sharing options...
Pete Dowson Posted January 19, 2009 Report Share Posted January 19, 2009 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 Yes, so you do NOT assign NUM3 to the Shift+3 keypress & release, as you said, but direct to the Panel_3 control! 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 Fine, same thing. 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. No, no. For panels with non-standard (i.e. not FS pre-programmed) control, like Panel_1 to Panel_9, you need to use the general ID panel selector controls. There are three in the assignments list: Panel id close Panel id open Panel id toggle You probably want the toggle. You assign this, and set the parameter value to the ID of the panel you need to toggle. You can find the panel ID in the PANEL.CFG file for the aircraft. For example, in the PMDG 747X, you'll find this for the overhead: [Window02] // PMDG_OVERHEAD_PANEL //file=747400_Overhead_Background_1600.bmp //file_1024=747400_Overhead_Background_1600.bmp size_mm=1600,1200 position=4 visible=0 ident=24 zorder=2 window_size= 1.000, 1.000 window_pos= 0.000, 0.000 so you use parameter 24. 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! No, it is nothing whatsoever to do with speed. It is a tangle of mesages confusing the KEYDOWNs and KEYUPs arising from real keypresses and "pretend" keypresses all overlapping. There is no way possible to overcome that. Just NEVER assign a keypress to a keypress. It makes no sense and will not work. Regards Pete Link to comment Share on other sites More sharing options...
guenseli Posted January 19, 2009 Author Report Share Posted January 19, 2009 For panels with non-standard (i.e. not FS pre-programmed) control, like Panel_1 to Panel_9, you need to use the general ID panel selector controls. 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. Link to comment Share on other sites More sharing options...
guenseli Posted January 20, 2009 Author Report Share Posted January 20, 2009 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... Link to comment Share on other sites More sharing options...
Pete Dowson Posted January 20, 2009 Report Share Posted January 20, 2009 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. Er, yes, of course, if you edit the INI file you need to use Reload to get FSUIPC to scan the changes. It saves having to close FS and restart it. Is that a normal behavoiur I have to do after loading an addon aircraft with a special profile? Are you using Profiles? What version of FS? What version of FSUIPC, please? I have read the hole manual, but due to language isses it could be, I haven't understood everything correctly... In this case I'm afraid it is I, not understanding you. What exactly is the problem? Can you spell it out, please, step by step. All you've said so far seems to be that after making changes directly to the INI file you need to tell FSUIPC to reload them. There's nothing special or different about the "Panel" controls. As far as FSUIPC is concerned they are indistingishable from any other FS control - they are merely posted off to FS to be executed. Note that if you are using profiles there are some fixes in the latest update, 4.421. Regards Pete Link to comment Share on other sites More sharing options...
guenseli Posted January 20, 2009 Author Report Share Posted January 20, 2009 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: Link to comment Share on other sites More sharing options...
Pete Dowson Posted January 20, 2009 Report Share Posted January 20, 2009 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) How strange. I'll need to see the FSUIPC logging for that, with button & keys logging enabled. It certainly sounds like you have the same key programmed twice, or even once by still for keyboard. Maybe you should also post the all the [Keys...] sections from your FSUIPC4.INI file. Then I can see what you have done. I think NUM3 Overhead and NUM8 Throttle are PMDG Standards?! No idea. I wouldn't have thought so -- they are used for two functions by FS itself, depending on NUMlock (views and flight controls). I think you still have the olde key-ress assignments in your configuration, you've not deleted them, only added more, so things are getting into a mess. 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... It just says please wait whilst settings are being loaded. I added that because some folks have large complex sets of settings and, what with the Profile lookups and JoyName matchings, it is starting to take enough time that it can look stuck. All that using the reload buttons does is repeat what FSUIPC would have done when first loaded. Certainly, it wil revise profile listings, so if there's something tangled up in your INI file it could get into a mess still. Maybe you sohlud actually ZIP your FSUIPC4.INI file and send it to me at petedowson@btconnect.com. It sounds like you've got into a bit of a mess. 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... Logging options "stick", so if you enabled the Button and Key logging and closed FSX down, the logging would stil be there next time. Regards Pete Link to comment Share on other sites More sharing options...
guenseli Posted January 20, 2009 Author Report Share Posted January 20, 2009 ok, I have set you a mail with logfile and ini. Thank you very much! Link to comment Share on other sites More sharing options...
Pete Dowson Posted January 20, 2009 Report Share Posted January 20, 2009 ok, I have set you a mail with logfile and ini. Thanks. I see you are using Aircraft specific settings, not "Profiles". It looks like FSUIPC is not, initially at least, overriding the generic key assignments (in [Keys]) for those keypresses which have aircraft-specific settings. The double assignments I see (there may be more) between the [Keys] section and the [Keys.PMDG747-400] section, occur for these Keypresses: 72,11 90,11 97,8 98,8 99,8 100,8 101,8 102,8 103,8 104,8 105,8 189,10 I suspect it is these double assignments giving you the problems you describe -- looking at them some do seem to be combinations like, for example, 97,8 operating both PANEL 1 and Panel ID toggle 30. I'll look at this and fix it as soon as I can -- it must be related to the changes I've added recently, maybe those for Profiles. I'll check those too. Strange how it corrects itself on reload -- there's obviously some parameter or flag I'm not initialising properly on first load. I don't know how long it'll take me to fix this, maybe a day or two. If you are mostly using only the PMDG747 then you could continue okay by temporarily disabling the [Keys] section (e.g. by renaming it [xKeys]). Regards Pete Link to comment Share on other sites More sharing options...
guenseli Posted January 20, 2009 Author Report Share Posted January 20, 2009 Thank you very much for this! Great support!!! I will see forward whats coming next... Link to comment Share on other sites More sharing options...
Pete Dowson Posted January 21, 2009 Report Share Posted January 21, 2009 I will see forward whats coming next... I am pretty sure the issue is fixed in FSUIPC 3.864 and FSUIPC 4.424, both now available in the Updates announcement above. Regards Pete Link to comment Share on other sites More sharing options...
guenseli Posted January 21, 2009 Author Report Share Posted January 21, 2009 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 Link to comment Share on other sites More sharing options...
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