KAPTEJNLN

well i found a problem when you use the 2 planes that it came whit. and the livery you can download the main problem is they changsed the names in the liverys you download seperately and thats why it might not work. to solve it just rename the file for buttons [buttons.PMDG Jetstream 41 House Livery] to [buttons.PMDG J] and the file that should run the display + led to: [auto.PMDG J] 1=LUA J41-displays 2=LUA J41-LED I have updated the data above, sorry guys i just dident se it before the re-install. and to show what cause it i had a look in the aircraft.cfg file and watch here: title=PMDG Jetstream 41 Flight Test title=PMDG J41 - British Regional Denmark you see why it stoped working? because we use the first part PMDG Jetstream 41 then the othere would work as it is named different PMDG J41 there fore i renamed it PMDG J as that part is in both. as it should only run when we use the J41. sorry one again.

[buttons.Captain Sim 757-200] 0=P158,14,CL92:R,0 1=U158,14,CL91:R,0 2=P158,4,CL89:R,0 4=P158,15,CL37:R,0 13=P158,16,CL49:R,0 15=P158,17,CL43:R,0 16=P158,18,CL44:R,0 17=P158,12,CL45:R,0 18=P158,19,CL39:R,0 19=P158,7,CL48:R,0 20=P158,1,CL47:R,0 21=P158,0,CL51:R,0 22=P158,20,CL38:R,0 23=P158,21,CL52:R,0 24=P158,2,CL41:R,0 25=P158,3,CL42:R,0 26=P158,9,CL40:R,0 27=P157,2,CL59:R,0 28=U157,2,CL59:R,0 29=P158,23,CL92:R,0 30=U158,23,CL91:R,0 31=P158,22,CL53:R,0 32=U158,22,CL54:R,0 33=P157,10,CL88:R,0 34=P157,9,CL87:R,0 35=U157,9,CL87:R,0 36=U157,10,CL88:R,0 37=P157,11,CL86:R,0 38=U157,11,CL86:R,0 39=P157,8,CL85:R,0 40=U157,8,CL85:R,0 49=P157,1,CL60:R,0 50=U157,1,CL60:R,0 51=P157,3,CL61:R,0 52=U157,3,CL61:R,0 53=P157,0,CL62:R,0 54=U157,0,CL62:R,0 55=P157,21,CL64:R,0 56=P157,22,CL63:R,0 57=U157,21,CL64:R,0 58=U157,22,CL63:R,0 59=P157,23,CL65:R,0 60=U157,23,CL65:R,0 61=P157,20,CL66:R,0 62=U157,20,CL66:R,0 63=P157,14,CL67:R,0 65=P157,13,CL68:R,0 67=U157,14,CL67:R,0 68=U157,13,CL68:R,0 69=P157,15,CL69:R,0 70=U157,15,CL69:R,0 71=P157,12,CL70:R,0 72=U157,12,CL70:R,0 73=U158,1,CL47:R,0 74=U158,4,CL90:R,0 75=P157,6,CL73:R,0 76=U157,6,CL73:R,0 77=P157,5,CL74:R,0 78=U157,5,CL74:R,0 79=P157,7,CL71:R,0 80=U157,7,CL71:R,0 81=P157,4,CL72:R,0 82=U157,4,CL72:R,0 83=P157,18,CL77:R,0 84=U157,18,CL77:R,0 85=P157,19,CL75:R,0 86=U157,19,CL75:R,0 87=P157,17,CL78:R,0 88=U157,17,CL78:R,0 89=P157,16,CL76:R,0 90=U157,16,CL76:R,0 91=P158,6,CL79:R,0 92=P158,11,CL50:R,0 93=P158,8,CL80:R,0 95=P158,5,CL46:R,0 96=P174,0,CL97:R,0 98=P174,1,CM12:2,0 99=U174,1,CM12:2,0 100=P174,2,CM12:3,0 101=U174,2,CM12:3,0 [buttons.Captain Sim 757-300] 0=P158,14,CL92:R,0 1=U158,14,CL91:R,0 2=P158,4,CL89:R,0 4=P158,15,CL37:R,0 13=P158,16,CL49:R,0 15=P158,17,CL43:R,0 16=P158,18,CL44:R,0 17=P158,12,CL45:R,0 18=P158,19,CL39:R,0 19=P158,7,CL48:R,0 20=P158,1,CL47:R,0 21=P158,0,CL51:R,0 22=P158,20,CL38:R,0 23=P158,21,CL52:R,0 24=P158,2,CL41:R,0 25=P158,3,CL42:R,0 26=P158,9,CL40:R,0 27=P157,2,CL59:R,0 28=U157,2,CL59:R,0 29=P158,23,CL92:R,0 30=U158,23,CL91:R,0 31=P158,22,CL53:R,0 32=U158,22,CL54:R,0 33=P157,10,CL88:R,0 34=P157,9,CL87:R,0 35=U157,9,CL87:R,0 36=U157,10,CL88:R,0 37=P157,11,CL86:R,0 38=U157,11,CL86:R,0 39=P157,8,CL85:R,0 40=U157,8,CL85:R,0 49=P157,1,CL60:R,0 50=U157,1,CL60:R,0 51=P157,3,CL61:R,0 52=U157,3,CL61:R,0 53=P157,0,CL62:R,0 54=U157,0,CL62:R,0 55=P157,21,CL64:R,0 56=P157,22,CL63:R,0 57=U157,21,CL64:R,0 58=U157,22,CL63:R,0 59=P157,23,CL65:R,0 60=U157,23,CL65:R,0 61=P157,20,CL66:R,0 62=U157,20,CL66:R,0 63=P157,14,CL67:R,0 65=P157,13,CL68:R,0 67=U157,14,CL67:R,0 68=U157,13,CL68:R,0 69=P157,15,CL69:R,0 70=U157,15,CL69:R,0 71=P157,12,CL70:R,0 72=U157,12,CL70:R,0 73=U158,1,CL47:R,0 74=U158,4,CL90:R,0 75=P157,6,CL73:R,0 76=U157,6,CL73:R,0 77=P157,5,CL74:R,0 78=U157,5,CL74:R,0 79=P157,7,CL71:R,0 80=U157,7,CL71:R,0 81=P157,4,CL72:R,0 82=U157,4,CL72:R,0 83=P157,18,CL77:R,0 84=U157,18,CL77:R,0 85=P157,19,CL75:R,0 86=U157,19,CL75:R,0 87=P157,17,CL78:R,0 88=U157,17,CL78:R,0 89=P157,16,CL76:R,0 90=U157,16,CL76:R,0 91=P158,6,CL79:R,0 92=P158,11,CL50:R,0 93=P158,8,CL80:R,0 95=P158,5,CL46:R,0 well im not sure if it would work but here they are.

You say assigned some buttons for MCP device? whit lua fiels or only the fsuipc and the 737 ? (just tested whit the latest version of fsuipc and 737 fix and on the short test it worked whit out CTD) and have you checked that autosave is off as that could give you problems

Yes then you need the gf driver and should not shut it down. what fiels? the gf config file could be open whit a text editor like Notepad the same for the FSUIPC4.ini, as the rest of the fiels should just be inserted whit out any editing.

about how to shut down the GF driver if you ONLY use the MCP-PRO. You only have to look for the plane whit the green icon in the right corner when FSX is started. then click on it and say exit then it is shut down.. and the displays would show nothing after you shut the driver down until you load the 757 then fsuipc reads the lua file and the displays would show the same as in the plane.

..

find: Kollsman inc/dec in the fsuipc drop down menu

ok dam then it would work as fix for iFly. but as fix for VS and altitude bug for the latest 2 gf drivers. Thanks Pete, then i just have to wait for the pmdg 737....

ok i used your EX. from another post to identify whitch 1 there is active like this: but i found that L:IAS Mach Pressed is used, the log shows L:IAS Mach Pressed=1 then L:IAS Mach Pressed=0 so it seems i cant use that as for some reason it just changes to 1 then back to 0. so i think a offset would be req to work. then i had some looks on other forums about the sel button and seems hard to define. then i had a look in the fusipc.log for what it could be it use of the default names but nothing in the log.. then i look at the offsets from the sdk dokument but no sel button or something like that. then i think what can it then bee i should look for? as the lvar here is to no use. DES = ipc.readLvar("L:IAS Mach Pressed") if (DES ~= prevDES) then prevDES = DES prevspeed = -1 prevMach = -1 end if DES == 1 then Mach = math.floor( (ipc.readUD(0X07E8) / 655.36) + 0.5) if (Mach ~= prevMach) then stringMach = string.format("%01.2f", Mach/100) gfd.setDisplay(GFMCPPRO,0,1,stringMach) prevMach = Mach end else SPD = ipc.readUD(0X07E2) if (SPD ~= prevSPD) then stringSPD = string.format("%03d", SPD) gfd.setDisplay(GFMCPPRO,0,1,stringSPD) prevSPD = SPD end end

