Automan

Verify in edm plugin options that export hidden objects is unchecked.

Hi all, Edm plugin released today should include 3ds max 2023 & 2024 support.

Hi, while we love mods, sometimes they conflict with official products, and this is the case: try remove the Eurofighter mod from your Saved Games and the problem should be gone.

You can set fps limiter to 30 in the preferences, and check "reduce fps when in background" too. This will help.

The forum section dedicated to MB-339 liveries is online now MB-339 - ED Forums (dcs.world)

Fixed internally. Hopefully solution included in next OB release

Una differenza macroscopica visibile all' esterno è la presenza delle formation lights, il resto è tutto dentro. Pre-MLU MLU: a primo occhio subito identificabili in quanto presenti le luci di formazione, ed il bacchettone dell'antenna ELT. Le 2 antenne sulla deriva sono posizionate più in basso, e la TACAN superiore è stata arretrata lasciando il posto all'antenna GPS (funghetto) Naturalmente la creazione di un argomento per le varianti è nata per venire incontro ai creatori di livree storiche o per quelle aeronautiche che a differenza nostra non hanno mai avuto in linea la variante MLU. Una nota a riguardo agli Emirati Arabi Uniti che hanno riconvertito il MB-339A a NAT per l'uso acrobatico degli Al Fursan: si tratta di pre-MLU revisionati e portati allo standard PAN con l'aggiunta delle sole luci di formazione ed il supporto al Quick disconnection per le taniche da 500(4 di questi sono ex-AMI), e pannello luci a parte il layout del cockpit e tutto il resto dell'avionica non ha subito aggiornamenti.

If you see the description.lua of the livery MB339A ITALIAN FACTORY, you can notice that there are a lot of entries that fallback to MB339 'Factory'. DCS during loading join livery folders of the main game with the one from Saved Games, so the fallback is perfectly working even from Saved Games/DCS folder/Liveries. I've included here a zip with a new decal livery as example, put in liveries of your Saved Games MB-339A.zip

@Snuten With wet runways you should always keep pushed relight button on your throttle. Page 145 of the Flight Manual (included in Docs) Take-off from wet runways Take-off from wet runways may result in compressor stalls or flame out due to ingestion of water splashed by the nose wheel into air intakes. To prevent such occurrences, following precautions should be taken: -Taxi at the lowest possible speed, avoiding puddles and water-covered areas. -During the take-off run and until lift-off, hold the “RELIGHT” push-button pressed. -Lift the nose wheel from the ground as soon as possible.

Posta qui il dcs.log che Provo a capire cosa non va nella tua installazione: se vedi le stesse cose poste nell’immagine dell’altro utente, ipotizzo un problema di conflitto con la vecchia mod(caricamento della vecchia texture) Put here your Dcs.log, maybe it’s loading some old texture from the old mod. A conflict issue I suppose.

I'm not the author of the missions but I would say the instructions should be revised. The BAP-100 we have done is the L65, the most used variant, calibrated for release at an altitude of 65m(200ft). The L80 is calibrated for 80m(250ft) release. According to the brochure of the constructor, the BAP-100 should be dropped in horizontal flight at very low altitude (65m) with a speed not exceeding 600kts. So, for aircraft without a firing computer like the MB-339, mantain the higher sustainable speed and just before passing runway threshold start the release sequence. For extended area denial, including taxiways and parkings, the best approach is crossing the center with multiple vectors. Ouadi Doum runway strike by AdA during Chad-Lybia conflict @beppe_goodoldrebel

@Santus faster than me eh The tip-tanks are not jettisonable, so they are included in the main external 3d model MB-339.edm. You can play with the slider of the argument 525 to switch between the visibility of two types of tip-tanks, elliptical and cylindrical.

Yes, I’m quite sure we must remove a 0 from the milliseconds of the delay range In RL the firing interval of the rockets is set on the launcher at ground and the settings depends by the intervalometer installed. Launchers with different intervalometers will have a different range of delay between the sequence of ignitions. Some of preset RL values: LR-25 and Matra 155 33ms LAU-10 95ms, LAU-3 40ms. Since we haven’t found a way to load dinamically the sliders with the right value during the loadout change accordingly to the type of rocket launcher, the best we can do would be modifying the range to 33-95, presetting a midrange value of 62.

Unfortunately seems that the some of latest changes we made, including static force and damping of nosewheel improvements, were kept out by the update of today. We hope to find a window for release the fixes again as soon as possible.