Mission 10 bugs

[scotth6]

Hi,

 

I just updated to DCS World 1.5.7 today (release version) and upon continuing the campaign I found a few issues. Not sure if they are mission bugs or related to the update.

 

In Mission 10 I ran through my pre start and start procedure then began to taxi. As my lead was approaching the last turn on to the last taxiway he stopped just before he made the turn. Now I figure I just got too close to him, so as I was just next to the E-3's large apron, I did a u-turn and taxied back a bit and then my lead continued. I just mention this in case it led to or was related to other bugs coming up.

 

We then took off with 15 second separation. As I approached Chevy 1-1 I noticed he was going VERY slow. I braked but still flew past him. This is the first time a lead has flown so slow in the campaign. I circled and joined up but I could barely stay airborne at the speed he was flying. Eventually I just sped up a bit to stay airborne, hit autopilot, and had a look at his speed using F2. His speed remained a constant 283-287 KM/H. Note, not knots, but KM/H. I don't remember this speed indication being labelled in KM/H, so maybe that's something to do with a cause.

 

I then had a look at my map to check things out. Another thing was that my lead's call sign was Chevy 1-1, but even though I was his wingman mine was Chevy 2-1 (should be 1-2?).

 

Then I noticed my aircraft turning on the map so I quickly pressed F1 to get back to the cockpit but nothing happened. I tried several times but could not get back to my cockpit. I tried F2 and F3 and those views worked. I also could not control my aircraft which by this stage was in full afterburner no matter what I did with my controls.

 

So something bugged out big time, and I'm not sure what. I will refly the mission soon and report back if anything has changed.

 

Cheers,

[Ramsay]

I then had a look at my map to check things out. Another thing was that my lead's call sign was Chevy 1-1, but even though I was his wingman mine was Chevy 2-1 (should be 1-2?).

Keeping the player(s) unit as a separate 'group' is normal/correct - often script functions and mission triggers are only available or work best for 'groups' e.g. as Chevy 1-2 can't be used, I often use 2-1, 3-1, etc. to represent flight elements 1-2, 1-3, etc. as it remains logical and an easy way to see which unit is which element.

 

I had a glitch in one 1.5.6 mission where a trigger seemed not work, I checked my Gameplay settings (think I had km/h and MGRS) and replayed the mission without issue (so it also could have just been a DCS thing :) ).

 

What are your settings ?

• Options\Gameplay\Language = English
  
• Options\Gameplay\Units = Imperial
  
• Options\Misc\ Co-ordinate Display = Lat Long Decimal
  

[scotth6]

Hi,

 

Thanks for the reply Ramsay.

 

I was going to check/change my settings, but I thought I would run the mission through before I did to rule things out before I changed anything. I thought I had my settings same as yours above, but I am yet to check since the update.

 

Anyway, good news to report is it seems to have been a one off bug. Not sure what caused it (or them) but it seems good now. I just completed the mission and Chevy 1-1 did not stop on the taxiway and he was flying at normal speed.

 

I have a hunch, although it shouldn't happen. When I first loaded that mission previously I messed up the initialisation while punching in the INS coordinates (Altitude can't be set to 26000 feet at WP4 for some reason and that's still happening). While mucking around with those altitudes I tried to reset the INS (which I haven't figured out how to do) and because I couldn't I quit the mission back to the Campaign menu and started again. Previously there was a bug that caused DCS World to CTD on exit if you ran more than one mission, so I'm wondering if DCS was just bugging out because I exited the mission and restarted. It shouldn't have, and I haven't seen that behaviour for a while, but it's just a hunch.

 

Cheers,

[myHelljumper]

Not sure what caused it (or them)

 

Wine, 9 out of 10 times it's wine :D.

[scotth6]

Wine, 9 out of 10 times it's wine :D.

 

:music_whistling: :drink: :pilotfly:

[baltic_dragon]

Hi,

 

Thanks for the reply Ramsay.

 

I was going to check/change my settings, but I thought I would run the mission through before I did to rule things out before I changed anything. I thought I had my settings same as yours above, but I am yet to check since the update.

 

Anyway, good news to report is it seems to have been a one off bug. Not sure what caused it (or them) but it seems good now. I just completed the mission and Chevy 1-1 did not stop on the taxiway and he was flying at normal speed.

 

I have a hunch, although it shouldn't happen. When I first loaded that mission previously I messed up the initialisation while punching in the INS coordinates (Altitude can't be set to 26000 feet at WP4 for some reason and that's still happening). While mucking around with those altitudes I tried to reset the INS (which I haven't figured out how to do) and because I couldn't I quit the mission back to the Campaign menu and started again. Previously there was a bug that caused DCS World to CTD on exit if you ran more than one mission, so I'm wondering if DCS was just bugging out because I exited the mission and restarted. It shouldn't have, and I haven't seen that behaviour for a while, but it's just a hunch.

 

Cheers,

 

Glad to hear it worked! Three more to go :)

[AMEDooley]

I just had the same issue with leads speed. He is traveling at 167 knots after take off. I'm plugging away and hitting the speed according to the MDC but I'll see what happens.

[AMEDooley]

