Hootman9104

TBH I'm not sure I had noticed there was a manual slew on the H-64 like the H-60, but the 60 it's a manual switch on the stab control panel on the lower console (the pinky switch for emergencies). I just didn't notice it on the collective nor would I have thought to look for it there. If it existed I think I assumed it would be a panel switch. Learn something new every day. I'll look at setting that on my HOTAS and giving it a go. Not sure how I missed that doing all my programming of the HOTAS. And yes SunDown, it can be handy, but listening to Raptor kinda sounds like it was a take it or leave it method based on each pilots given preference. I do find taking the stab out of auto operating slow on top of the trees to be beneficial in my case. And I can certainly understand people not wanting to fiddle with it. As noted with the issues with the 60's we had in the 80's, we got pretty scared for a while flying low level at speed. When the fix was the DynCorp teams coming around putting the pinky switches in to release us from the 80 knot restriction, we kind of looked at it and said "that's it?". I can't remember how long it took to actually do the mods with improved Stab Amps in the aft cabin and the shielded wiring, but it wasn't overnight, that much I recall.

So this seems to be DCS Liberation focused, but I thought I would post here to see if there is something maybe on my end that I should fix. Of note, I have been able to load other mission like created from my own ME and they load into my dedicated server fine. The issue seems to be with Liberation generated missions. I checked over in their Discord, one other reported the same black screen issue with joining the server (getting in aircraft) but another person says their Liberation works fine. So I start the server, load the mission, select coalition, and can actually see the map view, and see my Blue units moving around (like the Reaper and AWACS) and the timer on the server is clicking right along. I wait a couple of minutes just to let the server load/catchup before trying to joing. I join, but goes to black screen and just sits there. I can see posted messages about units being killed, etc. So it seems as if the mission is ongoing and the server is running. It's not locking up, freezing, etc. I can hit ESC and get the DCS menu. I can exit the server fine. It just never seems to show anything, just a black screen. So...I just thought I would post the log hoping maybe someone sees something there that might be on my end I can change or fix. Of note also, I just did a clean full removal and reinstallation of both DCS and the Server files. I do have some old/legacy command line entries in there, I left them as I'm not sure whether I need them when I occasionly fly in VR. But those have not been a problem at all before the update. (D:\SteamLibrary\steamapps\common\DCSWorld\bin-mt\DCS.exe --force_enable_VR --force_OpenXR --restarted) Also, there are a LOT of errors in the log, but we're used to seeing those right? I also disabled/unchecked TACVIEW in DCS, but normally I have it running with no problems, my system seems to handle it just fine. It's just the black screen issue since update. Does anyone see anything here I can change/fix, or is this probably just an issue with Liberation missions? Intel 13900K 64G Ram Nvidia 4080 Super E-Cores disabled in Gibabyte Mobo bios as one of the performance options (Z790 Aorus Elite X WiFi7dcs.logdcs.logdcs.log

I actually went to see if adjusting in the Nvidia Game filters tool in game would help....and forgot the sim doesn't support that Nvidia feature Which is a shame, that tool really helps when dealing with lighting and getting games/sims looking good. It really helps FS2020 make night look like....night. And in Elite Dangerous it REALLY is nice getting the cockpit looking great. Maybe when Vulkan arrives that the Nvidia overlay with all the tools will be supported. I use OBS to record, but I have messed with Shadowplay a bit, and having all that stuff at your fingertips in-sim would be awesome...especially the filters.

Realize it's early access, but is it just me or is the ambient lighting waaaay too dim? First flight today and I was tooling around Kandahar and the base, at first it looked like there were no city/building lights at all, but once I got directly over the city I saw the lights....just very very dim. Landed at the airfield and parked next to a hanger, and the hangar lights barely even lit up the ground. Other maps you can certainly see cities and roads from way off, they might almost be too bright, but Afghanistan seems the exact opposite. Too dim.

Makes sense. It certainly acts funky if you leave it on and drop speed to where it comes into play, you quickly become aware it's on with the nose drop. We had no such setting on the H-60. Manual stabilator slew switch down on the center console but that was never used. I do find it easier getting into hover mode and slow rolling through the trees though. Stabilators/Stabilizers can be a downer, literally. I was at Bragg when the H-60's had the issue with EMI back in the mid 1980's, nosediving in causing a few crashes. They restricted us to 80 knots for a couple of months until they modified and put in the now-standard stabilator slew pinky switch on the cyclic and eventually shielded the wiring. kudos to the Sikorsky folks for coming up with that fairly quick, I can only imagine the pressure they were under for a fix. Of course the Navy already HAD their 60's shielded due to their operating environment. And following their normal procedure, the Army denied there was an EMI problem for quite some time. It was terrible flying around at 80 knots, the aircraft wallowed around, I was in the A Troop 1/17th Cav (Same unit as Casmo) and at the time we had H-60's, AH-1's, and H-58 (A models) in each Troop. During those two months the AH-1 guys were non-stop on the radio giving us a hard time about creeping along like a turtle, which I guess was fair given the years of comments going the other direction.

Was just looking for this meself. Would be nice for some external screenshots, etc. As you say, not urgent, would be nice tho...

Flying around tonight I was making good use of a mode that probably most pilots ignore in the AH-64, "Nap of Earth" (NOE). It can be enabled in the FMC controls in the MPD utility menu located at the bottom of the list of the SCAS "ON/OFF" buttons. The guide describes it as follows: "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. It's really helpful hovering around slow around the trees and during approaches, and trying to finagle the aircraft into hover mode. If you haven't been using this neat ability or playing around with it, I encourage you to do so. I find it very useful. For those of you with Voiceattack, I even programmed a little macro in VA to quickly enable and disable NOE quickly, just a matter of telling it to push 3 buttons on the MPD. I have each button programmed to a voice commands (Left MPD or Right MPD and the corresponding buttons (such as the M button, the WPN button, or just buttons called out by location, so to press the Left MPD Bottom 6 button, I say "Left MPD B6"). Then I just use my voice activated macro to press the three buttons to enable/disable NOE by saying "N O E on", and the button pushes are executed and I'm in NOE mode without even looking or fumbling around in the MPD menu. I also added in the Voiceattack macro to have Microsoft Zira Desktop Voice to tell me it's enabled and a short beep. Execute command, 'Left MPD M'; (and wait until it completes) Execute command, 'Left MPD B6; (and wait until it completes) Execute command, 'Left MPD L6; (and wait until it completes) Play sound,'internal:Bedebeep' Say, 'Nap of earth flight enabled' Takes about 1 second to turn it on or off. Enjoy!

It just takes practice and getting your curves etc. the way that works best for you. Myself, I have the axis tunes at : Pitch and Roll Saturation X: 85% Saturation Y: 100% Curve: 17 Collective: Saturation X: 100% Saturation Y: 85% Curve: 0 You might think I have the Pitch and Roll saturation backwards, but for me adjusting the X axis makes the cyclic a LOT easier, it's not as "reactive" to the inputs, sort of damps them down a bit. The Collective saturation seems to make it easier finding the sweet spot in the middle, and less "jumpy" in that 15-25% torque range (but this may be just be a false observation on my part). If you go into Utilities and turn off all the SCAS flight assists you can tell exactly what it's doing for you. Still flyable, but really requires a lot of hands on and delicate touch. I did 20 years as a UH-60 maintainer, crew chief, and Technical Inspector (TI) and while that system is called the AFCS (AUTOMATIC FLIGHT CONTROL SYSTEM) is a bit different performs the same functions. I spent a lot of time underneath a UH-60 and also looking down through the cargo hook access panel during sling load ops, and there is probably nothing more that tests your mettle than being underneath a 16,000 lb behemoth at a hover while you're hooking the load, with nothing sparing you from being squished like a grape other than the pilots ability to maintain the aircraft at a stable hover, and the SCAS/AFCS systems in both aircraft is what allows that. I watched UH-1's doing the same operations and that looked REALLY terrifying as the basic UH-1 doesn't have any of that fancy smanshy assist and REALLY relies on pilots with a steady hand.

Another thing, general question since you seem to use the lua file for server settings manually. I use the server for Liberation campaigns, just for myself, and I find sometimes it just grinds to a halt and freezes up, usually around an hour or so. The last time it did it the other night was during a mission with heavy weather. I have a good system (13900K, RTX 4080 Super, 64G ram, Z780 Gigabyte Aurous mobo) that I built in January, so basically it runs DCS very well, can't turn ALL the graphics up, but I have a lot turned up and limiting to 60FPS in NVCP to allow the extra graphics. Doesn't really seem to be any rhyme or reason to the server freezes, of course I'm assuming it graphics and CPU load. Just wondering if there are any manual settings in the serverSettings.lua that I can dial in that would make the server more stable / not grind to a halt. Of course dialing down the graphics would PROBABLY do it, but really, I don't have them maxed out, and I don't see any reason for the server to grind to a halt after 1 hour. I'm also running with E-Cores disabled, as I can do that in my mobo BIOS, it's part of the Boosting tweaks for the card. I found that in general on my system DCS seems to run better with the E-Cores disable. Might try it with them on a few times to see if that makes a difference. Maybe DCS needs those E-cores to run the background computations? I know about enough to be dangerous with computers, been building my own since the 90's, but some of the newer tech I'm not fully versed on. I do know that P is the performance cores and E the supposed "background" task cores.

I did a search and found the actual file, it's now in Saved Games\DCS.server\Config, no longer in saved Games\DCS\Config. They probably made that move when they switched everything around and basically did away with the open beta stuff, so it's writing to another directory which is why i was seeing that old one in the old directory. I deleted it, and it recreated, so we'll se if it starts holding the settings now. Worst case scenario I'll just keep a copy of it and rename it back to default every time. It's just acting odd and I don't understand why it's overwriting/changing the settings without me telling it to do so. But it IS saving. I'll keep an eye on it and see if I can figure out what it's doing if it keeps it up.

It's probably been covered but I can't find it. I've seen and read several topics that make reference to the server settings, including the serverSettings.lua. I have located the file in Saved Games\DCS\Config, however when I look at the file it is dated back to May 2024, and it does not appear to be updating when I change options in the Webgui. Shouldn't it? Basically having an issue with the server settings not saving it seems. When I launch the GUI, many options seem to revert back to settings that I don't want, mainly pure client and allowing object exports (for TACVIEW. Yes, I know, but I have a great PC and don't have an issue having TACVIEW running, as I like to review that after my campaign missions and add them to my mission OBS recordings to go over the mission events). So I THINK what I see, is the serverSettings.lua is not updating. Any suggestions?

