Jump to content

Bugs and Problems


baltic_dragon

Recommended Posts

  • 2 months later...

For the Red Flag I am trying to find a solution, this is something linked to the general taxi behaviour at Nellis. If all goes well I'll have a fix for the next week's update @Xillix and @BiscuitBoustifon. The more campaigns I have out there, the more difficult is to keep track of all the bugs introduced with different updates, but I am doing my best (I am just one person...) 🙂

  • Like 3
ce535d_9d347b62819c4372b3c485a4f95d2004~mv2.png
Link to comment
Share on other sites

  • 4 weeks later...

I am not sure if I am having the same issue as described, but in mission 3 of the red flag campaign my wingman does not take off. He does follow me on taxi. But after tower (the f10 tower) clears me, I take off and he does not nothing. He’s 45 degrees on the runway and just sits there. He also blocks everyone behind.

Strange enough, I switched to the 3 mission campaign (Hormuz) and I have the exact same issue.

 

I am wondering if I do something wrong. I am using the f10 menu and on the right radio channels.

Link to comment
Share on other sites

  • 2 months later...

Mission  13: Cavalry Has Arrived.

 

Kneeboard and briefing notes both refer to the laser code as 1688, but in-game dialog with Ghost still says 1668 (until you get to the comms lasing dialogs, then it's correct again).

I'm not updating this anymore. It's safe to assume I have all the stuff, and the stuff for the stuff too. 🙂

Link to comment
Share on other sites

  • 2 weeks later...

Mission  13: Cavalry Has Arrived.

When you are approaching the mountains, you hear an AWACS (?) alert msg that you are too high, can be seen, and to get lower, except, it's addressed to your escort's callsign, and then your player replies anyway, and the escort doesn't. (I think the original msg just has the wrong call-sign, and it's supposed to be directed at the player, not the escort, who is not trying to be low in the first place).

I'm not updating this anymore. It's safe to assume I have all the stuff, and the stuff for the stuff too. 🙂

Link to comment
Share on other sites

  • 2 months later...

Coup D'Etat #3 SA-342 Gazelles not engaging, they just flying around and keep getting punish by AAA. Some of them shoted down, one of the Gazelle lost its tail rotor, but AI was able to RTB safely 🤣 = not fault of the mission

No message about neutralizing AAA received, -> no engagement clearance received 🤒


Edited by GumidekCZ
Link to comment
Share on other sites

I have just played a little with that mission last night in DCS editor a found some issues - but not single one related to mission scripting.

1) helicopter Search and engage in zone is broken somehow in DCS, at least for French army Gazelle / UH-1. They both didn’t found anything to open fire on.

2) helicopter AI is just dumb! AI helicopter was engaged by AAA, as soon as beyond the range of AAA, he will turn back in attack run on less threat ground units and will be shoted down because AI needs long aiming time and forgot that he almost died few seconds ago. In test I also noticed some suicide behavior of AI when attacking - diving on target with rockets like German Stuka smashing into ground and his wingmen colliding with civil building after he just evaded AAA fire. If the AI will not engage ZU-23 on first attack run ... they are DEAD! Strange thing is, that in first attack run I had at least partial success with UH-1 Huey unguided rockets, Gazelle cant hit anything, not even pilot with skill set to ACE by default in this mission. AI needs to see the ZU-23 from direction of first attack heading, if is hidden behind building or wall, helicopters are practicaly dead.

I almost forgot, than Gazelle have some glitch in mission, not showing the arm - holding unguided rockets. After just setting same weapons in ME, the arm show up correctly.


Edited by GumidekCZ
Link to comment
Share on other sites

  • 4 months later...
On 8/3/2022 at 1:23 PM, GumidekCZ said:

Coup D'Etat #3 SA-342 Gazelles not engaging, they just flying around and keep getting punish by AAA. Some of them shoted down, one of the Gazelle lost its tail rotor, but AI was able to RTB safely 🤣 = not fault of the mission

No message about neutralizing AAA received, -> no engagement clearance received 🤒

 

same here

--------------------------------------------

i7 12700F | 64GB | RTX 4090 | Asus Z690-P WIFI D4 | 2TB SSD

