Redglyph

At least it's crash to desktop. What I get is a complete freeze and the only remedy is the power switch (with all the disk checks that implies, let alone data loss).

Glad it helped :) I just dusted off the A-10C and was getting crazy because of all those inconsistent switches, I haven't patched it up since 2.0.

Additionally, the ADF doesn't switch off when the ADF function select switch is set back to off (which also answers Tholozor's question - see below for expected behaviour). 23.2.1.1.4 ADF Function Select Switch. The ADF function select switch has positions labeled 1, 2, and OFF. Placing the switch to the 1 position turns on power to the ADF set and indicates ADF bearing to the station selected on the comm 1 receiver-transmitter. Placing the switch to the 2 position turns on power to the ADF set and indicates ADF bearing to the station selected on the comm 2 receiver-transmitter. With the switch set to OFF, power to the ADF is removed. The ADF bearing symbol is a small circle displayed on the HSI display and indicates the ADF bearing to the station selected. Squelch is deselected when the ADF is selected. After the ADF is turned on, the SQUELCH has to be reselected.

Not sure what this last one had to do with the cockpit lights :confused:

I second that, it's really comforting to have such a good feedback! :)

Same behaviour here, but I don't know the systems well enough yet to tell it's a problem or not. All duplicate mappings removed from joystick trim hat. In cruise flight, moving the hat in any direction does not seem to have any effect, the trim is not moving (visually) on the stick in the cockpit. Using the default assigned keyboard keys does not have any visible effect either. That was tested in training missions 2 and 3, today's update (DCS 2.5.2.17978.385)

DCS 2.5.2.17978.385 Great to already have those missions! :) Nicely done, there are just enough explanations to justify the procedure without overloading the user with details. Just a few remarks, some related to the DCS mission environment. 1. Introduction 1) The next active gate gets bigger, then progressively smaller as the user approaches, which is very confusing because all notion of distance is made impossible. Perhaps a simple change of colour would be much more helpful. 2. Cold Start 1) I've noticed that the training missions were not always registering when the user presses a switch (when he's asked to). It's very noticeable with DDI interaction, also with the trimmer reset for example. The user has to press again until it's registered (and usually one has to cycle back to the mode the mission creator intended to get at). 2) Also, the highlighted brackets that point to which control the user should pay attention to is often masking the labels, which makes it awkward. Example with the INS that we have to set to GND, the user has to guess the position because it's not visible anymore. 3) I noticed that a few switches have to be pulled up with the left mouse button instead of the right. For example the FCS BIT, if it was possible to correctly hold it up with the right button, perhaps the left could still be used to click on the DDI at the same time? Not sure though, perhaps the keyboard shortcut is unavoidable. 4) Perhaps I'd leave the subtitle text somewhat longer or even indefinitely until an action, when the user is expected to press SPACEBAR or wait for something which is not immediate. If he didn't catch what to do, he won't have any support to continue. 5) Why 20% RPM before throttle to IDLE? From the flight manual, it's 15%. 3. Taxi and take-off 1) The user is told not to exceed 75% RPM, but at least 90% is necessary for the aircraft to start moving, and to sustain the roll. 2) No ATC clearance request before taxiing / entering the runway? Approach free before crossing the holding point to the manoeuvring area ;) 3) A phrase is cut at the beginning: "In a Hornet, you always take off [in afterburner. ...]" cut by "As you roll down the runway, ...". 4) I'm not entirely sure it's not my fault, but I noticed before taking off that the flaps were on FULL, not HALF, are they preset that way? I can't check it again right now. 5) I'd give the indications of what to expect next, before the take-off roll, because after that things go pretty fast; the 190 kt limit for the tyres, and 250 kt for the landing gear and flaps seem to be important information.

Ah, that's what you meant, I suppose it's better, yes, or it could say "turn right". But I'm confused now, are you the developer of the campaign, or is this mwd2?

You missed a word, see the screenshot again ;) - "TURN LEFT OVER[...]" Then there are all the other issues in mission 1.

OK, thanks!

DCS 2.5.2.17559.377 Two problems: 1) Landing and taxi lights illuminate the cockpit as if those lights were inside. 2) The main white light knob does not rotate, but its light is switched on/off as before (the problem is only with the knob model not moving in the cockpit).

Same here in 2.5.2.17559.377.

Bug still there in 2.5.2.17559.377 (if the campaign's author still cares, seems not to be around anymore)

Good to know... that's obviously a very nasty bug worth reporting in DCS 2.5. You can edit your %PROFILE%\Saved Games\<DCS>\MissionEditor\logbook.lua file to force the mission as a success, but make a backup of that file first, it's easily broken! EDIT: Found back a link to an explanation on how to change the logbook. Don't do it if you don't feel comfortable with it.

Wow, that's great! So many training missions for this awesome aircraft, plenty of joy! :) I really don't know where you find the time to make all that ;)

