Old 744 Forum

Archived posts

FiFLi add-on - First officer and Flight attendant for PSX - beta 0.62

Page: « < 1 2 3 4 5 6 7 ... > »

Author Post
Member
Registered: Aug 2014
Posts: 101
Ok, that is working :)

Doors closed, cabin ready indication, the Flight Attendant went through their speech....

PSX stayed responsive with no issues :)
Member
Registered: Jun 2014
Posts: 317
Ok, a quick test and all seems good, no crashes :) this is also with Basic 013 - Climbing to final cruise.

is it possible to install FiFli on a different PC?
Moderator
Registered: May 2009
Posts: 2449
Location: KTMB
If FiFli is networked, there should be zero reason why it must be on the same PC as PSX.
Moderator
Registered: May 2009
Posts: 5140
vito wrote
Yes, the ejected Q message strings flow is ok ! :D PSX correctly shows in the network ---> main : client accepted, after the check box is removed: client disconnected. After that again connects correctly.

I was just asking because I was curious how your ejected strings look like, and how often they are ejected.


Regards,

|-|ardy
Member
Registered: Aug 2014
Posts: 101
One suggestion...maybe expand the form to list say what the Flight Attendant things that will play and the triggers?

Don't know how easy it would be to update the form as ones are completed?
Moderator
Registered: May 2009
Posts: 2449
Location: KTMB
In general, experience has taught us (the hard way) that state machines that trigger on "normal, always happening" event sequences are quite tricky. Even the built-in PSX ATC Robot manages to escape "normal, routine" events if the pilot is just a bit out of his routine today. And some state machines are fiddly in getting back to work; ACARS OOOI is one of these.

In such a case it may help to at least document exactly what state machine (diagram) and trigger events (list) has been implemented, and sometimes also to post the current state of the machine somewhere out of the way but visible. This aids a lot in debugging and in searching why the machine seems to be locked up.

If at all possible, it is better to design a stateless machine. Usually this can be done by building a list of permanently monitored variables, and trigger an event when a specific combination of variables and exceedances occurs, without needing to know the current state (previous trigger). This is especially helpful when the stateless machine suddenly needs to cope with a midflight situation change. A state machine now gets hopelessly confused, while a stateless machine just picks up (and may go back from "landing announcement" to "takeoff announcement").


Hoppie
Member
Registered: May 2009
Posts: 142
Location: Zagreb
HercMighty wrote
One suggestion...maybe expand the form to list say what the Flight Attendant things that will play and the triggers?

Don't know how easy it would be to update the form as ones are completed?


Yes, I was thinking to do that and I will soon as we escape this initial rumbling with beta! :-)
Member
Registered: May 2009
Posts: 142
Location: Zagreb
HercMighty wrote
Ok, that is working :)

Doors closed, cabin ready indication, the Flight Attendant went through their speech....

PSX stayed responsive with no issues :)


Thanks for testing this, now I can safely say thst the problem is in "pause" routine or function. 8)
Member
Registered: May 2009
Posts: 142
Location: Zagreb
Hardy, can you suggest how to implement wait or pause function? Mine obviously is not working correctly, it messed with main thread and managed to disrupt even PSX. This is not trivial and mine expirience / knowledge here is at least ... 8)


Best regards

Vito
Moderator
Registered: May 2009
Posts: 5140
The wait and pause is already implemented if you're using my code example in AddonExampleNetThread.java.