Y'know, I retired in 2005 (did 3 years in the 82nd, and 17 years as a full-time National Guard at our Army Aviation Support Facility), and even though I still live near my old Battalion and we have a pretty active group that keeps up with retirees and current members, I was not aware that the ALQ-144 was retired in 2009 (according to the user guide). So if you install it in the mission editor, it removes the AN/AAR-57 Common Missile Warning System. I tried it in mission editor, and it seems the APR-39 remains in both configurations. So the AN/AAR-57 Common Missile Warning System also came after my time, and I'm a bit confused as I thought that system would replace the APR-39. But I guess they are both used? The APR-39 was always passive and we used to joke that it was just there to let you know what's about to kill you. Chaff, Flares, and Disco Ball was your bread and butter. Not that I would miss the 144, they were notorious for being inop most of the time, and just a hassle moving them around on the aircraft. It got to the point once where we kept them off, and kept the working ones in the Avionics shop to be installed when they were actually needed. P.I.T.A. Learn something new every day. Side note, I was in the same unit as Casmo, A Troop 1/17th Cav, but I predate him there. I was there when the Cav troops had 5 UH-60A, 5 OH-58A, 5 AH-1 (not sure what model), and an infantry scout platoon. I was a Blackhawk Chief, and we'd fly the scouts out and drop them off "behind enemy lines". They even had some camo dirt motorcycles at one point we'd load up and take with. In late 1986-early 1987, the "AOE-Army of Excellence" program came along, which mandated switching the Cav over to the then "new" OH-58D's, and getting rid of the Hawk, A model Kiowas, and Cobras. They made absolutely no plans what to do with the people during the transition, so me and some guys went pro-actively looking for a slot, I went over to the 82nd Aviation Battalion which was then stationed at Pope AFB (not Simmons AAF), and they put me right into a Crewchief slot there. As part of the AOE, soon after that the 82nd Aviation Brigade was formed, and we became A Co "Redhawks", 2nd Battalion, 82nd AVN BDE. 1/82nd AVN was fielding their brand new AH-64 Apache's and were at Fort Hood for a year TDY for that. We moved over to Simmons AAF into the brand new hangers designed specifically for the H-64 and H-60, and we got brand new 1986 model UH-60's. I ETS'd a year later. When I got to my Guard unit the next month (they had just begun getting UH-60's) lo and behold the aircraft on the ramp was the same ones we turned in from the 1/17th and the 82nd CAB.....the Guard unit even had my first Blackhawk I crewed at Bragg, 80-23464. The people there didn't believe me until I showed them in the tail boom where I had inked my name with a felt pen years before. And a year after I got in that National Guard unit, two of the Flight Platoon leaders I was with in A 2/82nd joined that same Guard unit, one of them being my former platoon leader. We all remain friends now 40 years later. I love Army Aviation, it's a large but small community, and if you hang around long enough you seem to run into the same people from time to time DCS bringing all the Army Helos has been a great thing for me, so many memories, and I get to "re-live" a great period in my life. Sometimes I just fly around in the 60, 64, or 58 just enjoying the scenery and reminiscing. Flying along at treetop level, doing some NOE, watching the trees below and remembering hitting a few every now and again, man, it's great. Really looking forward to adding the <profanity>hook to my inventory also. If we ever get to the point we actually have physical troops animated loading and disembarking from the H-60 and H-47, and maybe even the ability to do some paradrops, I'll be in Heaven on earth