pete i dont know i tryeid whit that today whit out luck but i think what i missed was 655.36 as i used it as in the manual 65536. but found 655.36 in the ex of vrinsight mach. mabee thats why i could get it work, i just feel so stupid tryeid different of your ex and whit out luck and in the end i was close earlyer today.

Here is the code i was refering to (this works but whit out("%01.2f", Mach) as i tryeid your other option to test if i did it right) but miss the 0.00 as now it is shown whit out the . Mach = math.floor( (ipc.readUD(0X07E8) / 655.36) + 0.5) if (Mach ~= prevMach) then stringMach = string.format("%03d", Mach) gfd.setDisplay(GFMCPPRO,0,1,stringMach) prevMach = Mach end It have some looks at the explanation you gave the other day and tryeid to edit the part f but i dont know to what i understand that that 2 is = 2 signs but is there any difference whit this when i use it whit offsets for the mach any changes there should be made in order to work: ("%01.2f", Mach)?

the reason i ask was this part of a post you gave: f says the number is in floating point form (all numbers in Lua are floating point, but can be uses as integers too, losing the fraction). But what for the offset ?

ups sorry delt

well should it also look like this for a display when using the offset: stringMach = string.format("%01.2f", Mach) becaus when i try use it it dosent work whit destimals after the dot (.00) as 1.00 is shown and 2.00 when it is displayed in the plane but the 00 dosent move so i was thinking if it should be becaus F should be replaced? as logicaly when the code look like: "%01.2f" i would mean that since the first part works it might be right so far: %01. but some thing in the last part needs to be changesed

well what i ment whit iFly 737 was i could use the codes from yesterday, to replace the interface from gfdriver as there is some lag which is a down side, could be seen here in the end of the film, then i think you know what i mean(i fly option was set to CRS2 so thats the lag when you normaly select ifly in the dropdown menu of goflight software): As the default variables works but whit the version 2.01 and 2.02 they made a error to the altitude and vertical speed. so i could tweak the goflight cfg file to use a mix of default and ifly commands. so this file from yesterday fix that, i just fogot the mach but would try get that working as then i know some people there would be happy :wink:

sorry pete i take all your time, i know im not the best guy for this, i realy try to understand and yes in the end you have the magic word. i just realy try to find out of the things so you dont need to help and i realy hope that whit the 737 NGX i can manege to do it by my own. the plane i did the past here was some experimental ones where i released the captainsim and pmdg j41 not for my own joy as i dont fly captainsim anymore but realy wanted to give other people the option, as i know how it was for my self some years ago. having hardware but could use it for more then the default plane and level-d. so it might be it for now, but 1 very nice thing by the codes here made it posible for me to create the display for all the displays for the default plane which i am sure could be used or should i say i know it works whit the iFly whitch is realy nice as that is a plane i fly until the pmdg 737 NGX. but due to the bug in the gf software the ifly 737 dosent work that good. now whit the displays here i can get rid of that bug whit lag on the displays, as i already tested it so might upload when done whit the files. so Pete your work is more then appreciated. and that´s also why i want to stop now whit the A300 as i realy want the abilety to ask you when the NGX gets out as that have my bigest priority, if we are gone be able to do some files for it. and yes i know there would be an sdk but i realy wants it to work throu your program as there is no lag as whit the gf driver together wit level D and ifly so far. so i dont hope you think your time have been waisted i just want to keep an helping hand when it is realy neaded. so another sorry pete for my low level of knolege.

my fault it was for the display and by using the button inside the vc it show at the display the right ft when it is above -. so +100 +200 and so on works but when it should show VS as -100 it show 65436 on the goflight device it show it right inside the plane but not on my gf device when it is below 0000ft i have also tryeid whit math.floor( (ipc.readUD(0X07F2) * 3.28084 / 65536) + 0.5) but dident work as i saw that in anothere ex so i use the 3.28084

