Caldera

OK... I had been trying to learn High and Low trajectory missile launches. To my understanding, to do for example a High trajectory launch, the missile is fired at a "spot" then at 12 seconds TOF remaining the laser is turned on. In the above case the spot was T03. While doing that, I noticed that I had no TOF indication for any of my High trajectory launches. So I switched the trajectory back to Direct to test to see if it was working correctly, as I had not paid much attention to the actual time on the counter. TOF was indicating for Direct, but I noticed that the time was way off. I never got around to testing Low trajectory launches. My apologies, the pictures maybe a bit confusing: Direct at launch = Direct trajectory launch just after the missile left the rail TOF at launch = 34sec The range at launch = 5921m Direct at impact = The same missile as above just after the missile hit the target TOF at impact = 14sec TOF at impact should be ~ 0sec TOF continued to count to zero after impact actual TOF was 20sec High at launch = High trajectory launch just after the missile left the rail launched missile at T03 with laser off no TOF indication visible no way to know when to turn on the laser By coincidence the picture of the High trajectory launch just happened to be my last Hellfire. But, the missile was still in the air and the TOF should be visible. I had thought this would be true for any missile in flight, but I guess this might be a bug. The rocket motor probably still burning when the picture was taken. The missile eventually landed some where off in Nah-Nah Land (as did all the rest). I had be turning on the laser at various times for other High trajectory shots, but I was never successful at getting a hit on target. I have not learned yet what the HE or HF terminology indicates, so yet more confusion on my part. I must be not correctly launching to a spot on High trajectory, in this case to T03? Caldera

Hey All, I few pictures, please take a look. RPM is in the green at 101% sitting on the ground with no movement. No collective no pedal: No collective full right pedal: No collective full left pedal: Why is the torque value changing? Caldera Just noticed, why is the Trim Ball Moving? Caldera

Can't?

Raptor, OK, Thank You! I would have never thought about: I find it amazing that the FC computer can do this. Yet, can not indicate by the Trim Ball when the aircraft is flying in a skid or true to the direction of flight indicated by the FPV. There must be just too many variables in the mix due to the fact that the aircraft is a helicopter (not a dart) and inherently wants to always fly a bit sideways. 86 KNOTS 99 KNOTS 144 KNOTS Speed has a major effect. Caldera

Hey All, My TOF is really wacked. I must be doing something incorrect. It is not showing at all for High Trajectory missiles shots. Direct at launch: Direct at impact: High at launch: Anyone clue me in? Caldera

Shagrat, Thanks! OK... One thing that I do notice is that for firing rockets using the best aiming solution, something seems a little off. I had thought that aligning the Rocket Steering Que, the HMD cross hairs and the Head Tracker would give the best results. This is not what happens, at least most of the time that do it. With the Rocket Steering Que and the HMD Cross Hairs in alignment the Head Tracker will generally be to the left a small amount. The rockets will hit the ground on the Rocket Steering Que / HMD Cross Hairs line and not the Head Tracker line. (I hope that makes sense) Wouldn't the rockets would always shoot directly down the bore of the aircraft IE the down the line of the Head Tracker? To be most accurate it seems that I need to be in a skid by just a small amount. Not this: Why would that be? Caldera

Shagrat / Squirrel, I believe what you write! Interesting topic for me, and not really all that important, because it is what it just is. What I think I know... The RL Trim Ball indication uses a gyro system as a reference instrument? (Not a bubble or a gravity detection instrument) A gyro (usually in two planes of rotation IE two gyros at 90 degrees) can detect any movement or directional vector of motion that is out of its plane of rotation. This results in gyroscopic progression within the cage. Gyroscopic progression is the result of relative change in position between the gyro (movable) and its cage (fixed). This produces an error signal. The error signal often is used to re-align the gyro within its cage (due to the mechanical restraints of the gymbal) and is used for other control functions and indications. Because the cage and the aircraft are mechanically fixed to each other the cage is essentially the aircraft itself. So the magnitude of the error signal is more or less proportional to the magnitude of the relative angle for the out of plane position of the aircraft. Gyroscopic instrumentation can be pretty precise? Indications derived from the error signal could be an Artificial Horizon Indicator, a Vertical Speed Indicator or a Trim Ball Indicator (True Air Speed?). If the aircraft is level, not changing altitude or not skidding then the gyro is not producing an error signal (discounting that the earth is round). So, if the Trim Ball is centered then the aircraft is moving in the same plane as the gyro. If the Trim Ball is not centered then the aircraft and the gyro are not in the same plane. All that said, it is not a perfect world, there would be inaccuracies and it might not be as simple as what I would think. I can only guess. But the FPV is the result of a calculated value for all of the above and quite a bit more data. But I would also guess, that the root of those calculations in based upon a reference provided by the gyro. Caldera

