Redglyph

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 At night, there are lots of red pixels switching on and off from the pilot's view. You can see them on the left / centre of the screenshot. That doesn't look natural at all. The red reflection of the flood light on the canopy is nice though, even if it's looking concentrated in two dots. I like the way they move with the pilot's head, unlike the usual reflections on the canopy that are static and look like stains. Perhaps those red reflections are linked to the graphical bug above? I saw that during a flight at 18h40 on 1st August close to NTTR, for reference, but it's visible in any flight during the night.

By the way, perhaps you can check out this (long) thread about RSBN stations on the Albatros, there were discussions on how to add the missing stations, for ex. on Nevada. Perhaps it's not relevant anymore, and/or perhaps it's the same as the link given by Rudel above (thanks!), I can't verify that right now. https://forums.eagle.ru/showthread.php?t=184072 Who knows, maybe one day we'll be able to create that in specific missions, as those little trucks are supposed to be mobile. That'd be fun.

You're right, the MiG-21 definitely has something about it. Perhaps a mix of several things, it's a bit mystical, linked to the Cold War, to the Constant Peg programme. It's a mix of interesting technologies, quite old and still analogue but with a radar, good navigation tools, and nuclear capability. You can even find alcohol in it ;) It first looked ugly and ridiculous to me, until I finally got curious and bought the module, and I've been almost obsessed with it right away :D Well, once I got past my disappointment at the poor training missions and the lack of campaign. I just discarded that part and learned from the Pilot's Flight Operating Instructions available on Avialogs, which instructs quite a different start-up procedure. It's a wonderful machine, and a great implementation of it in DCS :)

You'll find them in Mods\aircraft\MIG-21bis\Cockpit\Systems: R_NAV_data_Caucasus.lua R_NAV_data_Nevada.lua R_NAV_data_Normandy.lua R_NAV_data_PersianGulf.lua

\o/ That wasn't easy to catch, only had this a few times on all the flights. Congrats!

You need DCS 2.5.3.23225, if I'm not mistaken (see here). Have you updated and are you in the openbeta?

The thread is marked as [can't reproduce] so it's probably not watched anymore, you'll have more chance creating a new one.

And to add insult to injury, they seem to opt for the F-35 (I guess F-35A) for the replacement of their F-16s. Sad times.

QFE is given in all units on the briefing page, but it won't help you if you're landing somewhere else, and it won't help you with aircraft and terrain avoidance, transition altitude, semi-circular rule and so on, that's why QNH is used internationally (except in some countries, like Russia apparently until they finally moved to QNH in Feb 2017). Unfortunately, QNH is never given by ATC so it's indeed to be considered broken right now, and it's only given in mmHg and inHg on the briefing page, not in standard units which are used by most aircraft. There were projects of upgrading ATC, but I have no idea what is actually planned right now, it's still noted "in progress" on the roadmap page but that's no guarantee. EDIT: you can actually patch the briefing page (Scripts\UI\BriefingDialog.lua) line 507, to add correct international units, but if the Yak has mmHg, it's already there :)

Good to hear the Fishbed is getting an overhaul! :) About the cockpit: do you plan to fix the mouse click bug with switches? (so, simply releasing the patch I gave you about 2 years ago)

Yes, I was thinking about something like that but with an external program, similar to how PWCG has brought dynamic/persistent campaign to another sim. I'm not sure it's possible to launch DCS on a specific mission and exit, but after all the data saving part is what Tacview does by grabbing data in real time (or alternatively the temporary track file could be decoded). It's probably the only, not-too-invasive way, but it's indeed lot of work, requires the user to launch a specific mission, and to exit DCS properly. One also has to hope it remains compatible.

The only "persistence" you get officially is the mission branching depending on the score, have a look at the manual pg 105-. Depending on the score, <50 (failure), 50 (draw), >50 (success), you can define which mission is next. A bit poor, but that may be a workaround depending on what you're trying to achieve.

Q: Will there be new features in the ME and mission flow to allow for training/"civilian" missions? A few items to clarify and illustrate the question: - support in Lua to read the gauges and model parameters, and to write updated values on actuators: most of the time it is much easier to put that in a script than using many triggers and actions, especially when it has to be repeated several times - more precise triggers to gather info: typically, what horizontal/vertical speed at touch down, or what is such model parameter when the user hit such trigger in space, flag to indicate whether something happened, even a short event for which current triggers would react too late - 3D zone triggers (currently only 2D circles, and very visible green gates): typical examples are control of pattern flight, approach and departures - module state persistence: it is strange to get a fresh new aircraft at the start of each mission during a campaign, maintenance could be available but the negligence should have consequences ;) - campaign data: the same idea but for general campaign state, idea of progression, items still to achieve, scores, ...

That's actually a bad example, the A-10C is a complete mess :D There's a patch for this one if you'd like (I haven't tested it in the latest DCS versions). But yes, since then they followed consistent rules to avoid that kind of situation. I'm sure Razbam will fix it eventually if that's not done already, they had a similar process on the M-2000C when it was in development.

Sure, no big deal. It was confusing and it's just so easy for a problem report to be drowned in noise, that's why I'd rather have other issues in other threads. Now to be honest I doubt this will ever be read by Razbam. If it hasn't after all this time, it has to be considered as dead anyway ;)

I don't understand your post, is this a question related to the bugs above, a report of more mouse clicks that are incorrect, or something that has nothing to do with this thread?

Not sure it's in the stable version yet, here are a few pointers :) You can see the latest announcements of the stable version here: https://forums.eagle.ru/showthread.php?p=3638932#post3638932 For the beta it's here: https://forums.eagle.ru/showthread.php?p=3650609#post3650609 Looks like the PFM made it in 2.5.3.22652, stable is only 2.5.3.22176. You can also watch the 'real' current versions here (sometimes the threads above are late): http://update.eagle.ru/ And the whole log is here: https://forums.eagle.ru/showthread.php?t=114030&p=2249076

Welcome back ;) Yes, it happens now and then, that's why the suggestion of a default config that is copied to a new, config-less module seemed to make sense, it would set the user's default mappings which usually cover more than half settings of each module (and that would remove all non-sensical mappings like buttons on pedals, POV or trimmers on thrust levers and so on, which take even more time in the config process than the actual remapping). There is a default config, but I didn't find its purpose.