doodenkoff

I have found that getting level flight is a careful balance of trim and power. Don't forget to adjust the throttle when trimming. I can usually get it balanced well enough to fly the plane with slight adjustments on the trim switch alone.

You can also remove the gun sights/camera in the L-39C for a cleaner view. I believe its in Special - L-39 - and choose 'dismounted' for gun camera.

Thanks gentlemen. Hunted down remnants of Ricardo's mods and fixed the issue for me.

I think the joke is supposed to be that the poster actually is Kim Jong-un. Then it is a little bit funny to be berating the powerful leader of a country.

So the next Chevy Silverado model is completely free? I can expect that? GM has even deeper resources than ED.

I know. The die-hards want you to setup the github repository the development environment, and probably a dozen other things by now....when at an absolute minimum, you need the MOOSE.lua file itself, and a text editor that can parse the lua language; Notepad ++ will work. Search around and find the example lua files. They can be edited to fit your needs and without even becoming a hardcore developer you can nearly immediately create more dynamic scenarios.

Except for the one where, you know, you don't take a blunt stick to the fight.

I think this is satire.

While in the air, press Rt CTRL + Enter and see what kind of inputs you may have going on.

But that's the way the cockpit is. It just is.

Did you try deleting the trigger and recreating it?

I don't think I've ever had the urge to go exploring up a simulated plane's air intakes looking for flaws.

You don't literally have to remove the "DO FILE" trigger and re-create it. I'm not sure you're stating that, but I thought it could be misconstrued. Simply browsing to and re-selecting the file you edited is sufficient. That causes the new, edited file to overwrite the existing file in the .miz.

I've had to re-write this post twice now. I like this scenario because where exactly the convoy stops could be slightly different each time depending on how quickly/slowly the bridge is destroyed.

You'll need to attach the mission file for someone to give you a good answer.

But I'm not recommending a person never use the LDT. I have been very careful to state that if you're interested in learning more about Lua and scripting in general, it's a great idea. I'm not disagreeing with anyone. Why does it seem so difficult to admit, "Yes, the 43 individual steps described in the MOOSE Setup Guide aren't really needed to get started using Moose.lua"? Intellisense literally does nothing to improve the quality of a mission created in the Mission Editor. It serves as an addon in a scripting environment only and improves the quality of scripting; not mission design. I'll repeat this: the developers who have collaborated and created this great framework, have done a miserable job of lowering barriers to using it. There are four important things a person needs to start using Moose.lua immediately; the latest Moose.lua file (2.4.7), the example .lua and .miz files, a basic understanding of triggers, and a text editor.

I’ll never understand why hurdles and challenges must to be thrown in the way of someone who wants to start having fun with MOOSE. The folks that have developed this incredible framework have also created one of the most chaotic environments I’ve ever seen as far as simply getting and using the tools. Again, if you want to learn the scripting, and about the .lua scripting language specifically, go ahead and get the Eclipse environment. I use their Python environment and it’s the bomb. But if you just want to make an armor group patrol in a zone, or setup some random air traffic, do this. Go here and get Moose.lua – https://github.com/FlightControl-Master/MOOSE/releases Click the Moose.lua link and save it to a location you remember. Go here and get the example missions and scripts – https://github.com/FlightControl-Master/MOOSE_MISSIONS I highly recommend using the “Clone or download” button and getting the .zip archive. It will include everything you see in the list. Open a mission. Create a trigger that occurs at mission start. It will have no conditions. Its action will be “DO SCRIPT FILE” and the file will be Moose.lua. That will load the Moose framework in to the mission and make it available for ‘stuff’. Personally, I keep my missions in individual folders and within there I have a copy of Moose and whatever script files I create. Create an armor group somewhere on the map. Name the group armor_patrol and give it a route to follow with some waypoints. Make it “patrol-like” by looping the waypoints back to near the starting point. Maybe around an airport or small village or something like that. I’d suggest a relatively short route for this first test. Navigate in the example scripts and missions to GRP – Group Commands/GRP-550 – Patrol a route. Right click on GRP-550 – Patrol a route.lua and open it with Notepad++ (no matter what anyone says, you should have Notepad++ for general purposes anyway). From that example, copy these two lines into a new, blank document in Notepad++. Take note of the comment lines. They offer hints about what these lines do. You can copy them as well, but they aren’t needed: Vehicle = GROUP:FindByName( "Vehicle" ) Vehicle:PatrolRoute() Replace the word “Vehicle” with “armor_patrol”. On the Notepad++ menu bar, you’ll see “Language”. Click it, scroll down to “L” and choose Lua. Save the file as armor_patrol.lua where you can find it. Make a new trigger. Set it to occur ONCE. I like to stagger events a bit, so use a condition of TIME MORE and 2 or 3 seconds. The action will be another DO SCRIPT FILE and the file will of course be armor_patrol.lua. A little hint here. Either make the route short for this first test, or use the Ctrl + Z combo to speed things up. Run the mission. The armor group should run through its route repeatedly. Now your taking your mission skills to the next level. Congratulations! If you’d like to learn about classes and finite state machines and wrappers and blah, blah, there’s a lot more depth to this than what I’ve described. But if you want to have fun right away, Keep It Simple.

If you want to learn scripting and how to script .lua specifically, by all means get the Eclipse LDT. If you want to start using MOOSE to make mission designing a bit more fun, skip it, install Notepad++ and use the generously provided examples to incorporate elements of MOOSE.

Download link not working.

Turns out, I had been away from flying the L-39 for so long that I completely forgot the "throttle stop" step to killing the engine. Thanks for the reminders. :)

Ever experienced the case where after closing all of the circuit breakers the engine won't shutdown? Just keeps on running. The engine shutdown switch does nothing either. L39_silkworm_sortie.miz

I think understanding the permutations and combinations that can be achieved with flag values may be the key to good mission design. With that in mind, if I set a flag to get a RANDOM VALUE, with a LIM MIN of 1, and a LIM MAX of 10, is 1 and 10 inclusive? Or will you get values from 2 to 9?

You shouldn't have to delete the trigger and re-create it. If you edit a .lua file that is called as a "DO SCRIPT FILE" action, browse to the file and select it like you did when originally creating the trigger, then save the mission. It should work as expected now. In a nutshell; go back and re-select the file called in the trigger if you make a change.

The first page of each discussion thread about those tools has links to the latest version.

Do you have the Civil Aircraft Mod installed? https://forums.eagle.ru/showpost.php?p=3268436&postcount=89