All Activity

Don't know why ED won't offer help.

I am not seeing the document updated. It's still "DCS: F-16 Early Access Guide" dated Dec. 29, 2024 on the DCS web site. Can't seem to find the updated doc with sniper pod.

That does not make sense. All three systems discussed where already approved and operational. Of the three, only GM-1 was considered required special handling, equipment, and training due to the liquid nitrous and icing concerns even though it was approved for use. C3-Einsptrizung was approved in July 1943 and it's instructions are found in the POH. In August 1943, investigation began into using it at all altitudes. That investigation was completed in September 1943. By that time, teardown, testing and examination of the engines from SS+GL, BC+XO, and the other aircraft that participated in the first C3 Einspritzung testing was complete so work began on examining just a straight manifold pressure increase instead of the more resource intensive C3 Einspritzung. That investigation was complete and approved on 20 December 1943. The investigations are done, complete, and approved in all three systems discussed. In fact, the February Travel Log publishes the exact same information a month earlier. In context, it makes NO SENSE. Yep, GM-1 was problematic. It was approved nonetheless and its published manual did not appear for a month after this document briefly covering the boost systems of the FW-190. The system is included in the FW-190A5 Weight and Balance sheets: As stated, dealing with liquid nitrous required special equipment and training on the part of the ground crew and pilots. AFAIK, GM-1 was only used by those units receiving the R11 All Weather variant. Those units required additional training in Instrument Flying as well. Even that was not as problematic as one might think as the Luftwaffe routinely used LOX and was already familiar with the HAZMAT/Handling concerns of Liquid Gas. It also increased the risk of intake icing so pilots had to be aware of the conditions it was used as well as recognize the symptoms of intake icing. That being said...all airbreathing airplane engines are subject to intake icing even today. I turn the Engine Anti-Ice on every flight when conditions warrant. Explain the fact C3 Einsptirzung was published in the FW-190A5 Flugzueg Handbuch almost a year earlier. Explain the fact Erhorte Notleistung was approved 3 months beforehand and GM-1 Given the fact all three systems are tested and approved translating this as some pie in the sky "we are checking into it" makes little sense at all. C3 Einspritzung - Approved in June 1943. GM-1 - Approved in December 1943 for higher injection rate of 150gr/sec and approved/used at 85gr/sec in mid-1943. Erhorte Notleistung - Approved for use in December 1943.

Same as mine. You might need to flash it again. Can't remember how. Sent from my SM-A536B using Tapatalk

Today's update is causing my missions to fail when loading the MIST script (the latest version available) in Dedicated Server. I understand it has to do with the changes in the Scripting API??... Is there a quick fix for this?. Thanks!

Look in the User Files section, I know that there are several of them. But why the F-14B? VF-41 only ever operated the A.

After the latest patch I would consider the following points reported previously resolved: Large lighting towers in inappropriate locations Taxi way lighting placed in inappropriate locations Taxi way markings are now yellow, as they should be What I would love to see addressed in a future update is the terrain geometry and the infrastructure. Pferdsfeld has some very notable and large Hangars and terrain features that I would love to see represented in the map. Great work so far and looking forward to seeing more!

@Chipensaw Tested with today's update. It works fine in MP on my server (tested with the "Easy Rhino" slot and the 135 AM frequency).

this has been reproduced and reported thank you

Exactly. Effects like buffet during a stall are nice but the most important thing when it comes to FFB are trim forces. Without the aircraft feels dead to me who is used to having true force feedback implemented

SAme here Error seems related with Flight.dll dcs.log-20250723-180657.zip

I'm seeing the same thing. I found this video from 2022 (pardon if it's already been posted) of an F4U-1A doing an engine off 180-ish. It definitely shows that the tail wheel should be castoring at least 90 degrees. I know this is probably a minor issue for most, it isn't Digital Taxi Simulator after all, but it'd be nice to get it updated. My test was a taxi up to 20kts at 20in full prop rpm the full left rudder and left toe brake and I could barely get the plane to rotate past 90 degrees where it just came to a halt. I honestly can't get this thing to ground loop at all, even abusing the hell out of it. Might have been a conscious choice to make it easier to taxi and takeoff while it's in early access?

thanks so what was the real livery?

