laudey1

That is exactly what I was waiting. Thank you Pete

Thank you Pete. Of course, I use common profiles, but there are so many aircrafts to personalize...that makes a lot of sections. The sections are not so big, the most complex is that of the PMDG 737NGX on my Goflight modules. I must also confess that I do not use the lua, as I am not a programmer at all.... I am very satisfied with your answer. Do you mean also that if a section is not used, it is not loaded ?

Hello Pete, I hope that you are allright, A very simple question: since many years, I add and add new planes with mouse macros in my FSUIPC.ini, and I have now more than 2000 lines in it, the size is 65 ko: How far can I go without problem ?

Many thanks Pete, I will wait a little before rebuilding my macro....

Thank You Pete For the letters of PMDG that actions in the making of the macro, it is the G or g, L but not l, and a third one i can't remember. There are only three. Thank you for the explanation of the code change. That's why I have my problem, for sure. As you wrote, i have rebuilt my FSX.cfg without any change.... For the 2 instances of FSUIPC.dll, I spoke of the [TRUST]section of FSX.CFG, i have only one FSUIPC.DLL in the Modules Folder. With my rebuild, I have only the latest one now, no problem. Is there a way to replace the code which changes without rebuilding all the macro file ?? As you saw, my macro has about one hundred lines, and PMDG will issue some more changes of their DLL, because of the remaining problems (autothrottle disengaging, speed maintains not correctly, no pedestal in 2D, which does not to action the fuel CUT OFF levers in the macro and so on...).

I am wondering: I installed the first and second hotfix of PMDG, and FSX asked me to trust the module PMDG_737NGX.dll again. So I have now 3 versions of the PMDG_737NGX in FSX.cfg in the section [Trusted] !!! Does the macro refers to only one specific version of the DLL ??? I could delete the 2 old versions. In the same way, the 2 hotfix installed each time a PMDG_HUD_Interface. I have also 2 instances of FSUIPC.dll. I will recreate my FSX.CFG to see if it changes anything

