Mirage over Caucasus Fighter Mbot DCE Mod

one last question... what triggers the escorts to take off? for me to loiter for a certain amount of time at nav 1?

It's really a strange bug I never had. You are starting cold so I don't know why you can't power them after a normal startup ?!?

There's no trigger for escort : they respect the mission timing (look at the briefing) In the readme file you can see that I put a really big timing between player appearance on the ramp and the real mission start : I like take my time and depending on the mission I can refuel with my wingmen before going to the target or the CAP zone. You can change this in the camp.ini file (see the readme file ;) )

It's really a strange bug I never had. You are starting cold so I don't know why you can't power them after a normal startup ?!?

There's no trigger for escort : they respect the mission timing (look at the briefing) In the readme file you can see that I put a really big timing between player appearance on the ramp and the real mission start : I like take my time and depending on the mission I can refuel with my wingmen before going to the target or the CAP zone. You can change this in the camp.ini file (see the readme file ;) )

ahh see i thought the ingame time was broken. because the start time is a few hours prior to TOT. so do you accelerate time? I'll pay more attention to the readme file. thanks for your help!!

Hi,

i just played the first mission with a buddy in 2-player coop and it was much fun, so thank you and mbot for these campaigns :)

We did encounter a few problems though, which i did not have when playing the campaign in single player mode. These only occurred after restarting the campaign in 2-player coop mode:

• Neither of us were able to contact AWACS at all.
  
• When contacting Airbases for takeoff/landing etc. there was no audio output or text messages.
  But i guess the "state*" of my flight changed. As could be observed by subsequently contacting the tower. This would result in having the dialog option of e.g. aborting the takeoff/landing.
  *(state as in situation, don't know how to phrase it better, sorry)
  
• Neither of us could pick up the ILS frequency.
  

Attached is the generated .miz file for the first mission.

Let me know if you also want anything else, such as the tacview track.

edit: weird, simply opening the mission in the mission editor and saving it seems to solve the problem.

Mirage over Caucasus-Multirole_first.miz

Man! I'm getting creamed in this thing. Has it always been this hard? I'm playing the multirole v5 in 1.5.8. Any way to dl a newer version? Or any hints? SAMs everywhere and enemy fighters. Crazy. Couple versions after 5 aren't there? I'm not saying it will be any easier but just curious. Great job though. Thanks.

Well first missions are really difficult because SAMs EWR and Intercept fighters are at full strength ! The campaign system should try to weak them a little by destroying EWR first to stop Intercept red missions and only allowing less effective CAPs.

When you are flying a strike mission with escort let them go first to clean the sky a little and if it seems to difficult go back and wait for an easier opportunity to go through defenses. Try to adapt your waypoints to avoid not targeted SAM sites (It should be done by DCE). When you are in a big dogfight try to avoid to fly over enemy SAMS or Airbases. Begin your attack run from high altitude and launch bomb higher as possible and of course make only one bomb run using all of them to destroy one target, then run away quickly !

Thanks for the tips. I'm doing a little better. Part of the problem is I'm not quite up to speed in the Mirage. Getting better though. No mistake PB...this thing is a hoot! Works great. Thanks for doing it. Guess I'll have to get off my duff and upgrade to 2.5. Thanks pal.

Lctrl + Z will accelerate time. Lalt + Z will slow it back down.

Hi,

 

i just played the first mission with a buddy in 2-player coop and it was much fun, so thank you and mbot for these campaigns :)

 

We did encounter a few problems though, which i did not have when playing the campaign in single player mode. These only occurred after restarting the campaign in 2-player coop mode:

 

• Neither of us were able to contact AWACS at all.
  
• When contacting Airbases for takeoff/landing etc. there was no audio output or text messages.
  But i guess the "state*" of my flight changed. As could be observed by subsequently contacting the tower. This would result in having the dialog option of e.g. aborting the takeoff/landing.
  *(state as in situation, don't know how to phrase it better, sorry)
  
• Neither of us could pick up the ILS frequency.
  

 

Attached is the generated .miz file for the first mission.

 

Let me know if you also want anything else, such as the tacview track.

 

 

edit: weird, simply opening the mission in the mission editor and saving it seems to solve the problem.

Hi,

I didn't try the campaign in MP, and I don't know how well you master the M-2000C systems.

But what you are describing looks like a bad use of the radio.

You have 2 different radios, each one with their "Push To Talk" button to map on HOTAS (or use keyboard).

Each will trigger the coms menu.

But, by default, only one of the radios (UHF from memory) have the missions preset channels.

So if you use the preset channels of V/UHF and/ or V/UHF PTT button, it won't work.

One question,how can I change the time of the takeoffs, I always have to wait 30 minutes, it's too long when I play alone? Thx

Readme file, Changelog version v8.0 :

"New Mbot DCE version (december 2017). New variable timing for player start. It gives time to Mirage 2000C drivers to prepare the plane and even to refuel before crossing frontline. If you want less time, you can change timing on line 21 in "EN/Campaigns/Mirage over Caucasus-Fighter-Light/Init/camp_init.lua" file using free notepad++ for example :

startup_time_player = 1800, (defaut setting gives you 30 minutes before normal take off ! If you want 15 minutes put 900 for example... )"

;)

Hi,

 

I didn't try the campaign in MP, and I don't know how well you master the M-2000C systems.

 

But what you are describing looks like a bad use of the radio.

You have 2 different radios, each one with their "Push To Talk" button to map on HOTAS (or use keyboard).

Each will trigger the coms menu.

But, by default, only one of the radios (UHF from memory) have the missions preset channels.

So if you use the preset channels of V/UHF and/ or V/UHF PTT button, it won't work.

