guuruu

Dec 7th 1941, Hawai ;-) .................................................................... Sep 31st 1940, late afternoon 303 on its first operational sortie

corrected vortex ...

Don't worry Master, there is 0% of risk, that she can login again. But if she can, my advice is "marry her', she is like Einstein, Zweisteint and Dreistein together .

Your planes aren't perfect Master. This is next level over 'perfect', I must think to name this level ;-)

Sure, navigation lights don't need 3d model. First you must add light to correct plane part. For example: [Fuselage] SystemName[next_number]=TopFuselageLight or [LeftOuterWing] SystemName[next_number]=LeftPositionLight Then we will need light description: // Lights --------------- [TopFuselageLight] SystemType=LIGHT Color=0.98,0.5,0.5 Brightness=0.05 Position=0.0,-0.35,0.92 LightSrcOffset=0.0,0.0,0.0 LightSrcRange=0.5 CanFlash=TRUE FlashTime=0.70 [LeftPositionLight] SystemType=LIGHT Color=0.98,0.5,0.5 Brightness=0.03 Position=-6.48,-1.95,-0.14 LightSrcOffset=0.0,0.0,0.0 LightSrcRange=0.5 CanFlash=FALSE If we have 3d model of plane, we can read light positions from one. But probably you haven't it, so you must experiment with correct positions.

Gear up ...

Just nice photo, test flight.

New HUD .

Cockpit under reconstruction. 'I'm the passenger' version 0.01 beta ;-)

I'm not sure, but think it's weapon type.

Smoothing.

will try this way ;-)

Ok, some explanations for these settings. These 4 things are like ReleaseRange. In fact they are angle of approach to drop. RollInAlt=870 RollInRange=10000 PullOutAlt=409.7 ReleaseAlt=410.5 And this is guarantee of correct alt and speed of drop. If it's lower speed can be too low to hit target. Plane is loosing speed when turn back. RollInRange=10000, SecondPassRange=10000 And this is insurance for some attack parameters deviations . ReleaseCount=2 ReleaseInterval=0.25

I know, this is only emergency solution ;-) Tried with same datas as for level bombing. It doesn't work. He is flying too slow and droping bombs with ... hmm, random AimPitchOffset ;-) He can drop 1 km before target or drop all left 6 bombs after target ;-)

Yeah, I know . I tried and all attacks are ok, but if AI decide to dive bomb there is no way to stop him. He will always slow down and climb . I tried to set some idiotic distance for dive bombing like 300 km, but AI will rather try fly away this 300 km than use level bombing ;-) So my question is rather .. 'Where is limit of idiotism, that AI will switch to level bombing ?' ;-) Below are my settings after HOURS of experiments . Level bombing is really cool. He is flying almost 500 kts at 700-900 feet and hitting with sniper accuracy . [RocketAttackAI] RollInAlt=800 RollInRange=10000 SecondPassRange=10000 ReleaseRange=6000 [DiveBombAI] ReleaseCount=2 ReleaseInterval=0.2 AimPitchOffset=3.0 [LevelBombAI] RollInAlt=870 RollInRange=10000 PullOutAlt=409.7 ReleaseAlt=410.5 SecondPassRange=10000 SecondPassAlt=800 ReleaseCount=2 ReleaseInterval=0.25 AimPitchOffset=2.4 [StrafeAI] RollInRange=5500.0 RollInAlt=1350 PullOutAlt=80 ReleaseRange=1800.0 SecondPassRange=4500.0 SecondPassAlt=1350 ReleaseCount=0.15 AimPitchOffset=-1.2

I wonder if it's a way to disable AI to use dive bombing. I hate watch Tornado AI dropping bombs as they should (low and fast) then going hi and slow like idiots .

Not a real camo, only specular and glossnes test, but it starts to look coll ;-)

Templates, templates, templates ... slow forward ;-)

Sure. Not only GR.4, they will be available for GR.1 too. They used them since around 1990.

Finished arming system . If you have any sugestions, pls send me PM . RAF GR.1 ECM and flares dispenser are always loaded and there is no option to change it . 8 x freefalls or BL755, 2 x tanks, 2 x JP233, 2 x ALARM, 2 x Sea Eagle (GR.1B), 1 x WE-177, 4 x LGB 2 x tanks, 2 x ALARM, 4 x freefall or BL755, 2 x LGB 2 x IRM 2 x IRM or 2 x ALARM recon pod, ALARM, laser designator

B-52 ;-)

I must buy bigger glass .... Grats VonS ;-)