fl0w

Unofficial Training Missions Hey guys. As I mentioned previously in a post on this thread, I stated that I would be working on some training missions for the A-4E-C mod that will be interactable for users. I am happy to currently show off the 1st training mission in line: the startup. As time does go on, more and more will be made. Currently at the time of this writing, there is 1 other training mission in the works on taxi and takeoff procedures. I will be planning to provide a set of training missions in both the Caucasus and Nevada theatres. However, I will be doing Caucasus for now. Below is a video demonstrating the capabilities of the training mission. I hope for these to serve as aids for user inter actibility as since most teaching is now either in the Community A-4E guide or in the form of tutorials on YouTube. This is in no way meant to replace any of them. I hope you guys enjoy! (P.S., apologies for the TrackIR clipping out around the end and shakiness. Still a bit new to it. :P) - Sirius

"GEAR_LEVER" refers to the string/text within the gear_system.lua file. In Section 1-A, it shows how to create your own parameter handles. I hope that I was able to help!

Nice work. This definitely adds another level of detail to the module when looking upclose. :thumbup:

I would like to say here that apart of the A-4E-C discord server when I had declared this that I will be helping to bring in some training missions for people new to the aircraft to play in order to help with interaction and learning the aircraft aside from tutorial videos. The missions will include the subject(s) of: Startup Takeoff Landing Shutdown Carrier Ops Radar Circuit Patterns/NATOPS Weapons and more to come as time goes on. So far I am looking for people who are able to help out with recording some audio files. If anyone is interested, please contact me at the A-4E discord. Progress (as of the time of this writing) is being focused on the startup training mission. :) - Sirius

Simply, awesome. I am very excited to get my hands on this 3D print if you do plan on releasing it out. Maybe HB could give you a copy of the Tomcat for you to set up controls for so we can all download a set file with your electronics. :music_whistling: ;)

Awesome work!

In-depth look: Gear system Hello, everyone. As a way to expand onto the guide, I wanted to help users out a little bit more with understanding about how some systems work in particular. In this example, the gear system will be our first in-depth look on the matter. I must warn you, however, that before looking at this code, I highly recommend for those who do not understand this to read Section 1-A in the guide first on avLuaDevice before proceeding. With that being said, I will now delve in. As stated in the guide, in order for you to have a working system (in this case, landing gears) you need these 3 things: The internal DCS ID declared/listened a SetCommand() function to check if the ID is called and an update() function to loop the animation transitions Since the time of writing the guide, I have found out that you are able to add a "fluid" animation transition to also clickable elements in your cockpit. This includes, but is not limited to: 2-way switches, and levers. 3 new variables will be introduced in the script: GearParam, GEAR_STATE_PARAM, and GEAR_WEIGHT. These do the following as shown: GEAR_WEIGHT: Checks if there is any weight being applied to the wheels/suspension in effect. Grabs information from the sensor_data variable. GEAR_STATE_PARAM: a new variable to declare the position from 0 to 1 of the parameter handle's "state" or position. GearParam: a new variable to grab the parameter handle for our clickable element in the cockpit. Linked below is a script attached for solely this interest. There is more code in an advanced version that I have created, but I thought that it would rather be fairer to let people get a little bit of it and from there build up knowledge on how the process works. With this method, you can also apply this to systems like your flaps and canopy. (Some extra code may be required, however.) P.S., Remember to change "GEAR_LEVER" in the get_param_handle() function to whatever your parameter is named! Link: https://pastebin.com/fy0wFJ3s (Credit to BR=55=Sevas for giving advice on the gear forced value limits) - Sirius

Thanks. I did consider this in the past but I wanted to verify for any way to mathematically have it done to increment/decrement perfectly to 0 or 1 while using the time update rate/seconds wanted. It seems you can't do it unless you use an even value of division. Since I divided 0.01 by 5, I used an odd number to rep. my time transition which may explain the issue.

Hello, everyone. Lately, I have been messing around a bit with some Lua code for DCS aircraft systems in order to get my desired results of incrementing/decrementing values. In this case, I am using 2 if statements acting as loops shown in order to set a "fluid" transition animation of my gear lever. Method 1: -- If the gear is supposed to be up and is down if placement == 0 and lever_pos > 0 then lever_pos = lever_pos - 0.002 end -- If the gear is supposed to be down and is up if placement == 1 and lever_pos < 1 then lever_pos = lever_pos + 0.002 end Method 2: -- If the gear is supposed to be up and is down if placement == 0 and lever_pos ~= 0 then lever_pos = lever_pos - 0.002 end -- If the gear is supposed to be down and is up if placement == 1 and lever_pos ~= 1 then lever_pos = lever_pos + 0.002 end The issue is what type of way to check lever_pos is better, the ~= (or !== in other languages as 'not equal to') method of using the greater/less than operators. I have found that the "than" operators give you a range that works but it can either go backward or too much forward in order to be true. And with ~=, it does not fully "recognize" it (the lever_pos) at 0 or 1. In order to check, we can do simple math. We can assume lever_pos is going to start at 0 or 1. 0.002 is my time update rate (in this case, 0.01 or 10 ms/s) divided by 5, to represent 5 seconds of movement. Doing 1 - (0.002 * 5) will return 0.99, meaning still .1 is missing. Does anyone know a good method besides having a non-perfect value to level it out to 1 or 0? Any help is appreciated.

