scoobie

We got a winner! Thank you @The LT, the idea with presets helped solve the puzzle. I reported it in another thread. So, basically... two facts: 1. In the "few MHz" band English ATC people actually do talk on the frequencies given in F10 map. (I tested in MiG-15). Haven't tested the French, but I assume everything should be fine. 2. You can't contact stations at around 3.800 MHz, because if you set the transmitter to around 3.800 it's simply not that frequency. The transmitter actually "talks" 3.800 when it shows 3.700. Go figure. So, case solved (and bug reported). Thanks!

Ha, it's a bit of a pity as I actually preferred your solution over mine... even more so if someone else came up with a ready to use formula Laziness is a bad thing, I know, I know. I have no idea about this whole Lua language-like thing, so I wonder if 5th order polynomial isn't even slower than searching through a table, who knows. I'm very glad if you can make any use of this junk of mine in any of the cool things you're doing for folks here. That's the least I could do, really.

That's the one! The navigator's Morse key lets you talk to ATC In the Controls window it's called "T1154, key button - press" and by default it's LAlt + \ On T1154 select "R/T." (which supposedly stands for "radiotelephony"). OK, I know it wasn't a very practical excercise, but I checked ALL airfields on the English side of the Channel map, one by one. I ran through the list given below twice, which means I had to tune each airfield from scratch twice - to reduce the risk of dialing in a wrong frequency (both times). Same results each time, which may indicate there's nothing wrong with the radios in the Mossie (nor arcane about them, at least not voice comms), but maybe something wrong with frequencies/ATC on the Channel map. If anybody (out of boredom, I suppose) cares to check and gets the same results, I'll report it in the Channel map forum. Or maybe someone can test French airfields? Here's the sequence in which I attempted to contact specific ATC. All frequencies in MHz. Hawkinge 4.000 OK Detling 4.050 OK High Halden 3.800 no reply Headcorn 3.825 no reply Lympne 4.025 OK Biggin Hill 3.850 no reply Eastchurch 3.775 no reply Manston 3.975 OK P.S. Yeah, I know it's not THAT important, but I found it kind of sweet that Mossie is the first warbird in which you can talk to just about anybody, you're not limited to those 4 preset channels.

Hi folks, I guess I'm too dumb to figure out how to work with these radios, so maybe someone can give a tip? Have you ever been lucky talking to various ATC on the Channel map (single player)? I can tune 4.0 MHz and talk to people at Hawkinge (where my mission starts) no problem. They talk back to me, clear for start-up etc., but when I'm later trying to contact any other airfield, High Halden, Manston, whichever, while I'm already in the air (for example to call "inbound") - they always remain silent. There must be something I'm doing wrong. I just retune the transmitter and the receiver to the new frequency, isn't that enough? Yes - I keep the "standard" A/B/C/D channel radio (TR1143, IIRC) OFF all the time, so it doesn't get in the way.

