Captain Orso

Maybe the only "bug" is that POS/INS is default and not GPS. From my understanding, ever since GPS was added to the Hornet IRL, GPS is the default for everything, and INS is only for just in-case GPS is broken. I recall a former pilot saying that they train using INS like once a week, just in case. But INS always drifts over time, so POS/INS will lose accuracy, and require re-calibrate during your flight. Maybe McDonnell Douglas didn't think it important enough to set as default in the RL firmware, or maybe ED overlooked doing it. Who knows.

I'm glad you mentioned it, Dragon. I always get moaning and complaints that nothing is good enough for me, and I should be happy with the free help I get, when the one-line, dozen-word work-around is imbedded in a 17 minute video.

When you start a mission and your aircraft has waypoints programmed in, you will not seel them on the F10 map, ever. If the mission you are flying allows for pilot control, you can click an AI aircraft and see it's assigned path, if it has one. If an AI-aircraft is selected, in the lower-left you have a command menu with some rudimentary commands to give the AI-aircraft, like path and target. From my experience, this "path" is generally equal to a set of waypoints, but almost always WP0 is set to where the aircraft is when you clicked path, and it remains for ever, but the AI-aircraft will not try to follow it. After clicking path everywhere you right-click on the map sets a new waypoint for the AI-aircraft, including the altitude and speed. It works sloppy and buggy and getting an AI to do what you want requires a lot of trial and error and frustration. And you cannot set a path, at the end of which you conduct an attack, as soon as you set a target, the AI-aircraft will fly straight to that and try to attack it, ignoring the path you created. These are the methods of controlling AI-aircraft. Why do I explain all that crap, when you are talking about the aircraft you are flying? Because, for whatever reason, DCS puts the commands in the lower-left if you click on your own aircraft in the F10 map. You can add a path and everything, but all of it means nothing. Just think of it as a buggy way DCS works, which has no actual consequences and just looks buggy and confusing. The waypoints the mission creator add, or you added after starting the mission are the only ones which concern you, and you will never see these on the F10 map.

If the wings start folded: Put the mouse pointer on the wing-fold handle, and leave it on the handle for all further instructions. Scroll-wheel aft to pull the lever out. Right click the lever to rotate it CW (left click for CC). Once the lever-handle is in the horizontal position, the wings will start to unfold. You should actually only do this right before reaching the catapult, when the yellow-shirt signals it to you. Wings should generally be up while taxiing on the deck. Scroll-wheel forward to push the lever back in and lock it. After landing, and un-hooking the tail hook, start folding your wings before you start to taxi away. They can fold while you taxi. Just don't hit any other aircraft on the deck with your wings. You will not make friends like that.

DCS does NOT use threads, beyond that the sound processing process can share a core with the main DCS process, each 'acting' like a thread. So, you might keep two cores somewhat busy, leaving anything else running in background to share the remaining cores/threads. Since you only said "Nvidia GPU" I am almost afraid to ask, because DCS is heavily GPU-centric; at least you're not using VR*. In general I would always say, before you invest in CPU, invest in GPU. You really only need the CPU to feed all the date to the GPU. So, before going to an i9-12900K I would invest in an RTX 3090 Ti. Of course, for the price of one 3090 Ti you can buy three 12900K, so.... IDK absolutely, but my educated guess would be that you could more likely drive a 3090 Ti with a "smaller" CPU, but the fastest CPU will get you nothing more than your GPU will process. G-RAM makes a difference too. The more, the better. The more ~ the higher the range of hi-quality LOD you can have, so, how far out the trees pop up while flying low, for example. I fly VR so have no need for touch screens etc. I type 10-fingers blind and use a mouse. If you feel you are getting good use of all the screens, good for you - nothing else maters. Ummm... $2000 for HOTAS and pedals?!... How? I mean, what?

Yes, that's exactly what I wanted to do, but I couldn't find the target at all. I need to practice with GR in a more controlled environment.

So..... I'm an old man... kind of. I probably need new glasses. I'm using an Oculus CV1 HMD. And... ground radar doesn't find stationary targets very well... at all... Maybe playing with gain on the GR might help, but I couldn't find anything, and I knew where to look. I couldn't get the GR to see the waypoint, nor if I used the HMD to put a target marker on the ground, get GR to see it. Nope, GR doesn't want to play with others. Sucks to be me, I guess. But since most cases I recall encountering have been self-inflicted (forgetting to enter elevation provided by JTAC, forgetting to put a waypoint on the ground in the ME) I'll have to learn to live with me.

THAT'S why I lost my target! I accidentally dragged the waypoint away from it. Thank you!

Wow, that IS an idea So I look for the target on GR and then mark it by putting the GR uprights on it and pressing the TCD button. Will that get the TGP to look exactly where the GR is looking? I've never done this before. In fact I've rarely found good use for ground radar. At sea, that's another question, but over hard ground, not so much.

If I can find the target, that's all I care about. Sometimes I can't. The only other solution I can think of is to use the LAT/LON to find the location on the F10 map--yes, kids, I've done this before, but don't tell Mommy--and check the ground elevation and enter it into the waypoint. Oh well. Thanks for all the replies! It's not awkward, but it is time consuming so you need patience.

