Badger633

Hey @BuzzinChowski Yeah it is the crosswind pushing your ladder across. Just so you know you can centralise the ladder under these conditions by using the cage and uncage. Just remember you have done this as the velocity vector is then showing a false position.

@ayousry you have sent me the wrong track. This from another mission/campaign. Can you confirm you are playing the normal version of Mission 9 part 2, not the EZ refuel version, you are fully up to date, and you are not running any mods? I am sending you a private message with a link to my test track. This showing the bombs both hitting. Hope this helps.

Hey @ayousry Just flew mission. No problems, hit both targets. Must be something you are doing your end. I could send you my track if you want. This tested on latest Open Beta.

Hey @ayousry Just checked regarding PPL 1 designating different targets for each station. You are correct. I have normally used a different PPL for each target. Will fly the mission and get back to you. EDIT: Just did edited test on mission. Located player approaching target with enemy on weapons hold. Punched in coords , both on PPL1 and both bombs hit their targets. So will do fly through to check then also.

Hey @ayousry Thanks for the track. From what I can see you are making a mistake when putting in the coordinates. When entering the first set of coords you selected PPL1 at the top of the screen, which you did. But after you stepped to the next bomb you needed to select PPL2 on the top tab so that the second bomb has different coords. Not sure what overwriting the PPL1 for the second bomb does to the first bomb. This could be why it is falling short and you are hitting the second target and not the first. Others tips: Do not fly so high when you pass over the last ridge , there is no need and you overexpose yourself. Just clear the ridge and fly towards target you will get in range but make sure you are clear of the ridge slope before release. Noticed your aircraft was not actually pointing directly to the target on release which does make it harder for the bombs to correct their trajectory. I will check the mission out yourself but hopefully the above helps you.

Hey @ayousry Could you send me the DCS track so I can see what is happening. Thanks.

Hey @ayousry Have you got a track of your mission, that would be very useful to see what you are doing. I am not aware of an issue with the JDAM's at the moment but that's not to say there isn't one. If it is it will be a main DCS issue and not anything in the campaign as we have no control over the fall of weapons. Things to check is make sure you have set up the JDAM precise coordinates correctly and selected the correct entry format. Make sure you have activated the fuse. Also make sure you are well clear of the hill before releasing. Which version are you using normal or EZ refuel. Are you running any mods? I will check it out this end but your track will be invaluable

@Stadius Glad you got it sorted. Remember, practice makes perfect. You will get it. My Campaigns. When played in correct order will slowly make you become familiar with all aspects of F/A-18C Hornet. 1 Serpent’s Head 2 Serpent’s Head 2 3 Rise of the Persian Lion 4 Rise of the Persian Lion 2 5 Operation Green Line You can find some help videos and fly throughs of all my campaigns on my Youtube channel. I have also 22 free simple weapon practice missions for you to hone your skills available here. https://www.digitalcombatsimulator.com/en/files/3342585/?fbclid=IwQ0xDSwKg8ZBleHRuA2FlbQIxMQABHpq6HYwxFYftY2YitpyfoF6HlhZaE-o5NRdcrFjZF4ZTuDcvQLFdoe21DXhx_aem_Cor1yjRqXrPVWo8eHRn2_Q

Hey @Stadius Just flew the mission, “Going for the chop”. All went ok, no problem with the F10. Remember, after you hit the vehicle firing on the downed crew you do get a message to call in lifter, but only when its safe. You need to take out the three vehicles coming up the hill before you will be able to access the F10 via the radio menu to call in Lifter. Tip: use your surface radar in GMT mode to target the moving vehicles. After one is hit they may stop. If so you will have to target using the Maverick display. Hope this helps.

Hey @Stadius It’s not a bug as far as I am aware. Firstly you do need to access the radio menu first to get access to the F10 option. Just to check, are you aware you need to use a different keyboard selection for the radio menu when you are in the air, and they are different depending on whether you are using radio 1 or 2. You are using radio 1. See extract from another post below. If this is not the issue could you send me your track of the mission so I can see what has happened? ——————————————————— As most Campaigns Easy Radio Comms is off. Therefore to communicate you must use the following bindings to call up the radio menu. 1 On the ground use \ 2 Using Radio 1 (Pri) use the COMM1 (call radio menu) LCtr+/ 3 Using Radio 2 (Aux) use COMM2 (call radio menu) RCtr+\ ———————————————————