2025-07-23 16:41:41.812 ERROR Scripting (Main): No preset named 'MDRN_B_A_PGM_HTP' in table 'UNKNOWN'; called from: './CoreMods/tech/HeavyMetalCore/Database/Aircraft/B_52H.lua:215' 2025-07-23 16:41:41.812 ERROR Scripting (Main): No preset named 'LJDAM' in table 'CombinedSettings'; called from: './CoreMods/tech/HeavyMetalCore/Database/Aircraft/B_52H.lua:292' 2025-07-23 16:41:41.812 ERROR Scripting (Main): No preset named 'Paveway_III_HTP' in table 'CombinedSettings'; called from: './CoreMods/tech/HeavyMetalCore/Database/Aircraft/B_52H.lua:462' 2025-07-23 16:41:41.812 ERROR Scripting (Main): No preset named 'MDRN_B_A_PGM_HTP' in table 'UNKNOWN'; called from: './CoreMods/tech/HeavyMetalCore/Database/Aircraft/B_52H.lua:690' 2025-07-23 16:41:41.812 ERROR Scripting (Main): No preset named 'LJDAM' in table 'CombinedSettings'; called from: './CoreMods/tech/HeavyMetalCore/Database/Aircraft/B_52H.lua:726' 2025-07-23 16:41:41.814 ERROR Scripting (Main): No preset named 'LJDAM' in table 'CombinedSettings'; called from: './CoreMods/tech/HeavyMetalCore/Database/Aircraft/B_1B.lua:164' 2025-07-23 16:41:41.814 ERROR Scripting (Main): No preset named 'LJDAM' in table 'CombinedSettings'; called from: './CoreMods/tech/HeavyMetalCore/Database/Aircraft/B_1B.lua:174' 2025-07-23 16:41:41.814 ERROR Scripting (Main): No preset named 'MDRN_B_A_PGM_HTP' in table 'UNKNOWN'; called from: './CoreMods/tech/HeavyMetalCore/Database/Aircraft/B_1B.lua:362'

I tried out the new loadouts and tgp for the b-52. After a successful test with 24 gbu-38s, when accessing the b-52 aircraft loadout screen back in the mission editor afterwards, the game freezes.

Nice to see Manual updated same time the pod released, good job

Confirmed for F4U and for F-18 as well. Seeing reports coming in with other guys having the same issue. Couple of full repairs to no avail.

I would like to think I have a fair amount of Lua knowledge from the C and script side , but I have not seen a reflective approach to checking which file is being executed. I will have a think about that. (Not to derail the conversation into Lua technicalities, just wanted to say thanks for pointing out this possibility!).

Приветствую всех форумчан. У меня немного наивный вопрос. Можно ли поменять местами в кликабельных аппаратах движение курсора с обзором? Т.е. сделать обзор мышью, а при этом курсор двигать джостиком?

Carrier Tracking Aircraft Waypoint Situation: Carrier has a 7 NM airspace perimeter. A/C egress at 250-300 kts/500 ft. to clear. A/C Orbit ( 800 ft./4 min.) has a 2.65-3.2 NM radius, depending on speed. So, Rally Waypoint is ~ 10 NM out, on course, like an Airfield. Problem: The Carrier is moving, at 0.3-0.5 NM/min., on course, depending on wind/way. Deck-load Launch Cycle (R/T + 12 fighters) takes ~ 15 min. to the Rally Waypoint. The Carrier has moved 4.5-7.5 NM toward that Rally Waypoint, which is now well inside the airspace perimeter. Solution: Tracking Waypoint. Other ships use it, as does the Recovery Tanker S-3B. A Waypoint - fixable relative to the Carrier's current position. Please advise. Bowie

Just tested. Thanks much for the fix.

I can't believe nobody reported this and it still isn't fixed with the patch. Shrikes are utterly broken in MP. They track in SP and as soon as i play the same mission on my server (or any mission on a MP server) they don't track at all. This has been the case since the last patch. Can you please look into it?

So which additional functions will be added to this scheme in future?

It looks like the July 23rd patch has normalized the cockpit critical_damage values across the AI A and C Hornets as well as the flyable C Hornet. They're all set to a value of 8 now. I don't think this was mentioned in the patch notes.

Valid point. Since people will have to disable for an entire environment, the protection is effectively lost since they can accidentally run a malicious mission if they allowed for another mission. Same goes for IC, something gets added to IC and the only workaround is to disable it completely.