Sandman Simulations

Hi, Thank you. The date is correct 2005 but mission starting time is 00:00. Changing this did fix the bug. Might need to report ED about this. At least during testing phase of the campaign it wasn't like this. Thanks to you I now know how to fix this

Thanks. It should have landed and pick the pilot when it was above him. Seems that something was wrong with the helo about a mile before reaching the target and it started to fly abnormally. Don't know why it worked normally for me and hasn't done that before. Please contact me if this problem persists so I'll keep trying to find the cause for that.

I tested it but wasn't able to replicate the problem. Helo got to the crash site and back. Could you please send me a track file or tacview file if possible?

Hi, Thank you for reporting. I'll take a look.

I've been searching for the root cause of this bug like there is no tomorrow. I have the same problem as you have. Player aircraft is shown at Khasab airport in HSI. F10 map shows aircraft where it really is at the carrier.. When alignment is ready the aircraft position is instantly corrected but about 40 seconds after turning INS-knob to IFA the position returns back to Khasab. It also shows the carrier TACAN at same wrong point on HSI. Waypoints and targets in SA-page seems to be where they should be but player aircraft position is wrong. Very very strange. It seems to only happen in this stage (not other night stages), only in night time, only when cold starting on the carrier. I tried to set a new unit on the carrier and the problem is still there. I have no idea what could cause this kind of problem. There is no GPS or INS malfunction set in the mission. I found that if you do alignment normally but don't turn INS-knob to IFA but to NAV the aircraft position seems to stay correct. Until I find the fix (if ever) this could solve the problem. null

Hi, Thanks for your report. Sounds very weird indeed. I'll take a look.

Not the easiest mission at all

Hi, You are right there has been a bug since the DCS update introducing new fuzes. It's not just RE but all programmable bombs like GBU:s. There is already a fix for that but unfortunately I'm not allowed or able to release it other ways than via official DCS update which should become next week I hope. Changing weapon type is not recommended as it causes triggers recognizing the bomb to fail. But now that you asked I tested and you can change weapons via rearming menu on the deck. If you select different bomb, ask rearm and after crew has set those new bombs ask them to set back your first ones. Fuzes start to work. At least GBU explodes and also Rockeyes seem to open and explode.

Hi, Thank you for your feedback. It's always welcome. I have avoided keeping the lead following the tanker after AAR since seeing so many broken campaigns where the stop follow -command stops working and the lead won't proceed. As you said there is no point if you need to burn your fuel to catch the lead after aar. I will definitely set this to my fixing list. DCS update introduced some new bugs with the campaign and I'm working to get them fixed asap. With those bug fixes there will be update for the formation flying requirements for better playability and less nagging. I'll also add the player a possibility to report when he has the target in sight during JTAC talk-on.

Thank you very much for your feedback.

Made some tests and there is something weird at the moment when an aircraft is set to climb straight until given distance and then should turn to intercept. Reported this to ED. But until the mission gets fixed it seems to be possible to beat it but it's harder than it should.

Just checked your recordings. Thank you very much for those. Flight lead flies some very strange pattern (circle around the carrier at 10000 feet at 300 kts). Actually also Skull 5 flight launching before him does the same. Both have orders to fly straight climb and until now they have done that too. It seems that after the latest update the mission is broken. The carrier battle group missile defense system should also be able to take out the first wave of incoming missiles but in your recordings they failed to do that. I'll start looking for solutions.

Hi, Thanks for reporting. The lead should climb and turn to initial heading so something is not right there. I'll check it asap.

It might have. At least don't use spacebar or backspace for any key binding as they are used for mission interaction.

Hi, Thank you for your message. Unfortunately I have no idea what could cause this as there is no way it could be dissabled by the campaign. Can you open the communication menu at all or just some part of it? Have you checked your key binding for it?

Thank you very much for your feedback There has been some kind of issue with new fuzes after the latest update. It could be that. There are some problems in all campaigns and ED is working to make it fixed asap.

Unfortunately it might take some time unless ED releases a hotfix. I briefly checked and I think this is the only mission with the taxi problem.

Thank you for reporting this and thanks for the file. Just tested and it's just like you said. Something has been changed in the last update as it worked normally before. Need to report ED about this.

At least the fuze must be selected.

By the way what did you do to solve the mission 13 loading problem?

Great to hear it worked this time and you are so far in the campaign. Hits should be counted if the aircrafts are destroyed but I'll double check the hit counting. It's possible that you have made everything right but the target has only been damaged. Don't get the feedback in debriefing too hard.

The Tanker deactivation trigger is set to fire 120 seconds after player has reported "ready to proceed" by pressing spacebar and Jaguar 3 has finished refueling. Is it possible you reported ready before refueling?

Hi, Thanks for reporting. I'll take a look. For performance reasons tankers will be deactivated but it shouldn't happen before player is far away. If you are using Tacview please send me a file.

11/7/24 update M2 Intro. Wrong date - fixed M3. Some adjustments for AI behavior M6. Enemy skill level adjusted. Enemy ship sometimes hit himself - fixed

Great to hear you anyway have managed to play those missions. As I can't replicate the problem it's quite hard to find the solution. I still would be eager to hear if there are more players having this same problem if we could find the nominator causing it.