sunski34

Very interesting ;) If it is a real manual, I saw that a BRM push button is used for weapons and the joystick trigger is only used for cannon A/A and A/G modes (actually trigger is used for all weapons).

I will send you my mod asap.

Hi, see here : https://forums.eagle.ru/showpost.php?p=3189588&postcount=1 here is an extract : {down = 3193, up = 3193, cockpit_device_id = 7, value_down = 0, value_up = 0.5, name = _('Air Refuel Transfer Switch OFF ELSE ON day'), category = _('Add on switch')}, {down = 3193, up = 3193, cockpit_device_id = 7, value_down = 1, value_up = 0.5, name = _('Air Refuel Transfer Switch ON night ELSE ON day'), category = _('Add on switch')}, you just have to add those lines in the default lua joystick file. Hope that help. Sunski

Just a word ... EXCELLENT ... Thank you for those informations. Sunski

Ok... More tests ... I'm in W10 and in my case (1080 GTX), when full screen is set in DCS 1.5.7 then I have the problem. If ths option isn't set, it's ok. The problem seems to be random because of Alt+Tab key use (which desactivates this option in DCS).

Strange ... it's not a permanent problem... If I restart DCS then it's good. I will test again.

Hi, It dépends on what you call "fly".... Personnaly I started with A10C but M2000C didn't exist. Mirage is a FBW plane so for normal fly, M2000C is not very difficult compare to a spit for example or a L39. Those planes don't have electric or electronic systems to avoid (as possible) pilot errors. As a delta plane, the problem is AOA when landing for example or the loss of speed when turning at limits. A/A missiles are Fox 1 and Fox 2 so if bandit has Fox 3 (fire and forget radar missiles) or long range fox 2 that may be hard for you and you need a lot of practice to win ... Because of its unfinished doc, it's difficult to have all informations to learn correctly. This is actually a real problem for a beginner. As Jojo said, A10C is more complex (weapon and sensors) very interesting for A/G but not for A/A. M2000C offers the 2, even if A/G is less powerful (no pod for targetting) because M2000C is an interceptor first ;)

A big difference between 1.5.6 and 1.5.7 version when moving head rapidly in cokpit (test done with M2000C). I'm using track IR. The sync of the frame has a big problem and the image is simply bad when moving the head rapidly (one client, no AI). I did a rollback and all is good again. So a 1.5.7 problem :mad::mad:

+1 When is the real question.... Hope next 2.1.X update ;)

Agree with you .... But I'm not sure it's the case ... I never see a real difference ...

Yes faster so more scan of the zone in the same delay so detection will be better I think no ? :cry:

RWR may have problems like direction when locked on 1.5.X ... very difficult to see the direction because the symbol is displayed in the center (or nearly). When bandit unlocks, the time delay (sound and display) is a bit long ; perhaps this is the case in real life. Finally, sometimes, sounds continue with no display on RWR with the same delay after bandit destruction, but in that case, it's strange.

No real problem with the radar .... Sometimes the detection is hard even in good situation to detect ... Difficult to say if it's a bug or not. Sometime when bandit jammer is activated, the dash like which indicates the direction of the jammer is not displayed even if a corresponding "V" is on display ... Perphaps here a problem may exist but not sure What is strange there's no real change of the distance detection delay when moving 60/30/10 of azimuth for a given distance of scan (40 NM for example). I don't test with 1/2/4 lines... smaller is the detection zone, better is the quality of detection I think.

HOTAS MAG and CAN must be used to select AA+Magic or AA+Cannon. HOTAS PCA must be used to select PCA. If PCA is set on 530 then AA+530 is activated... So, from my point of view ... it's not strange having only one button to select magic (HOTAS MAG). But, if PCA Mag just activates the magic seeker, there's probably a good reason if this is the the real life functionnality of the PCA. That may be usefull to help for bandit localization ! Does anybody knows ?

I'm waiting for those two updates ;)

I spoke about what Zeus told us a few month ago : and of course there the FM adjustments.

This Zeus reply ... https://forums.eagle.ru/showpost.php?p=3097392&postcount=4493 and this https://forums.eagle.ru/showpost.php?p=3165798&postcount=4700 where a delay is indicated... Still wait and hope it's just a question of 2.1.1 ED actions ... So wait and see Sunski

So only land lights work in MP that's right?

Thanks Azrayen ;) So actual implementation in this module is good, that is correct ? As I understand, IFF works with mode 4 in DCS (liked to coalitions). When playing, we set the digits to 9000 ... If you know how it's work, can you explain a little bit the process or give me a link ?

Hi, when in MP (I was server), at the start (starting hot for example) or when changed by switch, those remote client plane lights doesn't illuminate .... If player move its switch then it's ok. Same problem when landing. Of course, in all case, taxi/land lights are turned on. I hosted the game. I didn't as a remote client. Regards

