drPhibes

...and here's why:

The description.lua for the new Yugo skin ("Yugoslav Fictional") refers to the wrong file names. "SA342_Youg_Camou_SVK_xxx", while the files in the zip lack the "SVK_" part. It's the same way for both the M, L and Mistral in 1.5.4 (I haven't checked 2.0.3, but I assume it's the same there). It's easily corrected by removing the "SVK_" bit from the LUAs.

Placement is more important than quantity. I might (but probably won't) give away a free Gaz serial to the first person that gets an actual Gazelle tattoo on the forehead.

Here are some Viggen related pics from the Swedish military archives: http://www.svd.se/unika-bilder-viggen-piloternas-fotokrig-med-sovjet#

I just updated, and I've got the Mistral, so at least some of the changes are included.

I'm seeing the same thing here. Full loadout (4xHOT, IR and sand filter), 50% fuel. With full forward trim (using the manual trim, not the mag. brake), I can only get 144km/h ground speed in level flight. Any more collective input and it goes skywards.

Slightly OT: Maybe some joker should make a server called "Leatherneck" with a mission called "AJS37-release-just-around-the-corner-test", just to see the Viggen thread in the LNS section explode :)

After cancelling their nuclear weapons program (yes, Sweden did actually have one, although it never resulted in anything going boom), they had to resort to other forms of unconventional warfare. This resulted in the FKA (Försvarsväsendets kemiska anstalt) developing surströmming.

Just crack open a can of surströmming, and it'll be just like flying in Sweden.

Landing on grass works fine here (1.5.4). Something might be a bit dodgy with your installation. Try running a repair of the module with dcs_updater.exe

Cobra only teases in text form. Actually, rumour has it that the whole Viggen wil be implemented in command line format only, to be more in line with what computers were able to do in the period when the AJS37 was developed. Who needs fancy 3d graphics when white text on a black background tells you all you need to know.

If you fully implement the Ferranti af532 sight at some point, the Gazelle can actually lase targets for other units. Or preferably for itself, with the hardpoints loaded up with APKWS-II launchers! If this ever hapens, I'll update the LaserShark skin for you :) [ame=https://www.flightglobal.com/FlightPDFArchive/1981/1981%20-%201291.PDF]https://www.flightglobal.com/FlightPDFArchive/1981/1981%20-%201291.PDF[/ame]

Both are wire guided. I haven't checked the range in the sim, but the lua files say Range_max = 3200 for the Milan and Range_max = 3000 for the Malyutka. I don't know if the "in range square" on the TV monitor sighting system is affected by this.

9M14 Malyutka and MDBA MILAN. The Serbs have some Gazelles with Malyutkas, but I haven't heard of anyone using the MILAN irl. The Malyutka is relatively easy to integrate, being MCLOS, which doesn't require any automatic guidance electronics in the helicopters; just a pair of binoculars and the control joystick (you control it manually all the way to the target). The missiles in the mod are SACLOS just like the HOT, but it's a good idea to adjust the terminal trajectory manually, as they both miss the target if aimed like the HOT (IIRC, the Malyutkas go low, and the MILANs go high).

DCS players are obviously a mixed abilities group. Skatezilla's guide tells you what to do, step by step. If you can't follow that, stick with the official liveries provided with the plane.

There are no PS files for that (yet; although I hope polychop will release them later on). You'll have to get the file you want from \DCS World\CoreMods\aircraft\SA342\Textures\SA342.zip and edit it the hard(-ish) way by converting the part of the image you want to edit to monochrome, play around with the curves to get a decent white background (with enough contrast for rivets and other details to show up), than add a color layer over this and use the multiply blending mode.

So there's no place for the living dead in the ALAT?

Unfortunately, 3rd party developers don't control when the bug fixes are implemented. I'd expect it to be included in 1.5.4 stable.

I've been poking around the default texture zip file, and found the quite interesting file SA342_V2_Sight.dds, which looks a lot like the gyro stabilized binocular sight used in Royal Army Air Corps Gazelles. Are there any plans to implement a simulation of a fully featured Ferranti AF532 sight (which was at least planned to have an optional laser designator module, though I don't know if this was ever used)?

Strange indeed. I watched your 342M track until after startup, then took control, and I couldn't engage auto hover. Then I re-started, took control right away, followed my standard startup routine which consists of the same steps as you took, just in an other order (I usually put the NADIR in warm-up mode, set gyros to GM, switch on trim/pitot heating/mag brake/AP while waiting for the 20 sec. fuel pump priming). After that, auto hover works fine.

Here's an example: I searched for "SA342_V2_Weapons_Optics" (the texture with the optical sight), and found the following in the 3d file: As you can see, the material name is listed a few characters before the texture file name. I then typed the following into my description.lua: {"Mat:SA342_V2_Weapons_Optics", 0, "SA342_V2_Weapons_Optics.dds", false},The flare launchers seem to be part of addons_2, so here the lua entry would be something like this: {"Mat: SA342_ADT_Addons_2", 0, "your_file_name.dds", false},

Part no. 8F-0101651-01 is expired. I wouldn't have expected that in a Swiss AF plane :P Or the picture(s) may have been taken 4+ years ago.

Again with the "feature xxxx in the beta version is wrong" whining. I always find it a little odd that people don't understand what buying a beta version of a product means. If you can't accept bugs here and there, wait until the final version is released. And btw, check the sticky post in the bug reports forum...

I can check exactly what i did in the lua file after work, but until then, try the following: An example {"Mat: SA342_Camou_ADT_11", 0, "SA342_Camou_RAF_11.dds", false}, = {"material name in the 3d file",0,"texture file name", false} (false = use local file) To find the material name in the 3d file, open the sa342l.edm(?) with some kind of decent text editor (I use Programmer's Notepad), and search for the file name of the texture from the ZIP that you have changed. Most likely, you'll find the file name with a "Mat: " (with space after colon), "Mat:" (no space after colon) or "Tex: " prefix. Copy this text string to the first part of the lua. IIRC, the material name of the optical sight was identical to the zip texture file name, with a "Mat:" (no space) prefix.

The first time I ran DCS after the 1.5.4 update, the default mapping of gun/rocket fire was set to the same button as missile launch, which doesn't work. I changed it to the inner detent on the Warthog trigger (with HOT launch on the first detent), and everyting works fine.