frostycab

Thank you, but that does not work. All volume dials set to max with all squelch knobs in the up position. "Hear like in helmet" is also set in the options. Betty is audible, but only just. It would just be nice if she was made louder with the ability to turn her down a bit if you don't like the level, rather than OK for some and too quiet for the rest.

Just tested the ADF knob on the ground. Makes no difference to her volume for me. Whether set to min, max or anywhere in between Betty still comes out at the same volume.

How odd. I just tested the Syria cold start, and the waypoints worked exactly as expected for me. I selected Direct to WP01, and the system sequenced onto WP02 as I passed within 0.1km. I was also able to select Direct to WP02 using the bezel buttons and also by using the MPD cursor.

Thanks for that. I hadn’t noticed that types codes weren’t unique.

A pacifist in an Apache. Now there's a paradox!

I still need to try this, but from the way the flight model feels right now I suspect I'll find myself nosing down and diving for the ground in order to keep enough air moving through the rotor disc. It strikes me that autorotating to a nice slow touchdown is going to be tricky, and is going to end up requiring a fast rolling landing.

The arrows you've marked show the scale across the whole of the displayed TSD. Above this you can see the size of each of the background grid squares drawn on the display, in this case 5km. As for the map being blank, it means there is no photographic background chart suitable for displaying at that map scale. It shares this limitation with other aircraft with moving maps such as the A-10C The scale option on the left allow you to choose which of the background charts you want to use at the selected TSD scale in your case 25km. (I think!) Again, it comes down to whether or not there is a suitable photographic chart image available for that scale.

The TSD has 2 "modes" for want of a better term: NORM and ATK. NORM is the default. you can switch modes using the B1 button. At startup you won't see TG points (and some others) in NORM mode. To enable them, go to the SHOW menu at the top, and then select T5 (I can't remember the exact label right now.) You should be able to select target points on the left side. Once you have done this, exit the SHOW menu again. You should now be able to see your TG points in NORM map mode. Alternatively, you can switch to ATK mode, which hides some of the things you see in NORM mode. If you want to enable them go through the same process as you did before. Some options are under SHOW at T2 and the rest are at T5. I hope this solves your issue.

Just a thought, and I've not tested to see if affects things after you've started to move around, but it seems that the INUs have a confidence of 55m when you power up the aircraft. 55m seems like a fair degree of accuracy for an older navigation method. It's also worth noting that we don't have an indication of INU alignment in the cockpit, only position confidence, so there's no way of telling if we're "good to go" right away or if there are any detrimental effects from not allowing confidence to improve. For me personally I'd be happy to go with 55m. The GPS satellites are boxed at just under 2 minutes from power being applied to the system, with INU confidence turning green roughly 2 minutes later, with accuracy increasing to 17m. I tried leaving the whole thing alone for a further 10 minutes and confidence only improved to 14m. For the time being I don't see 55m being a problem. That's less than the width of 2 FARP landing pads, and the Apache isn't really meant for precision instrument flying. I think for now I will just regard this as another WIP item. It'll be interesting to see how it develops. EDIT: One issue I did suddenly think of was adding TSD points, as coordinate entry uses the aircraft's present position to populate the KEU field, but I guess for now we'll just have to enter the full MGRS grid manually.

"MEDIC!!!!!"

Yes, I suppose that makes sense now that I think about it. Ah, ok. In that case I would surmise that at some point in the future we may get the option to manually enter our starting location into the navigation system to account for that rather than having it auto-populate as it does now. (Of course, this may be something that is done by the ground crew when readying the aircraft, but I have no idea.) My very limited knowledge of INUs from older civil aviation aircraft also makes me wonder why GPS would be required for alignment as it certainly wasn't an option back in the days of the 707 and other such aircraft which relied purely on inertial and radio navigation.

I'm guessing that this will require the same sort of activation conditions as the hover mode in the Gazelle then.

I thought that's what the doppler was for, but admit that it's something I turn on and forget about. Out of curiosity, why are you not getting GPS signal? It's not something I've encountered yet. If you look at the bottom of the TSD-UTIL page at B1, there is a label reading NAV LAND. If you click this it changes to NAV SEA, adding alignment options at R4 and R5. However I don't believe this is functional yet.

Please no! Reading red text on a grey background is virtually impossible for a lot of people, including me.

This isn't necessarily connected to the issue at hand, but it's worth moving all your controls a little bit when first jumping into a mission. Wags mentioned this issue in his "Settling with Power" video, and showed that sometimes your axes may initially not match your physical controls. In his example he referred to cyclic and rudder, though I would guess that this could also happen with collective in some instances. Here is the link to the relevant part of the video: EDIT: I just tried to reproduce this, and although I did manage to get the start to fail it required more than just a slight input on the collective. I would estimate somewhere around 10% of the full range on my physical throttle. Definitely ensure your collective is fully zeroed at mission start and I doubt it will be an issue. Track file below. Engine start fail with collective applied.trk

Following on from this, can I ask about the behaviour of auto-ranging in the CPG seat? I just did a quick test, and while the pilot reverts to manual range each time they action the gun, it seems that the CPG remains on auto-ranging and has to use the KEU if he wants to go back to manual after re-actioning the gun from his seat. Once again, I don't know if this is correct or not, so will let you decide if it needs investigation. I have included a track file below. I used external power to get it done quick and keep it short, but the behaviour is the same with engines running and full INU alignment. CPG ranging.trk

"How will FCR work?" Witchcraft

Ah yes, I see what you mean now. Perhaps one way to get consistency across all of them would be to make the right click a toggle function instead of just a pull, freeing up the left click for a click and drag function, though I don't see it as a priority issue. Once you are aware of the behaviour it's not a problem. Thanks for responding.

The volume dials on the communications panel exhibit inconsistent behaviour. The MASTER, SENS, IFF, RLWR and ATA dials are able to be turned up and down either by using using the mouse scroll wheel or by left-clicking and dragging, whereas all the other dials on the panel only work with the click and drag method.

Cool. Thanks for the clarification.

I noticed the kneeboard errors myself when I tried. Regarding MBM, I *think* you don't need to worry about selecting the point type on the TSD, as the actual type will correct itself when you enter the type code (in this case "EU") into the KEU. I think you only need to ensure you have the correct WP/CM/HZ/TG selected on the TSD itself if dropping a point using the cursor. Please do let me know if I'm wrong about this.

A perfect, concise answer! Remember that when dropping waypoints (for any aircraft) in the ME the system likes to put them up in the air, usually around 6500ft IIRC. Dropping them down to ground level will make them much more accessible in the Apache. Also, don't forget that in addition to the homeplate symbol itself you also get a steering cue on the heading tape at the top of the IHADDS display. As for creating things like hazards and control measures, I don't think it's possible in the ME right now. Indeed, I suspect that in order for us to be able to do so would require a considerable rewrite of the ME itself. While it would be nice to have the ability to add them there, I don't see this as high priority right now. Single missions generally won't require too many points to be added from the cockpit, and I think for large-scale, theatre-wide MP missions it could prove to be a hindrance if the mission creators tried to add enough points to cover the whole battlefield. Remember, the aircraft can only store 50 WPs, 50 CMs, 50 TGs and 6 TRN points. As a small side-note, I think that mission designers maybe need to consider the time it takes to add points when starting a mission. Many missions are created in such a way that they start as soon as you enter the cockpit. While that works for many aircraft, in the Apache it can take a few minutes to get all your points set up, so missions might benefit from using trigger zones to delay the action from starting until you are actually ready to go.

Is there a volume control for the voice warning messages? I've got all the volume knobs on the com panel turned right up, but I'd like to make Bitching Betty a little louder. She's not easy to hear clearly, at least for me.

I suspected as much.

Haven't bothered to do it myself yet for George's targets, but have you checked to see if your TSD is in ATK mode rather than NAV? Unless you've gone into the SHOW settings and its subpages to edit the defaults then I don't believe TG points are displayed in NAV mode.