Slims

They are not fixing the obvious bugs in flight systems and you guys think they will fix the "round" shapes ? lol.

What i say doesn`t work for toggle switches. it`s a few posts up. In my example it is pretty clear there are 2 different key commands for radar on/off. Most modules have this sort of arrangement.

Really nice man, photography and craftsmanship !

Well lets say radar ON is SHIFT+1 and Radar OFF is SHIFT+2 then you need to add a command for RDRNRM called radar on key command SHIFT+1 and for RDRDIS command named radar off SHIFT+2. Again for each don`t forget to click add event afterwards. Also name your commands it will be easier later to find the commands in the list. After you get good with adding normal commands you`ll find you want to use multiple layers :)

You start a new profile. Afterwards you get the 3d image of the stick and throttle on the left side of the screen. You press the button on the stick image you want to program and set a command for it. Also for switches use pulse command, and you have to program each position for the switch. Don`t use toggle commands for switches. Edit: Oh btw, don`t forget to click add event if it`s a new comand or save event if it is a modification to an existing command. You`ll see it`s pretty straight forward.

This is totally wrong and misleading. First of all 1.5 has no changed source code, all module are working on 1.5 even the fc3 aircraft for years and none have these issues. Secondly even if the source code has somehow changed you cannot damage something that is not and was not ever modeled like all the stuff people are saying that are MISSING from the m2k. And thirdly as state 100 times in this thread there are BUGGS in the mirage from day one of the release of this module on the store page, that have not been addressed until now and is becoming increasingly unclear if anyone wants to loose time and fix them. If the changing source code is the issue HOW can razbam focus on getting harrier out to pre-sell ? Isn`t the harrier programed on the same code as mirage ?!? I understand that the platform is evolving it is something exciting and absolutely fantastic. I love DCS for this. I accept that some things can get broken along the way and it takes time to get fixed, see lightning issues, reflections, exploding rearmament for viggen, etc. BUT this module is missing a lot of systems, some are coded wrong from the release, some stuff are placeholders and with all of this, the focus of razbam is on getting another module out the door. There at least should be a post made by the dev`s too silence all the unhappy customers with a road-map, so at least we understand what will change for the mirage in the coming months. As it is right now: DM - ED`s job (are we to expect ED to model subsystems in mirage and model how the aircraft flies with damaged modules ?); Missing systems ( implementation of air to ground radar - ED`s job ? ); Fixing radar (Ed`s Job? ); etc. We know nothing, everything is pure speculation and all of this leads to these discussions that are not constructive.

You sure you played mirage beta as released because i think you haven`t. Remember when screen would turn black when rebinding keys? Or Dcs fatal crashed at random points when turning radar on. Or being randomly disconnected from online play for whatever reason whenever flying online, oh man and so many more crashed when flying mirage.... Viggen buggs are nothing, i have not gotten on crash flying viggen, yes it has some buggs rearming bugs etc but again comparing a module released for 19 months with one released for 5 months is not fair. And also i reiterate there are so many buggs in m2k that have been plaguing the mirage since launch and are not being fixed.

Viggen has been launched on 27 of January so it is out for 5 months ? At launch viggen had all the systems up and running with slight buggs but playable. How many months since m2k has been launched ? i`ll help you out, it`s 19 months. Wanna compare m2k with viggen release ? I see people don`t remember that at release m2k did not even have bindable key bindings, i think i don`t remember right but i think it was sedenion who fixed that after a few months (if i`m wrong forgive me whoever fixed the bindings is the man). If you wanna compare 2 modules compare them at the time of release, and in this case they don`t even come close... As stated above right now m2k is in a far worse state than viggen so it is not fair towards the viggen to compare these modules.

I don`t understand why it`s ED`s fault that mirage is incomplete. It`s not ED`s job to model systems for razbam, it`s not ed`s job to model subsystems to improve the DM, not ED`s job to fix the broken radar since release, it`s razbam`s job. Even when the new improved damage model that will come from ED it will be razbam`s job to implement it, and model the subsystems that now are missing, ED won`t do anything to M2k. If you look at other models that have vibrating pitot tubes, or will have wingflex introduced if there are to appear in m2k RAZBAM must implement them no one else will ever add stuff to this module. So please stop saying this, it will never happen.

Unfortunately i`m on the same boat as you. There are more stuff that makes the m2k feel weird as a module i get a feeling that some systems are not correlated to each other, i mean you can shutoff stuff in mid flight and plane keeps on going. I love the harrier and would love to pre-purchase it but all this stuff in m2k...`

Also some of these bugs are here since launch, and the developers show no interest in fixing them, like the radar azimuth going berserk after you unlock. These bugs have been reported many times and even acknowledged but lately i see even the acknowledgement part has ceased as-well...

I would love to get the harrier, unfortunately i won`t, because i cannot trust razbam to deliver what it has promised. 1 year and 7 months have passed and the module is in a semi abandoned state while the team works on the next module. Also with so many modules on the horizon it would simply not be ok to buy a module and wait for 2 years for it to reach release state. Also i wonder since this has been released on steam as being future complete what is to stop razbam from keeping the module as it is now?

