hein22

But I think it is still PDI, so some sort of CW small beam is still used.

Are you asking or being funny? I don't get it sorry, not a native english speaker here. CW in pulsed doppler radars are performed via PDI. You are confusing lock, launch and guidance. Those are 3 different stages. CW or PDI is when you are being locked by a radar. It focuses the energy on a small beam to keep you on sight at "all" times. Then at launch the side lobes are used for datalink command guidance which the enemy's RWR detects and provides warning for. However there is something odd in DCS, that when locking with sparrow you get PDI indication on radar, but when locking with amraam you get the PRF. So I will stop here and let others more experienced tell us how it is done IRL.

Every modern radar has CW in its PD assembley. How would they fire SARH then?

1st: you don't, you guide with command data link. Remember we are talking about ARH here. CW is for LOCK, not for guidance. 2nd: CW can be achieved with the PDR

In fact, it mentions that what it lacks is a separate CW illuminator.

You misunderstood the sentence there. On p136 it is explaining how pulse doppler radars work in general as opposed to old CW ones. It is not saying that it lacks that mode for lock on.

Jeez, can't wait. I'm a navy fan so the Hornet and the SC are my favorite by far!!

I think CA integration refers to taking control of the SC like a vehicle. I'm sure setting a path for the carrier will be available just like any other ship. That's what I wanted, the possibility of changing course to account for real world procedures.

:O

Source for stating that those radars don't have CW?

I watched your track and you were not setting radar correctly. I took control and didn't have any trouble finding the S3. You radar elevation was too low for the 7nm distance it had at the beginning. Your TDC showed 15ft top but the tdc was over 20nm so the cone at 7nm didn't catch the S3. Give it a try and let me know.

I wasn't going to. Just posted to give some positive words about your huge and good work.

BN, as I described above, the issue is not present in my current OB. Waypoint 0 DSG update works perfectly with unrestricted satnav OFF. So satnav is not the problem here I think. Maybe the user can try this method? Make sure to first get the OK in the alignment and then do the position update. (Afaik this behavior is not correct in DCS but it works to get the issue away. Wp 0 should be updated first).

Nice!

Additionally, continuous wave is for locking. Launch warnings are given when command data link from side lobes are detected. The section you quoted is specifically talking about TWS.

We flew yesterday and all the airports in PG map were lights off. What is going on?

ARH launched in STT do give RWR warnings because they do CW. Correct behavior afaik. If you want not to give a warning use TWS.

So after reading NATOPS during a couple of hours, it seems that this is correct behavior so the pilot can turn GXMT to COMM1 and transmit an emergency call. So the previous behavior was incorrect and last update was updated to reflect this. I must say, what a nice job from ED catching these things without anyone reporting. Nice! :)

I know we are in front of a study sim and there are tons of stuff simulated but when I come across things like the one I'm about to point out, I feel happy and grateful that we have ED in our world. I also know there are things like the fire test closing the bleed air valves requiring you to cycle them, but I found something in NATOPS that was pretty deep and mixed in between stuff and I can't believe ED simulated it! NATOPS: "When the first ground power switch is set to ON, the avionics under-cool warning temperature switch performs an internal BIT (approximately 3 seconds). During BIT, the ground power switch(es) must be held ON or it reverts to AUTO." Well, guess what? We DO have to hold the switch or otherwise it returns to Auto. WELL DONE ED! Please be around for ever.

We posted at the exact same time :). See above I think I found something worth looking.

Ok, sorry for the repeated posts. I think I found something that maybe wasn't detailed in this thread. If you set chimney smoke to 0 without deleting fxo and metashaders and restarting the game then the problem persists. If you turn back on chimney smoke to any value above 0 you will have correct FLIR image and chimney animations as well. But if you restart pc the bug comes back, it seems that restarting pc does something with the shaders in DCS. Hope this helps users and ED.

It has been reported many times and everyone at ED states that it is correct for the real Hornet. I know it sounds crazy that a multi million dollar aircraft was built like this, but it seems it's true and we have to trust ED.

So I was just about to buy the hornet campaign and found this thread. I tested and indeed doing a position update with UPDT/DSG/ACPT after designating waypoint 0 makes everything work.

Can you expand please? I was not aware that the Hornet had INS simulated. We don't even have IFA (if you put it on IFA then your position gets inverted), we don't have AINS (aided INS, similar to EGI). What do you mean by align via TCN?

Radio 1 can be used with just battery on but remains unpowered. Track attached. radio1 bug.trk