Improve EFIS

[xcvb85]

EICAS still very basic yet. The goal is to have menu navigation with different system pages.

[xcvb85]

It's not just EICAS, also MFD and PFD need improvements.

[xcvb85]

The last days I was working on a new canvas based PFD. I wonder if it is ok for you if I add a new screen to the Flightdeck11.ac or if I should wait until you finished your great work on the overhead panel.

[HHS81]

I think it is o.k., I will keep the screen objects name. I fihured out some days ago, that we will need two pedestal. One for the prop, one for the jet as both quite differs.

[xcvb85]

Does this mean no ALS shadows on pedestals? I guess ALS shadows on pedestals would be more important than ALS shadows on overhead panel.

[HHS81]

I'm not sure yet, I have to experiment

[xcvb85]

Damn, I have to recreate the RMU from scratch. Currently nothing is working anymore but at least I got rid of all this chaos.

[HHS81]

Why? What happened?

[xcvb85]

The guys from the Citation X did all the logic in the xml file but the problem is that the buttons are not bound to a certain functionality. Instead the functionality is depending on which page is shown. So I must bring all the logic from the xml file to nasal files if I don't want going nuts. Actually it's not that big deal so don't worry but it will take some time.

[HHS81]

Isn't it what the real RMU does? confused

[xcvb85]

Why did you close this? EFIS is far from being complete. My intention was to activate the DME button to be able to set DME to a different frequency than VOR (like on Tu154). It could be that there is a way implement that as further condition in the rmu.xml file but I decided to set up a clean solution in Nasal where I can also have different pages like on MFD or EICAS.

[HHS81]

Sorry, by accident closed. The Manuals for the jet also mentions the RMU. Maybe there is something written. But it makes sense to set DME to another frq, since in RL not every VOR has a DME.

[xcvb85]

No problem. To have the possibility to set VOR and DME to different frequencies is not very common (Tu154 also allows this) even if it seems to be useful in some situations. The documentation regarding the DME button is very short ("it de-slaves the DME from active VOR") but in this picture it is obvious what happens (normal mode left, DME mode right): http://cdn-www.airliners.net/photos/airliners/7/3/6/0084637.jpg?v=v40 It seems that in DME mode you can only change the DME frequency but no longer the inactive VOR frequency. Nevertheless exchaning active and inactive VOR frequency could still be possible.

[xcvb85]

Basic RMU functionality working again (special stuff like "DME" or "1/2" buttons still missing). Now I can set e.g. ADF1 on RMU1 and VOR2 on RMU2 and activate circle and rhombus needles on PFDs:

In addition vspeeds are correctly shown depending on selected mode.

[HHS81]

Looks great! 👍 Makes me make work harder on the cockpit!

About the VSpeeds: As I understood according this source the FMC uses the weight and fuel inputs from the CDU and calculates the VSpeeds for Takeoff and Landing. (Not sure yet if OAT is also used...)

I think it is easier to use JSBSim to create a table which outputs the values for the MFD. I also think it more perfomance friendly.

So we could make (force) the users input the fuel and payload via the CDU theirselfs instead automatically by FGFS, JSBSim will calculate the correct VSpeeds and Vref depending on fuel consumption.

Do you agree? And if yes, where should those properties (Vspeeds) go into?

[xcvb85]

Looks great! 👍 Makes me make work harder on the cockpit!

Sounds good. I would also appreciate a non-perfect overhead panel 😄

So we could make (force) the users input the fuel and payload via the CDU theirselfs instead automatically by FGFS, JSBSim will calculate the correct VSpeeds and Vref depending on fuel consumption. Do you agree? And if yes, where should those properties (Vspeeds) go into?

Currently VSpeeds are calculated based on the weight in Nasal/vspeeds.nas. It's just a 3rd order polynominal through the data in your readme. If you have a better solution please let me know. Vmin and Vmax based on weight and flaps are missing but this is what I need for the red warning lines.

[HHS81]

Oh... wow! I just edited your posting accidently. Sorry, that should not be possible. I corrected it

[HHS81]

O.k. , again.

I will just simply add a table in the jsbsim file based on input given by the user and the various flaps settings, that is less perfomance heavy than nasal as it interpolates the values. With that we can easily also add Vmin and Vmax and other speed limits. Let me know which limits you need. (I think Vmo, Vne,...)

[xcvb85]

Warning lines: VMIN/VMAX T/O: V1, VR, V2 CLIMB: VCL CRUISE: VC, and as I already told you in the questions that I don't know the other two (3rd maybe VSTD) LANDG: VFL0, VREF SINGLE ENGINE: I have no idea

Jet version has different ones e.g. "T/O SPD" and "T/O PWR" -> have to check

[HHS81]

o.k., CLIMB and CRUISE will be set by pilot himself via CDU. CRUISE I guess will be VMO and VNE, I have to check

[xcvb85]

Finally found out what happens if you press "PGE" button:

These entries are missing on Citation X: NAVIGATION: Simple ND ENGINE: Simple EICAS

[xcvb85]

Just a short update:

ASTROTECH LC-60 CHRONOMETER not yet working.

[HHS81]

Cool! For the later shadow works in ALS I need the faces of these models included in the main panel mesh. I would uvmap them together with the main panel.

Do you mind it?

[xcvb85]

I know that we must do it this way. This is why I think that we need two cockpits for prop and jet because if we include different pedestals or overhead panels via xml files we will loose ALS shadows. At the moment I'm not really working on RCU and clock. I just adapted the RCU from Citation X (again not the best implementation) and I wanted to have something in the place of the clock. Currently my main focus is the RMU but it is quite complex and it will take some time until I implemented all the missing features.

[xcvb85]

The biggest performance issue is still the map framework on nd-page. I will try to optimize it further.

[xcvb85]

Weather radar working now:

MFD zooming and hideable waypoint identifiers:

[xcvb85]

CRT shader:

[xcvb85]

Ouch! Don't worry. I won't upload this. :smile:

[HHS81]

Why not? It is not a bug - it is a feature!😁

[xcvb85]

I had a better idea. Dirty screen with fingerprints: I didn't found a free fingerprint texture, so I will create one on myself. I also found a solution for the scanlines. The screen flickering effect and the reflections still need some work. Maybe the frame and the barrel distortion effect can be combined.