Patchwork

Sorry for the really late response. No actual mission objective that will give you a "Mission Success". I personally think by the end of the mission you'll know if you've done what you needed to do and as a personal choice I decided to leave out a "You Won" message as I'm not a fan.

Alright, I think I found the issue for why Carrier missions are not spawning the enemy aircraft (I am using 1.12). The "Push trigger" for carrier ops is using the "ALL OF COALITION OUT OF ZONE" Condition. This is not a suitable trigger considering that the carrier itself is part of the Blue coalition and will never end up leaving the push zone. This means the flag 1 value is never set properly, so the enemy doesn't spawn. In the meantime, I'm manually setting the condition for the push trigger to "PART OF GROUP OUT OF ZONE" and selecting the player group.

This is the mission that I used for my DCS F/A-18C "Ejército Del Aire" series on YouTube. I've also included an alternative version that is more complex and it is the recommended version for post-release. This is supposed to be a complete mission from ramp start to shutdown. And a disclaimer, I'm hardly an expert mission maker, but people have been asking for it, and I'm sure some of you will want some more missions to do in the Hornet when it's out. The task at hand is to Infiltrate Iranian airspace as El Ejército Del Aire, Ala 12 (wing 12 of the Spanish Airforce) and follow the flight path through a narrow corridor that is clear of SAM threats and strike a military compound south of Lar Airbase. Expect to be interceptors as you start to Approach Iranian Airspace. There is a tanker on station on TACAN 27X (Freq. 251.00) that is recommended you use either before the strike, after or both. AWACS is also tuned into the flight channel (freq. 305.00) These missions aren't overly scripted or complex, it's just a simple mission that hopefully you guys enjoy before more stuff is eventually released. Simple Mission File: https://www.digitalcombatsimulator.com/en/files/3300596/ Complex Mission File (RECOMMENDED): https://www.digitalcombatsimulator.com/en/files/3300597/ Let me know if you encounter any problems or if I need to update something.

Probably the last video from me until release. Thanks again ED and Belsimtek for this wonderful aircraft.

He publicado la tercera parte, la última de la serie.

Estaba experimentando con un nuevo editor de subtítulos. La parte 3 ya está grabada, pero intentaré mejorar la velocidad de los subtítulos la próxima vez.

Gracias tíos por el apoyo y comentarios entrañables. Voy a publicar la parte 2 en aproximadamente una hora. :)

First of a 3 Parter for a full mission I've been working on. I've also included Spanish subtitles for the Spanish speaking DCS community.

Hola a todos. He hecho una mini serie de tres partes volando como Ala 12 y he incluido subtítulos para vosotros que tengáis dificultades con el inglés. Quería hacer un vídeo porque hablo el castellano (horriblemente) y sé que muchos de vosotros estáis igualmente desesperado por el Hornet que el resto de la gente. La primera parte consistirá de la puesta en marcha y el despegue, el segundo es del cruce hacia el espacio iraní, y el tercero será la vuelta que incluye el reebastecimiento de combustible y el aterrizaje de vuelta en la base. Después de que el módulo sea disponible a todos pienso publicar la misión y traducirla al castellano, así que el que tenga el avión y el mapa podrá volar esta misión que les presento.

Description: Rotor disc (blade tips) don't seem to have structural damage of any kind when gently put in contact with the ground. DCS Version: 2.0.4.59428 Update 1 Map: NTTR SP/MP: Singleplayer Reproducible: Yes Step to Reproduce: Gently increase collective, let the helicopter (slowly) start tipping over and let the blades rest on the ground. Video: Controllers: Saitek X-55 HOTAS and Saitek Pro Flight Rudder Pedals (No Curves or Saturation) OS: Windows 10 RAM: 16GB 1600MHz DDR3 GPU: AMD R9 390 Mods: No Mods (Fresh Install)

Make sure you are pressing and holding the "Missile Uncage Switch" as soon as you hear a good tone. This will tell the missile to "keep eyes on this signal" and it will have a much larger tracking FOV and will be much closer to what you're used to. Most people aren't pressing and holding the missile uncage switch, so the seeker is fixed to the boresight.

Are you holding the missile uncage button/switch once you hear the tone? As soon as you hear the tone, you need to press and hold the missile uncage button. It should then start tracking the target as long as you're holding the missile uncage button. If you don't hold the missile uncage button as soon as you hear the tone it will be locked to that tiny FOV as you said.

Yeah, that's what I'm primarily asking about. Is if that dead-zone is a feature in the real plane, or if there may be something else going on. I have my curves set to a point I'm fairly happy with it, but due to the deadzone in the Fly-By-Wire it seems you'll never be able to truly have 0 deadzone.

I noticed even with 0% deadzones set on roll and pitch Axis in the control settings, the Fly-By-Wire system seems to have its own deadzone/filter. It's not a deal breaker, but for me personally it makes those tiny micro adjustments needed for AAR and formation flight a bit more prone to pilot induced oscillations. If you look at the graph in the bottom right, the Red (Physical axis) you can see it registering the micro movements I'm doing, but the white (FBW) on the graph is filtering that out. I was just wondering if this is accurate to the IRL Fly-By-Wire, or if it's a potentially a bug? [ame] [/ame] I've been working around it with more aggressive curves, but just wanted some input on what might be going on here? I was looking through the manual but it seems a lot of the Fly-By-Wire documentation is currently still not added and is pending release.

I just tested it with the Mirage 2000c, because I was having the same issues in the Oculus Rift, and it seemed to have fixed it. I just changed it under DCS World\Mods\aircraft\M-2000C\Views.lua [13] = {--default view viewAngle = 65.000000,--FOV hAngle = 0.000000, vAngle = -0.000000, --"-17.000000" x_trans = 0.000000, y_trans = 0.000000, --"0.010000" z_trans = 0.000000, rollAngle = 0.000000, }, The --"-17.000000" & --"0.010000" were my old values. Setting them to 0 seems to have fixed it in the Mirage 2000c at least for me. I'm going to try it in some other aircraft. Edit: Just did the same thing with the Mi-8MTV2 and it's also now fixed for me.

Yeah, for me the tracking issue seems to be that indeed it doesn't seem to be 1:1 movement anymore. In the mirage for instance if I lean forward I seem to be moving diagonally up and forward (+Y Axis, and +Z Axis) instead of just forward along the +Z Axis. It seems to be because the camera is tilted back a bit, and isn't perfectly horizontal. The Gazelle and the MiG-21 is a bit different in that it is aligned with the horizon, but the movement is over-sensitive and not 1:1. That is the best way I can describe what I'm feeling with the head tracking.

Getting the same in the Oculus Rift.

Oh, I was unaware it wasn't made public yet. I just found the link on Hoggit and I assumed it was already public. Sorry about that :/

http://www.digitalcombatsimulator.com/en/newsletters/newsletter29042016.html That sniper team though...

No, it wasn't available to download. I think they need to release the new 2.0.2 patch before it becomes available for download.

I managed to pick it up before they brought it down, yeah! This is going to be quite a day.

Well, as backwards as it may sound, U.S. calendars start the week on Sunday, so that was the reason for my confusion.