Yes I did this also, got some PTFE O-Rings done replaced the grease and it is working like a charm. Opened it up a few months ago after about one year of use to see how it is looking and both the grease and the O-ring looked like new. But as i reassembled it i got this itch to try and improve this thing, and make it more durable. And also more smooth if it could be achievable somehow. Edit: In the end ofc, it would be more economical viable to just go for another stick from VKB or something similar, but I thought that the way TM got this thing to work is quite ingenious and it looks really good. I`ll keep researching this maybe i come up with something. Thanks for the ideas. :)

Yes but wouldn`t the plastic part rubbing on the brass pin, the hole i mean, in time enlarge and end up with a broken ball like the guy with the broken ball a few posts up ? Even with a good grease in time it would simply wore off. Edit: Yea didn`t think it quite thru with the aluminium thing. Thanks.

Really good points. Thanks a lot. This is bugging me for a real long time, and somehow i would like to give it a try, but there are some stuff i did not take into account. Never thought of brass untill now. Excesive lube would decrease the risk of dust i think, but still a risk would exist. This would really be a problem on the "pins" that hold the first 2 parts of the gimbal for which I was thinking of maybe using some sort of bearing.

So i was wondering, if i could machine these 3 parts that make up the gimbal + the pressure plate out of metal (steel), and assemble it together do i have any chance that the hal sensor would still work, since it`s magnetic and all ? Is it worth a try or is it useless ? Also what should the tolerance be, as i doubt i could get it really identical some really small differences would exist. I don`t have access to casting, also because creating a mold using my existing hotas gimbal is quite expensive, and not worth experimenting. But i could try and machine these parts as i know some guys :). At first i would try with steel, and maybe if it`s working maybe later with aluminium. Do you guys think it might work ? Thanks.

I cannot imagine what platform you come from with better flight modeling than DCS... And also how do you manage to compare them, have you flown the f15, how do you know the other platform is more accurate ?

Thanks for the clarification m8.

So F14 A/B does not have IFF capabilities for radar ? This is going to be problematic in current dcs environment. :) Nonetheless can`t w8 for this to be released.

You use the same line every time someone posts something related to m2k, it doesn`t matter if it`s a bug or not. From the obvious issues with the FM, to any other issues related to this module there has not been a single thread without you saying that it`s ok like this.

But i don't get it A10C and Ka50 have these stuff modeled since release years ago, they still work today. It is also very easy to check you just have to go set the malfunction too 100% and voila it works. But in m2k i can set everything too 100% and nothing happens. Regarding the hits, i grant you i doesn`t always happen to survive direct hits, but when you do survive and i doubt this has not ever happened for anyone, the only stuff that malfunctions is: nose cone drops, radar is out, rwr stops working, and for some reason with fully operational engine in aft you can not pass certain airspeed (increase in drag) and that is it. This happens regardless of what hits you aim120, r27, AAA, sam, never more, never less. I think only once it happened for me after i survived a hit to get an engine fluctuation, and that happened right after that got implemented 1 year ago, it does not happen any more... I cannot even complain that the system indication panel does not light up, since nothing ever breaks except what i mentioned above. But when i get a hit i`m on fire loose a wing and go in an inverted stall towards the ground shouldn't something light up on the system panel indicator ? Except for the start up sequence and occasionally PCAB i`ve yet to see that panel indicate anything. I grant you there has been a slight improvement over the original release when you could fly without wings and on fire, but it is far from being ok...

I don`t think it`s ED`s job to script how the plane acts with total hydraulic failure, or for that matter any other failure. I know exactly what in term of damage is on ED`s side, the things i`m describing are not.... Also why is ground radar also on ed`s side doesn't the Viggen have air to ground radar ? The issues i`m describing don't happen in other plane the fact that you can survive direct hits from r27, aim120, sam`s, DIRECT hits to the cockpit, and every time you get hit the exact same things happen are not on ED`s side.

My biggest gripe with the module is with the damage implementation. It`s simply totally lacking, the panel is useless cause it`s scripted to light up in a sequence on start up and that's it. Whenever you will get hit you will loose nosecone, radar and rwr and you`ll get a drag increase and that's it.... You will notice it doesn't matter what hits you the damage is always the same. Nobody from razbam said they will work on this. Besides this there are a lot of issues with missing systems beside the visual stuff, you can browse the m2k thread and you`ll find what is missing. It`s true there are 3 third party developers in worse situation but at the same time there are 3 party devs light years away ahead of razbam to use the same comparison as above. I would suggest to wait a bit and see what happens after the release of the harrier. Because right now the same thing that was promised for m2k is promised for harrier, and m2k is in the stat it is ..

Just speechless... Awesome looking beast

Just to bump this, any news on getting an improvement over the damage received by the m2k ? In terms of systems and their indication on the panel. It is really bugging me this thing sorry to bring up over and over again but in mp it sometimes brings an unfair advantage over the other planes.