Surely not an easy debate, but we have seen this one under other appearances. The bottom line is, can you lower the quality to make it more affordable to anyone? And it's really what this is, do we have to fabricate unlikely scenarios and always stick to Caucasus just because a part of the users don't want to/can't buy a terrain which is more suited to a campaign/aircraft combination? Of course it's understandable that some don't want to buy several terrains given the price, but that is a choice. If the only free terrain is Caucasus, and someone buys a WWII aircraft, does it make sense to force the accompanying training campaign (that we would already be lucky to get free) into that region that has very little to do with the aircraft in the first place? It lowers the credibility of the simulation, in spite of all the efforts to produce a high-fidelity aircraft model. So if the aircraft you want doesn't fit the terrain you already have, perhaps you should expect to have to get another one. Or perhaps a good move would be allowing to select the first, free terrain that comes with DCS once a new user buys the first high-end aircraft (in which case the Caucasus would have to be bought back). In any case, and at the risk of being controversial, I'm against the principle of aligning the quality to the lowest affordable criterion, it has never been a successful strategy. Or we may as well have lower-quality and more affordable modules, as in other and cheaper sims, but that wouldn't be DCS anymore.

There are some info in the DCS doc directory, in the DCS user manual. In summary, you open the mission editor from the DCS main menu, you can then open any mission and edit it (except paying DLC content). Alternatively, you can do a one-time modification with the mission planner (button on the briefing page, just before starting the mission), which also opens the mission editor. You have to find your plane, click on it, and you can then modify the radio channels on the right part of the editor, by selecting the radio tab, see the screenshot. If you open the mission, you will be able to save the modified mission file, be aware it will be replaced on the next DCS update though, so save it under another name or elsewhere. If you use the mission planner instead, the modification won't be saved and you'll have to re-do it again. Or you can use that to quickly check the current frequencies, but if you have already tested them all perhaps it's pointless.

Oh yes, found it! Somehow the rudder pedals have non-existing X & Y axes which are mapped by default to pitch and throttle, who knows why. I had tried in the past to define the "default" setup for any new aircraft but could never achieve it, but I admit I had not tried very hard either. And sure enough, all those fake controls reappear every time on the rudder pedals (had that with Saitek, same with Crosswind). Now the synchronization works perfectly. Thanks again for the tip, that made my day!

That's weird. I'll check my settings or try with new ones, thanks a lot for the info! :)

The "Synchronize controls with HOTAS" is enabled, it doesn't seem to work. Last time I asked, in August 2005, I was told it was meant for the A-10C only and as far as I know, it's simply not implemented at all. I've tried again with 2.5.1.16978.363 - last 2.5.1 before today's update, same problem as above. 1) For example the Bf-109 campaign mission "difficult landing", - first time it's more or less fine, perhaps luck, - second time the engine quits because of the surge, even moving the throttle quickly after unpausing wasn't fast enough. Perhaps the "play again" does not reset everything. Still... 2) ... Another example, I made a very simple mission with runway start of the L-39C. My throttle is all the way back, - when I look at the throttle position in the plane before unpausing, it's back - when I unpause, the throttle in the plane jumps to max - only when I move the throttle does it come back to the correct position. This, by the way, is probably the problem many experience now when they are unable to move the throttle to IDLE with a keypress (mainly in the new campaign's reports). I was hoping for a reply from the testers or ED, but it seems my reports are being ignored, I can't remember seeing a [reported] or any sort of reply from them in a long, long time. I don't know if that's a personal thing or not, I'm simply trying to help by reporting what I see, but I have to admit it's getting very frustrating and I have the impression reporting problems is worthless. EDIT: I didn't save the track for 1), but here it is for 2), one can see the throttle jumping forward, then back when I move it a little bit. L39C.rwy_start.bug.trk

bump

DCS 2.5.1.16978.363 Some 3-way switches are not behaving correctly (left/right click inverted, and so very confusing) By convention, left click = down / left / counter-clockwise, right click = up / right / clockwise. - flaps power switch - armament mode control, fuzing control, all the way to release interval control - ground IR cool switch - HUD display mode switch - up/down gain switches of all MPCDs, MPCD day/night mode - compass light/test lights - fwd equipment bay ECS switch EDIT: Apparently it was already reported long ago :/ https://forums.eagle.ru/showthread.php?t=196690

Are you looking at the page with "1-3" at the bottom left? Don't confuse it with "3-3", which is the last page when you have to return. I think the U-turn you mention is on that last page, and indeed you'll need to join downwind at EP, then land. But at the beginning, you're at page "1-3", and you must continue on 212° after taking off, then at SP turn right from 212° to 265° when you reach the river, at WPT turn right from 265° to 031° above the city (and not left as said by the instructor). I think the confusing part is that DCS always place you on the page right AFTER the last user kneeboard page, and you have to go backward so you first see the last page. Well, actually you can go forward all the way through lots of page, then you find the custom pages, but that's a bit long ;) Agreed!

Reminds me a little bit of Sabre's great qualification campaigns, although they were more detailed and took a wider range of the training in charge like start-up, shutdown and so on (in several campaigns). It's not for everyone, and requires more commitment, it's not the kind of mission I'd do to relax after a hard day's work, but it helps being and remaining proficient. Yeah, on 2 also, I think I've drifted a bit too much to the right for the 2nd control point. No message for that, however, the instructor was so upset he wouldn't speak to me anymore ;) I find it particularly hard to monitor time and spot landmarks while maintaining altitude, this little jet is all over the place really. So still a bit of overhead until maintaining a stable flight becomes second nature. Reading the time when the minute hand is hidden behind the clock hands doesn't make it easier, I've always suspected those chronograph makers to be impractical and fancy ;) Next time I'm trying with my own watch. EDIT Actually, having the same in training missions, with runway start, would be helpful.

Another bug report (still no forum?) - mission 2 The instructor says to turn left on WPT ;)