Ultra

I posted this in the other 'next Razbam aircraft' thread. I'll put it here as well.

This is normal for a lot of people when using the 1.5 beta and 2.0 alpha. There is a memory leak in these versions at the moment. It's better than it was initially, but it's still there and being worked on by the devs.

I think a Mig-23 or Mig-25 would go well with our US legacy fighters. The PFM/ASM NATO planes we are getting (M2K, F-18, F-14) greatly outclass our only Soviet PFM/ASM plane, the Mig-21.

The X55 is worth it, due to the slightly better precision and mostly due to the toggle switches.

RWR is automatically on, the control C.D. Baird mentioned is probably for changing the RWR to 'priority threats only' mode essentially. It's difficult to deal with the IR SAMs in general. Staying as high up as you reasonably can find your targets helps. Also, yes it is common practice to dispense flares during attack runs as a precaution, as long as you can spare them. As mentioned, don't forget to turn on your IR 'jammer'. It's pretty much just a large infrared lamp in the back of the plane, but it's saved my a** many times.

He said it was reported as a bug, but I thought that later it was determined that this is actually the correct behavior. I'm not sure anymore.

I don't think there's a time frame, but they said they're working hard on it. I think it's very high priority as one would expect.

The rockets and bombs bother me as well. It seems usually only direct hits have a significant effect on any thing that isnt really soft. They need some remodeling to compensate for the lack of shrapnel implementation. Sorry for OT

Beta to be released next week, if anyone hasn't seen the DCS newsletter.

The module has been pseudo-confirmed by Steam's database. So it's being considered a sure thing. Also, the devs have contributed to this thread so....

This may be because it sounds like you guys are flying pretty close to each other. It's actually sort of difficult to search for targets that are very close because the radar cone is smaller at close ranges, the target is moving faster in relation to your radar cone, and the elevation differences (for the radar, not physically) are larger. At closer ranges I usually switch to EOS. In VS you can hold down the lock button to auto lock anything that comes into the radar cone. In the Eagle, VS will do it automatically (no need to hold the lock button). I never use Bore mode since VS is a larger search area, Helmet mode is also very helpful. I'm pretty sure it just controls the zoom of the HDD. I think the radar is at a constant power. Not 100% sure though. EDIT: About the HOTAS, I have an X55. I put my HDD range on a rotary, my radar elevation on a rotary, and my target cursor on a HAT.

Sure, so you probably know EOS is an infrared tracking system and is used to fire your heaters, the R27ET and R73. It has less range than your radar but it's still pretty good, like sometimes 50km, even more if the target has a larger heat signature. I find it sort of temperamental though. If you have the target radar hard locked (STT) and if the EOS is in range, you can simply turn it on to acquire your target in EOS additionally. I've found that since I am usually using EOS at closer ranges it requires greater elevation changes. It seems I generally don't have to go more than -5 or +5. Also many times if I am well within range for EOS, I will actually see the target immediately in EOS as I 'scroll' over it's elevation and it's marker will travel down the HUD. I think this is because the EOS acts more like a camera and 'sees' the target almost immediately. This may be confusing but you'll see what I mean when you're using it. Here's the two really important points about EOS: -There is NO IFF. You are only seeing a target's heat signature. There is no Radar IFF 'pinging' it. -Because there is no Radar 'pinging', EOS is 'silent'. The enemy will not ever know when they are being seen or locked by EOS alone. If you lock them with both Radar and EOS, they will get the radar lock tone. This is why it is important to turn off your radar if your are trying to silently hunt someone. Practicing is key. It starts to all come together in your mind when you actually use the systems. Once you understand it, it starts to become more natural to decide how to use the systems in combat.

Hey mangaroca, I don't have a ton of time in the 27, but I think I've got some of the basics down. I find target aquisition in the 27 more difficult than in the F-15, but the Russian RWR giving reference altitude for spikes helps. At far ranges when you moves the radar vertical position it is moving much more than at close range so generally I find things by staying within the '0' elevation, sometimes the -1 or +1 if they are really low or high. Once I get closer it is more normal to set it to -1 or +1 to track if they are below or above. I've found I usually don't need to move the radar much past these limits since once I get that close, I've usually hard locked and am preparing for a launch. Once you've STT locked, the radar will auto follow your target and all you need to do is keep it in the max radar limits. About radar modes, you probably know there are the 3 modes: head-on, chase, and interleaved. Using head-on or chase against an appropriate target will give you a farther detection distance than interleaved, but you have large detection penalties for using them at the wrong times, e.g. using head-on against a target flying away. So usually I just stick with interleaved to keep things simple. The detection range is acceptable against all targets. Note that if you switch to TWS mode, TWS is always in head-on mode. I don't use TWS a lot since it is blocked by any jamming, but sometimes it is helpful. My general detection practice involves scanning the 0, -1, and +1 elevations slowly with priority on the 0 elevation. Make sure to use the info from your RWR spikes to help in detection. Also, note that just because your radar is set to 0 elevation, does not mean you are currently scanning that whole section. Sometimes you need to move the radar just slightly above or below within the 0 elevation to pick up contacts that are just ever so slightly above or below. Hope this helps! (PS: EOS is another story. I can give you some tips for that as well, if you'd like)

I feel your pain, I can't get my TacView to work with 1.5 or 2.0 either. :( As far as I know, the new netcode and dedicated server are WIP and not really implemented yet.

You should post tracks or videos!

Thanks, tomorrow I'll check to see if it's only a MP problem or SP as well.

I understand, but here's my scenario: Starting/home airfield is Sochi. I take off, follow the waypoints, do whatever, then I land at Gudauta, which is not part of the flight plan. I shut down and re-arm and such, then take off again. At this point, after I'm airborne again, I cannot enter Enroute mode at all, only Return and Landing modes.

Isn't this just the testing phase?

I dont remember. I'll check sometime. It may just be on MP. Mine doesn't reset after cycling.

Is there any other way? If I've landed at an alternate airfield to re-arm, I would lose my position. Thanks for the help.

More often then not, when I land and then take off again I can't get the FC3 planes to navigate the waypoints again. After taking off, it will only let me cycle between Return and Landing navigation modes. Does anyone else experience this, and is there a simple solution?

You have downloaded the module through the 2.0 module manager? What is shown once you did that?

Brutal! :D

I'm in favor of a button as well.

Gimme gimme :D