Just an update, everything is going about 164 knots. Including Overlord. It's a bit difficult to stay in formation.

[AMEDooley]

Restarted mission and had the same results. Not sure if it is a bug. I'm going to check the ME and see if anything is wrong.

[AMEDooley]

Shutdown DCS and restarted looked at the ME and everything was where it should have been. Relaunched mission and everything was fine. The only thing I did differently was I didn't use the time acceleration during the INS alignment.

[baltic_dragon]

Well.. funny. Glad it worked, but I guess we won't be able to avoid such surprises with DCS in the future. Enjoy the rest!

[hellking]

I have been having the same problem!.. The first time it happened I tried to stay in formation with the lead and tried to keep ~130 knots. The aircraft immediately nosed down at couple of hundred feet and I couldn't recover and had a spectacular slow-motion crash. Well, things that you wouldn't do to stay in formation with your lead... ... I have been accelerating time during INS alignment but considering that alignment takes much longer than starting everything else up, it is a bit of a pain to wait in real time...

[hellking]

I would like to confirm that time acceleration during INS has nothing to do with this.. I have not done any time acceleration during start up and the (slow flying) problem was still there.

[baltic_dragon]

Try to completely exit the DCS and reload the mission. This is something clearly introduced with one of the updates, as I didn't touch the mission so I can't fix anything on my end.. plus the fact that I am on holidays without access to my gaming rig does not help either :( hope that the restart would fix things as it did for others.

 

I doubt that time compression has anything to do, but you can always untick the need for INS alignment in options and try then. Let me know if the problem persists!

[Sylosis]

Had the same speed problem in that mission. Everybody flying at 165 knots, making it impossible to finish the mission.

 

At first I tried closing the mission and trying again, without closing DCS. It didn't work.

 

I then closed DCS, rebooted my computer and when I re-tried the mission, I did not speed up time during INS alignment.

 

Not sure which of these 3 elements (closing DCS, reboot or no time acceleration) worked, but there was no issue in the mission after that.

 

And, the AI made it easy for me, as 2 of the L-39s crashed in the mountains by themselves during our encounter! XD

[baltic_dragon]

Sorry to hear about this issue, I will talk to ED people about this as it seems to be connected with the last update... thanks for letting me know!

[Whozdär]

there's something seriously wrong with mission 10 here.

i'm using OpenBeta branch on steam version.

 

Made a quick video of the issue, enabled labels and showed the map in case it helps figuring out what's up.

 

[baltic_dragon]

I confirm, there was a bug I introduced - after testing I forgot to change back one of the triggers. Fixed internally now, here is the link to updated mission - just download it and swap in the folder.

 

DOWNLOAD

[Cyrus]

Thanks for the updated mission! I was now able to finish it.

 

 

 

There is still one issue remaining: flightlead does not leave the HAS until my Mirage is near the runway. The consequence is that I took off first and had to to holding pattern until flightlead was in the air.

 

 

 

I restarted the mission and tried waiting for flightlead to come out at a point that I could just peak into his HAS, but he remained there until I had taxied almost onto the runway.

 

 

 

Meanwhile I have finished the campaign. Great job Baltic Dragon, I really enjoyed it. The Mirage 2000C is my first DCS aircraft and this was my first campaign. Really accessible for a beginner.

[epolta]

Hello,

Just updated to latest open beta today and attempted M10 Escort Duty.

Upon entering cockpit and getting radio checks on Green and Red another conversation starts.

During that conversation I hear my lead and character begin discussing leaving orbit and getting radar lock on another target while I'm still sitting in the chocks?

The only option I have is for F10 menu to report to my flight when ready for taxi. It appears the mission is jumping way ahead while I sit in chocks to get engines running.

thanks!

[epolta]

Hello,

Just updated to latest open beta today and attempted M10 Escort Duty.

Upon entering cockpit and getting radio checks on Green and Red another conversation starts.

During that conversation I hear my lead and character begin discussing leaving orbit and getting radar lock on another target while I'm still sitting in the chocks?

The only option I have is for F10 menu to report to my flight when ready for taxi. It appears the mission is jumping way ahead while I sit in chocks to get engines running.

thanks!

 

Ooops!

just read above my post.

I'll try the updated mission file!:doh:

[epolta]

Tried the downloaded mission and same issue persists. While sitting in chocks lead tells me to leave formation and intercept while still completing engines startup.

Seems to skip ahead somehow.

[Whozdär]

Tried the downloaded mission and same issue persists. While sitting in chocks lead tells me to leave formation and intercept while still completing engines startup.

Seems to skip ahead somehow.

 

Where did you put the file?

 

For my side (I have the Steam version), I'm placing it in ..\Steam\steamapps\common\DCSWorld\Mods\aircraft\M-2000C\Missions\Campaigns

 

You should be overwriting a file.

 

The path should be similar for you, it's not in My Docs but in the game installation folders.

Edited October 28, 2018 by Whozdär

[baltic_dragon]

That’s weird perhaps the update just got to Open Beta so far? pls check the file from the link two posts above and let me know if it works fine.

[Whozdär]

I don't think the fix has made it anywhere yet.

 

He was talking about the version you attached to your post here above.