sa63114200

My issue, turns out, goes beyond this model. I get this error even with the most basic object! When I create a simple box, assign texture/material, Make Cool and try to export it, I receive the same message. Obviously, there must be something either in the plugin (version 204048), or my 3ds Max 2020 setting - which is vanilla straight after a fresh install - but I cannot figure it out. I am stuck here until I can get passed it. Any ideas? I would really appreciate it.

I am new to 3DS Max 2020 (beginner level), and as my first project, I am simply trying to export a paid model without making any changes into .edm format. Unfortunately, I cannot get passed this error! I have come across the Beginners Guide to DCS World Aircraft Mods which states: "...create a bounding box around the aircraft using a dummy object and use scaling to size it to fit the aircraft. Make sure the landing gear extend outside the bounding box and set a user defined property of: TYPE = “bounding_box”; You will not be able to export the aircraft with bones until this is done." I have managed to create a box named Bounding Box with user defined property of 'TYPE = "bounding_box";' I tried both cases where entire plane is inside the box as well as when landing gear extends outside. The 'Make Cool' step is done as well. Still, this error persists when trying to export it! What am I missing? I'm sure this is due to user error, but need some expert advice to get me through. Thanks.

My fictional skin for IRIAF is available. You can download it from: dropbox.com/sh/pefys8tdgqmqee1/AAA76Rwz_h_Kc33qKZbckpcLa?dl=0 To install, add "Iran" to the country list at ~\DCS.openbeta\Mods\aircraft\Su-30MK\Entry\Su-30MKI.lua file. It should look something like: Countries = {"India", "Russia", "Iran"} Note that although I chose the MKI, but you can install as any variant.

And I have been twiddling my thumbs waiting for it Much appreciated. This great module deserves great skins.

It's been few weeks since the release. Do you have a timeframe when the paint kit will be available? I hope it's not too far off.

Absolutely correct. This may be the preferred way of doing it. Thanks. So there are two ways of doing it, as you have seen by reply from grishik. However, there are pros and cons to each method. If you do not have a whole lot of modules that require change such as this, and your intended module is stable enough that you don't have to come back and re-add the line after module update, then this simple edit is to way to go. But, if you do, then updating one db_countries.lua file in one location may be preferred. To give you an example, Iranian tankers are 747 and 707, which do not exist in DCS. So I use KC-135 AI instead. Instead of editing the DCS AI config after each release, I add another line to the db_countries.lua file. Of course because I have a bunch of other assets that I need to make such a modification, instead of modifying ten files in ten different locations (which I need to keep track of), I have written a simple script that will copy my master db_countries.lua file with all the necessary lines for me. All I do after a DCS release is to click on a shortcut on the desktop and I am good until the next release.

If you have BVR mapped to your Hotas, then pressing that button will unlock your target and you can proceed to lock a new one.

Thanks Kim. I chose the MKI variant, but this skin can be applied to any variant. For installation, - Download and unzip the "Su-30MKI.rar" file and move the "Su-30MKI" folder to your ~Saved Games\DCS.openbeta\Liveries. - Open the "~\Eagle Dynamics\DCS World OpenBeta\Scripts\Database\db_counties.lua" file using Notepad++. Add this line "cnt_unit( units.Planes.Plane, "Su-30MKI");" under the "local units = country:get("IRAN").Units" (run a quick search to find it) - In the Mission Editor, you will see the skin called "IR IRIAF 3-8214" under Iran. The only issue is that after each DCS update, the db_countries.lua file is reset, so you need to either, add the line again, or simply copy a backup of the file to that location (which is what I do) to see the skin in the mission editor. But, to only use the skin in your defined missions, you don't need to have the line present in the db_countries.lua file. Hope this helps.

Given the speculation that Iran is interested in buying Su-35 and/or Su-30, I was keen on making a fictional livery for IRIAF when this module came out. Since no exact timeframe has been given for the paint kit, I went ahead and did a quick/dirty skin to fill the gap for those who would like to fly with such a livery for the time being. This skin is based on the MKA variant, but I will redo and use an original pattern based on the IRIAF MiG-29A once the paint kit is out. You can download the skin from my repository of Iranian planes (with a few fictional ones): dropbox.com/sh/pefys8tdgqmqee1/AAA76Rwz_h_Kc33qKZbckpcLa?dl=0. Happy flying!

Oh, of course! Thrust Vectoring already defined under "ASC Direct Control" in the control mapping with the key 'S'. The naming comes from FC3 of course, but arguably, for Su-30 the description could include Thrust Vectoring as well.

I don't see any clickable switch on the throttle! So I am afraid, the answer is no. Generally speaking, any functionality, clickable or not, must be supported by the developer in their modeling. I suggest you send this request to freebirddz.

