Automan

Is this problem fixed in latest edition of plugin? What is the best "safe" plugin to use for export?

The uninstaller is integrated in the MB-339 installer: 1-Double click the installer and go past the Disclaimer 2-Choose the DCS branch in which the MB-339 was installed (in your case Open Beta) 3-Thick "UNINSTALL MB-339A/PAN for selected branch" (in red) 4-Click PROCEED and confirm This will completely remove MB-339PAN folder from Mods/Aircraft, but the export.lua will not be touched and in case must be edited or deleted manually

Last value is for transparency range of the Alpha channel. for solid blue for example 0x0000FFFF Keep in mind that the value will blend with original png associated. A useful page for convert values RGB(A) to hex.https://kilianvalkhof.com/2016/css-html/css-hexadecimal-colors-with-transparency-a-conversion-tool/

No, I don't noticed the delay since I use manly the armed 339:D Btw, have you checked for changes in SmokeColor.lua and SmokeColorWindy.lua under Bazar\ParticleEffects\effects\ColorSmoke ? Those files are dated 20th December 2018, surely something was changed here.:joystick:

This was an example for white colour… other colours must have their proper code. For Red: '0xff0000ff' For Green: '0x00ff00ff' For 0x mean: https://en.wikipedia.org/wiki/0X …. a prefix for hexadecimal numeric constants in computing;)

Found a solution to fix this: now DCS use hex colour declaration instead of RGBA. So, for example to get white smoke pod, in lua under smoke-pod declaration replace PictureBlendColor={r = 255,g = 255,b = 255,a = 1}, with PictureBlendColor= '0xffffffff',

To load the alpha of your dds after Make Cool do these step: Double Click on your Map Bitmap Parameters: Monochannel Output --> Alpha Alpha Source --> Image Alpha Double Click on your Material Material Attributes: Misc --> Alpha Test Btw, for completely transparent not gradient(like empty space in a fence) sould be better use dxt1 +1bit transparency

Dardo è un utente attivo nella sezione in lingua spagnola del forum, presumo non sia italiano;)

Hi, this is the right procedure to install correctly the MB-339 in DCS 2.5.4: 1. Use the executable installer 1.02 2. Install manually the hotfix (MB-339PAN.lua) overwriting the 1.02 file. No other actions are needed, but as I've said, we have noticed some problems in coesistance of different mods, particularly in multiplayer. The HUD is part of the 3d model of the cockpit, and its visibility is commanded at mission start by the presence of live weapons or not: so if you select an A payload with gunpods or rockets you will have the hud, while if you select the PAN payload you should see it for a very brief time but then it will be unloaded(hidden). Unfortunately, if you select a payload with weapons during a mission it will miss the HUD loading: we hope to solve this someday About your dcs.log, I still see a lot of mods in Tech, btw next time should be better attach the file instead of post its text:D

Hi, do you have other mods installed? Please post your Dcs.log here, we can help you better.

Ho la soluzione al tuo problema: è un crash all'avvio dovuto al nuovo database che ha eliminato un riferimento a cui era linkato la nostra mod dell'Mb-339. Sostituisci il file originale della mod con quello di questo post: https://forums.eagle.ru/showpost.php?p=3727720&postcount=379

Posta dcs.log, con la diagnostica magari si capisce qualcosa;)

E' confermato il funzionamento del fix. In caso qualcuno abbia timore di scombinare qualcosa, posto qui un link al file già modificato da sostituire . Sostituire il file originale nella cartella MB-339PAN con quello allegato in questo post: https://forums.eagle.ru/showpost.php?p=3727720&postcount=379

Ok, just in case someone is scared to use editor, below is attached the file that must be pasted (confirm overwrite:D) in MB-339PAN folder. This will fix the DCS 2.5.4 crash;) MB-339PAN.lua

Credo abbiano rimosso o rinominato delle entry dal database. Nell' MB-339PAN.lua c'è un richiamo a materiale in uso anche dal C-101 che con la 2.5.4 hanno transitato all'AFM. Chi volesse provare a risolvere può editare MB-339PAN.lua, sostituendo la seguente riga Guns = {gun_mount("M_2_L1", { count = 0 },{muzzle_pos = {0, 0, 0}})}, con Guns = {}, Fateci sapere;)

Hi Magot, this maybe a rapid fix for the problem: open MB-339PAN.lua with an editor like Notepad++ and replace this line Guns = {gun_mount("M_2_L1", { count = 0 },{muzzle_pos = {0, 0, 0}})}, with Guns = {}, Let me know

Actually the backseat with F4 is a magnified external view: so you should thick the DCS Options “Trackir external views” under MISC to make it work.

Come dice Duke, in certe manovre e con condizioni climatiche particolari sono visibili;)

Testing EFM Since the start of this project the team was aware of the SFM limits. We feel the need to move to a more accurate FM and now some manouvers as Lomcevak are possible. We are just at the beginning and a lot of work is still needed, but we have some very motivated ( and talented) people in the team;)

Ragazzi, è un bug conosciuto dell’ultima versione: disabilitate scalegui per risolvere.

Si ci saranno aggiornamenti, ma il bug da te segnalato è già conosciuto: al momento però non c'è soluzione da parte nostra al problema. Diciamo che il bug è aggirabile pianificando in modo mirato le missione: ad esempio, evitando di iniziare la mix in configurazione clean o con loadout inoffensivi se si ha l'intenzione di effettuare rearming. La livrea PAN d'origine è in fase di lavorazione, ma per il tutorial non saprei...anche io sono poco preciso:megalol:

The mouse pointer in 4k resolution with ScaleGUI set ON is broken: it acts like moving in a top-left 1920x1080 surface enclosed in 3840x2160. I was able to uncheck the scalegui option, and now the pointer is in sync. btw, using the gui in 4k res on 28'' monitor without scaling requires binoculars:megalol:

Considering random read speed of NVME m.2 are about the double of an SSD of the same size, I would say 100% faster loading (half time).

Basically, the engine of DCS will load the roughmet for any model (even the not updated) when naming convention and correct folders location are correct. Have you tried to put the *NAME_OF_YOUR_DIFFUSE*_roughmet.dds in DCS folder's Bazar/TempTextures?

Tried inverting the cable as I've suggested? Set at Single or Multiple rail? Taken from the official corsair forums: