hhs81 / do328 Goto Github PK

• reduce amount of duplicated code (prop/jet)
• remove unused code (moved to folder 'Unused')
• fix jet version issues

Update the shader to the improved uber-shader

CDU has issues if you try to save the flight plan.

half rain bug (rain appears only at one side)
fixable by changing the RMU-model to the one used by Pattens CitationX

Not sure if they should just be black when switched off or if we should add reflections like on CitationX. I don't know if the screens are reflecting at all.

on both the prop and the jet version

@HHS81: I already got CDU from CitationX running but unfortunately I mixed things with EICAS. Please merge branch issue17 then I can commit the fix.

Dornier 328 has six and not only two fuel tanks.

Development of EICAS

Fix exterior lightmap due to former changes to UVMap

Can be fixed by changing properties in STBYai.xml to "orientation/pitch-deg" and "orientation/roll-deg".

I guess it is a good idea to make a list about what is missing for a 1.0 Version which can be uploaded to fgaddon. Please feel free to edit this.

Mandatory:

• Overhead panel
  • Fix text positions
  • Circuit breaker texts prop
  • Circuit breaker texts jet
  • Button icons
• New cockpit model
  • Yokes
  • Modelling
  • UV-Mapping
  • Texturing
• Sound improvements
• Fix Bugs on model
  • Add a simple cabin
  • Close gaps at rudder
  • Fix position of lights
  • Close gaps at gear
• Better EFIS
  • Better PFD
    • Correct FMS Indications
    • Correct NAV Indications
  • Better MFD
    • Zooming
    • Correct Speed, Heading, etc. Indications
    • Weather Radar
    • Vertical Path Display
    • Settings (Softkey Menu)
  • Better EICAS-Prop
  • Better EICAS-Jet
  • System Pages 12/12 (sensors page unknown)
• Better Autopilot
  • Better controller
  • New GUI dialog
  • Integration into cockpit model
  • Correct AP modes on PFD
  • All AP modes working
• Better Electrical system
  • DC-Bus
  • AC-Bus
• Better RMU
  • Frequency saving
  • Flight Id

Nice to have:

• Better systems
  • Pressurization system
  • Hydraulics system
  • Air conditioning (ECS)
• Better FDM
• Better RMU
  • TCAS display
  • DME de-slave mode
  • FMS autotune
  • POST/PAST Tests
  • MLS dummy page
  • Squelch
• Pushback Truck

The slowest you can drive on the taxiway without braking all the time is about 70 knots which is quite quick.

Citation X is required for MFD screen.

Use the one from Pattens Citation X, but:

• remove Autothrottle, as the Dornier 328 TP and Jet never had any Autothrottle. The needed throttle settings are indicated by bugs on the Torque indicator and driven by the FlightManagementComputer

Rearrange flightdeck:

• remodel ceiling
• correct dimensions of RMU inlet at the center pedestal
• fix texture of flap indicator at center pedestal
• combine into one mesh
• more detailed walls
• retexture in less textures as possible (like c182s)

then add Overhead Panel Issue #1

To remove the bouncing of jet version after replay I replaced the jet fdm with the prop one (other engines of course).

I wasn't happy with the gear spring and damping coefficients. Now they are a bit stiffer and should show a more realistic behavior.

Please insert this and test:

<contact type="BOGEY" name="NOSE">
<!--structure by Michael Soitanen, coefficients by Heiko Schulz-->
   <location unit="IN">
     <x> -343.49 </x>
     <y>   0.00 </y>
     <z> -11.74 </z>
   </location>
   <static_friction>  0.80 </static_friction>
            <dynamic_friction> 0.50 </dynamic_friction>
            <rolling_friction> 0.02 </rolling_friction>
            <strut_force>
                <function>
                    <sum>
                        <product>
                            <value>-1</value>
                            <table>
                                <independentVar>gear/unit[0]/compression-ft</independentVar>
                                <tableData>
			0       0
			0.65   600
			1.3     45500
			1.31    49000
                                </tableData>
                            </table>
                        </product>
                        <ifthen>
                            <ge>
                                <property> gear/unit[0]/compression-velocity-fps </property>
                                <value> 0.0 </value>
                            </ge>
                            <product>
                                <value> -1100 </value>
                                <property> gear/unit[0]/compression-velocity-fps </property>
                            </product>
                            <product>
                                <value> -2600 </value>
                                <property> gear/unit[0]/compression-velocity-fps </property>
                            </product>
                        </ifthen>
                    </sum>
                </function>
            </strut_force>
            <max_steer unit="DEG"> 10 </max_steer>
            <brake_group> NONE </brake_group>
            <retractable>1</retractable>
        </contact>


  <contact type="BOGEY" name="LEFT_MAIN">
