eurofighter typhoon

[Algernon]

Absolutely. Good stuff. I thought I'd read somewhere about some countries requiring a naval variant of the Typhoon, so perhaps eventually, if it happens, there could be one model with and one model without the arrestor hook etc.

We're quite looking forward to working on the Typhoon now, hehe I'm looking forward to the download, thank you very much in advance!

[almursi]

Hi, new realesed 1.3, DivShare File - etyphoon_carrier_1_3.zip



In this package include a kook improved, better fuel consumption ratio, and basic animation of slats and ailerons. The AFCS will wait for further review, because of the impossibility of adapting other models already made. It also features a Spanish livery, drawn from real models based on Moron and other details.

If I have (more) time, the working plan is:

Review 4: AP-AFCS, external lights, other external details
Review 5: Improve cockpit lighting, instrumentation

Regards.

[Algernon]

Fantastic, I'm going to take her for a quick spin now. A decent AFCS would be brilliant, and I'm about to start fiddling with MFDs myself so hopefully I'll be able to contribute to this project too. Here's hoping you get some free time!!

[Canseco]

Me gusta la nueva livery,

Thx for your efforts and keep up the good work.

[Avionyx]

Brilliant work, thanks for that!

Alex

[almursi]

Hi, thanks to examples on use FDM Yasim script in Blender http://www.flightgear.org/forums/viewtopic.php?f=4&t=8989&start=0&st=0&sk=t&sd=a, I could fix a problem in the FDM model.

The value to be changed, in wing section, is sweep = "53" to sweep = "30". With the old value the angle of the wing was like a rocket ... and now is possible to define the flap-aileron correctly.

This is wing section in typhoon-yasim.xml, that I'm still testing (and still not final version -may include a dual use of aileron and flap-):

Code: Select all

  <wing x="-9.525" y="1.184" z="-0.199"
        taper="0.185"
        incidence="0.0"
      twist="-5.0"
        length="5.1"
        chord="6.815"
        sweep="30"
        dihedral="0">
    <stall aoa="21" width="8" peak="1.3"/>
    <flap0 start="0.001" end="0.95" lift="1.2" drag="1.1"/>
    <slat aoa="6" start="0.0" end="0.813" lift="1.8" drag="1.7"/>
    <control-input axis="/controls/flight/aileron" control="FLAP0" split="true"/>
    <control-input axis="/controls/flight/aileron-trim" control="FLAP0" split="true"/>
    <control-input axis="/controls/flight/slats" control="SLAT"/>

    <control-output control="SLAT" prop="/surface-positions/slat-pos-norm"/>

    <control-output control="FLAP0" side="left"
                    prop="/surface-positions/left-aileron-pos-norm"/>
    <control-output control="FLAP0" side="right"
                    prop="/surface-positions/right-aileron-pos-norm"/>
    <control-output control="FLAP0" prop="/surface-positions/aileron-pos-norm"/>

    <control-speed control="SLAT" transition-time="1.1"/>
    <control-speed control="FLAP0" transition-time="1.05"/>

  </wing>


Regards.

[Algernon]

Perhaps this is the reason the aircraft seems slower to manoeuvre than similarly-configured aircraft such as the Rafale. If you've solved this, it will be my biggest concern about it well on the way to resolution! Thanks so much for your continuing efforts on it

[Algernon]

Perhaps this is the reason the aircraft seems slower to manoeuvre than similarly-configured aircraft such as the Rafale. If you've solved this, it will be my biggest concern about it well on the way to resolution!

Wow! It really does make a difference!!

[almursi]

Wow! It really does make a difference!!

Hi, yes, now is much more maneuverable. I've also changed some other values, to ensure that the engines give speeds Match 1.4 & 2.0, and other small details. It may cost me tune the AP, but at least with these arrangements seem less urgent . (I hope to have another review ready soon, although my time begins to sag )

Look at this value (under wing section):

Code: Select all

<control-speed control="FLAP0" transition-time="1.05"/>

If you raise to 1.1, it is even easier (thereby soften the control response), but you lose a bit in agility.

Regards.

[almursi]

Hi,

Release 1.3b - Fixed FDM
DivShare File - etyphoon_carrier_1_3b.zip

* Reason of this released is only for Fixed FDM (wing size, engine, etc.), but includes everything else due to constant changes in other developing parts.

* On release 1.3b animations (slats, stick, pedals, hook) are only basics
on working development (fixing textures, sizes, etc -while I'm learning to work with blender )
* No Flaps (at the moment -> only by AFCS control)
* Slats seem do nothing -> on development
* Autopilot only work Wing Leveler, pitch hold and Auto Throttle (without reheat)
* No new Livery (under GPL-copyright request) -> Edited: The livery of Moron is still there. What I've stopped has been the development of which I have half, and I should probably start from the beginning.

Regards

[almursi]

Release 1.3b - Fixed FDM

Hi, just I send the changes to GIT, the rest of the changes will have to wait (cockpit design is quite arduous ) and go far more slowly. I've seen the display problems in 2.0 are due to need of bitmap textures (or better bitmaps).

(I hope that I sent the changes correctly, when I have not a howto I am always in doubt ...
... and yes , with: git commit -a --author='Your Name <you@example.com>' )

Regards

[Algernon]

I haven't had the courage to start learning about GIT yet, but I have been doing quite well with sounds and should have a whole sound package to add to the aircraft very soon. What's the best way to go about submitting something, if I don't use GIT yet?

I think myself and another chap at least would be interested in helping out with the instrument design.

[almursi]

I haven't had the courage to start learning about GIT yet, but I have been doing quite well with sounds and should have a whole sound package to add to the aircraft very soon. What's the best way to go about submitting something, if I don't use GIT yet?

I think myself and another chap at least would be interested in helping out with the instrument design.

Hi, with GIT it's very easy . But first I need to make a little howto. We can have a branch (another that master fgdata) to synchronize the changes that we will do (and merge changes when work is more advanced). In fact just as well that you mention it, because I had begun to change the sounds, so I can work in another aspect. I'm actually seeing how I can set up branch in git, so in one or two days I tell you .

http://gitorious.org/~almursi/fg/almursis-fgdata (Edited: may be better to rename typhoon-fgdata ? I'm going slowly, but I think in two days I can do the howto for collaborations.)

Regards.

[Gijs]

For Windows, there is a FlightGear-Git tutorial available at the wiki since this week: http://wiki.flightgear.org/index.php/Fl ... ng_changes
It is quite a long list, but when you are used to it, it doesn't require much actions. Others OSs won't be much different, they'll just require different Git software.

Btw, nice job on the Typhoon

[Algernon]

I really feel this aircraft moving ahead now. almursi, if it's alright with you I will continue with the sound package, and also, would it be okay to tackle the Nav Lights? I want a small, simple modelling/texturing/animating excercise to learn on and I think that's about the right size job! I could also do the afterburners while I'm at it. What do you think?

I'll certainly read the GIT article on the Wiki, and try and get up and running with it. Compiling and the like has never worked very well in my head, but I'll have a crack at understanding how to use GIT cos I'm sure there are some cool things in that version not in FGFS 2 which I use. Thanks for the link!