This is a bug when playing the generated missions in multiplayer with some aircraft types. The generator assigns custom frequencies to the players a/c but not to the other a/c in the flight. For some cases opening and saving the mission in the editor seems to reset the remaining a/c from their default frequencies to the new custom ones. For other a/c types it is better to manually set all the frequencies and save the mission prior to playing in multiplayer.

Well this campaign doesn't care of "winning" a mission or not. You have ground targets and your goal is to destroy them or to kill enough red planes to deplete completly red air force. You loose if you have too much losses and it's a draw if you don't win before the max number of allowed missions (40 I think for the normal campaign). That's simple ;)

Okk, then I understand that I can refuel and take off as many times as I wish in the same mission.

When you have finished, do you give a final mission, or do you advance the time to see how the battle between AI develops?

It's not exactly like this that this campaign must be played. It's a strategic campaign not a tactical one (bombing rather than doing CAS). Your goal is to destroy enemy planes and installations missions after missions. You prepare the mission (DCE makes most of the job deciding which plane will be involved), you fly it (trying mostly to survive doing the job) and then you land, look at the debriefing (when you exit the mission) and then you launch an other mission looking for what HQ had prepared for you :thumbup:

DCE will not work very well if you land reload and go back to fight :you will quickly be alone in the sky :music_whistling: and it will be boring no ?

This is a bug when playing the generated missions in multiplayer with some aircraft types. The generator assigns custom frequencies to the players a/c but not to the other a/c in the flight. For some cases opening and saving the mission in the editor seems to reset the remaining a/c from their default frequencies to the new custom ones. For other a/c types it is better to manually set all the frequencies and save the mission prior to playing in multiplayer.

Good to know, thanks :thumbup:

Thanks for the campain!!

Just had my first CAP flight yesterday but nothing happened, not a single bogey to shoot: but I believe that's good news :D

Just one question for the frequencies handling: how should we use the radio? I was forced to use only Vuhf on channel 1 (element) to talk to my wingman, where I'd prefer having the flight com on UHF while monitoring either element/awacs on VUHF. Am I doing something wrong?

Thanks for the campain!!

Just had my first CAP flight yesterday but nothing happened, not a single bogey to shoot: but I believe that's good news :D

 

Just one question for the frequencies handling: how should we use the radio? I was forced to use only Vuhf on channel 1 (element) to talk to my wingman, where I'd prefer having the flight com on UHF while monitoring either element/awacs on VUHF. Am I doing something wrong?

Strange you didn't have any bogey !?! Did you wait until the end of the briefed time for the CAP ? First missions are usually rather busy ! Did you use the last campaign version ?

I prefer using pre-defined channel to listen to AWACS ATC or Tankers and use the other radio to manually listen to my package all the mission long :thumbup:

Yup I was exactly on time... Strange I had no encounter then. Had a second mission where I found 4 bombers that I could shoot, and my 3 mission, an F15 strike escort: again no trouble: the F15 could strike the target without any bogey encounter for me and my wingman.

For the radio, I realized yesterday I was just stupid.... I thought the second radio couldn't use the same frequency range (because frequency ranges are different for both radios on the kneeboard)...... Then realized I could just set the package frequency on it :cry:

Problem solved :music_whistling:

Multirole link points to Fighter version.

Multirole link points to Fighter version.

Link fixed sorry :(

NP, thanks a lot.

Hi !!! I just installed the campaign but when I launch it I have that error message :

The following module needs to be installed : USN-deckcrew ... what is that please ?! :helpsmilie:

Thanks for any help !!

John "Kalon"

Hi !!! I just installed the campaign but when I launch it I have that error message :

 

The following module needs to be installed : USN-deckcrew ... what is that please ?! :helpsmilie:

 

Thanks for any help !!

John "Kalon"

Look in the campaign folder in the Init folder and find conf_mod.lua

On this line :

Keep_USNdeckCrew = false, -- (default : false), false = supprime US Navy deck crew dans la génération de mission (Ceci n'installe/desinstalle pas le MOD USN) Miguel Modification M23

Be sure it's false and not true (use Notepad++= to change it if necessary)

Salut PBO_CEF,

j'ai regardé dans le fichier conf_mod.lua mais aucune référence à USN-deckcrew n'a été trouvé :cry:

Pourtant le problème persiste que ce soit dans la version fighter ou multirole... Merci quand même pour ton aide :)

=========================================

Hello PBO_CEF

I looked into conf_mod.lua file but I saw the words USN-deckcrew nowhere :cry:

But the problem remains, wether in the fighter version or the multirole one... Thank you anyway very much for your help :)

John "Kalon"

Salut PBO_CEF,

 

j'ai regardé dans le fichier conf_mod.lua mais aucune référence à USN-deckcrew n'a été trouvé :cry:

Pourtant le problème persiste que ce soit dans la version fighter ou multirole... Merci quand même pour ton aide :)

 

=========================================

Hello PBO_CEF

 

I looked into conf_mod.lua file but I saw the words USN-deckcrew nowhere :cry:

But the problem remains, wether in the fighter version or the multirole one... Thank you anyway very much for your help :)

 

John "Kalon"

Argh désolé c'est une campagne très ancienne l'option n'est pas encore possible ... Je regarde ce que je peux faire avec le fichier mission ;)

Argh Sorry it's a very old campaign There's not this option yet. I will look at the base_mission ...

Remplace le base_mission qui se trouve dans le dossier Init puis relance une génération de campagne avec le fichier FirstMission.bat. J'espère que ça va fonctionner... sinon une campagne rénovée Mirage over PG sort bientôt ;)

Please replace the base_mission file in the Init folder then generate a new campaign with FirstMission.bat file. Hope it will work...

A new DCE version campaign will come soon : Mirage over PG

base_mission.miz