EinsteinEP

Charly_Owl, VORs (just radial info) are shown as hexagon icons in DCS. VORDMEs are shown as hexagons inside squares. In this image, you can see a VORDME on the left and a VOR on the right. The VOR (114.25) will only give radial info while the VORDME (128.93) will give radial info as well distance. DME from VORDMEs isn't working in the C101CC in the current version of DCS World.

Thanks for the confirmation! Seems like a really poor aircraft design choice.

Hey Vibora, The C101 (at least the CC) constantly adds nose up or nose down trim as long as the speed brake button is held in either the retract or extend position, regardless of the position of the speed brake. This seems really dangerous as it could result in large shifts in the pitch trim, particularly before takeoff. I know that checking trim is part of the takeoff checklist, but it just feels very unlikely that an aircraft manufacturer would leave this dangerous "feature" in a flight-worthy training aircraft. Is this really in the real C101? Shouldn't the trim adjustment halt once the speed brake reaches a fully open or closed position? Appreciate all your fine work, looking forward to getting educated on the C101!

Technically, the PCs are set for nose angle above the horizon, not AoA - you can have the witches hat on the PCs and be descending and reach or exceed 15° AoA.

This experience is reminding of me of how amazed I was with the level of depth of the Black Shark when it came out, and again with the A-10C. DCS continues to set the bar at impressively high levels for study-level simulations. The attention to detail shown in the numerous videos leading-up to the F/A-18 release and the model quality demonstrated by those lucky sons-of-guns who got pre-release access really shows that this product is a labor of love. Well done, ED. Well done.

Day one purchase for me.

If you can recreate this in other builds, save a track or video and share it with us. It'll be a lot easier to solve or confirm as a bug.

Can confirm the same. Refueling stopped once the internal tanks filled, but the AAR lights stayed dark and I didn't get the "refueling completed call from the tracker. Only the internal tanks were filled. I've been scrubbing the manual to see if there's a switch or button I missed.

{down = ufc_commands.Button_Comm1, up = ufc_commands.Button_Comm1, cockpit_device_id = devices.UFCCONTROL, value_down = 1, value_up = 0, name = _('Comm1 Button'), category = _('Up Front Control')}, {down = ufc_commands.Button_Comm2, up = ufc_commands.Button_Comm2, cockpit_device_id = devices.UFCCONTROL, value_down = 1, value_up = 0, name = _('Comm2 Button'), category = _('Up Front Control')}, Note that the Comm 2 button motion isn't animated, currently.

I was able to add Father to the FCLP by adding the following code to DCS World 2 OpenAlpha\Mods\terrains\Normandy\Beacons.lua { display_name = _(''); beaconId = 'lsoFather'; type = BEACON_TYPE_TACAN; callsign = 'EEP'; channel = 23; position = { -26663.270857146, 950.0, -20110.729714289 }; direction = 90.0; positionGeo = { latitude = 49.250833, longitude = -0.589444 }; } This alters the game install, which I generally prefer to avoid, but I wasn't able to find a simple solution just yet. As one option, you can put a ground unit near the tower and, using MIST, give it a TACAN beacon. I was hoping I could add a Beacons.lua to the .miz file somewhere, to add beacons to the terrain for just this map, but haven't been able to figure that one out just yet.

Not Deezle, but command_defs.lua has action items and their numbering. In this example, the AV8B's command_defs are at \Mods\aircraft\AV8BNA\Cockpit. ... start_command = 3000 ... DisplayBRTKnob = start_command + 289;

Great stuff, Hook! This mission really helped my polish my approach and landings. wUmK2KlFr_s

What is your total weight when you're trying to land vertically? The Harrier cannot land or takeoff fully fueled, even if all stores are jettisoned, even with water. As a rule of thumb, 21,000 pounds is the max wet vertical lift capability (19,000 pounds dry), although this changes with altimeter setting and temperature. Try landing again, but after burning/dumping fuel so that you only have 5,000 pounds left.

This is awesome! Well done, Hook!

Way to go, ED! I think one of the more underrated accomplishments has been the establishment and maintenance of very high quality standards for both ED and 3rd party developed modules. As a picky consumer, I feel more and more assured that whatever module makes it through the wringer that ED forces every developer to go through will have the same level of quality as all the other modules in my hangar. Well done. Also, is "in the coming weeks" the same thing as "two weeks"? ;)

