Terry Dactil

It has been a long time since I used TrackIR, but I think you have a command to re-ecener the viewpoint direction. If youu do then you should be able to use this handy effect I have in VR It goes like this .. Move to Nav seat. Turn head rightto look at the wing tip. Re-center the viewpoint Now you have the centered view with your head still turned far to the right So looking straight ahead you have this .. And now it is easy to look a bit to the left to see and access all the radio controls

Yep. Same problem here on occasions. However, I have found that increasing the revs to 1500 during warm-up speeds up the self errection process considerably. (Probably increased suction that speeds up the gyro or something similar is modelled). After that it seems to work OK for the rest of the flight. I have not been getting the previous huge errord developing in level flight.

Installing 2.8.3 Open Beta on a new Windows 11 computer. The basic program (the 2 aircraft and 2 theaters) installed OK, but i kept getting the “Server capacity may be limited at the moment. Please try again later” error when trying to install the other modules in my account. Tried numerous times selecting individual module or batch selections with no success. Tearing hair out until I decided to check these forums to see if anyone else had seen this problem and that was the smartest thing I did that day. Installed the VPN I was saving for later and everything then loaded OK. Thanks Slippa !

It seems like you don't see the little buggers soon enough. I suggest you set labels on to 'dot only/ symbol only' (whatever it is called now). I fly in VR and find this is pretty much essential for me to have any chance of surviving. The saying "lose sight, lose the fight" applies even more if you never never even see them coming.

