Coragem

Thanks, didn't know that was a thing before this update, i never had it ocurring before, and now I get that crash very frequently, good to know its mapped already thx for the info, any work arounds possible besides not using the DTC?

I had DCS Crash 2 times just hiting the previous dtc binding key. I opened kneeboard moved to the proper page, hit previous dtc binding and DCS crashed. 2 times same error. Wonder if this is a bug and where is the best place to report it Here is the stack trace from the log. And the F10 marker plan i had setup. 2025-09-26 02:20:50.637 INFO EDCORE (Main): try to write dump information 2025-09-26 02:20:50.915 INFO EDCORE (Main): # -------------- 20250926-022051 -------------- 2025-09-26 02:20:50.916 INFO EDCORE (Main): DCS/2.9.20.15384 (x86_64; MT; Windows NT 10.0.26100) 2025-09-26 02:20:50.917 INFO EDCORE (Main): C:\Jogos\DCS World OpenBeta\Mods\aircraft\AJS37\bin\AJS37-Avionics.dll 2025-09-26 02:20:50.919 INFO EDCORE (Main): # C0000005 ACCESS_VIOLATION at 00007fff5d54b2dc 00:00000000 2025-09-26 02:20:50.920 INFO EDCORE (Main): SymInit: Symbol-SearchPath: 'C:\Jogos\DCS World OpenBeta\bin;', symOptions: 532, UserName: 'varbe' 2025-09-26 02:20:50.921 INFO EDCORE (Main): OS-Version: 10.0.26100 () 0x100-0x1 2025-09-26 02:20:50.930 INFO EDCORE (Main): 0x000000000008b2dc (AJS37-Avionics): RadarMaterial::Init + 0x2CBC 2025-09-26 02:20:50.931 INFO EDCORE (Main): 0x0000000000115eba (AJS37-Avionics): cockpit::AJS37::NavigationIndicator::initialize + 0x2CCA 2025-09-26 02:20:50.931 INFO EDCORE (Main): 0x0000000000115c84 (AJS37-Avionics): cockpit::AJS37::NavigationIndicator::initialize + 0x2A94 2025-09-26 02:20:50.932 INFO EDCORE (Main): 0x00000000001de75a (CockpitBase): cockpit::avDevice::setUpdateHandler + 0xCBA 2025-09-26 02:20:50.932 INFO EDCORE (Main): 0x0000000000233a6e (CockpitBase): cockpit::avDevice::performClickableAction + 0x5E 2025-09-26 02:20:50.932 INFO EDCORE (Main): 0x00000000004009b7 (CockpitBase): cockpit::avSyncable::update_entity + 0xCC57 2025-09-26 02:20:50.932 INFO EDCORE (Main): 0x000000000085840d (DCS): SW + 0x23C1DD 2025-09-26 02:20:50.932 INFO EDCORE (Main): 0x0000000000b53ddb (DCS): SW + 0x537BAB 2025-09-26 02:20:50.933 INFO EDCORE (Main): 0x0000000000a623c0 (DCS): SW + 0x446190 2025-09-26 02:20:50.933 INFO EDCORE (Main): 0x00000000000c253a (WorldGeneral): ActionDispatcher::process_ + 0x7A 2025-09-26 02:20:50.933 INFO EDCORE (Main): 0x00000000000c2056 (WorldGeneral): ActionDispatcher::dispatch + 0x16 2025-09-26 02:20:50.933 INFO EDCORE (Main): 0x00000000000c5b80 (WorldGeneral): TimedActionBuffer::feedEventsUpTo + 0xF0 2025-09-26 02:20:50.933 INFO EDCORE (Main): 0x000000000000430f (World): wSimTrace::CommandsTraceDiscreteIsOn + 0x1DF 2025-09-26 02:20:50.934 INFO EDCORE (Main): 0x0000000000004aa2 (World): wSimCalendar::DoActionsUntil + 0x262 2025-09-26 02:20:50.934 INFO EDCORE (Main): 0x0000000000a6d1fd (DCS): SW + 0x450FCD 2025-09-26 02:20:50.934 INFO EDCORE (Main): 0x0000000000a6ced4 (DCS): SW + 0x450CA4 2025-09-26 02:20:50.934 INFO EDCORE (Main): 0x0000000000a90809 (DCS): SW + 0x4745D9 2025-09-26 02:20:50.934 INFO EDCORE (Main): 0x0000000000a44cf4 (DCS): SW + 0x428AC4 2025-09-26 02:20:50.935 INFO EDCORE (Main): 0x0000000000a46333 (DCS): SW + 0x42A103 2025-09-26 02:20:50.935 INFO EDCORE (Main): 0x00000000025b8d0c (DCS): AmdPowerXpressRequestHighPerformance + 0x1097D08 2025-09-26 02:20:50.935 INFO EDCORE (Main): 0x00000000010dac82 (DCS): SW + 0xABEA52 2025-09-26 02:20:50.935 INFO EDCORE (Main): 0x000000000002e8d7 (KERNEL32): BaseThreadInitThunk + 0x17 2025-09-26 02:20:51.822 INFO EDCORE (Main): Minidump created. F10-map markers plan Scooter 3-3 _ Coragem.ini

