Hootman9104

Came to the forums because of the LST auto scan issue, glad to see it's already sorted and reported, and a workaround explained. Was doing a Liberation Campaign mission, and had to abort mission as I couldn't figure it out. I figured there was probably a switch to engage/disengage that, but didn't find it. Great community as always.

So this may seem like a stupid question. I retired back in 2005 as a 15T (formerly 67T and 66T, O.G. Blackhawk type). The more modern APR-39 I guess I'm not familiar with, and I don't know what changes it's gone through. Flying the H-60 mod, occasionally there is an automated message that repeats over and over and over, I'm assuming it's the APR-39 trying to tell me something. Sounds like "auto chemo thrust" in a digital voice. I know that's not what it is, so what is it, and what is it telling me? I'm ASSUMING it's the APR-39. If not, what system is it, and what is it saying?

I just did some testing with and without weapons, there was no difference between the two. If you apply very slow collective, the aircraft will begin a right roll. If you don't push the cyclic a touch left, it will roll over. If you apply very slow collective, and use a very small touch left cyclic, the aircraft comes right on up. If you apply medium or fast collective, the aircraft pretty much pops straight up either with or without left cyclic. Basically what you are encountering is "dynamic rollover", because for whatever reason the aircraft rotor appears to be getting just a tad more lift on the left "retreating" side, and since the right wheel is still on the ground, it's pivoting on that wheel. If you raise it ever so slowly you can see and feel it rotate. I think most people don't notice this because they apply collective a little faster, or just automatically feel it and just barely tap the cyclic left. bottom line, once that wheel is off the ground, the aircraft is then "swinging" under the pendulum of the rotor, and your are automatically adjusting at that point. Whether it should do that, not sure, it may require just a minor tweak in the flight model, but the bottom line is, you aren't reacting correctly. So either tap the cyclic left as you should see it starting to rotate, or get a little quicker on the collective. I personally think a little tweak is in order, as the rotor (in theory) should be applying equal lift on both the advancing and reatreating sides of the blades. But even if they don't tweak it, there is really nothing wrong. Just commit to takeoff, don't dawdle around there, the issue is it's going into dynamic rollover by pivoting on the right wheel, and you are not reacting to it... In my 20 years we had one dynamic rollover, and that was in the desert in a brownout condition, the pilot didn't detect a slight drift to the left as he was setting it down, and the aircraft rolled over when the gear touched the ground. That's about the only situation you should ever have a dynamic rollover.

Here is a screen grab from a GoPro. It's hard to tell, and I don't know much about GoPro mounting, I think maybe it's on top of the helmet, based on the elevation above the boresight tube. Or, after boresight, maybe they elevate their seat for better visibility. But it would still show in general how close he is to the instrument panel. I think you are asking how close to the instrument panel you would be, and this is a somewhat fair representation.

I use VA in a several games, and have found that it runs totally seperate from the games with no effect on or from the game. In other words, I can start it before and after starting DCS, incuding re-starting it while in DCS. HOWEVER, if VA is using a Plugin, there may be instances when it doesn't operate properly if there is a plugin being utilized, for instance for DCS if you are using VIACOM-PRO plugin, it may act up. Every now and again, VA with VIACOM-PRO will stop functioning IF I start it prior to launching DCS, sometimes it will stop working once i load DCS, even the automatic restart that's part of VIACOM-PRO won't work, and I have to alt-tab out and restart VA. But starting VA with VIACOM-PRO after getting into DCS (alt-tab) works fine. If you are running VA with NO plug ins at all, nothing should be affected one way or the other, because all VA is doing is pressing keys based on your voice. It doesn't know what game you are running, and you should be able to start it before, or after you get into DCS. VA should not care where you are, it's just pressing keys based on your commands. So check if you are using any kind of plugins in VA. If so, try unchecking/disabling them in VA, and try it again, without the plugin. Bottom line, I can't think of any reason for VA to be acting up IF you are not using a plugin in VA that interacts with DCS.