(I don't know the answer to what Sarge55 asks.) @Bremspropeller, @Diesel_Thunder - thanks a lot!

This ^^ On top of that I do one thing more (I'm using TrackIR). When I'm "precision trimming" for cruise for the first time, as good as I possibly can (which takes a while), I first "shift" my head towards the centerline of the cockpit (a little bit is enough), then I press "recenter TrackIR" and move my head back to the left. This way my viewpoint gets shifted left, as if I leant my "virtual head" against the side window or close to it. Once she's trimmed - as said above - use "long term" gauges, the altimeter and DI, so that you can monitor when she drifts too much (and she will).

[deleted] (I thought I got it, but not quite.) Thanks! Now I know why flick the switch in flight., so why you need a switch at all. What I still don't get is why be so scrupulous to set "MOD" before take-off. If MOD = AUTO (at low alt), who cares if it's MOD or AUTO? They built it "the safe way", i.e. malfunction = low gear (safe).

Oh, thanks for the tip! I really need to get down to reading the pilot's notes at last - so it is: ↘+7 boost @ full throttle => supercharger AUTO. Where are my tentative checklists... bloody mess... Yeah, I wish I knew the exact reason why they put "MOD" position (I hope someone has more insight into this and can explain), but one simple thing is fairly sure - it seems to be a safety precaution, so someone who knew exactly how this automatic speed change mechanism worked (so an engineer, most likely) had to fear it may go wrong and kill the engine (and possibly a crew). I can't remember clearly, but a simliar patent is in the Spit. However, AFAICR there you need to flick the switch to "M.S." (or something like that) EDIT: then back to AUTO and only confirm the supercharger remains in low speed. Then you leave switch in "AUTO" and go taxi, take-off etc. So it's a bit different in the Spitfire (or I have a bad checklist, which is also plausible ).

Don't quote me on that, but I think it works like this: You start the plane in "MOD" (I don't know what "MOD" stands for, really) - this position of the switch keeps the supercharger at low gear/speed PLUS it prevents the supercharger from switching to the high speed automatically - just in case something went wrong, the supercharger automatic control went nuts, turned "high blow" at low alt and overboosted the engine or anything of this sort. You don't need trouble when taking off or low above the ground in general. That's my understanding of it, I may be wrong, though. Then, when you are at somewhat safe altitude and planning to climb higher and higher, you flick the switch to "AUTO". Auto means that the plane will switch from low to high supercharger speed automatically at a "prescribed" altitude (which depends on a specific engine installed in the aircraft). You need high gear at high altitude to keep high manifold pressure, thin atmospheric air up there is not enough for that, nor is supercharger low speed (which is "tuned" for denser air).

I fight magic wherever I can, so I'm sorry about it The pitch trim button commands "twitchiness" has NOTHING to do with the flight model, tail heavy aircraft or whatever regarding the real thing. Mossie doesn't have a motorized trim wheel, like they have in airliners, for example. So "pitch trim up/down" commands are just FAKE and it's strange to talk about how "realisitic" or "unrealistic" they are. They're fake in the first place. They're not there in the real Mossie. They (the button commands) have been prepared for those of us, gamers, who don't have a proper trim wheel, so instead we want to tap joystick buttons or keys on the keyboard to trim the elevator. It's NOT the flight model. All these trim nose up/down commands do is "magically" turn the trim wheel at the arbitrarily pre-programmed speed, set in a Lua file OUTSIDE of the Mossie's flight model. What we can talk about is is this pre-programmed speed OK for most of ppl or only for few of them? Or no one, IDK. Personally, I don't care, I got used to the fact that I find most of such pre-programmed speeds in DCS (for various controls) too big (e.g. target wingspan in gunsights), so I just tone them down in Lua files. For many it's a blessing that we can do it on our own, and TBH it was a very smart move from ED, because, at the end of the day, we have all sorts, types and shapes of controls and they (ED) can't really cater for everyone's needs and tastes. It's next to impossible. However, if lots of people - provided it actually is lots - find a very basic flight control (a trim) too twitchy, maybe something can be done about it? I'm not advocating for myself, but for others (I've solved the problem for myself). On the other hand, please notice that no one is whining about rudder trim. Why? Because its speed (for buttons: trim left/right) was so pre-programmed that most people seem to be happy with it. That's really all there is to it.

No cage knob in the British AH Mk. IB and IC, they rely on self-erecting only. Trouble is, they don't seem to work like this in DCS. I'm talking warbirds. I'm not sure about American and German birds, I guess they're all the same in this respect, but I have checked only the Spit and the Mossie where it's particularly important because you can't do anything about your upset AH other than fly straight & level (no cage knob/ring). Here's the topic both with the problem and a few publications (I gathered a few, I hope you'll find them interesting):

^^ Fun fact: the Russian one does! Gives all speeds in stereo: "XXX mph (YYY kts)". (I've just peeked at it.) Let's hope this "data loss" is reversible.

Let others speak for me. (AI = attitude indicator) Firstly an excellent computer animation of pendulous vanes: Secondly how it works in a real AI (fast forward to about 1:43): Thirdly an old picture. It may be from WW2 or later, I don't know, but it definitely shows an EARLY design. Source: https://commons.wikimedia.org/wiki/File:ArtificialHorizonVacuumGyroErectionMechanism.jpg Pay attention to how the vanes look like: Lastly the British Mk. IB (Spitfire) AI. Source: https://caggius.wordpress.com/artificial-horizon-mk-1b-6a-1519-teardown-spitfire/ The below picture comes from this site, but I added annotations in red: So, yeah, I understand there might have been little motivation to do self-erection simulation in DCS if (so I heard) the maps in DCS are flat (no Earth's curvature). And to an extent you may say it was fine for as long as all warbirds had either a cage knob (USA) or a cage ring (Germany). In these planes, if your AI goes bad, you're annoyed and as soon as you can fly straight and level, you cage/uncage and you're good to go again. But how about the Spit and now the Mossie? Once you upset your AI, it's scr*wed until you restart the mission, so it seems.

Hmmm... just did this experiment myself. Knocked the gyro and went flying straigh & level for over 10 minutes. It didn't erect, I'd say it got even more messed up than it was on the take-off (screenshot attached... sorry for not taking initial screenshot, I forgot). So umh... anybody knows how to erect a knocked gyro in the AI (AI for attitude indicator) if you don't have the cage knob? Maybe there's no vaccum, I need to flick some switch, ask nicely or something?

I can't check now, but... AFAIK that's how this British horizon worked (Model Something Mark A Few, can't remember off the top of my head). The same or similar instrument is in the Spitfire. This thing doesn't have cage/uncage knob for the pilot, but settles itself over time. Pretty long time, not seconds. I haven't checked in the Mossie, but maybe an experiment could help: first have your horizon "skewed" for whatever reason, disturbed, then enter straight & level flight and keep her like that for a few minutes. Does the horizon "straightens & levels" itself? If so, apparently it was meant to work like that. Yesterday I was cruising around neighbourhood just for the pleasure of cruising around and noticed that the horizon was perfectly straight and level. So maybe it just works? American planes had different horizons... and they were pretty bad, horizons that is, not planes - at least as they are depicted in DCS. On the other hand, these planes had sensitive slip & turn indicators, so at least for cruise you were supposed (I think) to use primarily them (plus altimeter and VVI) - they're excellent for that job. AFAIK, artificial horizons were kind of new tech at that time and were far from perfect, though I stand to be corrected on this.

Humble correction - at least on my part: for me no bug. I think I know what it was all about. I've just chased every light knob in the cockpit, but this time I was turning them with click & hold & move mouse, not a potentiometer. All the knobs I was lucky to find actually work as OFF -> MAX -> MIN, including the gunsight brightness. However, apparently all/some of them require "Invert" in the "Axis tune" window and I might have had a mixture of them with or without it, now I don't know myself. Anyway I made myself a puzzling mess of control assigments. I've checked the gunsight, too - it also works OFF -> MAX -> MIN. I've replayed your track @Tarres - it seems to be exactly that - when you think you are turning the (hidden) knob UP, because the gunsight gets brighter and brighter, you actually turning it DOWN, towards the "ON/OFF" switch. The reticle is getting super bright and suddenly it goes off and the viewpoint returns to left. I've tried with both the mouse and a potentiometer (this time with "Invert" ticked). So as far as I'm concerned, there is no problem/bug, instead a rather intriguing coincidence of knobs, which work like "in reverse", which however require "Invert" in Axis Tune to properly work in reverse, otherwise you get the reverse in the reverse and the OFF switch at the end of the rotation... uhm, yeah, whatever, I figured it out EDIT: Found one that works "normally" (MIN -> MAX)! "Emergency Lighting - intensity, axis".

Just to check if we're talking the same thing. Are you using a "real" trim wheel - an analog control? Or a keyboard? Or some trim hat nose up/down buttons on your joystick? I'm asking because: 1. An analog control will work just fine, it's not the subject of this discussion. 2. Keyboards are on average fast as hell, you can tap a key for a very very short time. 3. Joystick buttons (+ fingers woring on them) vary in speed, but on average are slower than keyboards.

Uhm... to straighten this up a little bit... To the OP: "Banks left/right" (or yaws left/right) - that's normal, just like others told you here. It's a good old "manual" plane, not an FBW spaceship. Don't worry - you'll get it and Mossie trims pretty nice. But the pitch trim - if you're using joystick button commands for trim nose up/down and you find the Mosquito terribly sensitive - this is another issue, outside of the flight model, and the cure is to change the value in a Lua file as pointed above. If you fix the pitch trim problem, bank/yaw trims should get easier - I imagine that currently you're easily pushing her out of pitch trim and that's why two other trims immediately go to hell. Try the fix for pitch trim (start with 0.25 value, it's quite good), then see for yourself.

(Sorry for elaborating. The important part in bold font below.) @Tarres The fact that the viewpoint returns to left hand side of the cockpit when you turn the brightness knob so that the reticle goes off, is EXACTLY because the reticle goes off, nothing else. It's coded this way (and I don't claim it's "bad" or it's a "bug" - it looks like a design decision). How do I know? You may experience the same with the following experiment: 1. Turn the "electrical services" switch on. 2. Turn the gunsight switch on. 3. Set the sight brightness so it's actually visible. (Your viewpoint is now centered, right?) Now... 4. Turn the "electrical services" switch off. The viewpoint will return to right left hand side of the cockpit. Correct? It's coded like that - as long as the sight reticle is visible, the viewpoint is centered. If it's not visible (for WHATEVER reason) - the viewpoint returns to the left hand side of the cockpit. So... the bug is really about the brightness knob, which is one example of more knobs that go OFF -> MIN -> MAX -> OFF, instead of OFF -> MIN -> MAX. If the knob(s) axis/axes in the code get(s) tuned correctly (hopefully!), the viewpoint problem will disappear on its own. It's a "side effect" problem, that's what I'm trying to say. (I'm so "energetic" about it, because I'm worried they will fix this single knob (gunsight brightness) and leave the others untouched. And I do assign such knobs to hardware potentiometers in virtually all modules, so I care about these things probably more than other folks.)