<!--structure by Michael Soitanen, coefficients by Heiko  Schulz-->
<location unit="IN">
     <x> -54.044 </x>
     <y>   -63.39 </y>
     <z> -9.11 </z>
   </location>
   <static_friction>0.8</static_friction>
   <dynamic_friction> 0.5 </dynamic_friction>
   <rolling_friction> 0.02 </rolling_friction>
           <strut_force>
                <function>
                    <sum>
                        <product>
                            <value>-1</value>
                            <table>
                                <independentVar>gear/unit[1]/compression-ft</independentVar>
                                <tableData>
                                    0       0
                                    0.042   555
                                    1.30  50500
                                    1.31    65000
                                </tableData>
                            </table>
                        </product>
                        <ifthen>
                            <ge>
                                <property> gear/unit[1]/compression-velocity-fps </property>
                                <value> 0.0 </value>
                            </ge>
                            <product>
                                <value> -2500 </value>
                                <property> gear/unit[1]/compression-velocity-fps </property>
                            </product>
                            <product>
                                <value> -3900</value>
                                <property> gear/unit[1]/compression-velocity-fps </property>
                            </product>
                        </ifthen>
                    </sum>
                </function>
            </strut_force>
   <max_steer unit="DEG">0</max_steer>
   <brake_group>LEFT</brake_group>
   <retractable>1</retractable>
  </contact>

  <contact type="BOGEY" name="RIGHT_MAIN">
<!--structure by Michael Soitanen, coefficients by Heiko Schulz-->
   <location unit="IN">
     <x> -54.044 </x>
     <y>   63.39 </y>
     <z> -9.11 </z>
   </location>
   <static_friction>  0.8 </static_friction>
   <dynamic_friction>0.5 </dynamic_friction>
   <rolling_friction> 0.02</rolling_friction>
           <strut_force>
                <function>
                    <sum>
                        <product>
                            <value>-1</value>
                            <table>
                                <independentVar>gear/unit[2]/compression-ft</independentVar>
                                <tableData>
                                    0       0
                                    0.042   555
                                    1.30   50500
                                    1.31    65000
                                </tableData>
                            </table>
                        </product>
                        <ifthen>
                            <ge>
                                <property> gear/unit[2]/compression-velocity-fps </property>
                                <value> 0.0 </value>
                            </ge>
                            <product>
                                <value> -2500</value>
                                <property> gear/unit[2]/compression-velocity-fps </property>
                            </product>
                            <product>
                                <value> -3900 </value>
                                <property> gear/unit[2]/compression-velocity-fps </property>
                            </product>
                        </ifthen>
                    </sum>
                </function>
            </strut_force>
   <max_steer unit="DEG">0</max_steer>
   <brake_group>RIGHT</brake_group>
   <retractable>1</retractable>
  </contact>

Here we can ask questions. Maybe someone knows the answer.

Unanswered Questions:
3.) Q: What is shown on MFD page "MAIN 2/2"?

Answered Questions (answer not sure):
1.) Q: How can I change the PFD styles (V-Bar and Cross-Bar Format)?
1.) A: I can imagine that for security reasons this must be done by the mechanics on the ground and that there is no way to change that by pressing a simple button. We could change the style depending on the selected livery but this is of course very low priority.
4.) Q: What is the content of "REF DATA"->"CRUISE"?
4.) A: VMO and VNE

