Terry Dactil

That's easy ... You missed the last step You use the AuthentiKit Tuning App to synchronize the movements PS> Not as accurate, but close enough for me; Use Bodnars setup to increase the number of key pulses per encoder click.

Are the guns armed? (Left Shift + Space_

Agreed that's a fair comment if you ask it about something disputed and there are many different opinions on the internet. However, asking for stuff from official historic documents like aircraft pilot manuals and performance regulations is a pretty safe bet to be correct. What errors did it make in this thread?

Yeah. It's understandable now. My aviation career was after WW2 and performance calculations were greatly improved and more precise. In particular I used (and taught) that the Take-off Safety Speed (V2) was the greater of 1.1 times Vmca or 1.2 times the stall speed. I guess if I was also carrying bombs that would be nowhere fast enough to keep me happy.

Thanks for your explanation Holbeach, what you say is correct. I managed to find a great site for aviation manuals Avialog: Aviation Library and downloaded the Pilots Notes for our Mosquito. It looks like your reference. Since I have been happily flying the Mosquito on one engine at max power by staying above 150 mph, I think adding 65 mph and calling it a 'Safety Speed' is a bit excessive. I would call it a 'Feel Good Speed' All this is understandable since Vmca in performance calculations was not official in WW2. ChatGPT has some interesting stuff on this subject ... The concept of Vmca (Minimum Control Speed Airborne) as a formalized element in takeoff performance calculations did not exist in its modern regulatory form during the development and operational service of the de Havilland Mosquito in the 1940s. Key Points: Vmca as a defined regulatory term became standardized in post-WWII civil aviation regulations, particularly with the introduction of FAR Part 23 and Part 25 by the U.S. Federal Aviation Administration (FAA) in the 1950s and later by ICAO and EASA equivalents. During WWII, aircraft performance calculations—including for multi-engine aircraft like the Mosquito—were based on empirical testing and operational experience, rather than a codified set of performance speeds like V1, Vr, V2, or Vmca. The Mosquito, being a military aircraft, was not subject to civil certification standards. Its performance charts and procedures included speeds for safety, single-engine climb, and control, but these were not labeled using modern terminology like Vmca. However, the underlying concept of a minimum speed at which directional control could be maintained after engine failure was understood by test pilots and engineers. They considered factors like asymmetric thrust, rudder authority, and yaw tendencies in both design and flight test programs. Summary: Vmca as a formal part of takeoff performance calculations was introduced in the postwar era, particularly with the advent of civil aviation regulations in the 1950s. For the de Havilland Mosquito, such a parameter was likely considered in practice but not named or standardized as "Vmca" in the way we know it today.

Where did you get that from? It's a myth that the Mosquito has a very high takeoff safety speed. Its Vmca (minimum control speed airborne) is 140 ~150 mph depending on weight temperature altitude and other stuff like bank angle. Sure, it's like any other twin and would get very exciting with an engine failure between lift-off and Vmca. Some more info from ChatGPT:... Geoffrey de Havilland, the legendary British aircraft designer and pioneer behind the de Havilland Mosquito, played a unique and bold role in supporting his aircraft's reputation during World War II—not just in the design office, but on the front lines of perception and morale. A persistent myth among some operational RAF crews was that the Mosquito had a dangerously high take-off safety speed, and that the aircraft was extremely difficult—or even impossible—to control if an engine failed on take-off. This belief posed a serious problem: not only could it undermine confidence in the aircraft, but it might also affect performance and mission readiness if pilots hesitated or overcompensated due to fear. To directly combat this, Geoffrey de Havilland himself visited squadrons flying the Mosquito, bringing with him not just technical data, but a dramatic and personal demonstration. On at least a few occasions, he would personally take off in a Mosquito and deliberately cut one engine during the take-off roll—the very scenario pilots feared. Even more impressively, he would then proceed to fly the aircraft on one engine, performing aerobatics such as loops and rolls, to prove that the aircraft could be safely handled even under such adverse conditions. This hands-on approach served several purposes: It dramatically boosted pilot morale and confidence in the Mosquito’s handling characteristics. It dispelled misinformation about the aircraft’s safety and performance. It reflected de Havilland’s personal courage and belief in his design—a powerful endorsement for frontline airmen. De Havilland’s willingness to prove its mettle in such a public and daring fashion became part of the lore surrounding the aircraft.

Agree 100% with bbrz. I used this training aid many years ago to hammer in the message "IF YOU ARE HOLDING CONTINUOUS AILERON YOUR RUDDER INPUT IS WRONG. MOVE YOUR FEET! (the down side of the yoke is pointing to the foot that needs to go in more)

Be aware that a small amount of bank can be helpful. Vmca for the Mosquito is defined with 5° bank into the good engine.

It can help if you know the the best climb performance speeds for the Mosquito. They are Vx (best angle) 140 ~ 150 mph Vy (best rate) 160 ~ 170 mph

I repeated this mission several times and may have found the problem. It is possible to have the large icon centered in the windscreen but with the needles on the gauge in the cockpit slightly off center. If this is the case the bombs will completely miss the target, and the mission fails. My suggested solution is to check the needles at the 5 miles warning, correct if necessary and nail that heading until bombs released.

Suggest you try using Voice Attack. You can then use verbal commands to the (unfortunately still invisible) navigator to do all the complicated multiple keystroke stuff. I get Nigel (my navigator) to read checklists, select the bombs, feather engines, select fuel tanks etc. just like a good navigator should. PM me if you want the profile.

Have you tried adjusting the viewpoint? I use VR and it generally puts me into the cockpit with my head a bit too high and left. You can use the keyboard, but I use Voice Attack and commands to "move seat position" R CTL + R SHIFT + NUM Key (4,6=L,R 8,2=Up,Dn)

Thanks for a great mod. (Sometimes little things can make a big improvement).

@cjayster13 How much memory do you have installed on your system? I checked how much memory gets loaded on my system if all my DCS options are available (12 aircraft modules, 8 terrains and tech packs and 9 campaigns). Started the Mosquito's V for Victory mission 3, along with auxiliary programs Simshaker, OVGME, Voice Attack / Vaicom, and Pimax VR ... Wow ! 27.4 GB If you are running a 36 GB system for an hour or so, then memory leakage from one of the running programs seems quite plausible.

It could be a memory leakage problem. Here is what ChatGPT has to say about it. Me: What are the symptoms of a memory leakage problem in DCS? Could it have a pulsing effect occurring after an hour? ChatGPT reply: Yes, memory leakage in DCS (Digital Combat Simulator) could cause performance degradation, including the symptoms you describe, such as a "pulsing effect" after prolonged usage. Memory leaks occur when the game does not release unused memory, leading to increasing memory consumption over time. Here’s how this might manifest: Symptoms of Memory Leakage in DCS Pulsing Effect: This may occur as periodic stuttering or frame-rate drops, especially noticeable during gameplay after an hour or more. The "pulses" could coincide with the game's attempts to reclaim memory or perform garbage collection. Gradual Performance Degradation: Frame rates may start high and slowly decline as the system's memory fills up. You might notice delays or freezing when transitioning between menus, maps, or missions. Increased System Memory Usage: Memory usage for DCS may grow continuously over time when monitored in the Task Manager (Windows) or Activity Monitor (macOS), even if the game state remains static. Crashing or Forced Exits: After prolonged sessions, DCS might crash to the desktop or trigger errors related to insufficient memory. Longer Load Times: Mission loading, reloading, or returning to menus could take increasingly longer as memory fills. Unresponsiveness: Input lag or delays in rendering textures and objects may appear as the system struggles to manage memory. What Causes the "Pulsing" Effect? Resource Reallocation: The game engine may attempt to offload unused resources (e.g., textures, models) periodically, leading to frame drops or stuttering. Paging to Disk: If memory is exhausted, the operating system might start using the pagefile (virtual memory), causing a noticeable "pulse" of lag when data is swapped between RAM and disk. GPU Overload: If memory leakage also affects VRAM usage, it might cause irregular GPU performance, resulting in visible stutters. Troubleshooting and Solutions Monitor Resource Usage: Use tools like Task Manager, MSI Afterburner, or a performance overlay to track memory and CPU/GPU usage. Reduce Graphics Settings: Lowering settings like texture quality, terrain details, or draw distances can reduce memory consumption. Update Drivers and Software: Ensure GPU drivers and DCS are updated to the latest versions, as patches often address memory-related issues. Modify System Settings: Increase virtual memory (pagefile size) to help mitigate memory exhaustion. Use utilities like RAM cleaners to free up memory during gameplay. Check for Known Issues: Consult DCS forums and patch notes for information on unresolved memory-related bugs. Test Mods and Scripts: If you use mods or custom scripts, disable them to rule out compatibility issues that could contribute to memory leaks. If the problem persists, it could be a deeper issue with the game's engine or a specific system configuration. Reporting detailed observations to DCS support or forums might help identify the cause.

No problems with it here. Processor 13th Gen Intel(R) Core(TM) i9-13900KS 3.20 GHz Installed RAM 64.0 GB (63.8 GB usable) GPU NVIDIA GeForce RTX 4090

Yeah. I take your point. However, the DCS profiles are shown as global, so they should get loaded automatically with the startup profile Vaicom pro, I would like to see what happens if this was reversed, or better yet if Voice Attack was set in diagnostic mode. (Also my favorites method of last resort is to nuke Saved Games)

Since it appears that your Voice Attack/Vaicom has a problem communicating with DCS, it may be worthwhile checking the export.lua files. These are in your ... \Saved Games\DCS\Scripts folder The Export.lua has a link to VAICOMPRO.export.lua The VAICOMPRO.export.lua file is full of technical stuff like sockets and stuff way beyond my comprehension. However it has one advantage. If you rename or delete this file it will be re-created on the next program start. This may be worth trying.

Agree that there is a discrepancy with the boost figures in the manual.. My post was having a smile at the idea that continuous could meant only after one hour had elapsed. Sorry.

Read more of the manuals and find the bit about maximum continuous power...

The latest updates had nothing of significance for the Mosquito - again. Makes me wonder just how many more years since its release in 2021 it will take before it gets completed. (Never mind - there are lots of new and shiny things coming that will get your attention)

Voice Attack IS a button press system. You don't have to talk to it.

Voice attack ... Press a button, or verbally pretend you are asking your navigator.

Yes. Completely agree. I have trained my navigator - Nigel - to do all that as well as read checklists, operate the radio and key the morse ID codes when required.. MY Voice Attack also sends the correct sequence of radio channel selections to operate the autopilot autolevel/orbit modes and then reset the radio to the original channel. Can't do without it.