Cruizzzzer

hehe... that would be it! just need their address

Just for info: Just updated the pdf to version 30052021 Greets! REVISION RECORD: 1. front page 2. index page reformatted 3. deck personnel added 4. page 50; HSI radial errors corrected; DOL = "Distance of Lead" added to clarify abbreviation 5. ENG START: notes added (page 13)

Thanks to all for the kind words! Appreciate it! Though found some errors in pdf which I am correcting just right now. Upload will follow today. Version number is indicated in the lower left corner by e.g. "REV 30052021"... Just renamed the "F/A-18C Checklist" to "F/A-18C Flight Manual [chapter-1]", as chapter-2 will follow, on which I am also working right now. But need to say, that "chapter-2" is a bit "insane". It's a bit more of "educational" use. And yeah... kneeboard shows still "not active". It's gonna take some more time for ED to release it...

ah, thanks... good to know... got a little impatient here...

Unfortunately my upload of the F/A-18C Checklist (kneeboard version) has not become active yet (for reasons I don't know)... So meanwhile just use the kneeboard builder you all know to create the according kneeboard yourself... Kneeboard Builder for DCS World (dcskneeboardbuilder.com) Sorry, for the inconvenience...

In the manual itself you might come across the "CASE II / III marshal consideration"... Where it says "AOB = standard rate turns = tas/10 +7; AOB max 25°" it only refers to the reversal turn passing the fix for the outbound leg. This is only an "airliners thing" as this will give you a standard rate turn of 3° per second. Of course you can pull g's like hell and do all the crazy things with the hornet if you need to reach the fix at the EAT to start the approach...

Thank you Weasel! Just uploaded the "kneeboard version"... should come available pretty soon (still shows "non active") ... Hope the manual helps in one or another way...

Hey everyone! Last time I was flying with my mates, they urged me to make my "F/A-18C Hornet Manual" available for the DCS public. This was never my intention, when I first started this manual about 1 1/2 years ago, and until now I was pretty reluctant (and maybe still am) making it public. First it was meant to be pure checklist, leading you through all stages of flight, starting from a "cold & dark", starting up engines, taxi out, taking off, cruise, until landing and shutdown. Later on I found I was not familiar with other systems and all the stuff that the hornet offers. So the manual got bigger until I had to cut it down again to fit in the kneeboard so it is useful during flight. Now, the manual (pdf) is build in such a way, that it is meant to read with two pages side-by-side set up in the pdf-reader. Background is chosen to be used in both day and night ops. I just uploaded the pdf in the user files section: (kneeboard will follow) F/A-18C Hornet Checklist (digitalcombatsimulator.com) Maybe it is useful to you. Special thanks to "Pokeraccio" and "Minsky" who gave me the permission to make my manual public, as I used they great work in the manual. THANKS AGAIN TO YOU BOTH! Lastly, I always try to be as thorough as possible writing down all the infos, but surely there will be mistakes or certain things missing. If you find any mistakes just let me know. Maybe this manual helps you in certain situations... Greets... cruizzzzer

perfect! many thanks!

Hey everyone, I stumbled over an abbreviation... What does "FE" stand for? Thanks for your help!

Hey everyone, now I hope that this is as complete as possible (at least to my knowledge)... maybe it helps... Greets

@Pieterras thx for the thorough answer! I will certainly come back on PM! thanks for the offer, appreciate...

@=4c=Nikolagonna write a PM as this thread is drifting a bit "offtopic"

yeah, it does... day and night version all in one and thanks! yap... writing manuals by yourself really gets you into the stuff. you start to think about all those little details and "how-to's". lots of work, but when it is fun, it's no work...

I am writing those manuals myself, trying to get all information for the hornet as close together from original sources available, packed into pdfs and converting them into the kneeboards for ingame use. Chose the background color so its readability in night-ops is given. In the above case it is the case 2 scenario, but got the whole bunch also for case 1 & 3...

on 1. totally agree on that... you will hit the burner, speed up to IAS 350 and enter the pattern... on 2. I don't think that a straight in case III approach will be possible from this point, as when having "worst case scenario" at 5NM flying at 250kts you won't be able to be fully configured at 3NM for G/S intercept (except if you rushed the approach: gear down, flaps down, speedbrakes extended, as to decelerate from 250kts to final approach speed). I believe that somewhere upwind you are being vectored to downwind (into the bolter/waveoff pattern), but not sure at which point you are going to configure to HALF FLAPS... on 2. I think it will look like this, but not really sure...

Hey everyone, I got two questions concerning CASE II recovery… as I cannot find the exact procedure in the manuals… 1st scenario: WX is such as you can complete the recovery with a CASE I recovery. Starting the CASE II recovery until 10NM it will be the same as a CASE III recovery, thus your IAS will be 250kts until 10NM. So assuming that you break the clouds after 10NM and going visual with the carrier, you ought to fly the rest of pattern as a CASE I recovery (via initial, break, downwind, groove and land). QUESTION: At the point where you get visual (between 10NM and 5 NM) are you going to speed up to 350kts in accordance to CASE I recovery? In my opinion I would say “yes” as continue flying with a “wrong” speed of 250kts for a CASE I will give you different parameters and gates. 2nd scenario: Same as above with the difference that you are able to break the clouds at 10NM but cannot get visual with the carrier at 5NM. Now the manual says, that you are being vectored into the “waveoff / bolter pattern” for a CASE III recovery. QUESTION: How exactly are you going to fly it “speedwise”? Are you going to configure to “FLAPS… half” just after passing inbound 5NM, or are you keeping IAS at 250kts until being vectored into the pattern? Or are you just going to do the “pilot stuff” and configure the hornet according to your “personal pattern”? Thanks for your help!

Hey everyone, I’m not really sure whether it addresses the problem, and of course, if it’s a hardware issue (broken cabel) nothing will help except for replacing it… Only once I had the problem that my G2 just shut-down while on standby and wouldn’t wake up. But this occurred only once. Luckily the G2 is not suffering from any sparkles… The problem I had, that while either parked on a carrier with many static F/A-18s parked on the deck my G2 showed squared “blackouts” only on the right lense, while turning my head. This also occurred while having four F-16 flying formation and following a tanker for aerial refueling. While turning my head my G2 had those blackout squares only on the right lense. During the last few days I messed around with the ingame system settings and STEAM VR settings. First I set the DCS PD to 0.5 and STEAM VR "per application video-settings" to 500% resulting in no more blackouts. PD set to 1.0 and STEAM VR set to 100% gave me the blackouts again. PD set to 1.0 and STEAM VR set to 120% gave me now NO MORE blackouts. I am running the G2 @ 90Hz with a 3090.

You could get out of the "ALT HOLD" by pressing MCP speed, i.e. changing the vertical mode, thus the B737 would maintain speed (according to thrust lever setting it would climb/descend). During "ALT HOLD" changing to V/S nothing will happen if you hadn't chosen/selected another altitude. And, phew, guess I need to test that on the hornet... it just popped in my mind when I read the thread title how it works with the boeing...

good to know...

the NOTE also points this out...

On the Boeing 737, while pressing "ALT HOLD" (= BALT), the A/P maintains the uncorrected barometric altitude, so i.e. ALT HOLD is NOT coupled to the altimeter setting, nor altitude will change while changing your altimeter setting. So, having set ANY altimeter setting is only an indication, but has NO effect on the autopilot itself, as it "senses" the barometric altitude "on its own" (ADC)... I guess that every aircraft shows this behaviour...

Hey everyone, I am german based, so looking for a squadron (team members) that are german based to fly with. Mainly I am flying and got some experience on the F/A-18C Hornet. Till november I flew pretty much the A-10C, but the question is whether I am still current on the warthog. Right now I am building missions (campaigns) for me and some guys I know, but unfortunately right now it seems that I am the only one who is flying. So if there is a squadron reqruiting I would be glad joining. Thanks and cheers. Looking forward to buddies to fly with... Cruizzzzer Hallo Leute, ich lebe in Bayern und suche eine Staffel oder auch Team Member mit denen ich fliegen könnte. Derzeit fliege recht intensiv die Hornet. Bis November bin ich auch die A-10C geflogen, es ist aber fraglich ob ich da noch "current" bin, da ich sie recht lange nicht mehr geflogen bin. Derzeit baue ich Missionen zusammen, aber dadurch daß die anderen Zwei mit denen ich versuche zu fliegen sehr häufig nicht online sind, fliege ich die Missionen derzeit zum Teil echt nur alleine. Falls es Staffeln gibt, die derzeit rekruitieren würde ich sehr gerne joinen. Würde mich drauf freuen... Bis dann, Cruizzzzer

Hey everyone, yesterday I flew a mission with plenty of MK151s loaded. Got everything setup: 1. master arm ... on 2. A/G ... selected 3. selected the 61S 4. chose CCIP 5. alternating between SGL and SAL 6. didn't change the motor setting, left it on M66 I was wondering that on the SMS the "61S" was crossed out, but I could still fire the rockets. Also had all the correct indications in the HUD. Unfortunately, I dont have screenshots or trackfile of that mission saved. Was there a problem of setup, or is it a bug in DCS? Couldnt find any information about this being a bug in the forums.

Ah, perfect. Thanks... Gee... so much to learn... but real fun!