Taking the countermeasure thing one last step further, I have modified the programs such that: P1 dispenses one flare. P2 dispenses one chaff. P3 dispenses one flare and one chaff (this is for when the threat is unknown.) On my Hotas, I have one button mapped to dispensing countermeasures (LCtrl-Del) and one button mapped to cycling through countermeasure programs (LCtrl-Home). Backup your original "stores_config.lua" and copy my modified file to Mods\aircraft\Su-30MK\Cockpit\Scripts\ECM folder folder. stores_config.lua

Ok, I think I got this countermeasure thing figured out. It's fairly simple. First thing to do prior to combat is to use your mouse to set the knob on the ECM panel to "Man." (Note to freebirddz, please reverse the mouse buttons for the knob to be consistent with other knobs in the cockpit; left mouse button should turn the knob counterclockwise and right mouse button should be clockwise.) At this point, pressing Dispense button using mouse (or LCtrl-Del key bound to Hotas) will start dispensing 5 flares in P1. If you advance the program to 2 (LCtrl-Home), it will similarly dispense 5 chaffs. Now, for those who prefer to release only 1 countermeasure at the time, all we have to do is to modify the count in the "Mods\aircraft\Su-30MK\Cockpit\Scripts\ECM\stores_config.lua" file. Use Notepad++ and change the "ecm_program[ecm_prod_count][seq]['qty']" from the default of 6 to 2. Save. -- R1:F6I30 ecm_prod_count = 1 ecm_program[ecm_prod_count] = {} seq = 1 ecm_program[ecm_prod_count][seq] = {} ecm_program[ecm_prod_count][seq]['etype'] = 'F' ecm_program[ecm_prod_count][seq]['qty'] = 6 ecm_program[ecm_prod_count][seq]['interval'] = 30 ecm_program[ecm_prod_count]['rept'] = 1 ecm_program[ecm_prod_count]['start'] = 'F' ecm_program[ecm_prod_count]['seq'] = seq -- R1:C6I30 ecm_prod_count = ecm_prod_count + 1 ecm_program[ecm_prod_count] = {} seq = 1 ecm_program[ecm_prod_count][seq] = {} ecm_program[ecm_prod_count][seq]['etype'] = 'C' ecm_program[ecm_prod_count][seq]['qty'] = 6 ecm_program[ecm_prod_count][seq]['interval'] = 30 ecm_program[ecm_prod_count]['rept'] = 1 ecm_program[ecm_prod_count]['start'] = 'C' ecm_program[ecm_prod_count]['seq'] = seq

Please see page 1 of this thread. freebirddz has provided all the links to the latest code.

Thank you. This was helpful. I agree with you that being able to release one flare or one chaff per pressing of buttons on Hotas is ideal, very much like all the other FC3s. Having said that, I did something to the F-16 to achieve just that. I manipulated the config file and changed the programs such that it would relase one countermeasure of my choice. I was hoping we wouldn't need to go there with this module. Let me poke around and see what I can do. If I can manage that, I'll report back here.

freebirddz, Thanks for fixing a whole bunch of issues. That's great. What about missing bindings to dispense flare/chaff countermeasures? Clicking on a button in the cockpit in the middle of a dogfight is not practical! This is a must have and above all else, in my opinion. Also, for those of us who do not wish to open an account on Discord, having a link to download your code on this forum is vey much appreciated. Finally, when can we expect to see the paint kit released? I assume this must be ready to go, as a number of skins were already included part of your Su-30 package at release.

Thanks for the tip. Although for those of us who prefer to keep our account numbers to minimum, I wish this was the main forum to discuss the issues and updates. After all, this is ED's official forum for all DCS related topics.

Beside the issues that have been brought up, mainly opening/closing canopy and lowering/retracting gear, I am struggling with dispensing flare/chaff via bounded keybinds to HOTAS, the same way that works for other FC3 or full-fidelity modules. Has anyone figured this one out yet? Also, I see a dash line along the canopy when I look up. Here is the picture: All in all, this is a great module and I'm already enjoying it. I am sure after these minor issues are sorted out, we will be enjoying it immensely. Meanwhile, I'm still waiting for the paint kit so while issues are being worked out, we can produce a bunch of liveries for it.

This plane is just wonderful. Love the cockpit, textures, etc. When would you release the paint kit may I ask? I am ready to jump in and start making liveries. Thanks.

My level of excitment is off the charts. I was in disblief that as of 2022 we still do not have a full fidelity F-4 module. No more. My only request to HB would be that we get our hands on the texture files a couple of weeks in advance of official release so we can start painting our skins and fly with them day one.

This is super exciting. Thanks for all your hard work. What about texture files to make new skins? Will the new version 2.0 include texture files? I downloaded the current 1.7.2 to check but didn't see any texture files in the package.