Thanks for all the replies! In some respects, maybe because of Early Access, I still think this is not exactly right. I get the way a helicopter flies for the most part, but to my mind by centering the Trim Ball it should fly straight to the FPV and not crab. Otherwise, a skid / crab would always be indicated on the Trim Ball. It is a catch 22. Currently it is off by noticeable amount. And, maybe I am just a rock head... Could it be the Trim Ball indication that is not quite correct? Quick Start Manual page 112: FMC Controls. Toggles individual FMC SCAS axes/modes: • PITCH. The SCAS will dampen longitudinal (pitch) rates and can command longitudinal cyclic in command mode. • ROLL. The SCAS will dampen lateral (roll) rates and can command lateral cyclic in command mode. • YAW. The SCAS will dampen directional (yaw) rates and provide heading hold and turn coordination. <--- This • COLL. The SCAS can command collective application in command mode. • TRIM. Toggles the force trim magnetic brakes on the cyclic and pedals. • NOE/A. Activates FMC nap of earth/approach mode. In NOE/approach mode, the horizontal stabilator is commanded to 25° trailing edge down when airspeed is below 80 knots. This provides better over-the-nose visibility for low-altitude flying. The above is in the game? I had thought that the AH-64D SCAS was similar to SAS in the A-10C. True or False? For example, I wish your opinion on two different methods to make a right turn. To make a high speed hard right turn and I want the FPV to lead the Head Tracker through the turn (nose of the aircraft). When starting the bank I must initially first push the left pedal pretty hard. By doing this, the FPV will move to the right of the Head Tracker. Then I must add right pedal to further coordinate the turn. Otherwise, the FPV seems to stay out of the IHADSS on the left and I am guessing results in a slower rate of turn. For this turn, I want to the nose to be on target when I come out of the turn with allot of forward air speed so I need to maintain more coordinated flight. For a spinning / sliding right turn (rotation) this is not a factor, where I might simply slam the right peddle to the floor. For this turn the forward air speed is consumed by the maneuver. The FPV is way to the left and out of vision. The dynamics are way different. Sound correct? I know that I am probably over thinking the whole thing and maybe jumping too soon. But as I said earlier, just a topic for discussion that I am enjoying to read and respond. Caldera

Hey All, How do you get the KC-135 to turn on its lights for night time AAR? Seems impossible to find, even with NVS in use. Caldera