Actually I just flew again and now it's working again...strange though, when it did it, it did it twice in a row and I had never seen it. All seems good for now.

Just started testing the new MT, gained about 10-15 in VR, but noticed what may be an issue with Viacom PRO. The comms menu (F10 I think) appears to open and close on it's own about every 5 seconds using the beta MT executable. Going to keep checking, but is anyone else noticing this?

Oh I understand torque, I did 20 years Army Aviation (UH-60). Just not a fan of how the system represents the collective action with the throttle. Other sims, like EECH, have a nice linear progression, it's not jumpy or sensitive at all.

Anybody else created a VA profile for the Apache? How creative have you gotten with it? I created mine last year, and have almost every keystroke in there, still working on occasion to add special commands. I pretty much built it to match the DCS control pattern template for the categories, and the remaining things to be done are mostly commands for adjusting the various knobs for the lighting and volumes. Those are a bit tedious as the commands I create adjust the knobs up and down in small increments, and each one is (of course) different, and has to be tested as I build it to see how many seconds (or increments of seconds) it takes to move the knob 10%. Also building small scripts of multiple commands, for instance "Night flight", which goes through adjusting all the lighting knobs and setting the MPD's with one commands, and providing verbal responses as each setting is adjusted. Also have mutli-command scripts to set the aircraft for NOE flight, jettison the stores, start and stop OBS, things like that. Also set commands for every letter of the alphabet and number keys for setting things like frequencies. Probably the most difficult thing was the couple of days of figuring out how I wanted to manipulate the MPD's, solved that by using a naming convention for the screens and buttons. I plan on creating commands to store targets and waypoints when I have time. VA is great, I never take my hands off the HOTAS

Just wondering what others have it set at. Since day 1 I've never been happy with the way my collective works, the percentages jump around as you begin to pull collective, then settles down as your push past 25% or so. Also has never seemed correct, way too sensitive in the midrange, and it feels as if there isn't a smooth percentage torque increase through the full travel. So I think I've finally got it set where I like it, using a curve of 25. This seems to make the collective nice and responsive from about the 1/4-3/4 range of my HOTAS throttle, which equates to about the 30% to 100% torque (again, on my throttle) in that middle range of the throttle travel. It's now very nice, not sensitive at all and very smooth transitions from 30% to 100%, easy to fine tune and maintain a hover. Of course if for some crazy reason you reach the upper end of that curve, it does advance way too much, but if I'm flying correctly to begin with, I shouldn't be in that position anyway. So just wondering what others have their collective control settings at? The 25% curve seems best to me, with X and Y at 100% (I've tried setting the Y here and there, but kinda feel like that needs to stay at 100%). Also, does anyone have a HOTAS where the throttle has a "100%" notch (detectable as you throttle up), and then past the notch is considered "afterburner" (I had a HOTAS once that had that, can't remember what type it was). If so, does the 100% throttle notch correlate to 100% torque in the Apache, and is past the torque past 100%.

I don't think it's a "bugged" feature, I think it's just an implementation of a feature to be expanded on in the future. Maybe they're trying to figure out if it should be assigned per livery (82nd patch for 82nd livery, etc.) or a a selection in the settings where things like the monocle is. I think that's where it should be, as the right shoulder combat patch stays with you as you move around the U.S. Army. That's IF they make a selectable feature at all. Maybe it's just eye candy and not meant to be a selectable feature. Very early in my career I was a 'Hawk crewchief in A Company (Redhawks), 2nd Battalion (Assault), 82nd Aviation Brigade when the Brigade was created. The 1st Battalion (Attack), 82nd Aviation Brigade, spent their first year assigned to Fort Hood learning their shiny new AH-64 Apaches. I'm not a fan of flying the 82nd livery with that "Puking Buzzard" (as we in the 82nd refer to them in brotherly jest) on my shoulder but again, just eye candy.