while (true) {
if ((message = in.readLine()) != null) {
try {
if (message.charAt(0) == 'Q') {
etc.


in.readLine() blocks (pauses) until a new message has arrived in the BufferedReader (called "in"). This "while" loop runs in a separate thread, so it blocks only itself.


Cheers,

|-|ardy
Member
Registered: May 2009
Posts: 142
Location: Zagreb
Thanks for idea Hardy :mrgreen: !

Now, here is latest beta FiFLi 0.36, just overwrite the original jar. The wait function is now written in the way Hardy suggested.

For quick test please load again Basic 013 - Climbing to final cruise ... after situ file is loaded start FiFLi and make it active. Cruise briefing should be played AFTER the pause which is cca 15 secs.

https://www.dropbox.com/s/wvt0tz4ii3smtn8/FiFLi.jar?dl=0

best regards

vito
Member
Registered: Aug 2014
Posts: 101
Better, but there is a noticeable freeze to PSX. Freeze's for a few seconds, but once clears the sim comes back under user control, don't have to close your app.
Member
Registered: May 2009
Posts: 142
Location: Zagreb
Thanks for report! :D

Best regards
Vito
Member
Registered: May 2009
Posts: 142
Location: Zagreb
Jeroen Hoppenbrouwers wrote
If at all possible, it is better to design a stateless machine. Usually this can be done by building a list of permanently monitored variables, and trigger an event when a specific combination of variables and exceedances occurs, without needing to know the current state (previous trigger). This is especially helpful when the stateless machine suddenly needs to cope with a midflight situation change. A state machine now gets hopelessly confused, while a stateless machine just picks up (and may go back from "landing announcement" to "takeoff announcement").


Hoppie


Thanks for suggestions! I designed FiFLi to catch up with any flight phase, at least it should do 8) but certainly there is big room for improvements. As soon as I can I will document trigers and flight phases.

Best regards

Vito
Member
Registered: Aug 2014
Posts: 227
Location: Sydney
Hi Vito,

PSX freezes shortly after the first sound trigger is played.
This is with your latest beta, 0.36.

Regards,

Ben
Member
Registered: May 2009
Posts: 142
Location: Zagreb
OmniAtlas wrote
Hi Vito,

PSX freezes shortly after the first sound trigger is played.
This is with your latest beta, 0.36.

Regards,

Ben


Thanks on your report Ben! After first freeze does it continue to work normal?

Best regards
Vito
Member
Registered: May 2009
Posts: 55
Location: LOWW
Hallo Vito,

I did some tests:

Flight Attendant ACTIVE

Beacon ON, Autobrakes RTO, Doors AUTO. At the same time I start the clock on the client instance.

after 60': BRIEF1 starts and server instance freezes, Client o.k.
after 180': BRIEF2 starts
after 270': BRIEF3 starts and server unfreezes and client clock resets, PSX works correct now.

After t/o no announcement anymore, when commencing descent and slowing down server freezes again and stays frozen - client o.k.

I hope this helps, Robert
Member
Registered: May 2009
Posts: 142
Location: Zagreb
Robert Staudinger wrote
After t/o no announcement anymore, when commencing descent and slowing down server freezes again and stays frozen - client o.k.

I hope this helps, Robert


Thank you for report Robert !
What did you mean by statement above ? Did PSX froze after you have landed and you couldn't get control of it or you mean that briefing just didn't play ?

When climbing you must pass 20000 ft and auto brakes should be in OFF position for briefing to be played.

When descending you must pass below 10000 ft and auto brakes should be selected: 1, 2, 3, 4 or MAX for briefing to be played.

Can you please load Basic 013 - Climbing to final cruise ... after situ file is loaded start FiFLi and make it active. Cruise briefing should be played AFTER the pause which is cca 15 secs.

Thank you !

best regards

vito
Member
Registered: May 2009
Posts: 142
Location: Zagreb
Here are triggers for various briefings that FiFLi can play:

doors closed, pushback and taxiout:
-> all doors must be closed,
-> autobrakes must be in RTO position
-> beacon must be on

cruise:
-> altitude must be higher than 20000 ft
-> autobrakes must be in OFF position

approach:
-> altitude must be between 3000 and 10000 ft
-> autobrakes must be in either 1, 2, 3 4 or MAX position
-> speedbrakes must be armed (this is important just for taxi in briefing not for approach briefing to be played),

taxi in:
-> flaps and speed brakes must be deplopyed
-> autobrakes must be in DISARM position
-> when you retract the speedbrake (this is the signal that we are actually of the runway) first officer will:
---> start the APU
---> turn off the landing lights
---> turn of the strobes
---> retract flaps
---> and you will hear taxi in briefing

and final actions(randomize external supplies connections) happen:
--> only if the taxi in briefing was played
--> after autobrakes are in off position
--> and doors are open

All of the above triggers are already included in standard checklists (that means they are part of the standard procedures), so if you use PSX first officer and go through them or you play from your memory you should :-) hear all of the briefings.

Best regards

vito
Moderator
Registered: May 2009
Posts: 5140
Hi Vito,

I believe these details are just side effects of another bigger, fundamental coding error somewhere in your network functions -- which freezes the server.

I would suggest to post the essential part of your code here in the forum (subforum "Networkers", that's visible only to members). Maybe some of us Java coders will help finding the error? (On the other hand, I can also understand if you want to keep it all private as your personal challenge and adventure. Just a suggestion :-))


Cheers,

|-|ardy
Member
Registered: May 2009
Posts: 55
Location: LOWW
Hi Vito,

thanks for your list of triggers - so I checked again.

As before between BRIEF1 and BRIEF3 PSX is frozen.

Thereafter everything is normal, BRIEF4 comes about 10sec after reaching FL200 and BRIEF5 comes 30sec after setting the autobrakes.

The taxi-in actions spool off (APU, landing lights, strobes, flaps) correct but after this, PSX is frozen for about 25sec, awakes again and BRIEF6 is playing.

I hope you are able to remove this bugs. Your add-on is very useful to simulate distractions while taxiing and flying. I suggest to include the list of triggers in your final download and maybe it is possible to connect this announcements with the setting of the audio control panel (CAB or PA).

Good luck, Robert
Member
Registered: May 2009
Posts: 142
Location: Zagreb
Robert Staudinger wrote
Hi Vito,

thanks for your list of triggers - so I checked again.

As before between BRIEF1 and BRIEF3 PSX is frozen.

Thereafter everything is normal, BRIEF4 comes about 10sec after reaching FL200 and BRIEF5 comes 30sec after setting the autobrakes.

The taxi-in actions spool off (APU, landing lights, strobes, flaps) correct but after this, PSX is frozen for about 25sec, awakes again and BRIEF6 is playing.

I hope you are able to remove this bugs. Your add-on is very useful to simulate distractions while taxiing and flying. I suggest to include the list of triggers in your final download and maybe it is possible to connect this announcements with the setting of the audio control panel (CAB or PA).

Good luck, Robert


thanks it helps a lot ! :D

best regards

vito
Member
Registered: May 2009
Posts: 142
Location: Zagreb
Hardy Heinlin wrote
Hi Vito,

I believe these details are just side effects of another bigger, fundamental coding error somewhere in your network functions -- which freezes the server.

I would suggest to post the essential part of your code here in the forum (subforum "Networkers", that's visible only to members). Maybe some of us Java coders will help finding the error? (On the other hand, I can also understand if you want to keep it all private as your personal challenge and adventure. Just a suggestion :-))


Cheers,

|-|ardy



Thanks Hardy, let me keep my dirty laundry just a few days more and after that ... :D

best regards

vito
Member
Registered: May 2009
Posts: 142
Location: Zagreb
Here is latest FiFLi beta 0.37:

https://www.dropbox.com/s/wvt0tz4ii3smtn8/FiFLi.jar?dl=0

just overwrite the old one :-)

best regards

vito
Member
Registered: May 2009
Posts: 55
Location: LOWW
Hi Vito,

sorry to say that, the same behavior as before.

Regards, Robert

Page: « < 1 2 3 4 5 6 7 ... > »

Old 744 Forum is powered by UseBB 1 Forum Software