Bullitthead

I found the in game training mission for CCIP high drag bombing to be helpful (after they fixed the QFE error in the mission text anyway).

I just bought the Mig and am also having difficulties with the landings, glad it's not just me!

Good find, I meant to tell you that the flight of chinooks coming in did look pretty nice! Didn't realize that there was a FARP though.

I think that you are right Paul. It looks like an issue with Maykop airport. I just flew your mission and am having the same issue that you describe. I tried take off from both directions of the runway and I also deleted your Viggen group and created a new one with the same results. I found that if I move the take off location to Sochi everything works correctly. I also noticed that on the kneeboard, page 11, the description for the take off and landing waypoints is ?? instead of the airport name.

Make sure you are not turning on master mode NAV too soon. It should only be turned on when you are on the runway or very close to take off. I think 2 minutes is the maximum allowed time limit for NAV to be selected before take off. Also I've noticed that you don't really need to use the reference button on take off anymore, I think that was fixed. You can see the compass align itself during the take off roll around 150km/h or so if you don't use the reference button. I usually still use it just out of habit though.

Use the BK90 with the MJ1+MJ2 mix, they seem to do better damage.

I thought that was fixed. Are you running the latest version?

You can already fire 1 rocket from all pods at a time. Flip the 2 switches behind the weapon selector knob and bomb spacing knob to the down position. One trigger pull should launch 4 rockets if you have 4 pods equipped. I've read that it works for bombs too but haven't had a chance to try it yet. Edit: Mattebubben is right, I think it's just the rear switch that actually needs to be down to enable this launch mode.

Wow, what a great list of fixes!

I actually had this happen to me once last night. It happened on a cold start for me though. The only thing I can add is that when I pressed T1 I got the radar cross and I could slew it but the destination indicator did not change from M3 to the flashing E3 that you usually get after pressing T1. I had set waypoint 3 as the target waypoint. It seemed like the T1 input was being received by the radar system but not the CK37 maybe? I'm gonna do some more testing to see if I can duplicate it again. This was a mission that I made for myself and had played many times with no failures of this type.

So cool, looking forward to messing with this!

The trigger has 2 stages. Pulling half way is the first stage=first detent. Pulling all of the way is the second stage. The detent stops the trigger from moving when it reaches the first stage. To pull it all of the way to the second stage you must pull it harder to make it move past the detent.

I have this problem even using the regular ARAK attack mode: mode switch to ANF, weapons mode switch to ATTACK. I've found that sometimes if I fire as soon as the firing que starts to flash but before I get the wings, they will be more accurate. Usually I end up aiming a bit in front of the target and firing as soon as the firing que flashes and fire 2 volleys, this seems to work usually. I wish I could just set the dot on the target and fire when I get the wings. I always disable sight motion compensation too: TAKT 221

Don't need both versions though. You can convert stable version to open beta simply by downloading the patch. And you can switch open beta to stable simple by downloading the stable patch. I would guess next week 1.5.6 will go to stable and people will have to download the patch then anyway, may was well do it now. That post by Rlaxoxo shows how to do it, very easy.

Here's another: TAKT BK90 91xxxx weapon approach altitude, 30 to 500 meters. Correct format for altitude input examples: 915000 for a 500 meter flight and 910300 for 30 meter flight. I wasn't sure of the format so I just tested it. I thought maybe the BK90 would have more spread and possibly further stand off range with the higher altitude settings but the bombs dive to their normal delivery altitude just before they reach the target and I still can't get over 6km of stand off range with them.

T0, T1 and TV are not inputs that you would want to cycle through with one button. If the sim allowed you to bind 1 button to cycle through all three inputs, you would have huge navigation problems as everytime you hit TV, when not in RB75 mode, your current waypoint fix would be updated. In the real aircraft releasing the radar stick trigger is T0, pulling the trigger back to the first detent= T1 and pulling the trigger all of the way=TV. So to slew the RB75 you pull the trigger to T1 then move the radar stick to control the slew, once over the target you would pull the trigger all of the way to lock the target, then you'd fire the missile with your flight control stick input. Or if you don't want to lock a target but instead you want to stop slewing and bore sight the missile you would release the trigger=T0. In the sim you need to assign 3 keys or 3 joystick buttons for RB75 control. Assign a button to T0, a button to T1 and a button to TV. These inputs are also used for setting navigation fixes and controlling the cross indicator on the radar screen.

I shot an RB75 at a sam site and it ended up tracking and killing a missile that was shot from the site after I had fired.

I have an X55 as well. For T0 I use the throttle button on left middle finger, for T1 I use left pinky up and for TV I use left pinky down.

Heh, practicing maverick locks on a school bus.........awesome!

I've been messing around with the RB75 as well and honestly it is so much fun the way that it is that I don't want it to change LOL. However, I agree that it's probably not accurate and accuracy needs to come before fun I suppose :) I set up a SEAD type mission vs. SA6 and was able to lock and launch around 17km. Honestly I could get lock before seeing anything through the maverick sight. I knew exactly where the sam site was which is the only reason I could find him to acquire a lock. Here is a link to the videos I made of this mission, part 2 includes the RB 75 launch. https://www.youtube.com/watch?v=KQitkiFofyM (for reference M1 is the sam location, you can use the waypoint distance as accurate distance to the sam.) I think that if RB 75 lock occurs at about the same time that the target is visible through the sight it would feel pretty good, as this distance is MUCH closer than the distances I was firing at. I have NO idea what is realistic though. I'm curious about the speed of the RB75 also, seems slow. I know the Viggen is much faster than the A10, but should it be able to out run a Maverick as easily as it does https://www.youtube.com/watch?v=hiF_Wr6z8T0? Also wanted to point out that the RWR doesn't always beep the way that it is supposed to, the SA6 video shows evidence of that as well. No sound from the RWR throughout most of the video, until the end and I made no changes to the RWR settings.

What exactly is the problem with the EP-13 in VR? I've been messing with it and it is usable, just wondering what is broken and how it may change when fixed.

I have to agree with Krupi here. I never really played DCS WWII much before the Spit was released. I flew a few online missions with the P51 and realized that I was outmatched so badly by the Germans that I gave up. Maybe I could have done better with the Mustang had I flown it differently, not sure. When the Spit was released I started playin online with it and I bet my kill death ratio against German planes is around 4:1! And I'm still new to DCS WWII!! Mjmorrow is correct, the German planes can determine the terms of the fight. They can choose when to engage and when to disengage but in my experience this does not determine their ability to kill the Spit, sure they can run but that is not equal to a kill....

Yup, the Spitfire is much better vs. the 109 in the current online environment than the p51 is. About the only thing the Spitfire can't do vs. the 109 is catch it when it decides to run. I'm not sure about the Spitfire being changed in a previous patch. Haven't been online in a few days but hadn't noticed any changes prior to that.

I made probably close to 50 landings before I finally got the hang of it. What helped me was using a standard traffic pattern landing instead of a long straight in approach. It helped me get centered on the runway as I could see the runway easier during turn in to the short final approach. Secondly I found that pulling the stick back fully shortly after touchdown seems to help the plane track straighter down the runway during roll out. Not sure why it helps, more downforce on the tail wheel maybe? Good luck and keep up the practice, it's much easier and actually FUN once ya figure it out! Here is a short video of a couple of my first successful landings recorded in VR. The resolution is stretched which is actually good in this instance because you can see the rudder pedals. https://www.youtube.com/watch?v=k2-snBo2sjY&list=PLBj4x7gLy4z6kds2WVn7TCy4OBzmCoUGj&index=2

Great, now I gotta relearn my takeoff procedure. Thank you for the information! :pilotfly: