hilikusopus

DCS A-10C Checklist [edit]

Try this one out - a good looking checklist by war-hawks.net http://war-hawks.net/A10_Training/WH_A10_Checklist.pdf

I had a similar problem with jaggies using the 190 drivers, but it seemed to resolve itself at some point. My main problem now, since installing 190, is that after a minute or so ingame the framerate stutters noticeably. If I Alt-Tab to the desktop and then jump back into DCS, the framerate returns to normal, but only for a minute or so before deteriorating again. Think I'm going to roll back to 186 and see if that resolves the issue for me. Doesn't look like there's any improvements on 190 that interest me anyway. Funny: my experience -- and I've only ever used Nvidia chipsets/drivers in gaming -- is that their drivers are stable, even their betas. p.s. Thanks for the tip diveplane.

I think I spotted something in the readme notes of the forthcoming patch that was included in the new hardcopy manual. I'm sorry, I can't really recall which change I saw included in the manual, but I think ED may have attempted to anticipate the changes coming down the pipe. Beyond that, you're most definitely on your own when it comes to keeping any changes up to date.

I bit the bullet last week and ordered it directly from the Fighter Collection. Anybody else do this? Paid an arm and a leg for shipping to the States, but I received neither a shipping confirmation nor tracking details, so I have no idea of when to expect my copy. They've left no way for me to contact them with these questions, since the contact info provided leads to a dead end. EDIT: I read backwards, and there are a ton of posts with the same complaint. Well, next time I hope there are shipping options or warnings..... EDIT: Just got my manual. Two weeks or so for delivery to the States from the UK. All simulation manuals should be spiral books!! Awesome.

@miguez Like DivinuZ said, I'd like the option to download the videos until the complete set were available on DVD, but you make a good point about copyprotection. That aside, I think you've put together a good plan, and I'm really looking forward to seeing it come together. As a side note, I hope you place special emphasis on tactics, as well as flesh out the details that go unspoken elsewhere (like you've done for various startup tests in your first video). That would contrast nicely with the orignal manual's dry, terse treatment, and provide some much needed context to the gameplay. cheers, hilikusopus

I love that I have to study to play a study sim. LB2 was different for several reasons, and partly on account of the pilot/gunner system. The Hokum pilot is almost required to manage twice as many systems as the Longbow pilot. Plus, the systems present in the Longbow, and missing in the Hokum - such as FLIR and the Longbow FCR - are ones that I would think alleviate the workload of the crew. That being said.....I want DCS Longbow!!!

cheers, fellas.

Disclaimer: I am neither a physicist, nor an aerodynamics scholar! But if the helo has a tendency to turn toward the wind then maybe it has a related tendancy to turn toward the direction of your movement. Say you're heading straight with some speed and apply some heavy rudder - even though you're orientation has changed, most of your momentum is still heading in the original direction due to inertia - when you recenter the rudder pedals the helo will tend to revert to the original configuration. I notice that this also happens in fixed wing simulators, as well. I wonder if it's the same principle as with rotary craft. I'm curious about an intelligent answer to this question too! ?

To answer the first question: the "no function" text is confusing because of the formating, but I believe it refers to whole preceding list of computer advisory lamps above, and not just the final one next to which is written "no function". That was my take when I first read it.

:megalol:

Panzertard: "Rotary wheel knobs: Hold left mouse botton on them - move left/right. Ex: HUD brightnes or Shkval contrast/brightnes." Thanks! I've been using my mouse's scroll button for these knobs, which doubles as the zoom in/out function as well, so you can image how frustrating and unproductive that could be!

I have a similiar experience with my keyboard. Try pressing the F-Lock key before you press the the F12/pause button. The catch is, when you want to use the F-keys for comms, you will need to press the F-Lock key one last time. After that you can use the Esc-key to pause/unpause the sim.

Thanks for the positive feedback! By the way: the pitot tube heat test toward the end of final checks does not seem to be functional, despite what the manual implies (i.e. the test lamps to either side of the test button on the overhead panel do not illuminate when the test button is depressed). I've decided to leave it the checklist - I'm operating under the assumption that this is an ultra, minor, temporary, bug and will get a fix at some point, or else you can just pretend the lamps light up. :) Also, I'm not altogether sure what the VHF-TALK switch is used for (Wall panel, used in final checks), whether it's "VHF-TLK" as its cockpit label indicates, or whether it's a typo and should actually read "UHF-TALK" as I've seen used elsewhere. EDIT 6/29/09: According to the manual, "Data link equipment provides jam-resistant secure communications via VHF-TLK channel for remote target designation." So there you have it: it's VHF, not UHF. Well, I'll let this version (2.0) float around for a while to see if any errata accumulate, and if an update is necessary I'll bite the bullet and make the changes. If you find anything please post it here and I'll take a look at it, thanks! I spent the better part of a week to get it right, so I feel like it's pretty tight at this point.