Thanks Guys, I guess my problem is that I do know that helicopters will crab (Skid), but the indications (as in theory, don't lie) confuse me as to what I am seeing. Again, I am considering Early Access and just wondering for point of discussion. My only other experience is the DCS Huey and it has no FPV. Quick Start Manual: Slip/Skid. The bottom scale of this symbol indicates horizontal acceleration. This clearly says "horizontal acceleration" so does that mean that the Trim Ball will not detect a horizontal movement if that movement is at a constant speed? The cockpit instrumentation clearly shows otherwise and to me simply indicates a skidding condition. If the aircraft is in trim and the horizontal movement is sideways, as indicated by the FPV, isn't that a skid? If the Trim Ball is centered this should mean that the aircraft is in trim. In fact, that is what the Quick Start Manual says. Where Trim Ball" is mentioned 16 times. Nines times it references "trim ball centered" and four times it references "center the trim ball". This is true for many flight conditions including landing, take-off and firing rockets (straight flight). I would agree to that except the FPV can be way off from the trimmed intentional direction of flight and essentially requires a banked turn at all times. To align the FPV with the intended direction of level flight, requires the Trim Ball to be not centered. Um? No... Quick Start Manual: It is important to note that the most accurate rocket employment with forward airspeed results when the aircraft is kept within coordinated flight with the trim ball centered. Pages 282-285 Um? No... Does the Head Tracker indicate aircraft center line, like a bore sight? Maybe I should just press the easy button... Caldera

Hey All, OK... Keeping in mind that I realize that the DCS AH-64D is still in early access, but I am trying to make the mental jump to the "Real McCoy" and how it would fly. I am talking about alignment between the FPV, the Trim Ball and the Head Tracker. There just doesn't seem to be much: If I fly straight --> With the Trim Ball centered and aligned with the Head Tracker --> The FPV is way off usually to the right. If I fly straight --> With the FPV centered and aligned with the Head Tracker --> The Trim ball is way off usually to the left. Shouldn't at some point all three of those flight assistance markers be in alignment, say hypothetically the aircraft is flying in perfect trim in the direction of travel. So this boggles my brain, as I can not quite think my way through it. Especially when the FPV is off to the right with the Trim Ball Centered. In my mind, there has to be a skid occurring for that to be true. The Trim Ball is a gyroscopic measurement if I am correct, and I had thought that this should indicate alignment between the aircraft direction and its path movement vector through space. I generally have been aligning the FPV with the Head Tracker, damn the Trim Ball, and getting better results. I was wondering how the rest of you deal with it? Thanks in advance, Caldera

To think... I might have found what I am looking for. Bunny Clark strikes again! Caldera

Hey all, I am talking about my original topic where the pilots seat MFD's will not show up on the second monitor. Currently, only the MFD's for the CPG's seat will be placed there. They look very nice, but go static when I switch back the pilot's seat. This is my monitor set-up: The top monitor is at 2560x1080 and the bottom one is at 1366x768 (13 inch monitor). This set-up works very well for placing the MFD's on the lower monitor (example A-10C). As I stated above, my vision is not the best so this really helps me out allot. I have attached my lua config file, where LEFT_MFCD and RIGHT_MFCD make the calls to the viewports for the CPG seat. I guess that I would be looking for the the calls to the pilot's seat. Would anyone have happened to figure them out or know what they are? Thanks in advance, Caldera CENTER+MFDs.lua

XC, I am not going to disagree with you. However, before this patch it was positively awful. It is much more usable now. Jay, This is always room for improvement. At least the cross hairs are visible. And I am not dinking with it every mission just to be able to see them. Caldera

Tholo, Thanks! Caldera

Some1, Thanks! I have been cold starting for practice. Caldera

Hey all, With 2.7.11.21408.1 I can no longer get auto ranging to work. I can set different ranges in manual and that seems to work as it did before. Is it just me or a glitch? Caldera

Hey all, I noticed that with 2.7.11.21408.1 the elevation indication(s) got changed. The only time I can see it is when I am using the display that shows the pitch ladders. How do I to set it up so that I can see them in other displays? Caldera

Hey all, With 2.7.11.21408.1 we now have trim reset and I like it allot. I am wondering about some new symbology on the controls indication. These are green lines and a green cross that sort of overlays the control diamonds at the center position, but out reach the diamonds when I move the controls. What are the green lines and the green cross trying to tell me? Caldera

2.7.11.21408.1 TGP is Good! Caldera

Jay, Yeah thanks! I did think of doing that, but I would only need those adjustments for a very small part of the game. While, my TrackIR settings work fairly well for everything else. I have the camera up/down adjustment mapped to my throttle and I have become proficient at alignment. For now it is working. Caldera

Hey All, I am probably using the wrong term, my apologies. To me FPM = Flight Path Marker or TVV = Total Velocity Vector is how I know it to be called. Anyways, I am getting better at flight in the AH-64D so I have more time to notice stuff. My biggest improvement was turning off Pitch and Cyclic force trim. I do use force trim for the Rudder (thrust) and I am noticing something a bit weird. The FPM is always hanging out to the right, For right turns it will sort of align to the boresight, but for left turns and most other times it is way off to the right. Please take a look a the picture. This was a fairly difficult screen shot to get and hence the reason it seems a bit twisted due to my body contorting to press the PRTSC key. What would I be doing wrong? Thanks in advance, Caldera

Hey All, I got it! My problem was my head position. I simply can't crouch low enough in my chair to get alignment using the default head position. I ended up having to move my head position down using the cockpit camera, about seven clicks (RCTRL RSHIFT NUM 2) and that seemed pretty close. Which seems strange to me as the default head position doesn't work, but that is what it is. I noticed that allot depends on the TrackIR variables I am using, I use minimal Y and Z. I may edit the LUA file in the future when Open Access is over to get it closer more of the time. Thanks to all, Caldera

Jay, Believe me I tried, the picture I show is the only position that the circles become concentric. Caldera

Jstnj, With everything going on in the world right now, especially the Russian hostility, I am surprised that we get updates at all. FWIW I believe that the same ViewPort more or less is used across many aircraft as I read that the F-16C and F/A-18 have common issues with the A-10C. Caldera