Oh, yes! I forgot about these! Yeah, a few work OFF -> MAX -> MIN. It may be realistic *), may be not, I'm not 100% sure (I can only suspect they are just coded wrong), but those that go OFF -> MIN -> MAX -> OFF just can't be right. *) Might (just "might") be realistic because if in RL Mossie some of those knobs weren't just pots/rheostats, but instead pots/rheostats with a built-in switch - just like we used to have in old transistor radios (volume knob was often combined with the OFF/ON switch on portable radios) - in the Mossie they might have wired it the opposite way (OFF-> ON+MAX -> MIN). I have no idea why they would do that this way, but at least it's technically possible, so I can't be 100% sure. Of course my "gut feeling" tells me they're botched just as the (majority of) knobs that go OFF -> MIN -> MAX -> OFF.

Haven't tried the gunsight myself, but tried a few other knobs - they seem to work as you say. For example flood lights - you turn the knob from minimum to NEARLY maximum and the light goes brighter and brighter. Good! Then turn a little bit more to the very maximum and BANG - the light goes off. Numerous knobs, same behaviour. Probably it is "copy-paste" of one poorly tuned axis in the code, something like that.

Damn, I must have overlooked this one! Sorry! Let's say this is to confirm that it doesn't work in single-player, either.

Yep, wing bombs won't drop if installed by the ground crew. A few other ppl reported it in another thread:

Ditto, though you don't really need to land to get this quirk. I'm using "Takeoff practice" instant mission on the Channel map. Open window, ask chief to stick in 4 bombs (the mission begins with no payload) and fly. Bombs 3 and 4 (bomb bay) will drop, 1 and 2 (wing) will not.

If you want a "calmer" elevator trim and you're going to use a joystick for elevator trim, go to file: <DCS dir>\Mods\aircraft\MosquitoFBMkVI\Input\MosquitoFBMkVI\joystick\default.lua You may now do two things: 1. Modyfiy the original commands for trim nose up/down, but this, while harmless in itself, will result in double commands shown in orange font in "Controls" window. Nothing will break, but you may not like it. Orange font and double entries on the binding list will disapper only if you make identical changes to the same commands in .\keyboard\default.lua file - this is a perfectly valid solution, too. 2. Instead (that's what I chose), you may add the separate "trim slow" commands to the file: {cockpit_device_id = devices.CONTROLS, down = device_commands.Button_16, up = device_commands.Button_16, value_down = -0.25, value_up = 0.0, name = _("Trim Elevator Nose Up Slow"), category = _("Flight Control")}, {cockpit_device_id = devices.CONTROLS, down = device_commands.Button_16, up = device_commands.Button_16, value_down = 0.25, value_up = 0.0, name = _("Trim Elevator Nose Down Slow"), category = _("Flight Control")}, Now you need to tune the numbers for "value_down" in both of these commands to your liking. The original +-1.0 are very fast, while +-0.25 seem very slow. I've just started testing it, but 0.25 seem to be good for cruise when you want very fine adjustments, so you can let go of the joystick and sip your coffee. However, they may be too slow for quick configuration changes clean/dirty/flaps/no-flaps/etc. I don't know yet. Of course you can also multiply such pairs of commands (just make sure you give all of them different descriptions like "Trim Elevator Nose Up Slow As Snail" "fast as hell" or whatever). For example you can make one pair extremely slow (fine trimming during cruise) and another fast trim pair. I, for that matter, have a tendency in warbirds to assign one pair of trim nose up/down commands to TM Warthog CMS hat up/down, and the other pair to the trim hat (where they technically belong). Up till now they've always had the same speed, but nothing prevents me/you to have different trim speeds on either of them. (CMS hat left/right is also great for rudder trim in warbirds, while ailreron trim may stay on the trim hat). Suit yourself EDIT: Sorry. As for the elevator itself - use as extreme curves as in the Spit. You may start with something as crazy as 30 curvature + sensitivity Y about 70 or so. Then work with these numbers until you're happy with the results.