Briefing, please! (Either I don't know how to do that, or else I only know "radar logging" by some other name... )

 

Run launcher

Check -l for logging, check radar for radar logging

Run game, the ge.log in the game directory will be extra large thanks to the additional radar logging

 

...

OK, that's why I wasn't recognizing radar logging. (launcher)

 

I also was not aware of the ge.log, anyway. (Might there be anything saved in the default (non-launcher) version of that log file, that would be worth me checking at this point, in regards to any of the various issues that I've seen - such as impervious air groups, ineffective missiles, etc. It's a little much to wade through without having something specific to look for... especially when I don't understand (yet) what a lot of it means or refers to... )

 

Dittos with the radar log packets, although I imagine I'll figure out some of the more obscure bits there during actual use.

 

Anyway, I'm give that a try and see what shakes out.

 

Thanks.

Is there another way to set up radar logging without using the launcher?

Is there another way to set up radar logging without using the launcher?

If you can't wait for someone like Tony I'd try using a short cut with

"your hce drive letter:\your HCE folder name\winharp32.exe" -l radar

as the command line

I guess the -l radar is the bit you need to add to a normal short cut.

I hope that works (I haven't used short cuts since the launcher).

Don

Don, you are correct (and thanks)! VitP you can see some more verbage in the beta testing area general forum in the beta tester manual

 

http://harpgamer.com/harpforum/index.php?showtopic=3574

E-2B Hawkeye performance

 

All airborne targets detected at Low altitude except where noted.

 

F-117A: 16 nm (maximum possible detect range 23.38 nm)

Rafale: none, missiles first (max possible 44.49 nm)

F-16: 49 (max possible 73.8 nm)

F/A-18: ?? (max possible 85.06 nm)

MiG-21: 57 (max possible 87.48 nm), target at Med altitude

MiG-23: 45 (max possible 104 nm)

MiG-29: 45 (max possible 104 nm)

Tornado: 46 (max possible 108.9 nm)

Su-24: 59 (max possible 134.76 nm)

F-15: 69 (max possible 146.46 nm)

Su-27: 74 (max possible 152.62 nm)

Tu-22KD: 89 (max possible 202.11 nm)

 

I could imagine questions arising about the above results, specifically the Mig-23 and Mig-29, why are the actual detects much shorter than the theoretical as defined by the radar RCS spreadsheet? It goes back to the roll of the dice, radar runs once every 30 seconds, PD on the radar is only 60 so you have a bad string of luck at the dice rolling table and detect ranges get downright scary.

 

 

 

 

Looks like everyone, EVERYONE, including Brad & Tony, missed the key point here. Mavfin found the explanation. Note how in all cases but 3, the ACTUAL detection ranges are less than half the theoretical range? Brad didn't say, but I BET that the Hawkeye and the 3 anomalies are all at Med altitude!

 

E-2B does not have LDSD radar, thus off-altitude detection ranges are halved!

Brad didn't say, but I BET that the Hawkeye and the 3 anomalies are all at Med altitude!

 

The E-2B was at High altitude and the targets, excepting the MiG-21, were at Low altitude. (Thanks to VitP for pointing out my typo).

Looks like everyone, EVERYONE, including Brad & Tony, missed the key point here.

 

Heh, keep in mind that Brad and Tony are pretty much at the end of their rope when it comes to explaining things. Its really nice when others (like mavfin) jump in to help.

Looks like everyone, EVERYONE, including Brad & Tony, missed the key point here.

 

Heh, keep in mind that Brad and Tony are pretty much at the end of their rope when it comes to explaining things. Its really nice when others (like mavfin) jump in to help.

So, perhaps Brad and Tony need a holiday from the easier explanation stuff, there may be other things to do that they can find

Don