As someone noted, the -10 is available at https://www.docdroid.com/ubI02yP/army-bell-oh-58d-operators-manual-pdf The cruise charts start in chapter 7 performance data. The cruise charts depict the basic (baseline) configuration which includes the drag for the mast mounted sight, a universal weapon pylon with ejector racks on both sides, a 7 shot rocket pod on each side, and a standard landing gear, and both crew doors installed. In other words, the charts in the -10 are based on having everything on there. Any changes on the configuration (which exact pods were loaded) were probably considered minimal changes and would not affect the readings on the charts that much. The charts are self explanatory. You would have to start by knowing which weight line to use, information obtained from the DD Form 365-4 filled out during mission planning. The Weight and Balance charts are included in the -10. As a former TI and Weight and Balance Technician in Army Aviation, this would be the charts we used to fill out DD Forms 365-4 (Form F) for each aircraft. The pilots are responsible for filling that out based on their mission configuration, but as a rule for the UH-60 we had probably 20 different configuration Form F in the logbook to ease their workload. So if you change what you're putting on the aircraft, you could use the WB info to find the weight to add/subtract to get the weight you need for the performance charts. I haven't gotten deep enough into the DCS Kiowa to know if the aircraft can display it's own current weight, as a lot of modern aircraft can do, but I don't think so. The only "weight" I see mentioned in the DCS manual is a reference to the WOG (Weight on Ground) which I assume is the same as a "WOW" switch (Weight on Wheels) switch, which is used to enable/disable some functions, and the display panel has an indication that just says you're on the ground. So I think figuring out your weight for the performance charts based on configuration requires manual work.

