JanMasterson

Ok, done some tests about Radar's PD. Tested ECR-90 (SS (airborne), LD-SD) at about 15 different PD values. It seems that from 9 up to 200, detection range is the same, below 9, detection range drop to less than 50%, at PD 0, it seems that there is no radar detection or at lowest range than viual detection (was 3nm). Will test airborne(360) tomorow. ("tomorow" is relative, since, technically, we are already "tomorow" ) Maybe Tony can confirm/ infirm these results? I'm heading to my bed with a PD of about 50% because my eyes are closing themselves Cheers, Jan

Okay, here are the DATA values for the Rafale. Base is 30. up to 15% of the max payload, nothing change; above and up to 60%, DATA is reduced to 24; and from 60% to 100%, DAT is reduced to 18. Now about Range values: Rafale C: Base range: 1000 up to 15% of the max payload, nothing change; above and up to 60%, Range is reduced to 800; and from 60% to 100%, DAT is reduced to 600. Rafale B Base range: 980 up to 15% of the max payload, nothing change; above and up to 60%, Range is reduced to 784; and from 60% to 100%, DAT is reduced to 588. Rafale M, equal to Rafale C. In fact the Rafale M have 15kg less fuel than C version.

What is exactly "area" ECM? because, AFAIK, Type-D, FLIR and Laser (Sub-Type) pods aren't functionnal at all. In fact, what is a "Type-D" pod? About "sensor flags" in the aircraft annex, FLIR allow to detect ships but not planes and IRST detect aircrafts not ships, isn't the opposed IRL? Thx, Jan

Is the official designation CF-188 or CF-18? Link 16 JTIDS? Wich are the new BVRAAM, AIM-120C or, as sometimes heard, Meteor? I've heard too that the Sidewinders will be replaced by Asraam, exact? In the second pic, isn't there some Mavericks (second line from the bottom) and Paveway III just behind?

AFAIK, at this time, loadouts designed for HC are issued from H4 forms or designed by DB... designer. AFAIK again, there aren't fixed rules about designing, at least, about range and DATA determination. If AFAIDK, there are rulles, the following wouldn't be usefull at all, but, please, let me thrust that the time i took to design it isn't wasted for nothing. What i suggest it to determine fixed multipliers that will influence DATA and range based on real life values and H4 rules. So i took the "Performance effects for Turbofans and Turbojets at cruise" issued in the rules book and adapted it. Here is what it gives: % of Max Payload Carried | Range/DATA Multiplier 0-15% => *1 (no changes) 16-60% => * 0,8 (80%) 61-100% => * 0,6 (60%) What do u think about it? Is it realistic? Jan

About these famous "DoNotUse", here is what TonyE said: Are the scen that Tony talked about no more a problem? One other method that can give some space is to only have generic military units rather than designated ones, like all those "X/Y Bn USMC" rather than only have one "USMC Bn" (Coy, etc.). What about those "Not Used" entries (id.: ID: 51208 52170 51205 51646 51523 51400 51449 51450 51479 51376 51445 51446 51447), can't we use them? Jan

Hi guys, after a "Very educational night" along Rook and HermanH, i'm thinking more and more about "specialized" databases, let's call them "thematics" databases, as they'll be intended to be exhaustive on a determined geographic area (Europe,Pacific,IO), timeline (Cold's war end '89-'91, Lebanon,...) or a fictional background (WWIII, United States of Europe,...). Why several databases rather than a big one? Because databases have their technical limitations and an only one database can't be exhaustive without being far bigger than actual limits allow. So, thematics DBs will alow to be exhaustive on platforms thanks to clear spatio-temporal limits. How can i (player) use differents database? There's no need to hide us the truth,it will require some files manipulation. It mean, u'll have to manage ur files with care. After one or two time, it will becomes natural to everyone to swap files. It seems nice, how can i launch a such project? A project like an entire database require some planifications. Ideally the first phase is consacrated to "technical evaluation", talking with "Database technician" like TonyE, Brad, etc. to define clearly possibilities. The second should be the logistical/administrative phase when teams are constituated (DB editors, scen designers, researchers), support site opened (to stock files, share ideas, communicate) and several other tasks that a team should do before anything concrete. Phase 3 will be the coding phase, when everyone codes (DB, scen). Phase 4, beta testing, debuging, in one word "validation" Phase 5, release. Off course, it's only a basic plan and everyone have his own way of managing a teamwork but, what do u all think about that? Jan

Good Job Dear CV32. Can u specify what are exactly "some clean-up being done in that annex" plesae? Good idea to just share the .res fille, smaller and easier. About installations types, a generic civilian nuclear facilty, a basic power facility, a generic railroad station maybe. Cheers, Jan