January 21, 20251 yr Hello, Example gauge95=hud!hud_att, 77,100,95,130 gauge96=KingAir!autopilot, 800, 190, 145, 39 gauge97=KingAir!vsi, 6, 490, 81, 80 gauge98=Airbus_A321!mfd, 200, 20,216,206 gauge99=Cessna208B_XML!hsi, 10,300 gauge100=Mooney_Bravo!Landing Lights, 10,400,32,50, gauge101=Mooney_Bravo!Pitot Heat, 60,400,32,50 gauge102=104asam1!Avionics Icon, 10,453,19,19 gauge103=B737_800!annunciator_speed_brake_armed, 210,471,35,20, I do not see the gauges 100,101,102 and 103 in my 2D panel... is gauge99 the max allowed? Thanks in advance Emile EBBR Z590 Aorus Elite, i9-11900K 3.5Ghz Nvidia RTX 5070, 32 GB Mem, SSD 3 Tera , 3 monitors Win11 Pro X64 LM P3D V6.1 Little Nav Map Hifisim Nvidia 591.44
January 21, 20251 yr 3 hours ago, Emile said: in my 2D panel... is gauge99 the max allowed? Not sure about the max number allowed, but it's normal to start numbering from 00 in each window within a panel cfg, and I've never seen a single window in a panel cfg get anywhere near those high numbers. Have a look at some of the other aircraft panel cfgs and see how they are made up. I suggest you backup your existing panel cfg and then renumber the gauges in that particular window, starting from 00, 01, 02 etc. John B
January 21, 20251 yr Author LM p3d SDK shows gauge00 to gaugeNN 2N means 2 digits? Emile EBBR Z590 Aorus Elite, i9-11900K 3.5Ghz Nvidia RTX 5070, 32 GB Mem, SSD 3 Tera , 3 monitors Win11 Pro X64 LM P3D V6.1 Little Nav Map Hifisim Nvidia 591.44
January 22, 20251 yr The SDK says "The Panel system starts loading gauges, starting from gauge00 until it reaches gauge99. After that, it loads gauge100, gauge101, and so on until it finds a break in the progression." So I believe that your panel.cfg should work, unless the gauges 100 to 103 are not valid or not 64 bits, tick in Menu>Apllication >Enable content error reporting, restart the sim and try again, in closing the SIM you will see a Msg about the error reporting, look at it . Jorge
Create an account or sign in to comment