PE_Tigar

Mine works, just need to hold the button, not push/release...

'Tis a mixed bag, this poll. You have Eurofighter, Harrier, Mirage F-1 and Viggen in development by third parties. Rafale, Gripen C/D, Tornado - still operational, a lot of systems are classified. Although Eurofighter is as well, and yet it's being developed. I'd pass on AlphaJet, we have more than enough trainers. M4000 - never operational. Therefore my preferences (from the list) are: F-104 (preferably G) Mirage IIIC J-35 Draken (F or J if possible) English Electric Lightning Not on the list: F-4E or F-4J (or both :))

I don't know if this is a general DCSW issue, or it's related to every a/c model specifically, but here it is: - if you don't own a MiG-21bis module, you cannot set the radio frequency presets for MiG-21bis in the mission editor. It's quite a PITA for mission builders, and is most annoying for MiG's, as it has only one radio, and can't tune frequencies in the air. Is there any way that this can be changed?

Yup, the same. There are problems with other missions, though. The key problem is with the AI burning through their fuel like crazy and generally being suicidal, but that's a DCSW problem I guess...

1-2 positions are the inner pylons, 3-4 outer ones - the weapon station numbering logic is different from common sense. Anyway, yes, the tactic was used in real life, IR+Radar shot, what you'd need to do would be: Lock up the target (rear aspect) Wait for the IR tone Fire IR missile Switch missile mode to Radar (RNS) mode Switch Weapon selector to appropriate position Fire radar missile Finally, firing two of the same kind simultaneously does nothing. If you fire one at the longest possible range, and then one at half range, that's a different story.

+1, really needed

Try this to install the module via command line shortcut. Using DCS_Updater to Install a Specific Module: In the Command Prompt Windows: Type: DCS_Updater.exe install <module> (ie DCS_Updater.exe install MIG-21BIS) More details in this thread: http://forums.eagle.ru/showthread.php?t=114030 It will cost you an additional activation, but you can always get the extra keys from LN, if you happen to run out of them.

I watched the first one - you've stalled the plane in ~85 degrees climb on full AB. By doing that you've disrupted airflow to the engine and experienced compressor stall. Some airplanes can do that and sustain airflow to the engine, MiG-21 can't.

A small correction here - that is not the afterburner switch, it is the "extraordinary afterburner" (literal translation) switch. You activate the normal AB by pushing the throttle forward. You can fly on normal AB and drain your tanks quite quickly. "Extra AB" is there for extraordinary circumstances, like trying to get away in a hurry... or something. It's switch-activated because it's time-limited.

I can corroborate this, we're having this issue pretty much every time we first start a multiplayer mission. A workaround seems to be to unpause the mission before anyone enters a slot and spawns in an airplane.

Thanks HiJack - will try that.

Thanks for the suggestion - so every airframe is its own group then?

Issue: When selecting a unit on MP unit selection screen units within the list are stacked randomly (see attached image). Although it may seem trivial, it caused us a lot of trouble when flying a mission yesterday - we've created a flight of four M2000Cs, and changed default radio frequencies only for the first two units (Colt 1-1 and Colt 1-2 in the mission editor). But once the first two units in the selection screen were chosen, the preset radio freqencies were different for the two planes... The most logical solution would be to have the selection screen rank the units within the flight according to their place in the flight, as in the mission editor. Could we have that please?

Just last week I was doing some approaches and intercepts with MiG, with a friend (former MiG-21MF pilot) sitting next to me instructing me on proper use of some systems. To be able to do that, in a desktop sim, is simply awesome. One thing my friend mentioned the sim lacks is artificial control resistance (maybe could be done through FFB?). In his words, it was very poorly implemented in the real plane, and could kill you if not tuned properly (introducing PIOs, over-Gs, etc.).

I thought this as well. There's one mission - Long day, single mission for Su-25T - that crashes the game in 30 seconds or so. That mission has an intro where there is artilery exchange etc. happening at the very beginning. Other missions crash later, but invariably there's a lot of activity on the ground. So it might be that it's an object doing something specific that triggers the crash.

Tried - that's not the issue. BTW with Flat Terrain Shadows OFF you're getting the new shadows, with Flat Terrain Shadows ON you get the old ones, so ON should be the safer setting... I suspect it is the issue with AAA or vehicles firing, should be clear from the logs anyway.

I found a mission that invariable crashes for me within 30 seconds (and I don't have to do anything) - "Long Day" from Su-25T single missions. Tried turning off shadows and whatnot, always the same result. The logs are attached. Logs.zip

Same in SP 1. Command Post Strike single mission. 2. Got hit by Igla, damage to port engine and flap 3. RTB, landed, taxied to the ramp 4. Engines off, repair 5. After repair airplane turned 90 degrees clockwise, floating in the air, flaps down, stuck. Airbrakes off, stuck as well.

Tried Sporg's solution and it seems that it works okay now.

Well - for AAMs I'll try it out in MP tonight with some friends. As for MANPADS - it could be that I was expecting too much. I haven't flown the Rook for a long time, so as of lately I've been breaking off my attacks way too late giving the Strelas and Iglas an opportunity to send multiple missiles my way...

Happens to me intermittently - I hit Esc>Quit, the menu music starts, but escape menu etc. stays. Have to kill it through Task Manager, no crash log is generated.

Strange - IR jammer acts normally/makes almost no difference against MANPADS.

1) this is very probably a feature - pitots on Su-25 are not constructed or calibrated to measure speeds below 80km/h. 2) this is annoying, I agree. In night training missions it's double annoying, because the contrast of white text vs. dark night kills your "night vision" 3) that is may be a feature too - the warning light and klaxon turn on due to "high AoA" indication (red light on the left upper side of the dashboard) - while stationary or moving slowly, wind can fiddle with the AoA probe and cause this. Not sure, however, because it stops later when you stop on the runway, for example. I have a few of my own observations as well: a) In training missions a "missile lock" tone will play with no way to turn it off from the instant you clear the briefing screen to the end. You can work around by re-starting the mission. b) In the Landing-Easy mission the instructions for ILS start when reaching the 10km finals on the opposite end of the runway (that has no ILS). c) in the "Internal cannon" mission (which is happening at night) no flares are dropped over the target, so you have to find unlit targets in pitch black night :). d) interface music continues playing throughout the whole mission. This may be by design, but it's a bit superfluous I think. e) numerous small discrepancies in systems descriptions and procedures - probably due to the aircraft modelling improvements and instructions text remaining the same.

Yep, so that makes three of us - the logs look very much the same.

I have seemingly random crashes in Su-25 campaign. I have tried running as administrator, repairing the installation, setting GPU fan manually to 100%... nothing worked. Logs and system.nfo attached. Logs.zip