Jump to content

DemonDNF

Members
  • Content Count

    27
  • Donations

    $0.00 
  • Joined

  • Last visited

Everything posted by DemonDNF

  1. That makes a lot of sense; I forgot Lorby gauges were meant for all aircraft. I guess this applies more to the G.W. gauge set for C-152. Yeah, just picked up last night that CIRCUIT BREAKER PULLED shuts down ADF and Transponder. I really would have liked to activate all the breakers we see on the lower dash on copilot's side. Robert
  2. A little something I've picked up today that could be added at the top of the display elements for the Cessna 152: The gauges will react like in-game and shut down if the battery is OFF, if the COM or ADF volume is OFF, or Transponder mode is OFF. ADF: <Visible>(A:ELECTRICAL MASTER BATTERY, Bool) 1 == (A:ADF VOLUME:1, percent over 100) 0 > and</Visible> COM1/NAV1: <Visible>(A:ELECTRICAL MASTER BATTERY, Bool) 1 == (A:COM VOLUME:1, percent) 0 > and</Visible> COM2/NAV2: <Visible>(A:ELECTRICAL MASTER BATTERY, Bool) 1 == (A:COM VOLUME:2, percent) 0 > and</Visible> DME: (added to top Element) <Visible>(A:ELECTRICAL MASTER BATTERY, Bool) 1 ==</Visible> (substituted on next 3 Elements) <Visible>(A:ELECTRICAL MASTER BATTERY, Bool) 1 == (A:Selected DME, number) 1 == and (A:NAV1 DME, nmiles) 0.1 > and</Visible> <Visible>(A:ELECTRICAL MASTER BATTERY, Bool) 1 == (A:Selected DME, number) 2 == and (A:NAV2 DME, nmiles) 0.1 > and</Visible> <Visible>(A:ELECTRICAL MASTER BATTERY, Bool) 1 == (A:Selected DME, number) 1 == and (A:NAV1 DME, nmiles) 0.1 < and (A:Selected DME, number) 2 == (A:NAV2 DME, nmiles) 0.1 < and or</Visible> (untested with actual DME operating) Transponder: <Visible>(A:ELECTRICAL MASTER BATTERY, Bool) 1 == (A:TRANSPONDER STATE:1, Number) 0 > and</Visible> I know the transponder display does not shut down in-game, but it should (unless the numbers are inscribed on a rotating circular plate - but I don't see any motion in the animation - and I've never touched a real transponder in a Cessna 152) I'd share mine, but I've gutted out all the buttons, switches, potentiometers and encoders since I'm using external hardware. Even if you don't update the Lorby gauges, and G.W. doesn't see this thread, at least it'll be there for the next guy. Robert
  3. WOOHOOO! I totally ignored that event cause it seemed targetting sound (mute). It didn't seem to imply it would light them (to me anyways). Thank you very much! Robert EDIT: Now I understand that it meant "a muted test of the markers".
  4. I'm building a console for the Cessna 152; every button, knob, slider, even throttle, mixture and flaps. At first I was going to include all gauges and numerical displays, but that quickly became very expensive. So now I'm modifying gauges to suit my liking (essentially reducing download of variables via USB to a bare minimum, and concentrating on uploading commands). At the very worse, I'll have my own 3 marker lights on my console along with a test switch; that way I can override my markers at will. Now, the last problem is figuring out what variable or logic controls that ammeter warning lamp (not an AAO problem, hence why I didn't post here): https://forums.flightsimulator.com/t/ammeter-warning-light/612265 I've seen on some forums that some have given up and just turn it ON when the needle reaches goes below the 50% mark. Robert
  5. Yeah, I'm still learning what's what. 😉
  6. That's what I had done, even saved my script to retry later once I learned what was wrong. So that means the SDK is wrong when they say the 3 markers are settable... 😞
  7. Both CLICKs give me a red light in the RPN editor when I include CLICK endmarks. 1st one gives red light without CLICK endmarks. But this one gives green light: 1·(>A:INNER·MARKER,·bool) I click on TEST and nothing happens.
  8. Cause I had tried and failed miserably to get that to work in the beginning. 😄 (haven't tried with these though) This is what I'm trying to accomplish. Robert
  9. I know, that's why I said I will control this from an external physical toggle switch (I interface with MSFS via USB). I use that modified DME gauge as a test bed. I use the click areas for NAV1 and NAV2 to set INNER MARKER on. Those events only concern the sound (it's the MKR button above the radio stack), I just want to turn on the lights. In a real Cessna 152, that dead toggle switch in MSFS is used to test the markers. I believe they light, but the beeping sound also comes on. But I'm afraid you might be right that MSFS immediately overrides my input and says they are OFF.
  10. I couldn't find an event in the SDK associated with setting the markers ON/OFF. I've never used "MSFS developer mode", no clue what that is. I've been updating this modified gauge for my testing cause it's about all I know when it comes to gauges (just started). Everything I read in forums says I should be able to change a variable using CLICK in gauge XML, but the vast majority use an EVENT as an example. (...reading your reply now...) Robert
  11. Sorry, cause I was desperate and trying anything at this point. I had taken that screen earlier today during one of those tests. This is current code that doesn't turn on the marker: <Mouse> <Area> <Area> <Position X="95" Y="70"/> <Size X="25" Y="50"/> <Click>(A:INNER MARKER, bool) ! (&gt;A:INNER MARKER, bool)</Click> </Area> <Area> <Position X="120" Y="70"/> <Size X="25" Y="50"/> <Click>1 (>A:INNER MARKER, bool)</Click> </Area> <Area> <Position X="95" Y="70"/> <Size X="50" Y="50"/> <Wheel DownEvent="DME1_TOGGLE" UpEvent="DME2_TOGGLE" Repeat="Yes" /> </Area> </Area> </Mouse> Robert
  12. ... and failing miserably for the default Cessna 152. I've scoured the web and found 2 different techniques. I couldn't get either to work. I know I have syntax errors, just clueless at this point. I'm using a modified LORBY_DME gauge to try to turn on the Inner Marker light. I use the DME1 and DME2 click areas as test areas, and keep the mousescroll area active to make sure MSFS isn't freezing on me. AAO says the variable name is A:INNER MARKER, it also states that the markers are available. SDK says all 3 markers are settable: (bottom of LorbyDME_MOD.xml) <Mouse> <Area> <Area> <Position X="95" Y="70"/> <Size X="25" Y="50"/> <Click>(L:INNER MARKER, bool) ! (&gt;L:INNER MARKER, bool)</Click> </Area> <Area> <Position X="120" Y="70"/> <Size X="25" Y="50"/> <Click>1 (>L:INNER MARKER, bool)</Click> </Area> <Area> <Position X="95" Y="70"/> <Size X="50" Y="50"/> <Wheel DownEvent="DME1_TOGGLE" UpEvent="DME2_TOGGLE" Repeat="Yes" /> </Area> </Area> </Mouse> The end-goal is to have that inactive switch to the left of the 3 marker lights come back to life; google links says it's a Marker Test (I just want to turn all 3 lights ON, no audio beeping test). I won't be using that actual switch, all my controls will be done by external hardware switches, interfaced with a PIC microcontroller via USB and and managed by VS2022 C++. Robert (retired mainframe programmer, dabbles in PIC BASIC, VS2022 C++ and now XML apparently) Updated Steam MSFS, and most recent AAO download.
  13. Thanks for the push in the right direction Lorby, and thanks to developpers like G.W. (G.W. demo gauges), and Huha001 (X-Touch Mini Gauge), I now have the 3 missing gauges for the Cessna 152. Last time I touched something remotely like this was when HTML first came out. 😄
  14. Thanks, I've gone through that manual backwards and forwards. This is for the next guy that just can't figure out how to add a new gauge into the layouts. The PLUS sign will add "some" gauge, in my case it was the fuel gauge. On that new gauge, CLICK on the tiny DOWN ARROW at the far right; that will give you access to all the available gauges. That vacuum gauge for the Cessna 152 comes from this: https://fr.flightsim.to/file/38162/x-touch-mini-gauge-for-use-with-aao-axis-and-ohs
  15. I found DesktopWebFips_MSFS.xml in C:\Users\Papa\AppData\Local\LORBY_SI\LorbyAxisAndOhsMSFS. I replaced LorbyClock.xml for GWClock.xml and resized from 190x190 to 240x240, but it didn't make a difference. It gets overwritten when I reload the Demo Layout. I can see my 2 custom layouts at the bottom of that file, but it must get initialized from somewhere else. The only thing I can think of is that GUID variable at the top of the layouts in that file, but no clue where to go from here. EDIT: some details... Yes, I run AAO as Admin. And yup, I've tried restarting AAO completely, not just reconnecting, no difference.
  16. AAO 3.60 b32 - MSFS licensed I know it's not an AAO bug, but I'm using this as an exercise to learn XML and MSFS gauges. The demo gauges from GW in AAO_DesktopFips_Layout_Demo_C-152.xml points to LorbyClock.xml, but LorbyClock.xml doesn't exist in default C:\Program Files\LorbyAxisAndOhs_MSFS\LorbyGauges\Gauges. But there is a GWClock.xml along with the other GW gauges in C:\Users\Papa\Documents\LorbyAxisAndOhs Files\UserGauges (no idea why GW didn't point to that one). Problem trying to use GW Clock gauge: open ClockBackground.png in 1024 folder for GW_Clock_C152 using Paintbrush to see exact size in Properties (240 x 240). edit AAO_DesktopFips_Layout_Demo_C-152.xml using Notepad. replace LorbyClock.xml with GWClock.xml, and replace size 190x190 to 240x240. terminate connection with MSFS in AAO (it was running). reconnect to MSFS and reload C-152 demo layout in AAO. The Clock still does not show up...? Any idea what syntax or step I'm messing up? <DesktopFipDef> <gaugeName>GWClock.xml</gaugeName> <xPos>-633</xPos> <yPos>455</yPos> <xSize>240</xSize> <ySize>240</ySize> </DesktopFipDef> Somehow the Clock does appear in the image downloaded along with the GW gauges. Robert EDIT: If I open GWClock.xml using the new Editor, it seems to be working fine, the minute hand moved. EDIT SOME MORE: This is what it looks like when I open the GW Demo Gauge Layout, no clock.
  17. You probably already know (I didn't find a single post using VOR2 in Search), and I can't find any other place to report this, and can't see Gerdis' coordinates anywhere. G.W. gauges for Cessna 152 from AAO download site (gw_fips_aao_c-152_1_0.7z). Folder: GW_VOR2_Gauge File: GW_VOR2.xml In case this helps someone without IT skills: 1. open the file using Notepad. 2. click EDIT on menu bar, then REPLACE. 3. enter VOR1 in 1st box, VOR2 in 2nd box, click REPLACE ALL. 4. SAVE file. That's it, VOR2 gauge will now show properly when you Load the C-152 Example Cockpit gauges.
  18. Solution (can't edit my post above to add Degrees): PointsTo is how the needle is drawn in the BMP, not how it is drawn by XML. Pointing up is North, right is East, etc. XML will draw the needle as it is drawn in the BMP, PointsTo is only telling it the direction for rotation calculation. Degrees is relative to PointsTo, and can sweep clockwise or counterclockwise, depending on the sequence of values. My Flaps gauge did not work because I told XML my needle was drawn pointing West, it was painted facing North (up), hence the 90 degree offset but the proper rotation. The Brake Pressure needle worked out of stupid luck. I told XML the needle was drawn pointing East, but it was also pointing North (up). So a value = 0 with 90 degrees will intend to rotate the needle from East to South using a needle drawn on its side. But since my needle is drawn pointing North, it rotates 90 degrees for value 0 and ends facing East, giving the correct position totally out of sheer luck.
  19. Thanks for your time Vololiberista, but adding an entry for value -1 would not have made a difference. The gauge works fine without that entry. You supplied an example from the VC10, but this Brake Pressure is for the Level-D 767 and comes from Lekseecon (variable 761 offfset 0x8b90). There is no -1 value for cold & dark. Lekseecon uses another technique to manage cockpit state. And yes, I did take the time to use parts of the examples to test. But no amount of testing is going to help if I do not understand why code behaves as it does. I didn't understand properly the concept of PointsTo until Tom illustrated the meaning on FSdevelopper. PointsTo is how the needle is drawn in the BMP; this is never mentionned in the SDK. Now I understand why Flap Position gauge was offset by 90 degrees, and why Brake Pressure gauge worked fine out out of pure luck. And I don't see anything wrong asking the same question in two sites. Now if I had posted in two sub-forums on Avsim, then I'd agree that would be spamming and considered wrong. I also posted on Level-D General forum, and still have a total of 0 answers there. I did get the answer to why my Compass needle was not working from an Avsim thread; I needed a mask colour of 1,1,1. But it's Alan on FSdevelopper that confirmed I was using the wrong type of BMP file and needed 24bit, not 256 colours. Unless there's an exclusivity clause I missed when I signed up...? Robert
  20. I reverted back to coordinates for both needles, and pointed Right needle to North, Left needle to West. Right needle is working fine, Left is offset 90 degrees. PointsTo is behaving really weird. I thought it was just a starting point to paint the needle until all the data came in, and then the rotation entries would take over. Apparently there's more going on. <Gauge Name="KK_FlapPosition" Version="1.0"> <Image Name="FlapPositionBackground.bmp"/> <!-- ========================= Flap Position - Left ============== --> <Element> <Position X="60" Y="60"/> <Image Name="FlapLeftNeedle.bmp" PointsTo="West"> <Axis X="8" Y="55"/> </Image> <Rotate> <Value Minimum="0" Maximum="10624">(L:KK_FlapLeft,number)</Value> <Nonlinearity> <Item Value="0" X="2" Y="60"/> <Item Value="1062" X="19" Y="19"/> <Item Value="2560" X="60" Y="2"/> <Item Value="5120" X="101" Y="19"/> <Item Value="5888" X="118" Y="60"/> <Item Value="8525" X="101" Y="101"/> <Item Value="10624" X="60" Y="118"/> </Nonlinearity> </Rotate> </Element> <!-- ========================= Flap Position - Right ============== --> <Element> <Position X="60" Y="60"/> <Image Name="FlapRightNeedle.bmp" PointsTo="North"> <Axis X="8" Y="55"/> </Image> <Rotate> <Value Minimum="0" Maximum="10624">(L:KK_FlapRight,number)</Value> <Nonlinearity> <Item Value="0" X="2" Y="60"/> <Item Value="1062" X="19" Y="19"/> <Item Value="2560" X="60" Y="2"/> <Item Value="5120" X="101" Y="19"/> <Item Value="5888" X="118" Y="60"/> <Item Value="8525" X="101" Y="101"/> <Item Value="10624" X="60" Y="118"/> </Nonlinearity> </Rotate> </Element> </Gauge> I'm just going to point the needle North.
  21. Ok, so I simplified the XML to a single needle with only 3 positions; - Left Flap = 0 - PointsTo="North" - <Item Value="0" Degrees="0"/> This is what I was trying to explain, the needle behaves at a 90 degree offset from where it should. <Gauge Name="KK_FlapPosition" Version="1.0"> <Image Name="FlapPositionBackground.bmp"/> <!-- ========================= Flap Position - Left ============== --> <Element> <Position X="60" Y="60"/> <Image Name="FlapLeftNeedle.bmp" PointsTo="North"> <Axis X="8" Y="55"/> </Image> <Rotate> <Value Minimum="0" Maximum="10624">(L:KK_FlapLeft,number)</Value> <Nonlinearity> <Item Value="0" Degrees="0"/> <Item Value="1062" Degrees="45"/> <Item Value="2560" Degrees="90"/> </Nonlinearity> </Rotate> </Element> </Gauge> The needle should have been pointing North. Robert
  22. SOLVED! 24bit BMP using 1,1,1 as colour for the mask was the answer.
  23. That's what I ended up doing, but it's wrong. Using 270 or -90 degrees makes no difference, both work fine. But for some reason that eludes me, I have to use East in this case. I fired up FS-X and loaded a flight with the Alternate Flap Selector and Flaps already at 5 degrees. For a fraction of a second the needle was pointing West, and then blipped to the proper direction for 5 degrees. And yet the XML instructs to point the needle East as an initial state. <Gauge Name="KK_FlapPosition" Version="1.0"> <Image Name="FlapPositionBackground.bmp"/> <!-- ========================= Flap Position - Left ============== --> <Element> <Position X="60" Y="60"/> <Image Name="FlapLeftNeedle.bmp" PointsTo="East"> <Axis X="8" Y="55"/> </Image> <Rotate> <Value Minimum="0" Maximum="10624">(L:KK_FlapLeft,number)</Value> <Nonlinearity> <Item Value="0" Degrees="-90"/> <Item Value="1062" Degrees="-45"/> <Item Value="2560" Degrees="0"/> <Item Value="5120" Degrees="45"/> <Item Value="5888" Degrees="90"/> <Item Value="8525" Degrees="135"/> <Item Value="10624" Degrees="180"/> </Nonlinearity> </Rotate> </Element> <!-- ========================= Flap Position - Right ============== --> <Element> <Position X="60" Y="60"/> <Image Name="FlapRightNeedle.bmp" PointsTo="East"> <Axis X="8" Y="55"/> </Image> <Rotate> <Value Minimum="0" Maximum="10624">(L:KK_FlapRight,number)</Value> <Nonlinearity> <Item Value="0" Degrees="-90"/> <Item Value="1062" Degrees="-45"/> <Item Value="2560" Degrees="0"/> <Item Value="5120" Degrees="45"/> <Item Value="5888" Degrees="90"/> <Item Value="8525" Degrees="135"/> <Item Value="10624" Degrees="180"/> </Nonlinearity> </Rotate> </Element> </Gauge> Totally stumped. Either I'm clearly not seeing the forest, or there's a bug. I'm a programmer by trade and this makes no sense to me. I can easily imagine an average person facing a situation like this and just giving up. Robert EDIT: Weird, that's the second time the bottom of my post beyond the code gets trimmed off and I have to edit.
  24. Nope, the needle has a 90degree offset this way. Thanks, but that was one of the many combinations I had tried. All my needles are drawn pointing upwards. <Gauge Name="KK_FlapPosition" Version="1.0"> <Image Name="FlapPositionBackground.bmp"/> <!-- ========================= Flap Position - Left ============== --> <Element> <Position X="60" Y="60"/> <Image Name="FlapLeftNeedle.bmp" PointsTo="North"> <Axis X="8" Y="55"/> </Image> <Rotate> <Value Minimum="0" Maximum="10624">(L:KK_FlapLeft,number)</Value> <Nonlinearity> <Item Value="0" Degrees="-90"/> <Item Value="1062" Degrees="-45"/> <Item Value="2560" Degrees="0"/> <Item Value="5120" Degrees="45"/> <Item Value="5888" Degrees="90"/> <Item Value="8525" Degrees="135"/> <Item Value="10624" Degrees="180"/> </Nonlinearity> </Rotate> </Element> <!-- ========================= Flap Position - Right ============== --> <Element> <Position X="60" Y="60"/> <Image Name="FlapRightNeedle.bmp" PointsTo="North"> <Axis X="8" Y="55"/> </Image> <Rotate> <Value Minimum="0" Maximum="10624">(L:KK_FlapRight,number)</Value> <Nonlinearity> <Item Value="0" Degrees="-90"/> <Item Value="1062" Degrees="-45"/> <Item Value="2560" Degrees="0"/> <Item Value="5120" Degrees="45"/> <Item Value="5888" Degrees="90"/> <Item Value="8525" Degrees="135"/> <Item Value="10624" Degrees="180"/> </Nonlinearity> </Rotate> </Element> </Gauge> I'm stumped. The Brake Pressure gauge was done using the Flap Position XML, and yet the Brake Pressure gauge works fine but the Flap Position is wonky. Robert
×
×
  • Create New...