welcome

You've got yourself a deal, if you also let me know whether it works well for you too.:thumbup:

@Talisa: I just finished creating my own and posted it in this thread: http://forums.eagle.ru/showthread.php?t=42692 I made a beginners' version, with explanatory notes, and a companion version, much more concise without notes (like a checklist). Both are for startup, though; and instead of photos, I use a notation to describe where to find a particular switch. I posted other Blackshark checklists that I found in the forums there, too. Try AlphaOneSix's for shutdown procedures. Dawu's checklist has photos that identify certain switches. Hope this helps. :) -hilikusopus

You got it. :thumbup: Otherwise, you're working with backup hydraulics.

@FOXFIRE There are two switches directly related to the hydraulic system. I'm surprised if the helo's flying better with either of them turned off! The first one you deal with almost as soon as you get into the helo is the master power switch for the EKRAN/GEARBOX/HYDRAULICS. This switch is located mid-low on the rear auxiliary panel and, upon entering the helo, it will be uncapped and set in the off (up) position. Turn the switch on (down) and cap. The second hydraulic switch is called the Hydraulic Servo Test Switch. It is located smack dab in the middle of the wall panel. It's basically a hydraulics-only power switch (as opposed to the first one above, that actually powers multiple systems), used to test the auxiliary hydraulic system. When set in the ON (down) position and showing through the cap, the main hydaulic system is powered. To test the backup system turn of the main hyd system by flipping the switch to "MAIN HYD OFF" (up). When testing, after turning the main system off, you'll notice that the main system pressure gauge on the auxiliary panel drops off, and two advisory lamps (MAIN/STBY HYD SYS VLV) illuminate to the left of the gauge. And if you're throttle is set to the AUTO power setting, you will also receive an EKRAN message "MAIN HYDRO". Just remeber to return the switch and cap when you're done. -hilikusopus

Great! I'll stay tuned....

Thanks for the reply, Matt. Okedoke. Having user-created campaigns and missions will be great. I guess my question is, will the non-mission files be lumped together, or will there be some organization, such as a section purely for checklists and keycharts, etc.? -hilikusopus

deltatango, Great idea! Oh man, that would be really cool to have a checklist on my handheld. Alas, I have a BlackBerry. (You're a dirty rotten scoundrel for tempting me though! Love the avatar, mate.:thumbup:) But if you make one for the Ka-50, you should definitely post about it on the forum, since there's bound to be some interest in a tool like that. Cheers. -hilikusopus

:) This was a personal project, although I did want to try to contribute somthing to this forum, because I think everybody is really helpful and cool here (including everybody from ED and the testers). But it makes me happy to know that at least a few other people have found what they were looking for. I'll try to put together a final version I'm satisfied with, and then I'll let my baby go free into the wild. Run, run little checklist, run!

Yeah, it's not a checklist proper. I hear what you're saying though. Not only does the manual lack a proper checklist, as you pointed out, I also found that it's "how to" section/s lacked the right amount of "how to". So, it was very difficult for myself and others needing more than a refresher on startup procedures to make sense of it all. Unfortunately, the in-game training tutorials, as enjoyable as they are, are not interactive. I was pulling information from half a dozen sources, trying to make sense of it all, and thought it would be so much easier to have it all in one document. A checklist has the skeleton, so I adapted it but getting some meat on its bones. This was simply meant for people like me who need to bridge the gap before moving on. Like I said earlier, once I get a handle on this, I'll probably create a companion version that more closely resembles an actual checklist. Here's Fabio Miguez's checklist, which strikes me as pretty close to the real deal: Ka-50 Checklist - NP.pdf

I understood your meaning. :) I guess I just managed to figure out where everything is, so I can get by without pictures, but the color-coded notation I'm using helps me get the flow of startup, like I'm conducting an orchestra. After reading your comment, it did occur to me though, that you could use my checklist or another one you prefer, and there are plenty of cockpit screenshots you could use to paste into the document. I hoped that by leaving mine as a MS Word doc, and not a PDF, it might be easier for you to do just that. I'm still working on my checklist using the manual, other checklists, and the forum. As a general rule, I've tried to include more rather than less. For example, if somebody on the forum discusses a particular procedure that is missing in the manual, I've added the procedure to my checklist. When I've found conflicts between one source and another, I've tried to work it out with the most logical solution. I think it's getting there though.