Yes, baby! We need more. :)

HB keeps on topping the F-14 with new firsts in DCS. Great work! These will all be great additions to this game. :D

I respect that. I would be the same way as most others about asking why some things were not shown and knowing that many CC's state the big "everything is still in development" line. Your party has worked very hard for so long to deliver a polished, golden product to the community that it almost feels wrong to critique and say otherwise. Great work, and please keep going!

I cannot speak on behalf of the dropbox links, but there is a new thread on the subforums for how to code your own systems. Refer to this link: https://forums.eagle.ru/showthread.php?p=3762385#post3762385

Virtual Red Eagles Team Et omnino, fidelic. Facebook: Coming soon. Discord: https://discord.gg/6x5qtWq Hello, everyone. On behalf of the Virtual Red Eagles Team, (or abbreviated as VRET) I am pleased to announce our entrance into the DCS World aerobatics community. Our team consists of a 4-ship of pilots, all who have a burning passion to fulfill: to use the L-39 for aerobatic display. Our team was founded during late December of 2018, new and beginning with bright ambitions. As of the time of this writing, (late January 2019) we are currently a 2-ship of L-39 pilots. We hope to begin showing off our own special acrobatic maneuvers along with our WIP skin. Additionally, we are currently accepting applications for our 2 remaining positions to be filled in for the Right Wing and Slot! We regularly fly on the DCS 2.5 Aerobatics Online OB server. Please check out our Social Media via. the links above for those who are interested. We hope to share more with you soon. :) For the meantime, please enjoy these screenshots so far showing off our progress being made for the year of 2019 and more to come.

It is neither a module or that mod. https://forums.eagle.ru/showpost.php?p=3766986&postcount=39

Found here: https://forums.eagle.ru/showpost.php?p=3779656&postcount=1

This is unbelievably impressive! Does it fully function with DCS?

While this aircraft looks awesome at the moment and may serve well as a testbed for the Super Tucano, I am still quite worried about the MiG-19 development. Should we be believing in what RAZBAM has to say on that or the ED newsletter?

Mini-update Dear all, I have not spent awhile on the BGSC guide, (mainly due to personal life reasons) but I hope to finish the Training Missions section very soon. A new section, for coding systems for reacting to a damage model, is also being considered to help those wanting to re-create the outcomes of a damaged aircraft. An example of this would be the iconic F-14 Tomcat module to soon be released into DCS World as of the time of this writing. I have also noticed that the code for the electrical system sample in the guide shown is outdated, and as that result, I will be re-coding a new example for those to copy down. The ability of those to download pre-coded files of the systems is also being considered, but this has been expressed as something that contradicts the belief of how the guide should work and teach the user instead of giving them free scripts. I hope to share more with you guys soon. :) - Sirius

What part are you referencing to? I assume the damage model table. I don't really know a lot about this subject and would heavily fall on the BGDAM for more information since that has a lot more documented than my bad memory. :)

I would love a continuation of their F-14 in-depth video series since Episode 1 was just an Overview. :(

And that's perfectly fine to be with that choice. Peoples' tastes differ from others and not everyone will prefer the same thing as one another. As long as the "Which is better" debate does not occur, all is well. :) For me, I will always be with the Kitty, because to me, it is a tried-and-true example of how better technology doesn't always equate out to a better outcome.

So indeed I was using Flat Shadows. I tried using the Low setting and did a quick test flight on the runway and alas, the issue went away. However, I am still unsure about why the rudder still disappeared from the shadow even if the 3D model is correct. Has this been a standard issue in DCS?

DCS calculates damage from the collision model and the damage table code inside the aircraft.lua file. In this example, it would be named as "FA-18C.lua". As you mentioned, it is in the aircraft.lua. It is linked to the collision file. The "shape_table_data" variable also will handle the collision model effects once upon crashing the aircraft. Do not mix up collision/damage model from your collision shell. The collision shell is comprised of boxes and lines for: Line_MAIN - Top view of the aircraft outlined with a Line shape, given the "collision_line" property. Bounding Box - a box with the height, length and width dimensions of the object's fuselage, given the "collision_shell" property. WHEEL_F - Front wheel collision box, given the "collision_shell" property. WHEEL_L - Left wheel collision box, given the "collision_shell" property. WHEEL_R - Right wheel collision box, given the "collision_shell" property. Unfortunately, I do not remember a whole lot on this subject, but that is as much as I was able to recall. For your question on making correct systems based via damage, if you are depending on the damage of the external model you are able to check the argument number animation values to see if the damaged part appears via. argument number in an avLuaDevice setup as shown. -- let us rep 300 as our damage arg number local DAMAGE_ARG = 300 local DAMAGE_PART = get_aircraft_draw_argument_value(DAMAGE_ARG) if DAMAGE_PART:get() == 1: print_message_to_user("Part is damaged!") else print_message_to_user("No damage. c:") end I hope I was able to help answer your question!

We do have some information of that on pages 16-17. Do you mean something by training procedures? There is a training mission part on page 30 but it's been paused so far. I like your idea, some kind of AI correction in the code would indeed be very nice. :)