Hello Pete, I have a strange thing. I had the problem with the macros, so i download the 4.722 version, and was abble to create the macro for the NGX (available for anybody who wants it as for the Goflight modules in the FSUIPC.in) . I made a flight and was satisfied of the macro. I Closed the flight and FSX. When I reloaded the NGX, the programmed buttons are functionning, but the macro actions are no more recognized, as if I had never created anything. The macro is under: It was necessary to change some letters, because when you type a G in the macro, the gear goes down and the letter does not write in the line of the macro, so I replaced it with a j, idem for Shift l which actions the panel light. My FSUIPC.ini works well with all the other planes and the macros also, so it seems to be related to the PMDG NGX only. Do you have any idea of what could be wrong ? [Macros] Module="PMDG_737NGX.DLL" 1=Battery=RX4ca10*Xe8cc 2=Navlits_ON (i have coupled several actions on the same button, so forget the doubbles) 2.1=RX4df00*X8bcc,31 2.2=RX4df00*X8bcc 2.3=RX4df00*X8bcc 3=NAVlits_OFF 3.1=RX4df00*X8bcc 3.2=RX4df00*X8bcc,31 3.3=RX4df00*X8bcc,31 4=Strobes=RX4df20*X8bcc 5=Taxi 5.1=RX4de40*X8bcc 5.2=RX4de00*X8bcc 5.3=RX4de20*X8bcc,31 6=Beacon=RX4df00*X8bcc,31 7=Climb1=RX4ab60*X8b05 8=TOjA=RX4ab60*X8b05,31 9=landin_lits_ON=RX4dca0*X8bcc 10=landin_lits_OFF 10.1=RX4dcc0*Xa1cc,31 10.2=RX4dd10*Xa1cc,31 10.3=RX4dd60*Xa1cc,31 10.4=RX4ddb0*Xa1cc,31 11=Probes 11.1=RX4d1a0*X8bcc 11.2=RX49100*X8bcc,31 12=landin_Alt_Plus=RX4da90*X8bcc,31 13=WindowHeat 13.1=RX4d140*X8bcc,31 13.2=RX490c0*X8bcc,31 13.3=RX4d160*X8bcc,31 13.4=RX490e0*X8bcc,31 14=landin_Alt_Moins=RX4da90*X8bcc 15=Fuel_Fwd_left=RX4cc60*X8bcc 16=FD=RX43230*Xe8cc,31 17=AT=RX431d0*Xe8cc,31 18=speed=RX43350*Xe8cc 19=N1=RX432f0*Xe8cc 20=speed_Plus=RX43440*X8bcc,31 21=speed_Moins=RX43410*Xe8cc 22=lvl_chan=RX43570*Xe8cc 23=VNAV=RX434f0*Xe8cc,31 24=Headin_sel=RX48d00*X8bcc 25=lnav=RX437d0*X8bcc 26=Vorloc=RX43850*X8bcc 27=APP=RX438d0*X8bcc 28=AltHold=RX43920*X8bcc 29=VS=RX48d40*X8bcc 30=Headin_Plus=RX43680*X8bcc,31 31=Headin_Moins=RX43620*Xe8cc 32=Alt_Plus=RX43970*X8bcc,31 33=Alt_Moins=RX43970*X8bcc 34=SPD_INT=RX43490*Xe8cc 35=Alt_INT=RX48d20*X8bcc 36=Vert_Speed_UP=RX439c0*Xe8cc 37=Vert_speed_DN=RX439c0*Xe8cc 38=Disen_Bar=RX43ba0*X8bcc 39=CMD_A=RX43a20*Xe8cc 40=CMD_B=RX43a80*Xe8cc 41=CWS_A=RX43ae0*Xe8cc 42=CWS_B=RX43b40*Xe8cc 43=ear_Down=RX4ace0*X8bcc 44=ear_UP=RX4ace0*X8bcc,31 45=Course_Plus=RX43130*X8bcc,31 46=Course_Moins=RX43100*Xe8cc 47=Autobreak_Plus=RX49b80*X8bcc,31 48=Autobreak_Moins=RX49b80*X8bcc 49=Altimetre_Plus=RX43e10*X8bcc,31 50=Altimetre_Moins=RX43e10*X8bcc 51=Irs_Moins 51.1=RX4e300*X8bcc 51.2=RX4e320*X8bcc 52=Irs_Plus 52.1=RX4e300*X8bcc,31 52.2=RX4e320*X8bcc,31 53=YawDamper=RX4d060*X8bcc,31 54=Apu_Plus=RX4de60*X8bcc 55=Apu_Moins=RX4de60*X8bcc,31 56=Transpon_Plus=RX4c600*X8bcc,31 57=Transpon_Moins=RX4c600*X8bcc 58=Prev_Power=RX4caa0*Xe8cc 59=Power_Plus=RX4caa0*Xe8cc,31 60=Apu_jen 60.1=RX4cb80*X8bcc 60.2=RX49000*X8bcc 60.3=RX4cb80*X8bcc 61=Winj_Ice=RX49120*X8bcc,31 62=enj_Ice 62.1=RX49140*X8bcc,31 62.2=RX49160*X8bcc,31 63=ext_Power=RX48fe0*X8bcc 64=Bus_Off_ON=RX4cb10*Xe8cc 65=PASS_Sins_Moins 65.1=RX4d410*X8bcc,31 65.2=RX490a0*X8bcc,31 67=PASS_Sins_Plus=RX4d410*X8bcc 68=Isol_Valve=RX4d930*X8bcc 69=Apu_bleed=RX4d990*X8bcc,31 70=Primary 70.1=RX4d8b0*X8bcc,31 70.2=RX4d8d0*X8bcc,31 72=emerjency=RX4d3a0*Xe8cc 73=Packs_Moins 73.1=RX4d910*X8bcc,31 73.2=RX49220*X8bcc,31 74=Packs_Plus 74.1=RX4d910*X8bcc 74.2=RX49220*X8bcc 76=jen_left_=RX4d970*X8bcc 77=jen_rijht=RX49240*X8bcc,31 78=enj_Start_Plus=RX4de80*X8bcc,31 79=enj1_Start_Moins=RX4de80*X8bcc 80=enj2_Start_Plus=RX4dec0*X8bcc,31 81=enj2_Start_Moins=RX4dec0*X8bcc 82=left_aft_pump=RX4cc80*X8bcc 83=rijht_fwd_pump=RX4cca0*X8bcc 84=rijht_aft_pump=RX4ccc0*X8bcc 85=fuel_ctr 85.1=RX4cce0*X8bcc 85.2=RX4cd00*X8bcc 87=crossFeed=RX4cd20*X8bcc 88=elec12 88.1=RX4d280*X8bcc 88.2=RX491a0*X8bcc 90=leftjen=RX49180*X8bcc 91=rijhtjen=RX491c0*X8bcc 92=hydrauliq2 92.1=RX491c0*X8bcc,31 92.2=RX49180*X8bcc,31 93=jenerator2=RX49020*X8bcc 94=jenerator1=RX4cb60*X8bcc