Yes they can. :(

It has always bugged me that the default speed brake mapping in the F-86F module left the switch hanging out in the IN or OUT position when using the speedbrake switch on the WARTHOG HOTAS (e.g., it wouldn't snap back to HOLD when I centered my speedbrake switch on the HOTAS, like it would in the real aircraft). I could have mapped a separate button to return the switch to HOLD but this approach was just too cumbersome. Same for the taxi/landing light. So I modified my input .luas at C:\Program Files\Eagle Dynamics\DCS World\Mods\aircraft\F-86\Input\F-86F\joystick with the code below to add this capability and thought I'd share here if anyone was interested. { down = hydro_commands.F86_CockpitDeviceCommand_AirBrakesHandle, up = hydro_commands.F86_CockpitDeviceCommand_AirBrakesHandle, cockpit_device_id = devices.HYDRO_INTERFACE, value_down = 1, value_up = 0, name = _('Speed Brake Switch - IN then HOLD'), category = {_('Flight Control'), _('Throttle Grip')} }, { down = hydro_commands.F86_CockpitDeviceCommand_AirBrakesHandle, up = hydro_commands.F86_CockpitDeviceCommand_AirBrakesHandle, cockpit_device_id = devices.HYDRO_INTERFACE, value_down = -1, value_up = 0, name = _('Speed Brake Switch - OUT then HOLD'), category = {_('Flight Control'), _('Throttle Grip')} }, {down = nav_lights_commands.F86_CockpitDeviceCommand_LandAndTaxiLights, up = nav_lights_commands.F86_CockpitDeviceCommand_LandAndTaxiLights, cockpit_device_id = devices.NAV_LIGHTS_INTERFACE, value_down = 1, value_up = 0, name = _('Landing & Taxi Lights Switch - EXTEND & ON then OFF'), category = {_('Left Forward Console'), _('Exterior Lighting')}}, {down = nav_lights_commands.F86_CockpitDeviceCommand_LandAndTaxiLights, up = nav_lights_commands.F86_CockpitDeviceCommand_LandAndTaxiLights, cockpit_device_id = devices.NAV_LIGHTS_INTERFACE, value_down = -1, value_up = 0, name = _('Landing & Taxi Lights Switch - RETRACT then OFF'), category = {_('Left Forward Console'), _('Exterior Lighting')}}, Depending on your control scheme, you may need to add these to the default.lua as well as any other .lua files for your desired controller. Ax8WsehLoC8

It was definitely difficult, but I'm not sure about well done. ;) Manually guiding these zippy rockets onto targets is tough. The large warhead has a nice blast radius, which makes hitting soft targets easier, but still not easy. I'm sure with more practice and attack approach discipline, these little Rb05's can be put to good use.

I absolutely loved that twitch (once I got to see the stable replay, that is!). Excellent commentary, lots of good action to spur a lot of discussion...looking forward to watching a bunch more of these!

I think this would be great! What dates? I would love to fly a slick UH-1, or even a slick Mi-8 in a massive event like this.

I'd love to hear more details about the expected level of fidelity of the helicopter flight dynamics: Dis-symmetry of lift Vortex ring state Translational lift Ground effect Retreating blade stall Autorotation Rotor stall Loss of tail rotor effectiveness

I know people are chomping at the mouth for something...er, anything new to fly in, but I am really looking forward to seeing the facelift on old stomping grounds. True, the meshes and textures are the same, but the lighting effect changes are different enough to make a noticeable impact. Folks who fly ONLY Nevada in DCS World 2.0 will be missing half the experience.

It seems to be a matter of shot placement - put the shells in the right place and she goes down. Scatter your hits across the E-2D and you'll put a lot of holes in places, but less likely to bring her down. Here's an approach that consistently works for me:

Interesting. I just went to repeat the mission and that E2 took an elephant load of shots to go down. I thought maybe I just had an unlucky experience, so I tried it again, three times, same result: that E2 takes a lot more hits to go down than I first experienced. My original experience was in the Open Beta, this last was in the public release. Later I'll try it again in Open Beta to see if there's a difference in the cannon effectiveness between the two.

Wow, that is the opposite of my experience. I've been dropping the. E2 with short bursts from either the 23 or the 37.