I... I will have a talk with myself , as I have been guilty of this too. it's easy to forget that the waypoint you place is always way up in the air.

So, overwriting LAT/LON with the same numbers gets nav. com. to lookup and enter the ground level?, or do you need to create a new waypoint?... That might work in the A-10, but I know it won't work in the F/A-18, bc I already had a thread, where that was the issue. I was working with a JTAC and the JTAC gave the MGRS for a target, and I neglected to enter the elevation. I had to self-laze the entered waypoint. JTAC couldn't laser it, bc the point was on a plateau and the JTAC was in the valley below and couldn't actually see the ground on which the target was standing. Laser on, drop GBU-12... miss. Laser on, drop GBU-12... miss. Laser on, drop GBU-12... miss. FUUUUU!!!! Then I realized the TGP was looking at the ground (forest with mortars below the treetops, ofc), and while I was flying laterally to the target, the TGP was slewing across the ground, bc - see the illustration above. I had entered the waypoint coordinates correctly, but neglected to add the elevation, with crappy results, because the nav. com. doesn't think and realize that elevation 0 in the mountains is underground, and not right.

It doesn't work in the F/A-18, and I've tried it with the A-10, and the AH-64D. In the F/A-18 and the A-10, the waypoint is saved with elevation = 0 and aiming the TGP at it shows it aiming at a point under ground, as in the above illustration. The AH-64D saves the waypoint at level 0, BUT when you set the WP to DIR (direct steering point) you actually see the home-plate marker at ground level, as if the WP were actually at ground level. If you look at the WP in the nav. comp. though, it says elevation 0, big as day.

To illustrate what I mean

And then the waypoint is at elevation 0 and the TGP does not point at the ground where the target is.

This is all relative to a running mission, for example in MP. You have a waypoiont, which is where your target it located--very friendly of the creator to give you this oh, so important tool for finding the enemy. The creator, however made the mistake of not putting the waypoint on the ground where the target is. Instead it is at 15,000 feet where you are supposed to be flying. When you designate the waypoint as target, your TGP looks up in the air like a day-dreaming child. What to do. Labels are off, Units are hidden on the F10 map. You are in the mountains, so the ground level below the waypoint could be anywhere between 1000 and 3000 feet. The target is a Grisom, so you can't just fly over it and put a markpoint down to use that as a reference for the waypoint, bc you want to get back home for a cold one. What is the simplest method of getting the waypoint onto the ground, where it belongs?

Documentations need to be clear and concise, and use a language properly to be understood. My misunderstanding is evidence of this. If you have to know how a systems works to understand the description, the description is 1) pointless, because you already understand the system, and 2) pointless, because without knowing what the document is trying to say, it cannot explain itself, because you have to know the system to understand the description.

OMG THAT'S what he means?! I'm just relearning the Harrier, so I'm pretty weak on some of the functions. I was sure he meant that, for example, the IGRS and EGRS lists of waypoints had entries, ie populated, and that colonized was a mistranslation of populated Still "colonized" has nothing to do with colons; that's not English. There is unfortunately no one-word-term to express something with a colon in front of it. One might use colon-marked, or colon-designated, but in general one can also say "selected", because every option in the UFC or ODU, which is selected, always has this denoted by a colon preceding the option.

BTW, I'm reading through the manual, and especially starting with 14.4.2.1 DATA PAGE (WAYPOINT)--but not only--the term "colonized" is is used very often, instead of "populated"

Hello Razbam, thank you for you time and effort in putting the AV-8B-NA manual together. Please, put the publication date and the version number into the document. This is the international norm for serious companies. It is especially necessary for documents, which will be updated and changed over time, like the Harrier manual. Thanks

Put all the files together in 2 designated locations; one for Day, one for Night. Before joining a mission, navigate to 'c:\Users\YourUserName\Saved Games\DCS.openbeta\Kneeboard\FA-18C_hornet' and delete all the files. Copy the designated Day or Night folder--depending on the mission--into the kneeboard folder above.

You don't need a networked repository. Networked repositories are only for sharing mods between more than one user and having one person managing them. If you are using OMM only locally, you simply add a Library Folder--where the packaged mods are stored.

I'm playing almost exclusively in MP. On the 4YA PVE Caucasus servers there are nearly always a lot of AH-64's doing their thing. You can also try the Rotorheads Server, but you have to register in Discord first--small formality. It is--as the name implies--only choppers.

Thanks! I'll put these into my fix too.

Many thanks for that answer, Ramsey. So that's why 285 KHz didn't work, and I then thought thess were NOT the NDB I did you wrong, Wambat! Not your charts are wrong, DCS is wrong! So to fix this, all that one would have to do , is edit Beacon.lua and change { display_name = _('Abumusa'); beaconId = 'airfield1_0'; type = BEACON_TYPE_DME; to { display_name = _('Abumusa'); beaconId = 'airfield1_0'; type = BEACON_TYPE_HOMER; and then it would work as it ought to. Modded it. Works in SP AND MP, so far.