Hello Pete, Sorry about a silly question.... :unsure: I use EYEfinity for my FSX outside view on 3 displays (5760x1200) in window mode on 2D panel. I am not able to have the frontleft/frontright views with Numpad7/9. Instead of that, i always have the Pan-Tilt action.(No idea why, my Standard.xml is not changed as for the views, my Camera.cfg is the original one). I did try to program my Hat using the offsets: [buttons] ..... 25=RA,32,C65734,0 ; Pan view 26=RA,39,C65681,0 ; Num7 View Front Left 27=RA,38,C65671,0 ; Pan Left 28=RA,37,C65873,0 ; Pan Tilt Left 29=RA,36,C65735,0 ; Pan Down 30=RA,35,C65874,0 ; Pan Tilt Right 31=RA,34,C65672,0 ; Pan Right 32=RA,33,C65675,0 ; Num9 View Front Right .... The pan is working OK, but the Left and Right actions are doing Pan tilt left resp. Pan tilt Right. So I suppose that it is the basic affectation of the commands that was modified, but no idea where to look at to correct the behavior. I have created two CameraDefinition000 and 001 in the aircraft.cfg to create the missing views Do you have an idea about what is eventually changed ? Thank you for your advise

Well well well,Ok Ok, the disapointment follows the enthousiasm..... What I "just" want to do is to displace an Overhead from any plane choosen from my Server screens on a screen of my Client PC "only"......, specially the Overhead for the use of a touch screen. 1/ There is a solution with a virtual Deskstop (already tested, and it works almost good), which is not quick enough from my opinion, but would be acceptable, but opens a security failure in the network, so far I know. 2/ With Project Magenta, you can only do that for the planes choosen by themselves. It would work for my B767 Level-D, but I search a solution for all the planes. It seems that outside the virtual Desktop, there is no solution yet. I need to work on the safety side of the virtual Desktop....

And again a good idea Pete ! On my Goflight TQ6, I have four throttle levers and four Reversers, but these are not axes, they are only on/off switches. And it is not very realistic nowadays, because most of the time, the reversers are forbidden on airports for noise reasons, you are allowed only to open the "shells". So on 2 engine jets, i assigned the Throttle 3 and 4 as reversers axes, and I have the proportional opening of the reversers as in real life. With you trick I will have the reversers coupled 2 per 2, just like the engines 1-4 and 2-3, which is much better that four independent engines and no proportional reversers: GREAT !! best regards Philippe

Hi Pete, And you are working on saturday, what will say your wife ?? Your answer is really a great news for me !! I will buy WideFS too So it is possible to have several WideFS Client, with only one acting as "normal WideFS" and the others specialized for one instrument panel each . What do you think to have a Graphic card with 3 ports, one with the outside view through Wideview, one with an overhead 1900x1080 "Classinstance 1", the last with an FMS/FMC "Classintance 2" on a 12" or 9" or less depending on readability

My Config: SERVER : FSX FSUIPC 4.60, WIdeview, 13 Goflight Modules, 4 screens 1900x1200, two for the front and forward Front views on a Nvidia GTX285 (works ok on Vista64 with an i7 extreme processor), and two screens for the instruments (Front Panel, FMC/FMS, Overhead and Throttle panel or else depending on the plane. CLIENT : FSX and Wideview, two screens 1900x1200. FSX only used to get the Front Left Outside view in 1900x1200 Everything is working well, the client follows the server very fluently. But I would like to replace a screen on the CLIENT with a TouchScreen for the Overhead panel (SERVER is full now). WideFS would be great for that... I have read somewhere that WideFS client does not like to see one FSX running too on the client. Is there a trick to make WideFS ignore the FSX on the client? That would be the only way that I know at this time to have the 3 Outside views in 1900x1200 (No 52 inches screen can do 3800x2400 in resolution, so far I know) Or should I go with Project Magenta instead of WideFS ?

I never found a solution for the ALTITUDE either. But nevertheless it works very well

Thank you for the advice Pete. The Battery in LevelD is not the same key as for standard Airplanes. I have understood that I will not get my LED work this way. I will study the lua plug-in for Goflight and see what I can do for my macros. Thank you very much

Hi Pete, I have finally found a solution to my problem. I have made macros to obtain the multiple actions with one press of a button. For example, I assigned the four window heat switches to one button, using the same macro command for each of the four switches. The action on the button makes the four switches act immediatly. Now my problem is: is it possible to have GFDisplay work with macro command ? On the LevelD, the key command fot the battery is SHIFT+ = In GFDisplay.ini, I have [GFT8.2] L0=X3102 U8 ; Battery Master The LED lights permanently with the switch Off or On. What am I doing wrong ? I am as young as you...but was never a programmer in my life (Electrotechnician....)