Redglyph

DCS 2.5.3.24436 I confirm that. On the right of the screenshot is a user aircraft, wheels correctly on the ground. The two on the left are AI, they are floating above the ground after (and while) taxiing, and when parked. 2nd screenshot with Viggen AI taxiing (floating). 3rd screenshot with F-15 AI taxiing (OK).

A few issues in version 2.5.3.24436: - In the settings, mapping "Taxi/landing lights switch" of the "Lights panel" category turns the position lights on. So it should be called "Position lights ON", or it's a label and tooltip mistake. - The position light brightness knob turns the wrong way with mouse clicks (left click should turn anti-clockwise). - The radar maintenance testing mode only turns with the mouse scroll, it's obviously a fixed-position knob and not a progressive knob, should be mapped to mouse clicks? - Magnetic declination correction, the user cannot see the current setting. - The 3 lights "SPAK", altitude hold, attitude hold: when ON, the green illumination is smeared horizontally across the other lights (see screenshot), such artefacts should be avoided. The other cockpit lights are OK. - Missing translation for "SPAK", "Slav SI", "Höjd CISI" (sic). - The 3-way button for radar mode does not always catches the middle position. Here the A0 (3 positions switch) and the A2 (3 positions switch) are mapped to a HOTAS 3-way switch and half of the time, switching from A0 to A1 or from A2 to A1 works, half the time it's not detected and I have to do A2-to-A0-to-A1 for example. - The weapon selector and weapon interval selector knobs are also turning the wrong way (and their texture is very low-res).

I like the way some of the items are set in the cold start training, mostly at the beginning. Items are highlighted (even though this highlight usually makes the item barely visible, but that's a DCS issue), and - either the user has to change the setting, then the training automatically goes on, - or the user has nothing to do, and the training goes on after a short pause. But after a few items, the coherency breaks down, there are a few issues that would merit some attention :) 1) There is no voice for the data cartridge insertion, unlike all other items. 2) Sometimes the user has to press SPACEBAR, sometimes not, sometimes a cockpit settings has to be changed and it's detected automatically, sometimes not. In the case of the lights, it's a mix of both, it's detected but yet the user has to press SPACEBAR and the training only goes on if all the lights are set correctly (by the way, I don't think the formation lights are necessary at this point). All that is confusing and it would be best to keep a consistent approach to how the training continues / pauses. 3) The "visible pin" of the trim which appears when it's centered is lost on me, what pin, where? 4) The "Hud visible glass position" highlighted pointer is at the wrong place (way below the control position). 5) The magnetic declination knob is unreadable, I can't tell its current setting. Also, magnetic declination has a sign +/-, it should be mentioned. 6) The engine starting part: "Keep the switched pressed for two seconds and the start sequence should begin automatically". A lot of problems with this sentence: - keep the "switch", not "switched", - it's not a press switch, it's a toggle switch, so it's not possible to maintain it pressed, - if I put it to ON, then OFF after 2 seconds, the startup sequence does not work, so I'm not sure what those 2 seconds are all about, - "the start sequence should begin automatically", it's not starting automatically since we have to toggle a switch for that. 7) "Press SPACEBAR to contrinue" (also a mix of "Press SPACEBAR to continue." / "Press SPACEBAR TO CONTINUE." / "Press SPACEBAR to continue" / "Press SPACE to continue.", but that's not a real issue), 8) "The next lesson will be on how to taxi to the runway and taking off".

Side notice, since it's somehow related and probably doesn't deserve a new thread: In the NTTR navigation mission, there is no message when the user is asked to turn to waypoint 2 and go there. I followed the instructions and got all the way to WPT 2 (some 6 minutes away) and nothing happened. Then I realized the space bar message may have been forgotten ;) It's probably best to add it, to avoid confusion.

This bug has been there for a very long time. You can simply start any mission with the M2000-C and change the settings from there :)

Nice story, thanks for sharing! :) It would be an awesome module technically speaking, but it wouldn't make sense in the relatively "small" DCS maps (and here I emphasize "relatively"). This bird best operates at speeds beyond 3.05 M and altitudes higher than 71000 ft. With a maximum load factor of 1.5 and a turn radius of more than 40 NM, this would allow for little excitement, even if there was a map big enough for a significant flight (and a PC powerful enough to load the required objects the Blackbird is able to photograph - probably the entire map, actually). Finally, the spy role is not supported at all in the current missions. Still, that would be a challenge to operate, even more with only one pilot :)

One of my DCS orders has disappeared from the list on the website, though it's still listed in the installed modules when I launch DCS. So not blocking, but a little worrying. It's the very good "A-10C 16-2 Red Flag Campaign", ordered on 11 Feb 2016, on the DCS website (not on Steam). When I check the shop, it's not shown as "bought", and when I'm looking at the list of orders, it's not in it. I still have the email with the serial, but not the order number, curiously that seems to be the only DCS licence email I've received without the usual formatting and the order number.

Here's the link:

OT again, it's not obvious to spin, trying to get into the 1st regime and turning with power, it seems both wings stall simultaneously, in contrast it's much easier to "achieve" with the Mustang. Perhaps using flaps makes it easier? It's easier to spin on the ground ;)

Anyway, this thread has not been seen by any dev since it's not [reported], we'll have to report it in DCS and hope it's caught there.

Sometimes it's a little bumpy, but it's still good enough to have a lot of fun with the new features and content. You can also report problems to increase the chance of having them fixed in release versions, although the whole bug-reporting cycle remains very obscure to me, seems like you've got to be lucky for the post to be seen. Or they are seen and reported but without feedback, this is always hard to know.

Thanks for the cleanup ;) And I suppose they switch on and off because they're at the limit of the size to be drawn? That would make sense. Well, it wasn't obvious, especially since other tiny sources were visible and moving accordingly to the head movement, while those pixels didn't seem related to anything. But now I understand (well, I think so anyway), thanks for clarifying that up. I still don't like it but that's just me, at least it's not a bug. :) Pit? Like in new cockpit? Looking forward to it!

I never had any problem with external power, but I've also done quite a few cold starts from the battery and never got any problem... except once when I took too much time (1st time while reading the manual) :) The battery does have a tendancy to deplete rapidly once you connect a few devices, like most airplanes.

That's explained in the user manual, that you are supposed to read before the mission ;) 6. POWER SWITCH. Used to power up the HUD. It has two positions: normal operation (right - click once) and test mode (accessible after second right - click). I don't know which version you were using back then, nor which mission that was (NTTR or Caucasus), perhaps try again? All I can say is that I did both, Caucasus months ago, and NTTR right now, and that was fine. Sometimes the missions break with some versions of the beta DCS.

I didn't have this problem. Perhaps it requires you to press space bar? I know it's confusing in this mission, sometimes you have to, sometimes you don't.

DCS 2.5.3.23954 It's great to see there are training missions in Nevada as well! :) I have noted a few issues below, nothing blocking or major. 1) "You will find a full list in the "Aircraft Procedures" chapter ... as well as on your kneeboard" (see picture 1) => there is no procedure information on the kneeboard 2) longitude adjustment: the audio is corrupted (see picture 2 for expected text). 3) Pressing the test switch: the highlighted indicator is impossible to locate (as a general rule, those indicator make it very difficult to read the knob labels and should be avoided altogether). See picture 3. 4) Bingo fuel, "You will usually find the required value in the mission briefing or on your kneeboard. Press SPACE BAR when you are ready". What value should I put? I see nothing on the kneeboard, and I didn't see any briefing info (only wrong coordinates, are they from Caucasus?). 5) The user is first asked to contact the tower. Then a few seconds later the text continues (with another voice), so I'm hearing both the tower answering and the instructions of the training, it's confusing. See picture 5. 6) The user needs to press SPACE after setting NAV / N once the INS alignment is completed, but it's not said. In general: sometimes the user has to press SPACE, sometimes the conditions are detected. I understand why because I used the ME to create missions, but 1) here sometimes it could be detected while it's not, and 2) it would be better to have a consistent protocol for the whole mission. 7) During the engine startup, the sound is suddenly inaudible / very faint, while it was very audible initially. It seems like a new sound bug in the latest DCS updates?

I set the mappings in the aircraft and this time it didn't crash (like before), the modifications above were not saved when it crashed. This time the kneeboard was working. So those two problems are as I remember they were long ago.

Are you doing a battery start? Usually the MiG-21bis is started with ground power, which leaves you more time to check things around. Before the startup, you could check the battery to see if there's a problem, so: 2. Check battery panel control/indicator setting/value RH 52 bat/ext power ON RH 60 drain tank fuel pump ON RH 57 #3 tank group fuel pump ON RV 43 PO-750 inverter start #1 breaker ON RV 17 radio systems ON CM 76 check: voltmeter >= 22.5 V CL 66 check: battery capacity >= 40 Ah RV 17 radio systems off RV 43 PO-750 inverter start #1 breaker off RH 57 #3 tank group fuel pump off RH 60 drain tank fuel pump off RH 52 bat/ext power off (the panel indications are related to the DCS manual) I did the check and it was fine. I did both the battery and external power start-up procedures and had no problem, at NTTR in DCS 2.5.3.23954. I have attached the official procedures from the manual you can find on Avialogs for ex., in case it helps. I completely agree with you on the radio channels :) I made a template that I'm copying for each new mission, to avoid the trouble. Mig21bis_procedures.pdf

