Gliptal

Which is not how you would fly the real A-10 at all. :D

Keep in mind landing speed and approach speed are different values. You should keep the approach speed (140 to 160) up until moments before landing, unless you're doing fancy stuff.

It also happens with live Mavericks: they disappear shorty after release, but in the sim everything is fine and Tacview reports the target as destroyed at the correct time.

The scripts running on the missions have been checked, and nothing is being despawned (in the sim you can see the smoke rockets or the bombs hitting the target).

With high angle dives, there doesn't seem to be enough separation for Tacview to not have the bomb hit the aircraft moments after release. I attached a Tacview file, you can see it happening at 21:22:54, 21:25:05, 21:25:35, and so on. The only time it doesn't happen is with the release at 21:23:41, which you may notice is a shallower dive. Also, M274 rockets disappear midair after a set amount of time (21:09:36, 21:10:40 and so on), but I believe this is the smoke version's behaviour. https://drive.google.com/open?id=0B-lTLrKHEXokcmF4dldHbzV1SHc

Feauture request: ability to drag and drop .xml files containing static objects, without having to place them inside the "Data/Static Objects" folder and restarting Tacview.

sedenion, I can create a more responsive and modern looking website for you: see Maple Flag's website for an example of my work: https://tlaschuk.github.io/home Also, small problem with 1.7s new GUI: no matter the size, the main window hides most of the mods version number.

Yes, it will be on the Nevada map.

It's a webapp, you only need your browser: click on this link https://gliptal.github.io/cartridger/ and use the GUI. Once you're at the last step, a download button will appear on the bottom right hand corner.

The way I see it there are three ways to editi a pre-existing .lua file: - use an existing parser - code your own tailored parser - manually output the whole file I don't know of any existing .lua parsers (that would allow you to programmatically analyze and edit a .lua file); coding your own parser (even if specifically tailored to your needs) is probably overkill; for Cartridger I ended up manually outputting the whole file, with only the relevant sections rewritten with the new settings. You can freely see all the code on github here.

Ah thanks, good catch.

I did leave 1.2.2, but 1.2.3 should be there.

Updated to 1.2.3, minor changes to the briefing. I am not seeing the skins problem on the UAV though: could you try a repair on your end Pochi?

This replaces your VTH++ in my book. Excellent work!

I completely forgot I had to update the mission with Razor18's feedback, I'll get to it this weekend. No requirements: just get close to the tanker (around 2nm IIRC), and as soon as the refueling message pops up, you are free to proceed to the AG range. This is odd. I used the italian skin, they may have removed it for some reason. You see nothing on the map because most units are set as hidden in the editor.

No, they're there simply as flair.

No. No. Again, both these things are now handled within DCS.

You can still select the folder within Tacview, through the usual submen. It used to be with the Beta 1.5.3 at least, I still have to check 1.5.3 stable.

Directly within DCS options.

Amazing work as always!

:cry:

Thanks, I'll test it right away! May I ask what the problem was? To me, the download finishes but the resulting file is corrupted.

Very well said TheBamse, I have the same issues (with large files not downloading entirely as well).

There was some sort of "donation" request to get a non-watermarked version of the mod that I didn't totally get, and that part was removed due to ED's non-donation policy. I guess the OP removed the entire mod for now pending decisions.

I did edit the generated file, with Sublime Text 3, right after creating it, on Windows.