Floyd1212

This is assuming only friendlies are enabled for the F10 map? You can always have George search for them. His eagle eyes are a little over-powered, but it works. If you don't want him to actually engage the enemy for you, use him to find the enemies, then mark enemy positions with user marks on the F10 map, then come back to them later. (It would be nice if he would actually lase and store, but that functionality isn't in the module yet.) You can enable Fog of War for the mission, then use Cockpit Recon Mode to spot them yourself and only the ones you have spotted will show on the F10 map. Does Liberation have support options for JTAC drones, or popping smoke on enemy positions in the zones? The Foothold missions have this and it makes them quite playable solo. If you are trying to avoid any of those "assists" mentioned above, it's all about scanning the battle space with a combination of TV and FLIR to find them. I don't know if Liberation places units is completely random, and you are looking for units in the trees and in the middle of towns/cities? If so, you might be better off flying something where you know the units are at least going to be located in the clearings. Also, I'm not sure if it is setup to keep the enemy units in a "red" alarm state, to keep their engines running, and thus more visible on FLIR?

Are you guys using Snap Views for this kind of thing? You can setup a camera position and save it to a Snap View "slot" that can be activated for the duration of a button press, then when you release the button, it goes back to the default view. This works well with a hat switch on your HOTAS so that you can hold LEFT on the hat to snap to a view of the left MPD and grip, then manipulate the cockpit buttons with the mouse, then release the hat. Maybe holding the hat DOWN snaps to the KDU for keyboard input, then release. Even with head tracking this is quite handy, as the snap view does not wander with your head, so the buttons you are aiming for with the mouse aren't drifting around while you try to click them.

I just hopped in to check it out in external view, and there is a slight coning effect of the rotor system when pulling pitch while still on the ground, but I'm still skeptical that the Coriolis effect on the rotor system exceeds the drag on the blades and causes them to over-speed. Maybe I am underestimating the Coriolis effect in my mental analysis of these forces in my head, but we aren't talking about a figure skater tucking their arms and legs in tight to their body, we are talking bout raising the tips of their outstretched arms by 2 inches. How much over-speed is necessary to induce the warning?

Is that a lot of work, or just re-saving what you have done differently in some way? It works fine to manually change the scale back to one of the two you have done already. If there was an easy way to force all the zoom levels to use one of your two versions, that would work.

Thanks for this great mod! I do have a question, though: When flying the Apache, zooming in and out will change the charts to different a different scale, which reverts back to the standard charts. Is there a way to prevent this from happening, or maybe rename/copy your charts into all the other folders?

Not that it helps you much to complete those missions you mention above, but this is where buddy lasing can be very helpful. A drone in the sky, or JTAC on the ground, or another Apache, or (in the future) the Kiowa can all help you get the job done from a safe position. For the mission with the mountain cover, I would use an LOAL trajectory from behind the mountain, and then pop up at the right time to lase the target but not stay exposed the entire time. You can also go for the SA-11's search radar and take it out, but the launchers can still track targets autonomously, if they are already pointing in the right direction.

You may not have read the entire thread to fully understand the conversation, but the OP was looking to eliminate some of the information on the IHADSS display, not all of it.

There have been discussions in other threads about how unstable the aircraft is when side-slipping at high speed, especially when combined with aggressive pedal inputs. Any chance you were doing something crazy trying to avoid an incoming missile? That's when it seems to happen to me at least.

nullA screenshot of what you are seeing on the IHADSS and your TSD page when this happens would be helpful. Like mentioned above, you want to make sure the Acquisition Source is set to TADS in order to see where the CPG is currently pointing the laser. If the TADS is looking 90 degrees off to the right, you won't see the dashed reticle unless you look off to the right for it. The little dots around the LOS reticle will tell you where to look for it in relation to your current head position.

It seems to happen when quickly pulling pitch from 0 to just to the point where you go light on wheels, and then stop.

Enabling LMC before making the position adjustment often helps. This lets you make small adjustments without having to manually track the target while moving again.

While tracking the target, move the TADS cross-hairs to a different position on the unit and press IAT Fwd again. It's the same procedure like you are adding a track to a new vehicle, but if you are already tracking that vehicle, it updates the position.

You are probably hearing "RPM Low". This happens when you are too aggressive on the collective, and pull too much pitch all at once. When you yank on the collective, the pitch of the main rotor blades change suddenly and there is a lot of resistance on the blades as they push through the air. This causes the rotor system to slow down and you get the "RPM Low" warning. The opposite will occur if you are flying along and all of a sudden drop the collective to the floor. The rotor system will have little resistance as they blades easily slice through the air and you will get "RPM High" warning. Bottom line: make gentle adjustments on the collective, especially when lifting off the ground to a hover.