F/A-18C Serpent’s Head 2 by Badger633 · Mission 8 all versions: Blue marker smoke reintroduced.

F/A-18C Rise of the Persian Lion 2 by Badger633 · All Missions: Data Transfer Cartridge note typo fixed.

F/A-18C Rise of the Persian Lion by Badger633 · Mission 13 EZ refuel version: Tanker name typo fixed. · Mission 8 all versions: ABE Tacan name fixed.

F/A-18C Operation Green Line by Badger633 · All Missions: Data Transfer Cartridge note typo fixed.

@Pavletto No problem. Glad you got it sorted. Enjoy the campaign.

Hey @Pavletto Just tried to run your track file and just getting error each time. This on latest update. My other tracks running ok?

Hi @Pavletto Thanks for the track, yes they do get quite big, I am away from my rig until Saturday so will not be able to download it until then. I will then take a look and get back to you. As i said before on the easy refuel version you will never run out of fuel. This is the only way you can create a mission where you do not actually have to connect to the basket, which some pilots are yet to master. In the normal version of the campaign you will definitely run out of fuel if you do not connect and stay connected to the basket. Regarding the landing I will get back to you.

Hi @Pavletto Not sure what you are doing. Are you actually making contact with the basket? If so you shouldn’t be flying the EZ refuel version. If your not yet able to refuel on the basket then the EZ refuel is the correct version. Your fuel level will not increase if you fly within 0.5 of the tanker, so not sure what you are seeing. Your aircraft is set to never run out of fuel so will reduce to a point and then stay at that level it will not increase. To trigger the next stage of the mission you will have to fly very close to the tanker in a position as if you were connecting to the basket. Hope this helps. By all means send me your track so I can see what you are doing.

Hey @Pavletto I have checked the mission out. The blue marker smoke was missing and I have reintroduced and hopefully should be in the next update Checked the height of the Tanker and it was at Angels 25 until it reaches the coast. It will then head for home and may well fly lower. As explained above you will not run out of fuel in the easy refuel version, but you must get in the right position behind the tanker for the mission to move on. When your ready to carry out a refuel fully you should use the normal version of the campaign. ( In that you will run out of fuel if you do not tank). Hope this helps. If you have any other issues a track will be very useful.

Hey @Pavletto I will take a look why you are not seeing the blue smoke. Also I will look to put it on repeat so it stays longer. Regarding the refuel in EZ mode. Your fuel will not run out neither will it show full. This is the only way you can make a mission version where the pilot does not have to link with the basket like in the normal version of the campaign. In the easy refuel version you make the initial call to the Tanker then all you need to do is get in formation with the tanker as if you were going to catch the basket and you will get a refuel complete message and the mission will progress. No need to make a ready contact call to the tanker on the radio, this all as indicated in the brief. I will check the height of the Tanker and adjust if not at angels 25. If you have a track please send it through. Thanks, will let you know what I find.

Hey @cm2 Yeah, the intention was the wing would delay his formation call until after the angels 15 call exactly to avoid that situation. Fixed now so wing will still delay his call but wait sufficiently not to step on the angels 15 call. Also think I have fixed the audio conflict relating to whether the lead kills the Mig before the wing hits the sub and visa versa. Fix should be in next update Thanks for the heads up.

Hi @cm2 Will take a look. It is one of those difficult ones, always a problem when you have one audio triggered by killing your two migs ( a variable time) and another audio triggered by Matrix taking out his two migs. ( another variable time) when they occur very close you can get this conflict. Play it again and you might not get it. I will look if I can resolve it though. Thanks.

Hey @cobragva Which level did you select the default or Ace? Have you got a track or Tacview file you could send me of the mission showing the problem. I can see exactly what is happening then. Are you running any mods? The wing should definitely not crash, this could be a DCS bug. What should happen is the wing makes the first attack. You then get two attempts to take out soldiers on the Dam. If you get just one hit it will take out all of them. Are you running the latest update. How many times have you tried it. I will check it out this end also but those files would be very helpful. Thanks This is how it should go

Hey @DN308 Your experiences are Impressive and interesting. Are there any books or info you are aware of regarding Hornets coming from the sea down to the Green zone in the Sangay Valley?

Hey @Hillman Yes the S-3 is a challenge, if you can manage that the bigger tankers will be a breeze. You were right there is a typo in the Tacan set up for the ABE. Fixed now will be in next update. Thanks for the heads up.