Answered Questions (answer sure or almost sure):
2.) Q: Why does the DO-328 has a TOGA button although it has no autothrottle?
2.) A: When the TOGA Button has been pressed the Bugs on TRQ gauges will be set to TO Values. I will send you an flight test report, where this Feature has been mentioned.
3.) Q: What is shown on MFD page "MAIN 2/2"?
3.) A: There must be at least "MAINT" (=maintenance, see exceedance page, standard specification p. 31-23)
5.) Q: What is the function of the small lever on the left and right panel, beside the mainpanel?
5.) A: Should be Air conditioning, the texts are "AIRFLOW" and maybe "FEET" (pull the lever if you have cold feet)
6.) Q: What is the correct color (hex value) of the MFD/EICAS-lines (currently #00ffff in issue17, before #3282dc)?
6.) A: #55bbee

Needs a change in the uvmap without breaking the current liveries (luckily easily possible!)

Maybe we can get them from other aircraft but not sure which one.

Something like this is what I had in mind:

Please let me know if you like it or if you have a better idea.

The Thrust reverser is secured in a special (and sometimes fatal! )way. You have to disengage a lock latch to reach beta range and reverse thrust range. When the lock is not properly disengaged, engines remain in psoitive thrust range - led to many accidents!

Disable Cabin View until Cabin is made

The Dornier 328Jet don't have the ability to pushback on its own like the Dornier328Prop.
I found a image on airliners.net, which shows how a Dornier 328Jet is pulled by a Towbarless Pushback truck Goldhofer-Schopf AST-3.

• create 3d-model of AST-3, and a smaller Towbar truck

• animate pushback, with simulation of lifting the nosegear by using the collision (HOT) feature
  EDIT: collision (HOT) feature broken in 2018.1

add textured 3-model of the Overhead panel

Steps to reproduce: Start the do328 in Flightgear 2016.3.1 on Linux (not tested on other os), select "stormy monday" weather and wait for about 1min. Then the aircraft jumps around and in bad cases it flips on its roof. This only happenes once and it never happenes if you start in the air. This issue does not occur in Flightgear 3.4 and I'm pretty sure that this is a bug in Flightgear itself and somehow related to this:
FGMEMBERS/ATR72#1
But there is one difference: Unlike ATR72 you don't have this problem during take-off if the weather is fine.

Hope this will be useful to you.
LC60_clock.zip

Added additional text.
Add slight bevel and button recess.

Here we can add new liveries.

The following systems need improvements:

• Pressurisation System
• Electrical System

Especially the Do329Jet needs sound improvements. GabrielYV sent me a PN in the Flightgear forum and offered is help. @HHS81: Is it ok for you if GabrielYV works on the sounds?

Only in 328-110 (prop) version.

Required for jet version.

Since Thorsten Renk pushed the final fix for the grey-reflection issue to FGData today, the refl-type is now obsolete on the livery-files. It can be removed for the upcoming FlightGear releases 2017.2.x

write short wiki entry here, and update FGFS-wiki

Osifont is a good starting point but especially the numbers need to be improved.

and add ALS lights by using the one from the Cessna 182S
See also Issue #67

To me it seems the ailerons have very little authority, though that's subjective, do you know whether it's a bug or a feature?

add paintkits for Gimp and Inkscape

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.

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

Currently there are three different variants how to name the two versions:

Do328-1XX/3XX - e.g. readme
Do328-110/300 - e.g. set-file and menu name
Do328/Do328-JET - e.g. splash screen (planned)

My suggestion is only to use Do328/Do328-JET which is less confusing for people not familar with the aircraft. I don't know if you had planned to distinguish between minor versions 100/110/120/130 and 300/310. We could add a menu where this can be defined like the different wheels on c172.

Adjust power curves, as it still has too much power / thrust at certain flight states. (sinkrate at Idle still to great)

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

Add textured 3D-model of the yokes.

add stall behavior to fdm, so aircraft will stall and spin at known speeds

Hi!
Changing the path from
Aircraft/do328/Models/Flightdeck.xml
to
Aircraft/do328/Models/flightdeck.xml
in the model .xml makes the flightdeck appearing also for linux users (which is very strict about correct lower/upper case).
LG

use real life measured coefficients from:
Brockhaus, R. (2013): Flugregelung. Physikalische Grundlagen. Mathematisches Flugzeugmodell. Auslegungskriterien-Regelungsstrukturen. Entwurf von Flugregelungssystemen. Entwicklungslinien. Springer Verlag Berlin Heidelberg GmbH