Its really sad that we have to chose either a module with no campagns like the Dora, or the K9 without the option for wing cannons/mgs nor the rockets. This is something that does not hurt balance at all if added and just makes the module more fun to fly in a A-G role. Tomcat was aproved to have rockets even if historicaly not used still fun to use in DCS.

I´m having the same issue on the F-14, using cbus-99 with the FMU-140 in Comp/TGT mode, dops the bombs way too short. Even in Comp/PLT mode they often also drop short. I´m going to try with other fusing to see if i also have the same issues.

Just checked out the new sounds on the last update, wow you guys fixed all the problems on the last update, Engine sound is audible, Well mixed, afterburner is obvious, and engine spoll up and down is sooooo much better than the last patch. Thank you HB for again develiring a excelent patch with those latest sound changes.

Not selected, old sounds had a lot more nuance, much better idle to mil transition and even with increase A/B noise in cockpit selected old sounds had better AB engaging tud. A simple solution would be to reduce the level of the high pitch whine and raise the engine level. Or give us a slider to adjust the whining sound separete from the engine or maybe a option to disable it completly so the engine can be heard again. As someone said on another reply above, the B is sounding as underpowered and just like the A now with the new sounds.

I use that option and even then is flatter than it was on the old sounds. At least for me the sounds are way worse than before. Especialy the high pitch whine that is the only thing audible in the cockpit now.

Could we have a special option for the old sounds back? new sound is very flat and there is hardly any diference from idle to mil power. Not sure if that was intended, but its much harder to fly without looking at the RPM all the time now. There is a very loud high pitch whine that drown the engine sound now. Its ear piercing and very annoying. Same can be heard clearly in the external camera from the front. If external camera is moved to the back the engine sound is great as it Always were.

Once engine goes over 8900 rpm you cant throttle down. null

Place IDN in the middle positions to set the offset, like on the Radio based offset from the CE. and the mode to RNAV-VA. (va = vector additionel) same as on the CE. Oficial manual page 208 EE annex. null

Sorry, not happening ever, already said by dev in interview, because of contract with Bell for the license. Timestamped for the trial part.

Nothing to be sorry about, its great news we getting those anyway.

Yeah this helps. @DmitriKozlowsky you can also try using the profiles armapirx uses on this video. Most of them are pretty good.

I really hope the Dual Racks make into tomorrows patch.

I managed to get Match 2.25 @ ~36k feet yesterday, From what I tested as long as the engine is within the Limitations chart, it will keep going. I think the "Implemented engine destruction due to engine overspeed." is working fine since as soon as i´m over the engine limit it will fail now, but i never tested on previews patchs so maybe going over the limits had no concequences before. I can't confirm. null

I was doing some testing this weekend. Managed to get to around Mach 1.8 at 24k feet. On second try managed to get to Mach 2.1 around 29k feet. On first attempt engine was fine, on second attempt I was getting warning lights near mach 2.1 and engine blew up right after reaching Mach 2.11.null Considering what i read about the FM here on the forum that sounds correct. but having more information on the engine damage model and limitations would be nice. How long the engine can be keep at 8900 rpm for example.

Just did this today, its a good workaround.

This brings amazing new life into the module, happy they delived it.

This can be done since the 22 may update that brought the new fusing options in the Rearm menu. And its working fine.

I have experienced that just pulling from a dive bomb, not sure if exceeded 6gs, but what I think would be good is if the ground crew responds with unable to comply when you ask for a rearm when pylon is ripped and back to base. Right now they will acknowledge and when the center pylon gets rearmed, it just falls from the plane and thought the ground and you have no ideia why that happened and Thinking hey that is a bug when its not. After repair it does rearm properly. Ps. Anyway other than felling i could know when i´m about to go over the limit and loose the pylon? Ps. 2 Yeah looking at tacview i did pull 8.2gs once.

Also having the same issue, the nadir arrow on HSI is all over the place, sometimes completely backwards, Distance and Heading on the NAdir Display including the ETA to waypoint is correct. Adding screens and track in case it helps.null navigation nadir.trk

First I´d like to thank you devs for your time and dedication to this amazing module that the MF1 is. I´d just like to ask if its possible to get a small roadmap update? Since some items like BE Variant and Cannon pod already released, and topics on the Original Post are almost a year old. We can see from the latests patches that a lot of work is being put into it, It would be amazing to know what is on the Dev team priority list and upcoming work.

Good to know its tracked, Thx

Thank you, I am just getting back to Gazelle and I was getting some crazy jinks real hard on some cases, It was the default mapping for the co-pilot roll it was mapped to my rudder pedal brake axis, that i was slightly pressing down by accident. Clearing the binds for copilot also fixed it for me.

Was doing some navigation today and also neddle was stuck in initial position. changing ADF did not work at all