Hmmmm..I did find an issue with OpenComposite in EliteDangerous, I was using a third party tool to change all the cockpit colors, and it did not like that, crashed on startup. I am not sure what that had to do with anything, it's just a color change, but taking that out and it launched fine. Are you using any third party mods or anything other than trying to launch a clean version of DCS in Steam (other than the executable --force_OpenXR, I have that in the command line and it works fine with that)

If you use Opencomposite, it's executable has a button, to use Opencomposite with OpenXR, or use SteamVR. That's litterally about the only interface it has. Or, you just start SteamVR and it reverts back to it automatically, and if you want to use OpenComposite again you just click the Opencomposite executable and enable it again instead of SteamVR When using Opencomposite, SteamVR is bypassed totally, not used at all. You use the openXR toolkit in your games once you get in there instead of the settings in Steamvr. But like I said, it takes 5 seconds to switch between SteamVR and Opencomposite And I've not had an issue with using Turbo mode in IL2, DCS, or Elite Dangerous. I'm not sure I still have it turned on, I really couldn't see the difference with it.

I have thE Reverb G2, the "jelly" is probably coming from reprojection. Follow that guide here on the forums, ensure you are running OpenXR Tools for Windows Mixed Reality, Open XR Toolkit, and Opencomposite runtime. Follow the guide in this post It's not that hard, just read it as you go along. Basically you will find ensuring motion reprojection is OFF is your best bet, in both the OpenXR Tools and the ingame overlay settings for OpenXR toolkit. This combination is absolutely FANTASTIC, and makes the world of difference. The OpenXR toolkit overlay in game is the bread and butter, that is where you have so many options, you can fine tune and get a GREAT framerate and smoothness. Basically it reads my Reverb G2 as a base resolution of 3092, and it can run like that smoothly (for me at least). The only thing draggin my system that was bumming me out was the Liberation Campaign tool, but following guidance to open my own MP server to join, and utilizing the three tools/runtimes in the post, and now I can run Liberation at great settings, having a blast. TRUST ME, IT'S WORTH THE TIME AND EFFORT TO SET THIS UP! Also, I have found that in the Windows Mixed Reality settings, setting the headset to 60 HZ, and not 90 HZ, seems to help. Also, I am frame limiting to 50 FPS using the The OpenXR toolkit overlay settings. Another thing in the The OpenXR toolkit is you can set up a little overlay that displays your FPS, GPU and CPU times, and how much GPU Vram you are using. That can be used while you are changing the settings to fine tune the The OpenXR toolkit settings to get your sweetspot

It actually started working in full screen again. Not sure what goes on with that. Since everyone is talking real NVG's, back in the day I started my Army Aviation career in the 82nd Airborne, with the 1/17th Cav when we had UH-60, AH-1, and OH-58A in each Troop. The UH-60 was still the "new guy" on the block. Those were the days when Army Aviation was a new branch, and Reagan's buildup was in full effect. We started out with basically full face goggles like a VR headset, and then moved to the goggles strapped on with velcro on the front visor and lead weights on the back of the helmet. Really wore your head and neck out, and hotspots were a constant aggravation. In '86, Sikorsky started bringing the new H-60's with the greenish/blue NVG lighting in the cockpit and cabin, and modification teams came around to all the bases and modified the pre-nvg aircraft from red instrument and cabin lighting to the blue/green lighting. When we had the red lighting, we also had to use the ol' green duct tape to tape up the "vids" on the panel (the little chicklet lighting for engines, torque, etc.), we taped them to only show green, as the yellow and red were extremely bright. So basically under goggles only the green vids showed, and if you had no green vids, well.... Before I left the 82nd, the "Army of Excellence" occurred, the Cav got rid of the Blackhawks and I found a job over in the 82nd Combat Aviation Battalion, which had their UH-60's on Pope AFB. Then the 82nd Aviation Brigade was created, with 1st Battalion (AH-64) and 2nd Battalion (UH-60) Did about a year at Pope, and then we moved over to the brand new hangars at Simmons Airfield, new hangars designed specifically for AH-64 and UH-60. We also got brand new aircraft around the time, like the smell of a new car During that time the 1st Battalion spent a year at Ford Hood with their shiny new Apache's learning how to fly and maintain them. That was a 12 month PCS for those Troopers, and there were some very disgruntled folks, and I think after a month they started arranging USAF and Navy flights between Hood and Bragg every weekend so people could go be with their families back at Bragg. I ended up leaving in '88, for my re-enlistment, I wanted someplace like Hawaii or maybe Fort Eustis or Rucker as an instructor for a while, but all they offered me was guaranteed to continue at Fort Bragg, or I was going to Korea for a year, and then coming back to Bragg. Back then that was a hardship tour in Korea, no family allowed. So I took my third option, getting out and joining the Virginia Army National Guard, which had began fielding UH-60's to replace their UH-1. Imagine my horror when I first walked on the flightline and saw the UH-60's they got were the ones turned in at Fort Bragg when we got new aircraft there. Virginia even had my very first aircraft I crewed in the 1/17th Cav, 80-23464. After a month I was offered a full time slot at the Army Aviation Support Facility in Richmond, Virginia, where I worked from 1988 until I retired in 2004. I got see see a lot of changes in Army Aviation during my years, night flying and the technology being one of them. People take a lot of the nifty equipment for granted these days, but those fairly early days with crappy goggles and not so great tactics made for some scary flights. Going inadvertent IMC under goggles, and then having another aircraft fly right underneath you about 30 feet away when you came out of the clouds is an "oh sh.." moment you can't forget.

Just a question.... Before when switching to NVG's, I had a nice full screen NVG view. Not really realistic, but nice nonetheless. I went and flew the UH-1 for a bit doing a night mission, and it had the NVG circle like looking out of the ANVIS goggles. Then when I flew the Apache again, the full screen NVG view was gone, and it was using the round circle ANVIS view. I realize the full NVG view is not realistic, but is there a setting that changes that back and forth? Looked all through the settings and couldn't find it.

I should probably go to their Discord, but thought I'd try here first. Having an issue with DCS Liberation generating AH-64 missions. I have followed the setup, so I have ensured that AH-64 is available, there are player slots assigned, etc. For some of the maps, like Caucuses, it won't generate AH-64 missions. There is one Syria campaign that mentions heavy helicopter use, and it does generate missions, and I have flown them. For some reason though, in other areas like the Caucases, it doesn't seem to generate missions for the Apache, not even AI missions. I even went through about 20 turns, but it never happens. Again, It works on one of the Syria maps, so I'm pretty sure I'm doing it right. The aircraft are available at the base, and Player slots are assigned to the squadron. It just isn't generating any missions. Do I just need to keep advancing the turns until it eventually happens? Any help appreciated "Hoot" Baker

In a helcopter what is the primary situation requiring reduction in power from the engines to the rotor system? To counteract a spin caused by a tail rotor malfunction. Summarizing, I think it's chapter 9 of the -10, "Tail Rotor Fixed Pitch Malfunction - In-Ground Effect" "A fixed pitch failure may be evidenced by slow, intermittent, or no response to pedal input or no pedal movement. A left or right yaw may be apparent." "If a failure occurs during in ground- effect hover, reaction may vary from adjusting collective and POWER levers during a left rotation to activating the CHOP button to stop a right rotation. In any case, the primary concern should be to land the aircraft with as little yaw rate as possible." "If the aircraft has an uncontrolled turn to the right, reduce collective to begin descent. At approximately 5 to 10 ft AGL, perform a hovering autorotation by CHOP button - Press or POWER levers - OFF" Power levers-OFF is generally not going to be an option, because where are your hands and what are they doing? No time to tell the front seater to pull the PCL's off. Thus the CHOP on the collective, where your hand is. Hoot-U.S. Army Aviation, Retired