Search the Community

Dear Community, Every time I export a 3D model from Blender [currently: Blender 4.2.1 LTS] using the official Blender plugin from ED [currently: edm_tools_blender_plugin-241504.zip], I encounter the following issues: The Roughmet texture is not listed under textures in the model viewer. The textures in the model viewer are simply scaled down. Normally, the main texture (excluding glass surfaces) has a resolution of 4096 x 4096. When I check the mapping box, the UV map does not appear. In the model viewer, mipmaps are scaled down, causing the UV map to no longer align with the texture, resulting in red edges (red is used for visualization). Section of the uv-map in blender: In my graphics software, I have extended the borders by 8 pixels around the UV seams to allow for enough tolerance. Seam margin of 8 Pixel (vector graphics program): When I zoom out on my model in Blender, no red edges are visible, meaning the UV map and textures match. The exact same issue occurs with all other 3D models I’ve exported from Blender. Screenshot Blender 3D viewport (Render): I suspect an error with the export plugin. Can anyone explain why these errors are occurring? Thank you in advance. Cheers Homelander

Does anyone have a working version of the EDM tool for 3ds max 2020/2021? or what versions works for you? I have the link for the FTP but can't find one that works with my 3DS Max.

Hi, I am working on a mod for DCS that requires building a model and then exporting it. I have the model in 3ds Max 2020, and I have tried several different versions of the EDM Plugin (including the most recent one) and none of them have succeeded in exporting a .edm file that can be read by ModelViewer2. At this point, I am pretty sure the problem is with the plugin, and not my 3ds Max install. Does anyone have a sure version of the plugin that they know 100% works with Max 2020? If so, could you please attach it, or tell me where to find it. Thank you so much, Armada

Hi, I've developed a new plugin for the F16 & FA-18 which is working with VoiceAttack (32/64bit Full versions only) You can see a demos here, JanJan DCS Demo1 JanJan DCS Demo2 Dynamic Phrases PopUp Planner Phrase Filter Dynamic Phrases It has over 50K commands. Download from JanJan discord server It can do the following: Vocal commands to control the entire cockpit. Perform ALL the radio communication commands you can say: Flight, attack air defenses Texaco, request rejoin Inboud for landing Checkin 15 minutes Ready to copy ...all of them Commands to control external views. Control the simulators and more. In addition, and this is the main strength of this plugin, it has other special complex command to perform other tasks. E.g.: Set ILS to any airport you select without specifying the frequency. After 'selecting' the airport you can ask for it's available runways and say set ILS for runway 26 left say Set TACAN frequency. Either set Tblisi tacan or set tacan channel 126 yankee followed by set tacan mode air/ground Set HSI course Set Backup UHF frequency Ask for a vector to the nearest airport Report external/Internal fuel level Set Com1/Com2 radio frequencies Set QNH Set and tune illumination for all available instruments Show/Hide and toggle kneeboard I also added many dynamic checks e.g.: Check that fuel flow is below your threshold value Verify airspeed is below your threshold before lowering the landing gear Verify speed brakes are closed Below are just a few of the complex commands: null JanJan_VA_plugin_for_DCS.pdf RECENT UPDATES 1.1.4.0 * Fixed bug related to user key checkbox. * Added missing dcs-bios files which are needed for it's operation. 1.1.1.8 * Adding config option to run FLCS bit test during startup. * Adding command to set laser start time, if you think 5 to 30 sec is not enough let me know, *set [laser;tgp] start [time;] [5..30][seconds;]* * Fixed MFD loading sequence - once in a while the F-16 MFD code gets updated, which effects the MFD commands. 1.0.35.0 * Adding an option under *Commands* Tab to use 'recenter VR Headset'. This will stop the view from recentering every time the plugin tries to 'press' Num5. See doc or tool tip for further instructions. * Fixing command parser which may have not read commands from general keyfile properly. 1.0.34.0 * **Adding Mariana Islands Support** * Fix bug when reading keyfiles * Updating/fixing typos in commands 1.0.33.0 * Fixed model not selected properly on fresh install * Fixed DCS export when variables are not defined 1.0.32.0 * Update profile * Update DCS-BIOS version * Fixed but with prevented reading data in 2.72 from ramp 1.0.30.0 * Supporting VAx64 1.0.10.0 * **Adding support for the 'Filter Phrase' command in 3D including VR.** * See plugin doc for this new feature and how to setup & enable it. * Modified *Show comm menu* command to prevent possible bug when using VAICOM * Saving selected option for Backup tab in Config Form * Adding config options to specify DCS saved game folder * Added vocal notification to set laser code

My idea would be that a 3rd party, like all of us scripters / mission creatives here, would be able to write a 'plug-in' that would add a new CONDITION or ACTION to DCS. These would be bundled with DCS in each update as new ones are submitted and vetted by ED. That way, new mission editor features would be available to all players and would no longer require the general user to learn lua. All that work will have been done by the plug-in author. They could have a different colour or an asterisks in front of them, telling users they are from a 3rd party not ED in case they only want to use vanilla CONDITIONS/ACTIONS. However if the 'plug-in' api and submission process was rigid and thorough enough then there could be no distinction between any of them. What this would allow is that rather than waiting decades for a new CONDITION i.e. Group's Altitude AGL above Limit, a scripter could write, using the DCS Scripting Engine code alone, the code for that, and then everyone can take advantage of it. It would negate the need and complexity of 3rd party super-scripts like MOOSE and MIST and the problems that come with them, because at the end of the day, everything any script can do, will be done via the DCS Scripting Language code. These 3rd party script libraries just obfuscate and work as facades for the DCS SL and add additional features by doing all the legwork for the end user's benefit. Having M.E. Trigger plug-ins would give EVERYONE the power of these scripts, in bite-size atomic CONDITIONS or ACTIONS and thusly relieving some of the pressure from the M.E. devs to add this stuff as they work on more larger and general improvements to DCS. What do you think? @Flappie Is there any way you could make sure the M.E. devs or people who do planning could see this please? I know it's a big ask, but this would radically expand the Mission Editor and mission capabilities for all players, without having to learn lua or scripting or use 3rd party libraries. Thanks.