If employing a real bug-tracking solution is off the table, perhaps using the "forum tracking" method more effectively could help? Create a sub-forum for bug reporting, and move the posts to another sub-forum when they have been accepted by the devs, then move them to another sub-forum when they have been resolved. This means there are shorter lists of posts in the reported and accepted forums for users to look through and understand what has already been reported and being worked on. Don't let just anyone post a bug report. You've got a nice readme pinned to the top of the forum, but apparently not very many people are reading it. Allow users to submit their reports for a moderator to approve before being posted. If it doesn't contain a comprehensive screenshot, a video, or a track file, don't accept the post. Ask the community to help confirm the bug by reproducing the bug with the included track file on their hardware before moving it on to the devs to look at. This is all just brainstorming for 5 minutes while I write this, but you get the idea. The bug reporting system in place right now is not working for the community, and probably not working very well for the devs, either. If nothing else, realize that you have community members that are taking the time to create concise bug reports with steps for reproducing the issue, and including the requested track files. At a minimum, come up with a reliable method for seeing them, downloading and viewing the track files, and processing the reports that are generated.

Going up against SAMs is one of my favorite things to do; much more exciting than plinking targets out at 8 km that don't even shoot back. For a particularly nasty SAM, LOAL is the way to go. You can use George in "No Weapon" mode to track the target from behind cover without lasing, launch your LOAL missile, then unmask and tell George to flip on the laser. Takes a little practice, but very rewarding when that Tunguska never even saw it coming. FCR is going to make this almost too easy...

https://forum.dcs.world/topic/312011-atgm-hit-destroyed-tail-but-anti-torque-rotor-still-active/

Today is your lucky day. Check the patch notes for the patch released 2 minutes ago...

As someone who makes large missions for my group of friends to fly, having the default to hidden on MFD, and the option to show the few units I may want to reveal would make a huge difference.

There are a couple things going on here... If you perform a "trim reset" while in forward flight, you can expect the nose to come up abruptly. You need to anticipate this and quickly move the controls to the previously trimmed location to counter this, or only use the trim reset function when the virtual controls are near their center already, i.e. when in a hover, and not in full forward flight. I posted a video in this thread on how to use Joystick Gremlin to avoid this problem when using Trim Reset. New-comers to the Apache might find it useful. I haven't heard of others experiencing the issue with the axis being ignored like you are describing. If you are using Central Position Trim Mode, is it possible you have some forward "drift" in your stick, and it is never registering as having been centered in the y-axis after applying the trim? You can try a slight deadzone to see if that does the trick. Your issue with the AT hold not working in a hover may also be because if drift in your joystick. The Attitude Hold is currently very "weak" compared to previous patches (like when Wags created that video), and it doesn't take much input from the controls to get the aircraft to override the hold and start to move out of position. Here is another recent thread that discusses that issue.

I do not have VR, so I have not tried myself, but I have read elsewhere that it does not work in VR.

The brightness of the exports has been an issue for a very long time, and is a problem with the core, not just the module. There are some threads about how to use ReShade to increase the gamma only on the exported areas, but you still have to crank the in-cockpit brightness to get anything workable on the external displays at night. lol, Apparently I already said that in the first page of this thread... Sorry.

Page 112 of said manual describes the FMC channels, and the UTIL page is where you can enable/disable each if you like.

There are two types of "misses"; both are annoying in their own way. Sometimes the laser is on the target the entire time, or at least for the last several seconds of guidance, but the missile still goes long/short, or falls behind a moving target. This is annoying because you feel that you (and George) have done everything correctly, but some mysterious glitch in the core engine is preventing the missile from hitting the target. Often times I will try a second shot, and the exact same miss occurs. This happens to me when I am in the CPG seat, too, so I don't fault George for these. Other times, George seems to wander off target and the missile ends up missing the target, but does hit where George happens to be lasing at the last moment. He seems to do better at close range, where the target is so big that when he drifts slightly the laser still stays on the target, and then further out around 7km where there is enough time for the aircraft to settle again after the launch, and George can get the laser back on target before impact. I'm sure we will see some improvements to both of these scenarios in the future.

This does sound useful. I typically use the SAT map as it shows the most detail, but I would switch to the DIG map if these features were displayed.

If you would like to make a video to drop some knowledge bomb on all of us, go right ahead. I think the official stance from ED is that this is currently an over-exaggerated behavior that will be toned down as the FM is refined.