The full details are Classified. As a former 20 year Blackhawk guy, I was there when the initial "Disco Balls" came out, later upgraded. Basically they spoof IR missiles by making the missiles think the aircraft is somewhere else in space. Think of it as a constant "flare". Pretty effective, not perfect, but better than nothing.

I work in the F-16 spares program IRL and the AF F-16 engineers at the Engineering Support Activity (ESA) at Hill AFB always pick at me because I continually use a lot of "rotorhead" terminology, like referring to AFCS (UH-60) instead of FLCS (F-16). 20 years in Army Aviation will do that. We were recently discussing the F-16 stick in depth as they're replacing / upgrading every stick in the USAF fleet in the near future and I used the word cyclic in a bunch of emails .

More good points. I noticed the stern light, though red meant off and green was good. So I'm looking for amber. Been practicing both approaches, and one thing I noticed watching some real life Youtube in cockpit cameras, the pilots aren't afraid to move that cyclic around in small increments and be pretty aggressive on the power up and down. I was trying to "fine" tune the throttle in increments and only use the cyclic for left and right, but after watching them I have now been getting a little more agressive with the power up and down, and using the cyclic a bit more as long as I stay in the E bracket. I'm finding that method a lot better than trying to approach with miniscule fine tuning. In other words, I'm being a little more proactive actually "flying" the jet, and think I'm getting it down and having better results staying on glide path and aligned. Flying like that, and the types of movements I'm making seem to pretty much mirror about the same amount of movements the pilots IRL are doing in those videos. I've managed to trap a few times, and getting more comfortable doing it. Practice, Practice, Practice. A couple of traps though, I hit the stern and absolutely mangled the landing gear. Plane captains not happy about that, no doubt.

