Fouga

Thank you for your answer Holbeach, I also found some 2016 discussions, including RaZbam team, stating that even without any visible impact on Runways after cluster strike, they were actually disabled for a limited time. This lack of visual effect is in fact quite old... Damage assesment is a bit more difficult this way.

Hi All, I am currently working on additional weapons for some french airplane MOD... to roughly simulate the APACHE anti-runway cruise missile. I modified some cluster/bomblets dispended from a cruise missile or glide bomb (Like AGM-154B or GB-6). I limited their quantity and enhanced their explosive power in order to damage concrete sructures and runways. It works perfectly and the runway is localy disabled. But, as I use bomblets and clusters, I only get the "tiny" cluster effect in game : dust and light. How could I add some explosion effect and a remaining crater ? Thanks in advance.

If you export the TEWS view (on another screen or in a corner of your main screen) there is no cut off on the exported one.

Same for me !!! Thanks Dud' I think I tried everything written about this issue...

Here is a way to reproduce it : 1- Start 8.000m and go into a -30° dive 2- Once you reach M1.3 to M1.4 ... pull on the stick It works 100% since M1.3 with full or medium payload It also works with a slick plane with only 1T fuel at M1.4 Note : as there is no G limiter on MiG-29, this behavior does not seem to be unlogical to me. MiG-29A wings away M1,4.trk

+1 with all mentionned issues/requests. MiG-29 could be outsanding with those few improvements.

:clap_2: Thank you te remind us the Old good time ! Note : At that time ... these were "Modern Air Combat" planes. :pilotfly:

Any news on this long-time awaited function ? Waypoint number to be added to HUD in a future patch.

Thanks so much ED !!! Caucasus now looks awesome with same/better performances than 1.5.8 I love To fly low with the P-51 in winter & morning conditions along the coast.

MICA are broken from ... let's say 1.12.11 We had to rebuild one from scratch "using AIM-120C datas" to use it in a MOD.

Scary !!! :fear: For those who don't speak french : the RIO wakes the pilot and inform him they are diving inverted, shouting (gently) to recover the dive...

The answer is : there is no more altitude holding (only) autopilot.

Correct but ... on Czar66's pictures, you can see that both Radar & EOS are active. On the HUD, you have several indications : - EORL written on the left of HUD => means EOS + Radar are active - ILL is written below the HUD => also means Radar is active If you swith off the Radar (by pressing I), you will only see : - EO written on the left of HUD => means EOS (only) is active - No more ILL below the HUD And then, the friendly Su-27 target will become a Foe - possible enemy aircraft. Important to understand : IFF is related to the Radar (true at least for russian fighters). When you scan for targets using your radar, you have the IFF interrogation on any visible contacts. If the locked target is friendly, it will respond to your IFF device and you will get the round symbol on MFD + the AFR written on HUD + no LA at range. If the locked target does not respond, it will be categorized as possible hostile (Triangle symbol on MFD + A instead of AFR written on HUD + LA at range). Important to know : the Vertical Scan mode (or any Close Air Combat mode) only uses EOS by default. So IFF is off until you switch on your radar. Note : If you switch from BVR mode with Radar On to VS mode, the radar will remain On. So, to be sure not to kill a friendly, pay attention to AFR & ILL symbol on the HUD. If you have ILL symbol and no AFR ... then you are 100% sure.

If I remember well, thas was the case in the first Beta version of the new Su-27.

Imperial as well. We (French) use to say this about the British :D That's because bits & Bytes sounds the same in french :smartass:

Hi Trooper, 1- There is a specific key command to "Return to search" (by default : Backspace) and AFAIK you cannot "cycle" between different targets. After the unlock, you have to designate and lock again. 2- Depends on the type of missile's seeker. For the Su-27 and Su-33 you only have 2 types : - R27-(E)R are SARH (Semi Active Radar Homing) and they need you to maintain the lock until it arrives at destination. - R27-(E)T and R-73 are IR (InfraRed guided), they are fire and forget but may follow the wrong target if several heat signatures are too close (pay attention if your buddy is "Merged" with bandit)

In case of Engine failure (triggered with the ME), it is always accompanied by Fire which makes it more impressive, I love this effect :thumbup:. When the failure occurs, Betty informs you about the "left/right engine fire" and you can see scary flames and dark smoke coming out of this engine. After a moment, smoke and flames automatically vanish ; even after shutting down the failed engine (Idle & Alt/Ctrl+End), the fire warnings (betty + 2 warning lights) are maintained as long as you fly or have fuel to burn. Is the fire extinguished or not ? Does my lovely plane shall explode at any time ? (it never did due to an engine failure) If you trigger a failure of both engines, smoke and flames will only be removed from the first engine to fail and not from the second one. Is there a kind of "only one fire extinguisher system for both engines" ? In the future, will it be possible to manually activate such an extinguisher system in addition to the engine shutting down procedure ? If yes, would it be one for each engine ? And then, shall the Fire warnings switch off ?

+1

It seems that with the new PFM Su-27, there was also some modifications on the hydraulic systems logic : In case of Hydraulic failure (as defined in the ME), you rapidly loose any hydraulic pressure and can't move airbrake, flaps and any other control surfaces (on wings and stabilisers) which rapidly leads you to a catastrophic loss of control of the plane. That corresponds to a failure of both hydraulic systems. In the past, In case of Hydraulic failure, you were not able to move the airbrake and flaps but could always move the different control surfaces and get back the plane to an airfield. That was corresponding to a failure of one of the two hydraulic systems (assuming the flaps were controlled with the same hydraulic system as the airbrake). If you switch off or loose one (or two) engine(s), you will keep every system functional as long as it remains some RPM – which is the case while you are flying. After some tests on the ground, I concluded that : - the Hydraulic system #1 is related to the left engine and controls the nose wheel steering - the Hydraulic system #2 is related to the right engine and controls the airbrake - Both Hydraulic systems are controlling the different control surfaces including flaps To visualise the drop of pressure in those hydraulic systems, we are missing animated pressure gauges (they are always showing full pressure), I hope this will be added in a further update of the flanker. I also tested Hydraulic systems of the other DCS-like planes of FC3 : Su-25 & Su-25T loose their airbrake, flaps and nose wheel steering in case of drop of the hydraulic system #1 pressure. They will also loose the ability to release / retract landing gear in case of drop of the hydraulic system #2 pressure but they will keep their manoeuvrability in case of failure of both hydraulic systems – this might be because they are not using fly-by-wire. In case of failure, you can monitor the remaining hydraulic pressure thanks to the accurate gauges. F-15C only looses its airbrake and nose wheel steering in case of failure of both hydraulic systems, it cannot also retract the landing gear. But it will remain controlable as every control surfaces keep on working fine. Is this the case IRL ? A-10A doesn't loose any system in case of failure of both hydraulic systems.

According to the translated Su-27SK Manuel (available on the net), it should be : "the scale of angle of attack with the limiting values". It's used for both Take Of and Landing (LNDG mode).

+1

Hi Valium, It Might be easier. Try this : just change the line here after in the file "Script/Aircrafts/_common/CustomHuman.lua" If you want to use the Mig-29G (M2000-5) cockpit instead of the Su-27 (Rafale B/M), replace the line in "--AdA Mod planes" section : CustomHumanData[PlaneType.Su_30 ] = CWSType.iCWS_Su_27 By CustomHumanData[PlaneType.Su_30 ] = CWSType.iCWS_MiG_29G

FC3 is: MIG-29s (A and S) SU-27 ** SU-33 SU-25A* (not the same as the free SU-25T) F-15C* A-10A* Three of which have Advanced Flight Models already (marked with a *) One more at least is supposed to get "shortly" Advanced Flight Models (marked with a **)

Even if it is not a complete new bug, Russian Vertical Scan Mode has definitely lost it's Auto-lock with 1.2.7 => It's worth 1.2.6 : - With 1.2.6 you have to lock manually (only) one time and then, auto-lock is "activated" for the rest of the flight. - With 1.2.7 you have to lock manually every time ; no more auto-lock at all. See difference of behaviour in the same situation with the 2 tracks (1.2.6 & 1.2.7). Maybe I's not a bug but Auto-lock is still mentioned in the documentation and I did not noticed any change about it in the previous change log ... VS 126.trk VS 127.trk

Same as for briefing images ; all this stuff is integrated info the mission.miz file. Maybe you could use low quality sounds in order to avoid big files.