Pieter

PETE, totally right I just missed the upper limit ... my mistake ...think I was to hasty to get it working BUT its all working fine now .... I used 12 because on the original setting FSX doesn't really inc it by full digits THANK YOU SOOOOOO MUCH for your time, fast replies and fixing my problem.... you can put a big SOLVED next to the topic :))) Pieter

Pete, lifesaver I should say :))) WE ALMOST THERE 1st programmed the buttons with "Offset word set" QNH(x552E) and DH(x5532) to STD(16211) ........ WORKING ,when pushing the button QNH goes to 1013 then "Offset Uword increment" for QNH inc with offset x552E and parameter 12/0 ....NOT WORKING ,when turning the knob it jumps to 1014 and stays there "Offset Uword decrement" for QNH dec with offset x552E and parameter 12/0 .......WORKING, when turning know QNH dec by 1 so 1013,1012,1011...etc I swapped efis panels because I thought might maybe be the rotary knob faulty but on both panels it does the same :( ANY SUGGESTIONS ? Goflight not supports much I must say ,...as like you said its actually PM or whatever software you use ...nothing to do with them

Hey Pete, all off the above I already knew ...just didn't need to tell you as I think we both know what we talking about the only thing I'm asking is for lines to make the F/O side to do what I want.... as you said c65883 and 4 are controls for CAPT side QNH (I did found it in your docs in FSUIPC list) ...AND I did look at the project magenta offset page just its all confusing ... IF for the capt side the efis uses standard FS controls ...then I don't think I can set the F/O side as there isn't any control for that? the only 2 offsets I found on PM list are 552E = Copilot QNH (same format as FS 0x330, active is non-zero) 5532 Co-pilot decision height (10s Feet, 200FT=20, 1050Ft=105, neg value is MDA)(Read/Write) (!) 552E has to be set for this to work so how would I translate this now in a usable offset int he FSUIPC.ini greets, Pieter

Pete, just changed all the offsets.... by adding +100 on the parameter ... all buttons are working EXCEPT : DH F/O side inc , dec AND reset to 200ft QNH F/O side inc , dec AND reset to 1013 on the CAPT offsets its 130=P170,28,c65883,0 131=P170.29,c65884,0 132=P170,30,c2065,0 133=P170,31,c2064,0 do you know these offsets commands + parameters for F/O side???? I cant seem to find then anywhere (while I clearly found that 2065 and 2064 are PM PFD decision ht inc dec, so I guess that 65883 and 65884 are QNH) but that's all the info I can find...I cant find anything on F/O side control and also the pushbuttons to reset the DH to 200ft and QNH to 1013 I can t seem to find for F/O side where the capt side offset is 117=P170,14,cx010004FA,x14 118=P170,15,c66040,16211 thank you for your help Pieter

hey pete, well I found it in a conversation between you and Cbaye. "revisiting Goflight EFIS support" the offsets I just had to copy past into the FSUIPC.ini file. I attached the file in text regarding the 171= 170+100 ...its not what I meant in the PM offset folder it says that you have to ADD +100 to the parameter for the F/O side E.g. 104=P170,4,c2999,93 CAPT SIDE making it 104=P170,4,c2999,193 F/O side (does that seem correct???) however then I don't know how you would change the 117=P170,14,cx010004FA,x14 AND 118=P170,15,c66040,16211 those 2 are indeed related to DH (117) and Altimeter (118) pushbuttons to reset DH to 200FT and QNH to 1013 EFIS offset.txt

Hey Pete, sorry to ask but I'm really little bit struggling here I just bought a second go flight efis control panel for F/O side ...using Project magenta Now the CAPT side I conf with the offset file you posted, now do you have a offset file for the other side???? I did read somewhere that you just put 100+ for the parameters ...and obviously change the panel number (e.g. 170 = capt side , 171 F/O side) is that correct??? AND in saying that what about these two lines then: 117=P170,14,cx010004FA,x14 118=P170,15,c66040,16211 Sorry I think this question prob already asked before but I couldn't find it on the forum Greets, Pieter

its working OMG pete you the man thank you soooooooo much

i used same cabin alert sound and it works also

tought you could save the picture and zoom in.... the log says ....waiting for event....i took off and climed to 12000FT ,without result 117203 System time = 10/11/2012 17:04:49, Simulator time = 02:03:05 (01:03Z) 117203 LogOptions changed, now 80000000 00000001 174658 Sim stopped: average frame rate for last 48 secs = 13.0 fps 216326 LUA.0: Offset Change event: calling "check10000" in "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\alert10000.lua" 216326 LUA.0: Waiting for an event in "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\alert10000.lua" 234766 LUA.0: Offset Change event: calling "check10000" in "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\alert10000.lua" . . . . . 383747 LUA.0: Waiting for an event in "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\alert10000.lua" 383840 LUA.0: Offset Change event: calling "check10000" in "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\alert10000.lua" 383840 Sim stopped: average frame rate for last 55 secs = 9.4 fps 383840 LUA.0: Waiting for an event in "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\alert10000.lua" [Log closed by user request, and continued in new file] 404370 System time = 10/11/2012 17:09:36, Simulator time = 02:06:47 (01:06Z) 404370 *** FSUIPC log file being closed Average frame rate for running time of 231 secs = 11.6 fps G3D fix: Passes 19719, Null pointers 0, Bad pointers 0, Separate instances 0 Memory managed: 59 Allocs, 56 Freed ********* FSUIPC Log file closed *********** my lua file is: prevalt = -1 mark = 10000 function check10000(off, val) if (val >= mark) and (prevalt < mark) then sound.play("10000FTalert.wav") elseif (val <= mark) and (prevalt > mark) then sound.play("10000FTalert.wav") end prevalt = val end event.offset(0x3324, "SD", "check10000")

just tested it Pete didn't work i did everythng according you said ... made a .lua file ...saved it in modules folder ...entered he lines into .ini folder and the .wav file in fsx sound folder i atached a picture any idea?

okay Pete sorry for the confusion...i'm testing it now will let you know thank you so much in advance

so basically this is it prevalt = -1 mark = 10000 / 3.28084 --10000 feet in metres function check10000(off, val) if (val >= mark) and (prevalt < mark) then sound.play("10000FTalert") elseif (val <= mark) and (prevalt > mark) then sound.play("10000FTalert") end prevalt = val end event.offset(0x0574, "SD", "check10000") SAVE IT AS LUA file in MODULES ...then just add into FSUIPC.ini [Auto] 1=Lua alter10000 and i'm good to go?

the other "problem" is: FSUIPC ELIMINATOR has stopped working and Wideclient needs to shut down? ======> this occurs when i plug in an external hard drive, use it and then plug it out ALL when Wideclient is running. Not that its major problem...but just find it strange that it does that

hey Pete, thanks for the QUICK response again... so if i'm getting you right ... i name the .wav file "10000FTalert.wav" AND enter this file into the FSX sound folder.....next i copy past (in notepad): prevalt = -1 mark = 10000 / 3.28084 --10000 feet in metres function check10000(off, val) if (val >= mark) and (prevalt < mark) then sound.play("10000FTalert.wav") elseif (val <= mark) and (prevalt > mark) then sound.play("10000FTalert.wav") end prevalt = val end event.offset(0x0574, "SD", "check10000") AND SAVE this as .lua into FS Modules folder AND just add into FSUIPC4.ini folder [Auto] 1=Lua alert10000 ===================> should it not be 1=Lua alert10000 ???? YES of course ... typo! THAT SHOULD BE IT??? yes indeed want 10000FT altimeter reading .... it can be just on 10000FT doesn't need to be that exact So am i right in doing all this? In FSX should i activate something? AND see in the text file were it said "fill in name of sound file" do i have to use the extension? greets, Pieter regarding other problem i wil get back to you about that

just want to add one more thing, regarding a problem i said occurred with wideFS... if i'm running wideFS on client pc, and i plug in and after use out a external HDD ...the wideFS fails strange hey :)