Good stuff, and thanks. I should have thought to look at the Case I-III recoveries, but being an Army Aviation guy IRL the vast majority of my experience is into actual fixed airfields shooting for a helipad if available, or FOB's where just about anything goes. Departures are similar as well, most controllers are happy with helos as they can get you out of their hair quite quickly and will accept just about anything you ask to do for departure as long as it gets you away from the airfield. Reading through those should provide most of the answers, and the angle of 9 degrees for the deck is definitely something I was looking for. It's really hard to see how you're lined up to the deck until it's almost too late, and I've usually been lined up too far left. Still learning the IFLOLS and how it relates to aircraft position, seems a little hinky at times compared to the ICLS, but I'm sure that's because I'm not lined up correctly. It's a lot to digest but I pick things up pretty well and have a set pattern of learning aircraft and systems that works for me, programming the HOTAS and Voiceattack while reading the manuals for the system I'm setting, all while sitting in the aircraft. Sort of a "learn" followed by "do" method. Thanks again, and I'm sure I'll have more questions which I'll ask in this same thread.

So I've been at the F/A-18 for about a month now, working through tutorials and building my HOTAS and Voiceattack profiles, progressing nicely. Actually a little surprised that a lot about the F/A-18 is intuitive once you figure out the DDI's and UFC. Anyways, set up ME to allow me to practice carrier takeoff and landings on the GW. Got the launches down now, and working on the traps. So I started just using the TACAN approaches, that's ok, but a little hard to figure out the angle. I'm coming approaching way too low, working on that, but one question I have reference a TACAN approach. Is there a standard CRS offset for the TACAN that would line you up with the angle of the landing deck on the carrier, so if you approach using THAT CRS offset, you'll be lined up with the landing deck? I hope this question makes sense. Reference the ICLS approach. That's pretty simple, just a few steps. Here's my dilemma though. I find myself not knowing the proper altitude I should be at to intercept the glide slope. Going off what the carrier is telling me (and I'm assuming I'm interpreting this correctly) I set up the TACAN with the heading course they say (343 in my case), set the CRS line at 343, and fly outbound for 163 climbing to 7,000 out to 22 miles. I then turn back inbound to 343, getting down to 250 knts, dropping the gear and hook, and going flaps full setting up my AoA (I've got that process down pretty well). So my questions on the ICLS approach: 1. How far out does the carrier ILS transmit? I seem to pick up the localizer far out, research shows that a standard ILS localizer can broadcast out to about 18 miles, but that far out it's not super accurate, but I do pick it up. Research also states the localizer becomes pretty accurate 10 miles out, and that some aircraft and/or localizer can be picked up much further out. The glideslope indicator comes in much later. research shows that at 10 miles. 2. At what altitude should I be approaching to pick up the ICLS? As noted, the carrier has me climb to 7000 outbound, but I don't really see anything telling me what altitude to approach at (I may very well be missing a radio interaction?) The reason for the question is I'm looking for the optimum altitude to intercept the glideslope at. If I can't figure that out, I'm toast. trying to chase a glideslope at a descent rate of 2000 fpm 5 miles from the deck is, well, suicidal no? 3. Also, it appears I can have TACAN and ILS operational at the same time. Is that correct, and is that useful? I THINK it is, and having the TACAN course line helps keep me on path approaching the carrier until the ILS kicks in. My last attempt I intercepted the glidescope at 7.5 miles out, approaching at 3000 feet. That probably indicate that I'm coming in too low, no? I did almost make it, but hit the end of the deck. Also the ICLS seems a bit screwy near the end, making me take a late right course correction, and back to the left. Doesn't seem superaccurate near the end.