ok i testet this in the default plane to see if it was becaus off the add-on but the same happend to the default plane by using vertical speed: 07F2 Autopilot vertical speed value, as ft/min it works as long as it is + but when it gets - it jumps to some thing diferent. -100 was shown on the Goflight mcp-pro as 65436 im just woundering why, should i make a calculation when it gets into - ?

You was faster then mee to type i just found by try 3.3 and it worked as i was tryeing to find the caculation so now i think i start to get the way it works as you say the meters from the offset code then you multiply to get it to feets thats logic yes. sorry my slow understanding

so for the Altitude there is noted Autopilot altitude value, as metres*65536 so now the reading is in meters as the reading was 3048 which is 3000 ft so by reversing the code it should give feet. Then it shiuld be reverse by say devide insted of multiply as the line say above: math.floor( (ipc.readUD(0X07D4) / 65536) ) but i might still miss some thing as it dosent show it right yet i also try as you say for the other by ad 0.5: math.floor( (ipc.readUD(0X07D4) / 65536) + 0.5) and about: Where are you looking? The INC and DEC controls are listed in the List of Controls installed in your FSUIPC Documents folder. They appear in the Buttons and Keys assignments dropdowns. You can send them from a Lua program by using the ipc.control function, with the control number as listed in the List of controls document. i have tryeid to assigne a button to the increase by selecting from drop down menu but nothing happens when i do so, or it would say it seems to changes on my mcp pro the first time you try after i hve assigned the button but becaus it dosent update in the plane it jumps back right after (in a split sec nerly not viseble to se the changes on the goflight mcp-pro so....

about: The controls for AP speed can be found by clicking the airspeed up and down on the autopilot speed adjust knob whilst logging Events. I think you'll find they are named AP SPD VAR INC and AP SPD VAR DEC. I have been throu that but it dosent include or any othere: AP SPD VAR INC or AP SPD VAR DEC as then it was easy but they are not there as i can see only: AP SPD VAR SET is there. no other for speed or something close to that About: Why on Earth do you want to do such computations? It says it's in knots! What sort of speed value do you want, kilometers per hour? What's wrong with knots, that's what pilots use after all! Why not just accept it? well no problem at spd display i was talking of heading. altitude also dont show right. as lets say heading in the plane shows 130 but on the mcp-pro i get a reading of 236.

it seems to be 07E2 Autopilot airspeed value, in knots as i tested it by set it to the display and it shows it corectly and when button is rotated inside the plane the display follows it. now i miss how to use a button whit that offset to get it increase in crease the vaulve. as it might be a parameter thing right? as test i assigned a button whit the name AP spd var set and set parameter to 100 when pressed it turns to 100. and how to get it show the right on the display as only speed is shown right as some you should use math as for HDG:07CC Autopilot heading value, as degrees*65536/360 does that mean like for the captainsim: hdg = math.floor(ipc.readUD(0X07CC) * 65536) / 360

well the reason i think it was those to codes was that 66037 was 101F5 in hexi and from the other codes i saw it was only 4 destimals so i removed the first, and the next was the parameter then it shows that parameter as hexi as i think it was matehematic, but that was dead end as you say. But i realy cant find the offset for it in the sdk dokument i can finde Ap spd var set (66037) in the dokument that was instaled together whit FSUIPC, but not in the offset manual from the SDK. the closes i could fing might be: Autopilot airspeed value, in knots which is about ap airspeed in knots, and seems to work is that good enough ?

ok when it looks like this in the log: 135268 *** EVENT: Cntrl= 66037 (0x000101f5), Param= 140 (0x0000008c) AP_SPD_VAR_SET so i have to just type the ipc.writeUD(0x01f5) as isent the offset the 4 last decimas in the code above, (Cntrl=66037 (0x000101f5)) ? but then i just woundering about how get it changes the vaulve so i add 1 every time i use the command. EX. hdg 123 when i then press the button it should add 1 so my display changes to 124 and the othere way if it was a decrease button. isent it right observed that in the code: 135268 *** EVENT: Cntrl= 66037 (0x000101f5), Param= 140 (0x0000008c) AP_SPD_VAR_SET the first part is the offset code and the next part is prarmeter so if set 008c it would show 140 inside the plane which means i stil miss some thing that caculate the new parameter? when it adds 1 it should set a new hexidecimal as parameter to show the new HDG right?

here is a video of it in action so if set right it would work as this