tacts.zeagle

My flight-simming started in the 80's. Janes brings back memories. Anyway, I am a recent Apache convert. I love to fly her.

First, I fail to grasp the reason for the above code. If you are just setting the values once and never changing them, then they are better set in the ME not in code. Second, this is a brute-force method of changing every weapon in every friendly base. Why? Why not just change the items you need to? Think efficiency. These kinds of things have the potential to really bog down performance. And lastly, if you are going to run this code, try using a time delay to allow everything to load up before you go and start iterating through all the airbases. Make sure your carriers are actually loaded before changing their internals. As far as readability goes, using a single letter for your warehouse is not good practice. Also naming a table "inventory" when it actually contains "weapon" is another pitfall.

Here is a listing of a typical inventory table for an airbase. I hope this helps someone. Notable is the indexing of liquids at [0], which, although normal for C, is not good Lua practice. Lua arrays typically start at index 1. Also of note is the inconsistent use of the underscore and the hyphen in the naming of weapons. The AIM-9 series is a good example. The AH-64 internal aux tank simply has no name other than "weapons.droptanks." Also, the inventory uses a plural for liquids and aircraft, and a singular for weapons. ( inventory = {liquids = {}, weapon = {}, aircraft = {}}... "weapon" needs an "s" at the end.) This is why we programmers have no hair. edit: this one includes the resource map as well. inventory.lua

I use curl to send json data to my webhooks. No need to use some .exe file. The only thing is that the implementation of Lua that runs inside DCS will limit the number of characters you can send directly with an os.execute call. So I write my json data into a file, and send it from there. But curl works perfectly.

Just what I needed

Ok. I feel better. I thought I was missing something.

Well after further testing, I am still getting the warning even if ground start at Pahute Mesa.

At Pahute Mesa, start on ramp, needs ground air, has fuel transfer failure At Pahute Mesa, start on ground, needs ground air, does NOT have fuel transfer failure

I am sure that I am missing something in the cockpit causing this issue, but.... When I start my Apaches on the ground, no problemas. When I start them on ramp (cold start), the pneumatic system is depleted. No problem. I just use ground air. But then, after engine start, I get a fuel transfer failure message. Is there a setting or a systems page or something where I charge up the pneumatic system ? I am pretty sure it's me.

I dont think so. I must have mis-read your post. I thought you had a virpil. My coffee meter was on the low side I guess.

Thanks for the kind words Mav. As for the NTTR scenario, it's a place where one can come and just sit in the cockpit to get familiarized with a new bird, fly formation with friends, train on weapons and procedures, or test skills in the live-fire exercise. Users can reset their server stats if need be. The idea was to create a training environment that was somewhat realistic without requiring users to download third-party objects. I write my own code for the site in order to keep it running as smoothly as possible. Also, the mission resets every 24-48 hours in order to accommodate day/night training. Weather is randomized from scattered to high broken. I hope someone finds it useful. Hope to see you all in the air.

yes. But only if you map that axis as buttons. You have to go into your Virpil Configuration Software and bring up the stick. Then double click the axis you want to map and select 0, and 100% if you just want two buttons, then go to the BUTTONS tab and on the far right map the buttons. It's that simple. I had to do this for my F-16 TMS on the Virpil Constellation Alpha stick. I just used a different axis than you. But the process is the same. Then go into DCS and set one of those newly mapped buttons to wheel brake left and one to wheel brake right.

The TACTS BLUFOR training server running a custom NTTR scenario is online. Nellis ranges 62A, 62B (Dogbone Lake Model Test City), 66, and 76 are replicated as closely as possible using in-game assets. A live-fire exercise runs at range 76 for those so inclined. Voice comms are via SRS. Use real world procedures when possible. Broadcast intentions. Monitor GUARD. Server stats, mission stats, and situation reports are available via the radio menu ->F10 menu item. Kneeboard pages are available for the target ranges. Discord https://discord.gg/kYSsvEGTZ8

For heaven's sake there is a Mig29 they could use to make a module. This one Here's Who Bought Paul Allen's Pristine MiG-29 Fulcrum Fighter (thedrive.com)

That looks like a video card issue to me. I have not seen that in the F-5 on my system. It definitely looks bad That's a real life F-5 ... lol