On a higher note you probably have noticed that there are some "_" and "+ _" next to every expression. This was the easy and elegant solution to that problem. Which basically stated, that if A321SB returns anything higher than 0, return 1, else 0. But I would also like to have the Auto feature mean something, so that is why I came up with the idea, that when the switch is in the Auto position it would give a 1 (Sign on) when below 10.000 ft and 0 (Sign Off) when above. Which basically means that if the Zibo Dataref gives anything higher than 0, it will return a 1, else 0. We could have accomplished that easily by just writing Obviously, we want the Off position to give 0 and the two on positions to give 1. The Zibo has three switch positions: Off (0), Auto (1) and On (2). This can be a little confusing at first, but let me explain the expression at the Zibo plane. This means that the operator is followed after the operand ( (1+2) / 3 is 1 2 + 3 /). First you need to notice that the expressions are written in what is called Reverse Polish Notation or RPN. The expression is where the bulk of the work goes and it was also here I spent the most time. Somewhere between 1-3 should be sufficient. 1 is every flight model frame, where 8 is at every 313th frame. The priority deals with how often the Offset is updated. PACX is "listening" for seatbelt switches from the Offset 0x341D, so we have to create an Offset definition too. But in any case, you need to find the Datarefs for the airplane you wish to add. The ToLiss series of planes do however use the same programming, so the Datarefs are probably similar, as the FlightFactors may also be. These are specific to almost every 3rd party plane (Zibo is a 3rd party mod) and these here are therefore specific for the airplanes I have added. The first four lines deals with the Datarefs. The solution looks as follows for the Zibo 737-800, FlightFactor A350 XWB and ToLiss A321 (Neo):ĭataref ZiboSB laminar/B738/toggle_switch/seatbelt_sign_pos floatĭataref alt sim/flightmodel/position/elevation floatĭatarefĚ321SBĚirbusFBW/OHPLightSwitches intarray You do need to edit the XPUIPCOffset.cfg file, but I am guessing that anyway you would like to add offsets, you would have to edit these files nonetheless. So, the solution I have found looks as follows.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |