ST0RM

No offense, but many of these VSN flyables are now available as full modules. Why not skip the headache and use them?

There is a LUA edit to make it deployable. I lost it, but know it exists.

I added the AMCI pod, during my initial edits sent to Merker and team shortly after release. As you've seen, it doesnt have an associated rail, so it just attached to the pylon and looked goofy. But nice for an Adversary.

I guess E/A in Russian means As-Is

They'd also have a dedicated HAVCAP to help protect it, and retrograde if necessary.

A pair of Crusader FJ-2s, based off HomeFries' Sabre skins

The M61 gun sound is incorrect for sure. Its like a single barreled cannon, instead of the rotatory Vulcan.

So happy you got these completed. Bravo!!

Great looking skins, all. Hope to see them released when they become ready.

I had the same issue with Jester last night. Repeating voice loop during AAR. Additionally, during the loop, graphics started blurring and becoming double. Anything outside of the cockpit was split into two. HUD numbers, tanker and hose/drogue. Finally had to leave our server.

SD has to support the "home team". He's part of them now. But yes, the growing frustration with another module that hasn't received needed attention, does give the appearance its been given up.

Your sig block shows your passion. I'm not going to argue with you as I'm also a fan of the sim. I want it to succeed. And I do understand code changes. I'm sure ED's changes to DCS World are part of the issue. However, the dev still has the responsibility to keep up with the changes and bug reports. This simply isnt being acknowledged and that is what people are asking for. An acknowledgment of and a correction to the problem. Silence is not the solution. Part time or not.

The MiG isnt in early access or Beta anymore. This issue has been on going since last year. Frankly, I'm tired of the devs (all) disregarding bug reports that are easily replicable. THEY need to spend more time listening to customers instead of blowing them off, or the appearance of such. And the argument of dont use Beta... blah blah doesnt even apply since this was pushed to Stable as well. If M3 is only doing this as a side job (as its appearing with many 3rd party devs), they need to be honest and not expect full price for part time work. Sorry, but this has gone on far too long. This project was a Kickstarter back in 2014. 5 years now and its still limping along. Besides the Fishbed driver, this affects M/P servers who use the MiG-21. How is it fair for the non -21 players to shoot at them, only to have it fly off unaffected? It kills the number of players on both sides. BLUE wont play if its unbeatable. And if its placed as AI only, (currently the only way to get them to die) RED Fishbed drivers wont join. Someone needs to stand up for the customer, as we're being left to fend for ourselves.

+1 Appears so. Another VEAO case

No, pre-planned targets. Set the WPs on the ground, from the F10 map. Still off.

If I may elaborate a bit. Using F10 on a set range of targets for practice. The tanks are static. I hover over and copy the coords into my jet as a WP. At first it was to get an area, for CBU use. But as I've discovered, they're still WIP and dont cover beyond 50ft, and no matter what you set the VT to. So using the same coords, I was going to try CCRP with the Mk83 to plink tanks. But the input conversion is off on the final numbers so the impact point is misaligned.

Yes Sir

I've found that using F10 Map, the coords are off enough to render CCRP useless. Despite the mouse being directly over the target. And CBUs are nearly worthless beyond 50ft.

I'm using CTLD & the 99th's FAC script to allow the Gazelle to be an AFAC, autolasing targets for Hornets. However, the "on-station" call is immediately countered with an "off-station" message within a few seconds. Is there a way to allow the manned Gazelle to use F10 to call on-station/off-station? The rapid cycling also changes the laser code, so its becoming useless. Is it based off of altitude? I've tried climbing, but it keeps cycling. I've looked through both scripts, and the FAC Lua refers to the CTLD script for JTAC/FAC ops, but I'm unclear as to what to modify. Any help or ideas?

Seems the AGM-65Fs are very iffy in M/P. Loaded up on the ground x4 (via rearm menu), swapped 2 out for Mk83s, took off toward target. No cooling countdown and couldnt get them to slew or uncage. Back in SP Instant Action mission, they worked fine. This whole issue started when they introduced the unrealistic function, last update. What track file would be required to show this behavior? The actual trk or what, since this is internal?

Oh wow. Those look stunning. Great job. I'll definitely be flying it.

:thumbup:

Like this? https://www.digitalcombatsimulator.com/en/files/3300918/?sphrase_id=16076163

Typically, anything cockpit or sound related, needs to go the install location. Try that.

Or use RS Mapper and you dont have to hand edit any luas