Hey, please find here a few lua lines to add a new category and some new binds for joystick default lua file : {down = iCommandSwitchMasterArm, up = iCommandSwitchMasterArm, name = _('Master Arm TOGGLE else STOP'), category = _('Add on switch')}, {down = 3450, up = 3450, cockpit_device_id = 16, value_down = 0, value_up = 0.5, name = _('Landing Lights OFF else TAXI'), category = _('Add on switch')}, {down = 3450, up = 3450, cockpit_device_id = 16, value_down = 1, value_up = 0.5, name = _('Landing Lights LANDING else TAXI'), category = _('Add on switch')}, {down = 3249, up = 3249, cockpit_device_id = 6, value_down = 1, value_up = 0, name = _('Selective Jettison ON else OFF'), category = _('Add on switch')}, {down = 3454, up = 3454, cockpit_device_id = 16, value_down = 0, value_up = 0.5, name = _('Navigation Lights OFF else DIM'), category = _('Add on switch')}, {down = 3454, up = 3454, cockpit_device_id = 16, value_down = 1, value_up = 0.5, name = _('Navigation Lights ON else DIM'), category = _('Add on switch')}, {down = 3453, up = 3453, cockpit_device_id = 16, value_down = 1, value_up = 0, name = _('Anti-Collision Lights ON else OFF'), category = _('Add on switch')}, {down = 3455, up = 3455, cockpit_device_id = 16, value_down = 1, value_up = 0, name = _('Formation Lights ON else OFF'), category = _('Add on switch')}, {down = iCommandPlaneCobra, up = iCommandPlaneCobra, name = _('FBW G-Limiter Mode else OFF'), category = _('Add on switch')}, {down = iCommandPlaneModeCannon, up = iCommandPlaneModeGrid, name = _('AA Gun Select ELSE PCA Select'), category = _('Add on switch')}, {down = iCommandPlaneModeFI0, up = iCommandPlaneModeGrid, name = _('MAGIC Select ELSE PCA Select'), category = _('Add on switch')}, {down = 3276, up = 3276, cockpit_device_id = 6, value_down = 1, value_up = 0.5, name = _('Bomb Fuze: INERT ELSE RET'), category = _('Add on switch')}, {down = 3276, up = 3276, cockpit_device_id = 6, value_down = 0, value_up = 0.5, name = _('Bomb Fuze: INST ELSE RET'), category = _('Add on switch')}, {down = 3193, up = 3193, cockpit_device_id = 7, value_down = 0, value_up = 0.5, name = _('Air Refuel Transfer Switch OFF ELSE ON day'), category = _('Add on switch')}, {down = 3193, up = 3193, cockpit_device_id = 7, value_down = 1, value_up = 0.5, name = _('Air Refuel Transfer Switch ON night ELSE ON day'), category = _('Add on switch')}, {down = 3468, up = 3468, cockpit_device_id = 7, value_down = 1, value_up = 0, name = _('In-Flight Start Switch ON ELSE OFF'), category = _('Add on switch')}, Hope that help. Regards Sunski

Hi, on some french video on YouTube, people said that IFF used two instrument parts in the cockpit : One, just behind the joystick, which is used to program the onboard IFF (transponder) One, on the left side, which is used to select only the IFF scan, the four digits display the current IFF (or transponder) of the locked target. So thoses digits cannot be changed by the pilot. Actually, this part is used to program and select IFF on board So what is the real implementation in M2000C ? and why the part behind the joystick isn't implemented ? Thanks you for your answer. Sunski

@Skitter : Please read all the post before reply.... see here for more informations https://forums.eagle.ru/showpost.php?p=3187304&postcount=202 I just reused words baltic_dragon used ;) and from my point of view the question is not minor or major but when thoses things will be done/fixed... Having a road map is the best way ... Regards

Those two modules are not in the same state... and Viggen is Viggen, M2000C is M2000C.... RAZBAM has to do some work to add (or fix) minor things as told before in that thread... So just let RAZBAM tell us when those updates will be available....

Of course, this module is a great DCS Module, I enjoy (love) it and of course it's a real pleasure to fly ... The problem is not the quality of the work RAZBAM has done... But as you said, some minor things (bugs or problem) are still existing ... Yes minor... and those minor things seems to need a lot of time to be fixed or done ... What's why some of us are disappointed ... The fact is no real update since April, announced delay to have an avionic update shifts (3 weeks at most announced by Zeus67 on June 12th) ! and no news ... As we say in french "Le diable se cache dans les détails" .... Devil is in the detail ! I know it's hard to have two versions 1.5.X and 2.1.X, I know that RAZBAM waits for ED functionality... But why it isn't possible to fix or do in a correct time the minor things you spoke about ? Regards