DCS 2.5.3.23954 I'm comparing the behaviour of the KPP horizontal and vertical needles to the user manual (Mig 21Bis Pilot's Flight Operating Instructions, available on Avialogs among others). The test was made on Nevada terrain near NTTR. The needles I'm reporting are (4) and (8) on the KPP/FDI diagram (also called ADI in the DCS manual). There are 3 modes: - navigation "NAVIG" (RSBN channel) - landing "LDG" (PRMG channel) - "LETDOWN" or most probably, "descent" (RSBN), this is called "PROCEED" in the DCS English cockpit and manual, which I find strange, perhaps a translation issue? (Пробив, is that from Пробивание? I don't speak Russian so I'm at a loss) From the original manual, see FDI explanations in attachment: (b) means that in NAVIG (RSBN channel), needle 8 = track position relative to aircraft position © means that in LETDOWN (RSBN ch) or LDG (PRMG ch), needles 4 and 8 = flight path relative to aircraft position What I see in DCS: NAVIG: 8 = aircraft position relative to track (if aircraft right of track, needle is right, opposite of what is expected), 4 = ? seems to be stuck high instead of neutral LDG: 8 = localizer position relative to aircraft (OK), 4 = localizer glide path relative to aircraft, except when the aircraft is too high but there is no pitch channel failure flag (I think it's the left 'T' flag in DCS, though the figure pg 54 has no legend for those flags), (so, mostly OK when channel received). It also seems like the glide path needle 4 is too high, especially when approaching the runway. LETDOWN (or "proceed" in DCS): 8 = aircraft relative to track, 4 = ? (not clear) So it seems that in DCS: "proceed" should be renamed to something more clear LETDOWN mode should work differently, for now it's the same as NAVIG for 8 and unknown for 4, it should be the flight path relative to the aircraft for 8 and probably neutral for 4 NAVIG mode should have track relative to aircraft on 8 (and not the opposite), unless it's badly expressed in the original manual (or unless I misinterpreted it) LDG mode, 4 should be checked, is it too high? shouldn't the pitch flag be set when the aircraft is too high in LDG mode and the 4 needle is stuck at the high position (and should the needle be stuck there?) shouldn't the 4 needle in neutral when not used (NAVIG mode)? I tried to compare to the L-39C, but couldn't find any documentation on how to select the PRMG or RSBN channels on the Nevada map, I assume they haven't been implemented at all from the posts I've seen, and that navigation is not available on that map. I didn't test the NPP (or CCI), it looks like the needles 5 are behaving like 4 and 8 of the KPP, which is not what is described in the Pilot's Flight Operating Instructions manual.

I have no problem on my end. I'm not sure the devs will be able to do much without more details on your system, the DCS version, the type of mission and when the framerate drops (if there is something particular that makes it worst - for example: if I'm flying Normandy with any module, it stutters when flying low). A track would allow a comparison.

I can assure you that's not the impression it gave me :D At first I thought my graphics card had a problem, like overheating or so. To make sure there's no confusion: what I see is pixels, not the canopy scratches we see on most or all cockpits when there is an external source of light. Those pixels are randomly appearing and disappearing. I'm attaching a few successive screenshots, TrackIR disabled, nothing is moving and I'm on the ground (but the engine is on, and with the physics perhaps the canopy/head relative position might be changing slightly though I doubt it would have an impact). You can see those square pixels switching on/off in time, around the bigger reflected red spot. They disappear completely if I switch the red flood light off. Is there an option to disable these red pixels? Too bad for the other, nice reflections but those are too distracting.

Is it normal it's flickering? It looks very annoying, as a graphics glitch. I can't say for sure if that's when I move the head, I didn't try to disable TrackIR, but it looks random.

...

Canopy "reflections" incorrectly visible DCS 2.5.3.23954 When the canopy is open, the stains that mimick the canopy reflections are still visible as if the canopy was closed. The canopy handle and the whole structure is correctly shown as open, and the sound is audible correctly too. Note: the "reflections" do not move when the pilot moves his head. I see similar reports but they are in an old thread and in other conditions (VR) so I suppose it's something different.

DCS 2.5.3.23954 I was trying training mission 1 in Nevada, then I realized it was not possible to turn the kneeboard page to get the current coordinates (this is an old bug IIRC). I tried to configure the setting with another key, to make sure: - open settings (while in sim), click on the "next page", type another key => not possible to save, the option is greyed out, only cancel is possible. I thought that perhaps it was due to a new mapping conflict, so I browsed the settings from the main screen (not in sim anymore). I only saw the usual bug that assigns the POV to all devices, so trying to map POV U/D/L/R to my rudder pedals for instance. - painstakingly cleared them one by one - SAVE => black screen I had to kill the process. So it looks like two bugs: - kneeboard not working properly - assigning keys crashes DCS in main screen I'm pretty sure those bugs were seen months ago, if not more.