Upon close inspection , not enough holes.
Ok. Radio set. Nose cold. Probe out. … funnel width set.
Let’s talk. - “Do you have the guts to enter turn now , eh?”
- btw @Trueno , What’s that skin of '16 ?? I like… give ? … pretty Please!
I tested much of possible variations in air to ground vs sam engagements.
So far I saw , sam (sa-10, sa-17) will engage only Harm’s , but no Jsow’s , SDB’s - gliders. , slam/er , cruise missiles … all legal sam targets.
I was perfectly able to obliterate sa-10 (well, put it out of action) unit surrounded with sa-17, sa15,sa-19, with only with 4 Jsow-A’s (flying FA18E).
I don’f find it much possible given the strength of that kind IADS. - for which is able to even shot down a GBU
Is that by design , will/can this be refined in some update?
My 2 Harm’s were intercepted with no problem…
but, with no other (sam) targets flying around.
just as soon more then 4 air targets (mixed, weapons and planes), sam’s begin to behave erratically , not quite composed. - panic mode (no Awacs cover for any side, for early detection)
If not for 4.36.x then for 4.37 , please have this in mind , sam can (and will) engage everything above mentioned.
There is/was implemented “system wind” in Falcon (BMS),… I don’t know if that works right in 4.36, but I remember it was working before.
See for yourself, just use CCIP with something “freefall”
That means that “targeting computer” takes account for wind on current altitude and moves CCIP on predicted point (along with maneuvering). You can see this if you fly higher … CCIP pointer will be left/right even you fly level.
Can’t say for CCRP , probably the same thing, just it isn’t so much obvious, … you can try to test with stronger side-wind in mission , then you will see that target point will be also left/right from vertical bar., more offset when stronger wind.
But, again , “system wind” is not “magical” , and now we have different winds per altitude and turbulence and crosswinds , … system is not perfect… even it would be impossible for detect all parameters around you., even today with eg F35.
So as @VDK says , use WCMD if you want better precision from higher altitudes … but , if you’re still in for a “knife-fight” , then you’ll have to be significantly flying lower to avoid differential winds… it’s not impossible , but is kinda risky because , eg… if battalion have sa-19 , … but that you’ll know on RWR
“Fly into the wind…” , not sideways
@Aragorn … Yes it was fun to watch, action wise. but saw few mistakes too.
I know , easy to say from hindsight, but BMS is still not punishing enough … - but overall nice Iron Eagle
@Kevstosmart Mate… all is fine… … But how can you “miss a mountain” … jokes aside , worst air accidents happened that way… but it was mostly weather/visibility.
In F16 (Bms) … dear “Cara” or even better “TFR” (if carried lantirn-nav pod) will scream (warn) in this case.
F18 have even built-in solution , radar in “TA” (terrain avoidance) mode… scan 10+ nm (or more 15? 20?) in front of plane for terrain.
Ahh. but for 2d map… yeah , map heights are not quite “visible” … so ,
understandable., your concern.
But I’ll give you a hint… how to make your own “height-map” …
Open your save with MC (mission commander) and use that button up-right “save map”… there you have few options what you want on that map, heights, roads , towns … etc … on/off.
You can even select color for everything,
Build a map … and voila … terrain with heghts.
Cheers… and enjoy.
Hmmm… I think I know - 99%. I’ve had similar problem with registry in the past , probably 4.35 and now with 4.36.
I’ve had to edit security on root key to allow users, probably everyone or I couldn’t change theater from BMS.
BMS could read reg but couldn’t write… strange. but!, since setup is admin , that goes… since BMS is not admin process it fails if security is not “worked around”.
I would say it is/was a windows “thingie” since some update, but… for some people it works “normally” so … question remains what exactly.
I don’t know, not really hard to try… and see if it would work in his case.
You broke the engine, probably with “random error generator”.
Can’t say what exactly (you sucked a bird … poor birdie), but engine was in SEC, even switch was is in PRI (default).
Your engine temp was in excess 1000-1100C , OVERHEAT, it was miracle you didn’t catch fire.
Land ASAP, or bail. - or try flameout if feeling lucky
or BRAA if the proximity conditions are met.
Even better,… for bullseye still non-lovers
mmm, now you mentioned, I do have this in .cfg , but honestly can’t recall if I saw them last time in U3… maybe to check with a bit of the weather forced in tac … good point
set g_bShowFarRain 1 set g_bShowRainDrops 1 set g_bShowRainRings 1
I think one or two other comms on the carrier page also overlap … “report airborn”?
They won’t overlap if you use @Tomcattwo “approach” … +1 btw.
Separate carrier and ground with “prefix” (eg … Carrier, Mother) for carrier ops.
We launched a new installer for that purpose.
Forgive my ignorance, what is the diff between legacy and new (full) install… this with fw opening ports etc.?
(btw, this might be misleading a bit)
I’m not Igor, but you made my day !
I think I know who is., but won’t share … hihihi (don’t know is he around anymore tho, this was ages ago)
I had some time browsing .dds shop also … boy are there some easter eggs,… even in db warehouse was named “whorehouse” in 4.32 or so (b4).
Mate, you haven’t offended anyone… at least from my perspective.
For pro simmer (vir-pilot) T.Flight is … hate to say it …
trash, …not with these words, but … “inadequate” … copy that.
But for anything else, even X-Wing vs T-Fighter, bloody even MSFS ,… it is perfectly fine.
You better beg Thrustmaster for forgiveness