[RELEASED] Miltech Simulations M2K-C & 2025 Roadmap

I have previously mentioned that I fly military jets almost exclusively and I look for the best with graphic fidelity a high priority. I am loving this jet, but if Im going to nitpick about textures/graphics, can you please enhance the lighter gray areas on the sides/walls of the cockpit? They need sharpening. See the pic you posted above referencing the autotrim. The cockpit side/wall to the left is an example I am referring to. Thanks

With the Velocity One, there’s an option to change the trim wheel from analog to “button press”. I had issues with the analog setup so sticking with the button press for now.

Sorry that’s not an exact answer, not at home this week.

1 Like

It could be upscaled to 8K, will take a look. It could also be enhanced using detail maps. Though I must say that in any “normal condition”, its texel density is adequate. You won’t normally get that close.

New from v1.0.2 update?

working on final details before distributing

2 Likes

Miltech Simulations M2K-C V1.0.2 is all cleared for release, and will be available shortly (distributors working on the release). V1.0.2 will also be the release version for PC and Xbox on MS Marketplace, later this month.

  • ADDED: Weapon/Tank jettison is now supported
  • ADDED: ILS Needles on main ADI
  • ADDED: Cage Flags are now visible on both ADI
  • ADDED: Blue DIRAV light is now lit to indicate NWS
  • ADDED: Conditional to prevent spoiler/slat deployment or retraction after complete shutdown.
  • ADDED: A and F lights now light up to indicate speedbrakes extension.
  • FIXED: Several Flight Model/FBW Improvements. Sensitivity PIDs have been adjusted on the FBW system to linearize the inputs at low speeds, aircraft does not overreact to pitch up input when flying an approach. Resolved FBW issues with aircraft not holding attitude at speeds under 230 Knots. Approach and landing handling characteristics improved.
  • FIXED: Mach Tuck modeling has been reviewed and improved, overmodeling of pitch down tendency has been compensated. Mach Tuck is still present and it is normal at speeds above 0.7 Mach, at which you will see a slight pitch down in level flight (increasing linearly with speed)
  • FIXED: Readjusted CG on Z axis to fully neutralize the off-axis aileron roll.
  • FIXED: Spoiler Clickspot on Throttle now functional
  • FIXED: Euler rotation of chute handle has been linearized.
  • FIXED: ALT AFF Default V/S Increased to 2500fpm
  • FIXED: Oxygen Lever Indicator no longer displaying 0
  • FIXED: Flickering on G Force and Speed Tape should be fully resolved now.
  • FIXED: Nav Lights emissive texture stuck in “always on”, even when the lights have been turned off.
  • FIXED: Adjustments to fuselage reflectiveness, some dirt layers migrated to the PBR Roughness layer for increased depth of textures.
  • FIXED: Various discrepancies on tooltips resolved.
  • FIXED: Default External Camera Distance position has reset to a slightly closer value.
  • FIXED: Mirror Reflections in FS24 improved
  • FIXED: Drag Chute logic has been reviewed. Chute will only deploy when aircraft is on the ground, gear is down, spoilers extended and chute lever in the release positon. Chute will only extend once per flight session, restart of the flight is required to use the chute again, emergency use only.
  • FIXED: Selection/highlight outline removed from HUD, VTB and all other displays when using an Xbox controller.

FS24 Bug, pending Asobo to address:

5 Likes

I tried the new release and the improvements were definitely significant but I found some problems/bugs:

a) in the attached image you can see that if the PCA APP option was used during landing and the APP button was not pressed before turning off the electrical system, the APP light remains erroneously on.

b) After several unsuccessful attempts to use the drag chute as indicated in this post, I realized that the problem was not due to the drag chute logic but to the button used to activate the airbrakes: since the command is a toggle switch, using a bistable button produces a continuous and extremely fast activation/DEACTIVATION of the airbrakes which therefore does not activate the drag chute. This IS NOT EASILY VISUALIZED IN THE EXTERNAL VIEW in msfs2024. Setting the airbrake control on a throttle button that automatically returns to neutral, the problem is solved, but it is not certain that other throttles of other types/brands have the same possibilities.

c) Point b) leads to other considerations: on my throttle (Thrustmaster Hotas wathog) I have only one button of that type that I originally used to activate the afterburner. Now this function has been moved to a HAT of the same (which is self-centering when released), but the solution is not entirely satisfactory, both for users who have cheaper throttles but also in view of the possible evolution of the M2K systems. In addition, in the real M2K the activation of the afterburner does not seem to occur with the system implemented by Asobo for the F18 (which was instead the norm for the Mirage IIIC/E). So it would be useful for the user to be able to choose an alternative method of operation of the afterburner, without prejudice to the availability of the current system for those who wish it.
Thanks good work

a) is definitely a bug, have logged it for review

