First, thanks for constantly improving the features of blackbox.
Here are two small addition I suggest:
- in case of bigger and more complex blackbox files it would be handy to add comments and remarks.
- add a timer for events (e.g. event triggered after x secs/mins elapsed or event action occurs after a delay of x secs/mins)
thank you
Jörg
Blackbox addition
Moderator: FSAirlines Staff
-
- FSAirlines Developer
- Posts: 1564
- Joined: Sun Sep 25, 2005 10:40 am
- Location: Munich, Germany
- Contact:
Re: Blackbox addition
The timer for events is a cool idea, I put that on the todo-list. Actually both variants (delayed event and trigger after x secs flighttime) should be pretty easy to implement.
The possibility to add comments is already given as the blackbox is a standard xml-file. You can add one using <!-- comment --> anywhere between the xml-tags. Here's a little example:
Maybe I should add that to the wiki article, too.
The possibility to add comments is already given as the blackbox is a standard xml-file. You can add one using <!-- comment --> anywhere between the xml-tags. Here's a little example:
Code: Select all
<blackbox>
<!-- log landing lights on -->
<event var="landinglights" value="1" method="equal" multiple="1" text="landing lights turned on!" />
<!-- log landing lights off -->
<event var="landinglights" value="0" method="equal" multiple="1" text="landing lights turned off!" />
</blackbox>
Konrad - FSAirlines Developer
Re: Blackbox addition
Thanks a lot. I wasn't aware that the comments are already available.
While editing the xml I got another idea for a new event trigger: the status of the passenger signs (seat belts and no smoking)
While editing the xml I got another idea for a new event trigger: the status of the passenger signs (seat belts and no smoking)
Re: Blackbox addition
And again another idea:
Conditions should be invertable (negateable).
example: means event triggered when it is NOT in flightstate 3 ("landed")
Maybe you find a better way to implement. It's just a suggestion.
Conditions should be invertable (negateable).
example:
Code: Select all
<event var="flightstate" value="3" method="not" multiple="0" />
Maybe you find a better way to implement. It's just a suggestion.
Re: Blackbox addition
For me, I've always just set the flightstate to where the event would occur naturally.MadJosch wrote:Maybe you find a better way to implement.
Perhaps if you could show me exactly what you'd use this for, maybe I would understand the use for it better.
As a suggestion: Trigger using a set key combination
Matt-FSAirlines DB Admin
Re: Blackbox addition
I understand it is hard to see what I mean when the event is standing alone.
My intension is that this event is a part of a combination event.
example:
This would play a reminder for the airspeed of a B744 between FL100 and FL120.
But what if I would exclude especially one type of aircraft? Let's say I want this check for ALL aircraft EXCEPT the B744?
By inverting the above event all work would be done.
It would be a waste of time to write combined events for all other aircraft (on positive logic), rather than to write one exception.
This is just an example. I think there would be much more occasions where a negation would be handy.
My intension is that this event is a part of a combination event.
example:
Code: Select all
<combination text="Speed check" sound="voice/check_your_speed.wav" multiple="0" >
<event var="altitudestd" value="12000" method="less" />
<event var="altitudestd" value="10000" method="greater" />
<event var="ias" value="250" method="greater" multiple="0" />
<event var="aircrafttype" value="B744" method="equal" />
</combination>
But what if I would exclude especially one type of aircraft? Let's say I want this check for ALL aircraft EXCEPT the B744?
By inverting the above event all work would be done.
It would be a waste of time to write combined events for all other aircraft (on positive logic), rather than to write one exception.
This is just an example. I think there would be much more occasions where a negation would be handy.