I for one would like to know why the 2 CPU cores are pretty much maxed out no matter what you do. I have a good system, so I'm not trying to be a "woe is me" person, and I can get 120 fps with good graphics and push my 3080 Ti to about 95%. In general though, I like to keep it FPS locked to 60 or 90 (using those increments as TrackIR operates at 120, so 120, 90, or 60 keeps it in good synch). Mostly I run at 60 FPS. I do mostly helo flying. With my system, I can even run the "heavy" Liberation maps on my own server with good results. Running it off an SSD, But recently I bought the F/A-18, and noticed that I was occasionally get an intermittent stutter/lag, no real pattern to it other than watching MSI Afterburner and seeing that it appears to be the CPU being bound. Overall, I only am using about 30% total CPU (windows resource monitor) when locked at 60fps, with about 50% GPU load. So I started playing around with settings, including bios, NVCP, and in game. I've been building my own PC's since the 90's and gaming longer than that, so I'm pretty familiar with all manner of tweaking. What I noticed was, even if I set the DCS settings on the "low", the 2 CPU cores stay in the 90's, mostly 95 and above. Adjusting FPS and other graphics settings can change the load on my GPU, but it seems nothing can reduce that load on the CPU, which just stays up there all the time. Right now I seem to have reduced it a bit by using my mobo bios settings on the Gigabyte mobo setting of "Instant 6 ghz, which offers 6 Ghz on 2 cores. That seems to give it a little extra "oomph" and for the most part the stutter is not consistently there with that setting. In the past I've also disabled E-Cores (another Gigabyte tweaking option), but the E-cores disabling doesn't seem to have much effect anymore one way or the other. Tried turning off hyperthread in bios (terrible), and just about every other trick in the book, but those 2 CPU cores stay maxed or high 90's all the time. Again, compared to many people my system is great, so I'm not boo hooing, just wondering why oh why are those 2 CPU cores so high all the time, even with the game settings on "low". I don't need them at 35%, but getting them down to about a CONSISTENT 90% or below would provide enough overhead I think to eliminate those random major stutters methinks. Just wondering why those 2 are maxed out like that, and what, if anything, can be done to reduce that. As stated, I've tried every low setting there is, and it just doesn't seem to do much. Attached a couple of screens, with what I run generally but at 120fps in this case Intel 13900k WD_BLACK 4TB SN850X NVMe Internal Gaming SSD Solid State Drive EVGA FTW 3080 Ti 64G Ram DDR5 Z790 Gigabyte Aorus Elite X WIFI7 mobo

With a new module I actually have those guides open as I'm configuring my control settings and setting up my Voiceattack profile at the same time. By doing that, and testing / pausing in the aircraft as I go, I actually learn a lot about the systems as I'm going along, before I even try to go out and do missions. Otherwise, I don't think I'd have the time or patience to print it out and sit down and read the whole thing. Might make some good crapper reading material though, that's about the only time I do any reading nowadays

Fun Fact....while flying as a gunner tonight, I was looking around and noticed some info on the gunners seat armor, which was a number, SPO460-95-C-5285. That is an actual Defense Logistics Agency (DLA) contract number. DLA procures most of the spare/replacement parts for military aircraft. I work at one of the 3 primary field activities, Defense Supply Center Richmond (DSCR) which is the home of "DLA-Aviation". I have worked since 2004 as the Quality Assurance Specialist on the F-16, working with vendors who have contracts to supply spare parts, and working also directly with the USAF F-16 engineers at Hill AFB in those efforts. The "95" in that contract number indicates it was a fiscal year 1995 contract for replacement armor panels for the H-64. So obviously they used photos from an actual aircraft, and it's pretty neat they even put those little details in our cockpits...

Nice...may I ask where you got the livery? I was a Blackhawk crewchief, started out in the 1/17th CAV, 82nd Airborne Division when each Troop has 5 H-60's, 5 H-58's, and 5 H-1's. I was there when the "AOE-Army of Excellence" happened, and the changes were that the 1/17th converted to the OH-58D, so I had to go find a home. That home was with the 82nd Combat Aviation Battalion, then stationed at Pope AFB. We quickly formed into the 82nd Aviation Brigade, and moved over to Simmons AAF into brand new hangars designed specifically for the H-60 and H-64. I was in the "new" A Company "Redhawks", 2nd Battalion, 82nd Aviation Brigade as an H-60 crewchief. The 1st Battalion "Wolfpack" also new, was at Fort Hood training on their spanking new AH-64D's for a year. I left Bragg before they PCS'd back to Bragg.

When you are setting up a mission in ME for training, and pay absolutely NO attention to what you are doing......

A couple of questions on the server install: 1. I have two folders that reference the server C:\Program Files\Eagle Dynamics\DCS World Server C:\Users\Mike\Saved Games\DCS.server What is the purpose of Saved Games\DCS.server? I see that It has about 10 folders. I also have the Liberation generator installed, and I see that Liberation created it's own folder in there and that appears to be where my "next turn" .miz files go. Is this a folder created by Liberation, or just an additional folder installed with the server installation? Just wondering. 2. (More important question) I run my server on the same PC as game. When I launch my server, run the GUI, load my mission and ensure it's running, and then go to multiplayer in-game, I am presented with 3 MP server options for the one I started. The differences are: 192.168.1.103:10308 (Ping 1) 127.0.0.1:10308 (Ping 1) 71.206.155.132.10308 (Ping 3) 71.206.155.132.10308 is the one shown in the GUI, and I realize that's the "public" server and others probably can't even see the other two. So, which server should I join to ensure the best running of the mission, and hopefully eliminate "freezing" or "crashing"? I'm sure it's probably one of the internal ones?

As a former 20 year H-60 chief IRL it's interesting to see the differences in the T-700 compared to the Hawk. I always knew there were some differences when perusing TM 1-2840-248-23 and TM-1-2840-248-23P, I mainly recall that the engine computer on the bottom (visible as the silver box with a cannon plug in the rear) was an ECU (Electronic Control Unit) on the 60 and a DEC (Digital Electronic Control) on the 64, but never really delved into the differences. Probably had something to do with adjusting fuel dumps into the engine via the HMU (Hyro-Mechanical Unit) as the aircraft definitely had different power demands depending on situations, with the 60 8-9000 pound sling load capabilities. It's a great engine, the amount of power compared to size is amazing. We could rip one of those out of the aircraft in about 30 minutes with an experienced mech. I was an inspector most of my career, and never really tore one down but used to inspect and sign off on all the maintenance done on them, and also responsible for borescoping them. I could tell by the whine of the engine if there was blade/fod damage, and more than once had an aircraft pulled into the bay to borescope it. There were a number of ports all over the engine that let you see pretty much every blade and internals from front to back, but you kind of had to be a contortionist when trying to borescope it installed in the aircraft. As a crewchief I once had an aircraft that was experiencing engine flameouts at low power settings (landing approaches) on BOTH engines, that is NOT fun. Spent weeks replacing parts per the TM troubleshooting, would pass the MTF fine, and then a week later another flameout. Almost got to the point of calling the GE or Sikorsky field rep, but eventually determined that it was the HMU on both engines, the odds of that happening one engine are slim, the odds of that happening on BOTH engines on the SAME aircraft around the SAME time are infinitesimal. The aircraft had recently been through a "refurb" / upgrade at Corpus Christi (a thing they were doing in the 90's). During those refurbs, all the parts were stripped and sent to various shops for teardown, inspection, and repair, and parts were placed in storage areas. When they finished with the airframes, they would go to the storage areas and just pick a new part out of storage and install it on the aircraft. The results was all the aircraft that came out of refurb never had the original components from the factory (gearboxes, engines, rotor blades, etc. etc.) Very few original parts left on it. So we figured that the engines were tore down and inspected, the same thing occurred, and there was probably a batch of HMU's refurbed during a time period that made it onto the engines that went into that aircraft. Probably the same mech working on those HMU's during that process making the same error on probably a bunch of HMU's.