doodenkoff

The weight of a single OFAB 100 is 123kg. If I select the preconfigured OFAB 100 Jupiter x8 loadout, my weapons weight clocks in at 1434kg. I thought that was odd given the weight of the bomb itself. If I select 4 individual bombs and put them on the pylons, I get a weapons weight of 550kg. The math doesn't add up. Somewhere there's a little over 300 extra kg in the configuration.

When moving closer to a mirror, your face fills more of the mirror and appears to be closer to the mirror. In the L-39, the 'reflected' image appears to recede away from the viewer. What's occurring, I think, is that the scale of the image in the mirror does not change. And the color of the overalls doesn't match the cockpit pilot figure. One is wearing olive and the other blue.

So I was using a C-101CC in the mission and that is what was triggering the RWR alerts. I still can't find any indication that the CC variant was equipped with radar. I flew this mission several times and got only RWR alerts from the C-101. At the time I thought nothing of it, not owning the module and not familiar with the airframe. THe tone was handy too, I could tell when the AI was making its base turn. I made a slight change to the mission; changing the rocket loadout to a low-drag bomb setup. That was it. Immediately afterward, I start getting the RWR lock alert from the C-101. Why would a blue AI lock my Viggen while on the ground? The tone persists after I power down the aircraft and kill all electrical. I switched the AI to the EB variant and have no issues. I'll switch back to the CC variant tonight and explore a little more.

I don't think that's a good example QuiGon. You didn't fly what is considered a normal attack pattern on the run. How the rockets hit in your example is not a good test of how they will hit when preceded by a high speed, low altitude approach, then a pop-up, roll, and dive onto the target. Also, make your starting spot near sea level, have a couple of waypoints to the target, and set a target point in the hills where the QFE value is 50 - 60 points different. For instance, start at a QFE of 940 or so and make an attack at 880.

I tried changing the RWR output setting. I cycled the selector between all three positions with no change; the tone persisted. Later today I'll get another capture. The tone starts the instant the CK37 becomes active. I mean literally, the instant. I'll test again without the C-101 in the mission. Again, I didn't know the C-101 even had airborne radar. I'm pretty sure it's only the "DD" variant that had a radar. I have the base trainer in this mission, but I'm getting an RWR event from it.

The initial RWR tone is from an L-101 approaching from the East. I did not know that aircraft had a radar system. And try to ignore the point where I discover the throttle forward. I was flying a Huey before recording this. This is my typical startup procedure for the Viggen. I'm not doing anything different than I normally do. The oddest thing is that it persists with the systems shut down.

I'm not sure if this is a bug or not. In a mission I've been flying with no issues, recently, just as the CK37 comes on line, I start getting a regular intermittent high-pitched tone. Nothing on the RWR. On the CK37 output panel is a series of 3 1's, and the rest zeroes. The tone persists after I shut down the plane and power. Nothing is unusual on the Master Caution panel. I did make a recent change to the mission by changing the weapon loadout from rockets to bombs. I've been digging around the web for an hour now trying to get a hint what might be going on. Any clues someone can toss my way?

Nope. No single shots, no pairs, no triplets. You dump all of 'em on a target and shag ass out of sight.

If you trigger a message to the enemy coalition, who is going to read it? Create a small trigger zone at the waypoint Type: 1 ONCE No Events Condition: Unit inside zone (unit and zone name) Action: Message to coalition

Good idea. You can hide/unhide zones with a single click, but not statics or planes, etc.

Not necessarily. As long as the client has the module, the mission on any server can include any airframe.

4 racks of rockets well delivered on a target is very satisfying.

Sure, stick a small trigger zone at midfield or so. Then: ONCE GROUP IN ZONE (Or, UNIT IN ZONE, according to feefifofum's post) MESSAGE TO GROUP

I think there's a place for a three ship Viggen strike on an important strategic target that softens it up for an assault by Ka-50s and Hueys carrying infantry.

You really don't need the LDT setup if you just want to use the framework and have fun. Download the base MOOSE lua (there's one that someone pared down to minimum size for faster loading), download the script examples and download Notepad++ to edit .lua files, enjoy yourself. Sven and his compatriots have a hell of a tool there but Sven's "setup" is geared more towards experienced developers.

Look for the referenced registry key(s): Make the "Path" string value whatever the path to your DCS installation is now.

We're watching you.

Yes. Runs like a champ.

How comfortable are you with creating registry keys? They are all straightforward string values.

Will there be a workaround to this if I have my installs in "non-expected" directories?

Try this: On a condition of the first group being dead, the second group will activate. On a condition of the first AND second groups being dead, the third group will activate.

I thought I'd run that through a quick mission to see if anything obvious stood out. Funny thing, I can't output any message with that script. And I see it is literally the exact syntax demonstrated at the Hoggit wiki. MIST loads fine; I can see that in the logs. But I cannot get a message to ouput. I've tried various conditions, "time more", UNIT IS ALIVE, etc....but nothing outputs a message. I have the units named properly. A workaround would be to make the planes single-unit groups, with group and unit names the same, then use the native "MESSAGE TO GROUP" to output the message. If you have a single group with two individually named aircraft, try changing it to two groups with single aircraft. A "Pilot01" group and a "Pilot02" group. I have a suspicion, MIST is treating groups as units (?).

Also, click at the top of the "ping" column and rank the servers by connection. The lower the ping, the better the performance, generally.

The infantry units in DCS can barely even be considered AI. More like random pixels bouncing around. What I meant to say was, this is one of the most entertaining and useful mission tools I've had the pleasure to mess around with. Many thanks to those responsible.

That is odd. I have to raise my seat during landings.