Highwayman-Ed

Nope, I follow ALL of your cockpit mods, and never fly without them. Keep the faith!

Hell, if you can just get it to stay overhead I'd do back flips... If you can get it to orbit 2.5 nm to the port side of the carrier in an anti-clockwise pattern at 250kts at Angels 6, I'll pledge my soul to 'Hello Kitty"

Bumping this one back to the top, along with a request for a new 'country' being United Nations and incorporating some of the skins from mods like these: https://forums.eagle.ru/showthread.php?t=183782

You sir are a star. Now, can you do the same for a tanker to stay overhead?

Hey guys, complete MOOSE Newb question, but would it be possible to make an aircraft orbit between two moving zones?

If you bolter, the LSO will still work without having to re-enter the 800ft pattern, so if you want to stay in the landing pattern without going around, just keep your hook up.

Nice job on that skin :)

I’d like to see this go one further with the ability to set a time for the effect to reduce. i.e. medium fire and smoke reduces to small fire and smoke and eventually ‘burns out’ after a configurable time. This could be set in the initial trigger as a value. Effect Size + Effect Duration.

The infantry in the picture shown are too close and prevent it from firing, but move them out to the distance of the ammo crate in the same picture and the mortar works.

OK kidding with the title, but when another unit is placed close enough to the 2B11 Mortar tubes to 'touch' them, they refuse to fire. Move the items further away, they happily shoot at their targets again. Not usually a problem, but when you're building fighting positions to liven up your missions decor, but also want them to function, it can be tricky... This made me lose a fair amount of hair this afternoon trying to figure out why they wouldn't fire that I can't afford to lose at my age!

For WWII Bomber formations, you can make them up to 256 aircraft I believe, but for standard flights of fighters, 4 is your limit. You can of course cheat by adding a second flight with the role of 'Escort' and have them escort your first flight of 4, and so on... but it only really works for Air to Air combat.

I'm looking for some voice actors for an upcoming campaign (and hopefully series of) that I plan to sell through the DCS Store although it's still in the early days. I need 5 individuals that can speak Russian and English to voice characters in the campaign for both Russian and English versions of it. The campaign will be 10 missions in length and one of the roles will be performing around 80% of the content as the player's wingman. I'm investigating how I can compensate any participants at this time, but I'm working on providing a free copy of the completed campaign for each actor, and a DCS module of their choice to the main actor. As this is my first campaign and I have no idea on the potential sales value, the number of copies that it would likely sell, or how to deal with taxation implications of providing any other method of compensation before going through the full process and submitting it to ED for sale. If you're willing to help, please PM me and let me know. The first 3 missions of the campaign are complete and just need the voice acting added prior to submitting them to ED for evaluation prior to working on the remainder and figuring out the financials! No experience necessary, no real requirements other than being able to speak both languages ideally and understand the context of what you are saying (excited, bored, funny, etc.) Most missions will only have between 1 and 5 short lines for each actor, although as mentioned the primary actor has 20 lines in the first mission. Thanks!

+1 request for Advanced waypoint action of 'Unlimited Refueling'

I had exactly the same thing. I blew everything away and did a clean install and it's now smoother than it's ever been... See here: Link

Alerax, I'd second the more stuff from the VLSO, for our dedicated squadron server the mission loads up very quickly, so I wouldn't see it being an issue to update it with more sounds if the scripts can support it. One note however for feedback, when you're in the groove flying the ball with the IFLOS, I've noticed that the LSO will occasionally tell me I'm a little high even though the ball is centered. Maybe the deck is pitching, I can't be sure, but the high calls do seem a little too strict. Thanks for your contribution, it's a great piece of work.

Nice idea, I really like the potential of this and will follow it keenly :)

Have you checked to see if there are any commands to import, I seem to remember having to update the command list in VoiceAttack to get the carrier I think. VoiceAttack prompted me to do this when it started though with an Orange warning dialogue. Here's what it guided me to in the manual: [PRO] Import F10 Menu: adds mission F10 (Other) menu items to the keywords database. Enable this option and fly the mission: items are added as new keywords starting with ‘Action’. Go to the Keywords Editor and follow the FINISH steps to update the VA profile to use the new voice commands: using an imported keyword will execute the menu item command.

Same here, no issues talking to the carrier with VAICOM 2.5.5

Further troubleshooting, I blew away my Open Beta, deleted everything and re-installed and it's smooth as silk... Not sure what had gotten caught up in there, or if it's that DCS has been update, over update, over update ever since 2.5 came out, but a clean start has made it run better than I ever remember it running before! If the DCS guys would like anything from the Stable release build for troubleshooting, I'll keep it on my hard drive for now.

So further to this I've done some troubleshooting and it seems that the problem is strictly related to Multiplayer or at least when an aircraft is set to 'client' In the attached video in the STABLE release of DCS (I tried it there after noticing the same thing in the Open Beta), the mission contains a carrier group, an F/A-18C cold on the deck and a couple of static objects. Also... I've noticed that with a new mission, textures are loaded into the ME much quicker than in my previous video where a pre-built mission is loaded. To the video... Here you'll see me load up the mission with the F/A-18C set to start as Player, I then quit the mission after loading into the cockpit without any issues at all, and make 1 single change to set the F/A-18C to start as a client. Note how it takes well over 2 minutes for the textures to load in when the client is set to multiplayer. You'll also note some audio 'stutters', this is pervasive throughout the entire multiplayer or client flight with the game effectively freezing every now and then for a split second. NEW BS CASE I - I.miz

Starting DCS in Desktop mode (Non VR) and forcing it to go full screen seems to resolve the issue.

Since the update to 2.5.3.22652, the textures are taking a long time to load at mission start, and when cycling through models in F2 or F7, the vehicle and or terrain textures are doing the same. NVidia Drivers 416.16 and still the same after upgrading to 416.34 It doesn't affect all missions it seems, more any missions that have triggers, and the more triggers the slower it seems to load them. The mission in this video in the last build loaded into the cockpit pretty much immediately. No Mods in use at all. Same issues in the ME as well where it takes almost 8 minutes to load the texture for the carrier and all aircraft in the scene. Please excuse the Fighter Pilot Podcast interview audio with Wags in the background of this video! Occurs in VR or on desktop

I've taken a quick look at the mission and I'd say that whilst there are a lot of objects, there aren't too many for it to handle. So that's not the problem. I would recommend that any ground units that are not integral to the mission or are required to shoot be replaced with static objects instead of actual units. This will reduce the overhead on the background engine figuring out which unit can see what and which unit can fire at what, etc... No help with what's causing it though, I suspected the B-52 might be the issue, but this fires fine on its own. I'd remove the triggers causing all the units to fire / spawn, and add them in one by one until you find the culprit.

Using Skatezillas DCS updater and linking the Oculus software in that did it for me

Odd mouse graphical artifacts appeared again in build 2.5.3.21708 but was then fixed last week in build 2.5.3.22176. After this weeks patch to 2.5.3.22652 it's back again. In the DCS GUI: In the cockpit: Highlighting a button in the cockpit: