Zeus67

I don't understand the question. You can do the following loads: Magic - Magic - Magic - Magic. Magic - Rockets - Rockets - Magic. Rockets - Magic - Magic - Rockets (not recommended). Rockets - Rockets - Rockets - Rockets.

Force Alignment overrides the aircraft's "INS always aligned" option, so you need to do a full alignment (4 to 8 minutes) on mission start.

I don't know what I can do. All I do is ask DCS for the wind status and it replies giving me wind speed and direction, which is what the PCN displays. Unfortunately it seems that the ME and DCS speak different languages that are closely related, like Spanish and Portuguese. They can understand each other but sometimes they are confusing as hell. I'll have to ask ED to translate between DCS and ME.

I think there is room to wiggle for discriminating between these aircrafts because although the electronic components are the same there is enough difference for the RWR to differentiate between them.

In this case the blame is 50/50 :music_whistling:. The RWR does return SU-33 but I can override that without problem except that I am not that knowledgeable in radar equiped aircraft. :smartass:

The RWR in DCS gives four signal types: UNKNOWN, SEARCH, LOCK, LAUNCH. It will return only ONE of those types for a given emitter. So if an F-15 fires an AIM-120 while on TWS, then the RWR returns LAUNCH for the F-15 regardless of its actual operational status. As I said, I could try to look for LOCK + LAUNCH but then I run the risk of breaking the RWR. So the pay does not justify the risk.

I'll see what can be done but I am reluctant to fix something while damaging another thing. As I said, all I do is ask the RWR if the enemy aircraft has launched. If it says it has then I turn on the warning and the circle flashes. So that is on ED side of the code.

A couple of observations: - Any flightplan created in the ME will have its altitudes changed to the terrain altitude where the waypoint is located at load time. In other words, if you entered 12,000ft for waypoint 03 in the ME and the terrain altitude at that spot is 450ft the PCN will store the 450ft and that is the altitude you will see. You always enter the terrain altitude for the waypoint location. - Please check that PREP shows the waypoint number you want to check. PREP 00 shows current position data, including altitude. It had a bug that it was reporting current altitude as 0ft/0m but that was fixed a few updates ago.

In due time yes. Right now we have other priorities.

Like I said, the problem was that since the round is reaching the target at max air-to-air engagement range nobody saw it. But since air-to-ground engagement use higher max ranges, 1800 vs 1100, the friction coefficient problem came to light.

I'll check. Thanks for the heads up.

My guess is that the round friction coefficient is off, which will cause the round to lose velocity too fast. Fixing that will require a lot of testing and we don't have the time at this moment to do that. We will fix it, but not right now.

The hard code was required in order to be able to load 4 magics and 4 rocket pods. Weapons firing management won't work in any other way.

It seems that the bullets ballistics need work. The piper position is calculated based on defined muzzle velocity, but the ballistic characteristics of a round have several other criteria to create a path. I've noticed that for the time being the best range to fire is at 1200 meters, which coincidentally it also max range for AA guns. Probably why nobody noticed that the ballistics are a little off.

Ecuador is currently flying S.A: Cheetahs.

We will consider the request when the aircraft is being finalized.

I do not control when or how the RWR reports a missile launch. All I do is ask if a missile has been launched. So if the RWR is "cheating" by telling me that a missile was launched when it shouldn't then that is on ED's side of the code.

No. I'm sorry. The PCA now has all allowed weapons hard coded. If you enter one that is not in the list then it will not be recognized and marked as a non-usable store.

You should see the missile because it has its own radar. You also get the F15 icon flashing because its radar has gone into STT/Launch lock. The problem is that the screen is too small and can get too cluttered, specially in the inner zone where all critical emitters are shown.

I'll check the option functionality.

1. Countermeasures programming is in the schedule. 2. VEILLE does not turn the jammer OFF in RL, it places it in Standby mode. Remember that in real life the jammer can jam its own radar, something that will not be simulated. Since I am speaking from memory and not from my notes, I could be wrong. But I do know this: the jammer has a radar priority mode. That mode stops the jammer from transmitting but does not turn it off. There are two control switches for this function: One in the ECM control panel and another in the HOTAS. The Three Position Switch in the Control panel probably works like this: JAM, HOTAS CONTROLLED, RADAR. The HOTAS rocker switch is probably locked on JAM, but you can click it to clear your radar and use it for a while. Or probably it works the other way. There is no public information on this device and we are working only from reading the switches labels in order to determine the best logical functionality.

The manual has not been updated in ages. I'll have to do that soon.

The only weapons remaining are the BLG-66 Belougas and the BAP-100.

I'll check.

Not yet.