This one works for me. Just open the window and tell the ground crew to start priming. Get Voice Attack to call up the 'Options' menu and the F8, F6 stuff. When I say: [Ground; ] [ready for start; start priming] Execute command, 'Options' (by name) (do not execute if already running and wait until it completes) Pause 0.1 seconds Press F8 key and hold for 0.1 seconds and release Pause 0.1 seconds Press F6 key and hold for 0.1 seconds and release (I also get Nigel, my navigator, to do all the switching & button pressing to actually start the engines. It's handy to have a helper)!

You have nailed it! It is designed for use on a heading that you select. It doesn't really care about the accuracy when the aircraft is pointing in other directions. Seems obvious when you put it this way.

Bugger! The RI compass is not as good as I thought it was. It has a large parallax error (about 10° on E-W headings) depending on how high your eye position is in the cockpit. Here is what the actual heading of 270° looks like - it's not the 260° the needle points to. I initially thought the needle pivot point was not concentric with the scale, and shot myself in the foot putting in a bug report about that. You can laugh at me here ... https://forum.dcs.world/topic/319007-remote-indicating-compass-needle-pivot-off-center/#comment-5149039 So it looks like we need to apply a parallax correction from zero if the needle is vertical, to about 10° if it is horizontal. Actually, I think I know why the RI has such an unusually long pointer - it is so you can also read the tail of the needle. It should be 180° off from the head of the needle. If it is not, take half the difference and that is the parallax correction needed. Apply this correction in the upwards direction from the indicated heeding. (or just think of a number between 0 and 10 and use that )

Yes. You are right and I stand corrected. It is a parallax problem with the needle so far away from the scale and not a shaft/pivot point problem. From a high viewpoint here is what appears to show 270° But down at a level viewpoint it is really 280° Here is what 270° looks like from the level viewpoint. And how we see it from the normal viewpoint. So, the RI also has errors. And I thought the P8 was the bad one! Update: I have had it explained to me by Bozon. Thank you ......... "... the correct way to use the RI is by setting the broad, manually rotating arrow to the direction you wish to keep. Then, the heading-indicating needle needs to be parallel to it - it stays parallel at all perspectives and is easy to monitor by a quick glance towards the dial. No need to read the numbers during cruise. " (So, unlike the modern compass, this one is not designed to tell you what heading the aircraft is on at all times, but to be accurate in keeping you on the one heading you have selected).

The needle pivot point is not concentric with the circular scale. It is on the vertical center line, but is some distance below the horizontal center line. The tail of the pointer needle should be 180° off the head. It is OK on the N-S axis. But will have about 10° errors on Easterly and Westerly headings. (The needle should be horizontal if indicating East or West}.

Yes. The P8 ring is set to the desired 110°M. The RI and DI has us on the correct heading, but the P8 wants us to turn about 10° to the right and stuff thing up!. Easy. Just turn it on with the 2 switches on the left and synchronize the DI to what is now showing on the RI cockpit instrument.

I have just flown that route with no problems. Forget about using the P8 compass as we have no deviation card for it. The RI compass is far more accurate and does not need corrections. Synchronize the DI to the RI and fly a heading of 110° This is what it looks like There appears to be about a 10° error on the P8 on this heading. (The AI never erected properly , but the DI worked OK) And here is our position marked on the map. I know it was only a short distance from overhead the departure airfield, but I'm sure we are on the right track (pun!) using the remote compass and not the P8.

T-V-M-D-C (True Virgins Make Dull Company) Is one of the first things you learn in flight school Navigation 101. Ger the True bearing from the map and apply the Variation to get the Magnetic Bearing. Use the wind correction triangle of velocities to calculate the magnetic heading to fly. (no wind correction in this case). To the Magnetic heading apply the Deviation correction to get the Compass heading to fly. Unfortunately, we have no idea of what the Deviation is. (Has anyone found a deviation card hidden anywhere in the cockpit?)

That is to be expected. The P8 compass is in bad position close to metal objects and electrical wiring which distort the local magnetic field. These errors are partially corrected by maintenance "compass swinging". This consists of accurately aligning the aircraft on a cardinal heading (say North) and adjusting a small N-S correcting magnet to zero that error. The aircraft is then accurately aligned South and that same correcting magnet is adjusted to remove 1/2 the current error. The procedure is also don heading East and West using the E-W correcting magnet. As you can see this does not remove, but only minimizes the errors. (This is called the "deviation" and the errors are listed, normally in 30° increments, on a nearby card, which we don't have in our Mosquito. You apply this deviation correction to what you see on the magnetic compass to get the actual magnetic heading). The remote compass sensor, on the other hand, is in a much better magnetic location and any errors are electronically eliminated so the indicator in the cockpit should be accurate on all headings and does not require a deviation card at all. /nit picking mode off /

Ever tried moving into the navigator's position in flight to set / tune a radio? This module badly needs an attitude / altitude hold function for when you move out of the pilot's seat. This has been requested many times, but I'm not holding my breath waiting for it to happen. (Nice to see that the new missions in the latest updates have scripted the navigator to set up and tune the appropriate beacons as required. Ho ray for now having a navigator! That is a lot easier and more realistic than trying to work all the radios stuff yourself while still flying the plane) Me too! The Mosquito may have its faults, but it is still my favorite.

My understanding is that the venturi type carburetor cannot draw enough fuel from the jets with the very low intake airflow at the low rpm provided by the starter. You therefore use the primer pump to inject an air temperature dependent measured amount of fuel into the intake manifold, and this vaporizes and will enable the engine to start and run briefly. This increases the rpm sufficiently for the carburetor to work properly when you select the mixture to the run position.

This also happens if you are doing a manual start and forget to get the ground crew to start priming. The engines will not start if they are not being primed. It looks like you have a communications problem to fix. If you can't talk to anybody, then the auto-start script probably can't talk to the ground crew either. Did you hear anything just after the window gets opened?

Same here. I could not find a kneeboard.dll file anywhere on my computer. I did find that the older Vaicom manual said that no download or install was required for the kneeboard, so it is probably buried somewhere inside the main program. That paragraph has been removed from the latest manual.

It looks like some new bugs come with the update. My kneeboard works OK, but the 'Options' - 'Take (n)' command is completely stuffed for me. It will sometimes show the text, but mostly just blinks on then off. If called up as a COM (\) command using the keyboard it , that works perfectly, so it does not appear to be a DCS problem. Doubtless all will be fixed sometime soon, and I must say a thank you for the work the new developers are doing to keep Vaicom alive.

I guess this is just another example of terrible British WW2 cockpit layouts. Probably in real life you would adjust that small floodlight on the left to point at the elevator trim gauge to make it visible. Unfortunately for us it fixed and set to illuminate a blank bit of cockpit wall, which makes it pretty useless. Maybe someone can find where a .lua file can be modded to adjust it?

Update: I had a better idea and added a manual trim for each axis. I have to work a bit harder flying the Mosquito now, but it was a bit like cheating to use the hat switch on the stick for a WW2 aircraft that didn't have that luxury! (A big thanks to Authentikit for their 3D print files that I modified).

Exactly. They are two entirely separate systems. Each has different advantages and disadvantages. The P8 compass does not require any power, but is in a terrible magnetic location with nearby metal objects ans varying electrical circuits. There will be a card nearby listing the corrections (the deviation) to apply to get the actual magnetic heading from what you see on the P8 compass. The remote compass requires power, but is in a much better location out on a wingtip or in the tail somewhere where any deviation errors do not vary and can be permanently corrected. Hence what you see on the indicator in the cockpit is the real magnetic heading and does not need correcting. Basically, the RI is the one to use until you get shot up and lose electrical power, then the P8 (commonly called the "standby" compass) will get you home.

It seems like the problem is that VR clips the display to a smaller area than the full screen you have in the non-VR display. It then moves that all over the place so I suspect the screen coordinates get massively altered, but the text coordinates don't. Hence a mis-match and clipping. Here is what I get with a normal fullscreen display. Everything works fine with the text now in a much lower position. Someone must have thought that was a great idea, but did not bother to check how it looks in VR!

B Be aware that all you really need is just Voice Attack to give you your desired keystrokes by a verbal command. Vaicom is a great plug-in for VA which bypasses ED's clunky comms menu and the multiple keystrokes required to do anything. For example: say " 2 attack <whatever is currently annoying you> and you get the required response without ever seeing the comms menu. All great stuff. Get them both. You won't regret it.

The best solution for that is to use PointCTL which keeps it realistic as you have to reach out to where you see the switch. The easiest fix is to use Voice Attack to actuate the switches. Death to Keyboards in VR!

Perhaps ED should take a close look at the DCS-SRS overlay. It can be moved about and also made visible or not. That one got it right for what the user wants.