Now, b) is actually by design. As indicated in the manual, spoilers must be associated to a temporary switch using the TOGGLE SPOILERS keybind. Spoilers, and by extension, Drag Chute are incompatible with axis or position switches that repeatedly trigger the keybind. This is not only accurate to aircraft of similar design (single-position spoilers), but also its due to a practical reason. We are using an “oversized invisible” spoiler to simulate drag exerted by the drag chute, fuel tanks and other surfaces on top of the spoiler extension. Our algorithm will therefore manage the amount of this invisible spoiler to simulate drag depending on the aircraft configuration. Any keybind assignment other than TOGGLE SPOILERS will interupt the execution of this algorithm.

In the specific case you describe, the continuous extension and retraction of the spoilers was indeed interfering with this algorithm, and hence the drag chute was not releasing correctly. In the situation of limiting hardware, there are a couple of solutions available:

  1. Use a keyboard keybind instead of a HOTAS Keybind
  2. On your MSFS24 Control assignments, there is an option for Continuous Input (or something along those lines) - unticking this option will only trigger the keybind upon change of state of the switch, instead of continuously.

Finally, regarding AB activation, we are using the F18 FS20 Templates, which do have a detent before Afterburner engages, requiring the user to either configure a keybind, or double-press F4 (Keyboard) or A(Xbox Controller). This is the native interaction method Asobo has programmed for the F18 in FS20, i’m unsure if this has changed in FS24, but due to backwards compatibility it will remain as-is. Offering different interaction methods in this case is probably unfeasible given that we cannot “hot swap” XMLs

1 Like

Thanks for the quick reply. Regarding the drag chute, I have a “historical” question: on the F104 the drag chute could be activated in flight as an extreme measure to get out of a flat spin, is this also the case for the M2K? If so, I think it is appropriate to restore the possibility of activating it in flight (which leads to a brutal lowering of the nose and destruction of the drag chute itself). If, on the other hand, this case is not contemplated as an emergency procedure in the real M2K, I have no objections and after having solved the problem mentioned above, I am very satisfied with your product.
What are the future development projects of the M2K weapon and radar system?
Thanks, good work

I do not have info of the chute being used in flight, in fact WoW is a condition to release the chute. Only used for emergency landings. Hence the recent logic change.

As for weapon/radar system future, I cannot comment much at this time. This is all heavily R&D and probably too early to tell for sure what works and what doesn’t - the idea is to add some degree of intractability over multiplayer, however, there are strict platform limitations and just a handful of variables to play with.

Hello, When the M2k-C on xbox ?

When approved by the MS Marketplace team for release :sweat_smile:

Currently its having delays due to ingestion problems and changes due to the imminent release of FS24 Marketplace. Cannot provide ETAs.

1 Like

Hi. I really like what you have done with this aircraft in MSFS 2024. I was just wondering if the roundel on the left fuselage is supposed to look this way as well as the lettering on the tail.
It really doesn’t look like weathering. It looks more like the roundel is missing a portion of it.
Any chance of correcting this? Are you planning on releasing any more French liveries as it seems fairly limited considering it is a French built aircraft.
Thanks for this great addition to MSFS 2024. My version is the latest from the inibuilds store.

This is in fact fully intentional!

This particular livery is inspired from french military aircraft flying from Camp Lemonnier, in Djibouti. The roundels/decals often get sandblasted and damaged as pictured here. This livery has been created based on photos of these aircraft, available here SPA 88 Le Serpent

As for more liveries - we leave those to the community. There are a handful available here: https://flightsim.to/discover/m2k

1 Like

After looking at the livery again and zooming in, it does in fact look weathered.
Sorry to jump to conclusions so fast without looking closely.
It is a very nice aircraft and I love the simulated weapons.
Thank you for your quick reply.

1 Like

Better to not go through with the f35 purchase and buy some typhoons. The f35 isn’t up to Canadian winters, is a hanger queen, and poor value.

Throw in a bunch of m400 atlas for transport and refueling.

3 Likes

Who knows, if things keep going to way they have been lately between the US and Canada that could end up being a possibility!

2 Likes

News for xbox ?

At this time with M2KC we are awaiting 3 things:

  1. Latest Xbox version being processed and tested. We were not happy with the performance on Xbox, so decided to further optimize, reducing memory footprint 20%. This has been submitted, just awaiting MS processing and testing.

  2. Marketplace localization and testing. Product descriptions are hand-translated by the Microsoft team, generally in advance of the release. However in this case, it did not occur in advance unfortunately as the team was focused on getting FS24 Marketplace ready - without localized descriptions, aircraft releases do not go live. This has just been completed today 14/03

  3. Finalizing some contractual paperwork to proceed with release

Apologies for the delay - It is on our best interest to release M2K on Xbox as soon as possible. Things are just taking a bit longer these days due to complications and delays arising from FS24 Marketplace Release

4 Likes

First question: The navigation lights aren’t clearly visible from the outside. It would be nice if they were a bit more visible, especially on the wingtips.
Second question: You are workingcurrent on the CH-53? I can hardly wait to fly it. Thanks for your work, I just love the Mirage
 Great job.

1 Like