Link to comment
Share on other sites

  • 1 month later...
On 10/24/2021 at 6:22 PM, mono said:

Getting this exact same issue. Where the Mission Editor thinks this parked E-3 should be vs. where it appears in-game.

M02parkedawacsbug1.png

M02parkedawacsbug2.png

Hello guys, in Mirage campaign I am having the same issue in Mission 8. Everyone is stuck on taxi because of parked AWACS.

Link to comment
Share on other sites

2 hours ago, thrston said:

Hello guys, in Mirage campaign I am having the same issue in Mission 8. Everyone is stuck on taxi because of parked AWACS.

The campaign/mission was created with an earlier version of DCS that allowed the AWACS to spawn at Parking 79, the current version of DCS "forces" it to spawn at Parking 09 which blocks the taxiway for AI aircraft.

AFAIK the AWACS only spawns at Parking 79 for ambiance/eye candy and can safely be deleted and/or replaced with a static model without effecting the mission.

AWACS at parking 79 replaced with a static model

Screen_230220_102405.jpg

Here the AI flight has passed the static AWACS at parking 79 and C-130 at parking 09 and taken off.

After starting up the Mirage the taxiway is clear for player and AI to reach  runway and take off.

Screen_230220_104437.jpg

Tested using DCS Open Beta 2.8.2.35759

Mission 08 FINAL - with static AWACS.miz


Edited by Ramsay
  • Like 1
  • Thanks 1

i9 9900K @4.7GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 10 Pro x64, 1920X1080

Link to comment
Share on other sites

7 hours ago, Ramsay said:

The campaign/mission was created with an earlier version of DCS that allowed the AWACS to spawn at Parking 79, the current version of DCS "forces" it to spawn at Parking 09 which blocks the taxiway for AI aircraft.

AFAIK the AWACS only spawns at Parking 79 for ambiance/eye candy and can safely be deleted and/or replaced with a static model without effecting the mission.

AWACS at parking 79 replaced with a static model

Screen_230220_102405.jpg

Here the AI flight has passed the static AWACS at parking 79 and C-130 at parking 09 and taken off.

After starting up the Mirage the taxiway is clear for player and AI to reach  runway and take off.

Screen_230220_104437.jpg

Tested using DCS Open Beta 2.8.2.35759

Mission 08 FINAL - with static AWACS.miz 8.48 MB · 1 download

 

Thank you very much! How did you manage to step into the mission? I've tried to edit it and it seemed locked for me.

Link to comment
Share on other sites

2 hours ago, thrston said:

How did you manage to step into the mission? I've tried to edit it and it seemed locked for me.

1. I copied the mission to my "Saved Games\DCS\Missions" folder

image.png

2. Opened it in the Mission Editor and selected "Show Hidden Units" on the Unit List

Open_Mission_and_show_hidden_units_to_edit_Screen_230220_211417.jpg

  • Thanks 2

i9 9900K @4.7GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 10 Pro x64, 1920X1080

Link to comment
Share on other sites

  • 2 weeks later...

I have found some conflicting data between the briefing notes (the page with blue red and green writing on a lined page)  and the mission plates (the table with all the frequencies, wp altitudes, bingo info etc.) in Mission 7 and 8 of the caucasus campaign for the Mirage 2000. 

namely !

  • the IFF settings  aren't the same on the briefing note and the mission plate

I.E on mission 8 the briefing note says IFF 1987 but the plate with all the WP altitudes and frequencies says 1330

 

  • Another disparity is the QNH which differs between the Metar and the briefing notes. 

I.E. in mission 8 Metar says QNH 1009 the briefing notes says 1013.

  • on the mission plate of Mission 8 the Guard frequency is Red channel 3 but the during the mission it's red Channel 6
  • the flight name on the plate is Chevy 1 not Pontiac 1

same disparities can be seen in at least mission 7 (might be others)

it is confusing as to know which value to use to set up the planes or during the mission.

 

on another note, the AWAC and Cargo plane obstructing the taxi of the other CAS Mirage 2000-C pairs at the start of the mission is back. I had to remove them from the map to be able to fly the mission.


Edited by Mermoz
  • Like 1
Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...