F-35 status (in BMS) request
-
Exactly. The much higher range for new AIM-120 concers strictly on F-22. Meteor is a big leap forward in kinematics if it has similar sensor to AMRAAM almost the only thing where Europe has the lead comparing to US in fighters.
Then why is Canada buying them for their hornets?
http://www.dsca.mil/major-arms-sales/canada-aim-120d-advanced-medium-range-air-air-missiles-amraam
-
Why to buy old missiles? BTW C-5 is even not produced anymore…I think.
-
Then why is Canada buying them for their hornets?
http://www.dsca.mil/major-arms-sales/canada-aim-120d-advanced-medium-range-air-air-missiles-amraam
Because Meteor so far has not been integrated on any F-18. In Europe only Spain has in NATO (besides FIN and SUI which are not NATO members). Meteor is available for Gripen C/D with latest software upgrades and will be available on EF first. (The leased HUN Gripens could use them if we bougth Meteor.) CAN will buy old RAAF juts as an interim solution, they have much different priorites than integrating a new AAM on a figthers which has no long time future…
-
This post is deleted! -
Yes you can. It looks a little odd in the pit, but it works. Radar performance is 90% DB, it’s just a matter of knowing which fields to change. What you cannot do, is engage multiple threats simultaneously like most 5th Gen + AESA allow you to do.
Pls. show me how you can do it…
I’m very curious because except some modeling values for player controlled airplanes almost everyting is handled by the code. You cannot change any sweep parameters and modes of the radar and you cannot do sim. AG-AA mode which are capable to do ESA type radars.
-
This post is deleted! -
You CAN change sweep rate, just like you can change the beam width, and vertical scan limits, and range, and ECM resistance, notch effectiveness, and look down penalty. No, you cannot do simultaneous AA/AG, but not all aircraft which have ESA implement that feature, so it’s not a matter of modeling the radar, it’s implementation specific. Just because it doesn’t reflect in the azimuth indicator on the FCR, does not mean it didn’t work. Watch the FCR, every track gets refreshed every frame, regardless of where the beam indicator is pointing. It works.
These are for non human controlled jets. If you fly with any aircraft the sweep rate is exe coded…
BTW fast sweep rate is not equal with totally free beam forming and deflection in azimuth and elevation. If you set almost 0 time it would mean over modeling…
All other parameters are non used of does not have anything with ESA…
Have you ever try to MOD at least F4…? As I can judge you do not have a clue about the DB + exe… -
This post is deleted! -
Who’s talking about things they don’t understand now…
Sweep rate should never be anywhere close to 0, because it’s RADIANS/SECOND not SECONDS/SWEEP. Furthermore, the goal is to simulate behavior, not emulate function. You don’t need to beam form and calculate deflection to get the same EFFECT as an AESA radar. And the last time I checked, AESA is more jam resistant, and has better low altitude and low speed tracking than the old mech radars. All of which can be adjusted.
All those parameters don’t impact human aircraft? I’ll bet you a 2 year hiatus from the forums if you change the beam width you’ll see it reflected in the pit. I’ll bet you a 10 year hiatus from the forums if you lower the jam penalty you’ll see exactly where aircraft are even when they turn on the jammers–from the pit as a human player. I have mapped, tested, and confirmed the function of almost every field in every file of the database. If you have a better idea of how it’s structured than I do at this point, I’ll just go ahead and delete my account.Show me in video pls…
-
This post is deleted! -
Not at home, you’ll have to do your own leg work. Unless someone else following the debate wants to put it to a quick test.
Hm…. What you posted seems to me is just value of RCDs in DB. As I have said you can set what you want but it does not have any effect on human controlled jet…
-
This post is deleted! -
That’s exactly what it is. But it DOES effect the human jet. Try it and see.
I tried it this is why I know what happend…
-
This post is deleted! -
What happened? Post a video and a picture of what you changed. If I’m wrong I’ll take my hiatus. But I’m guessing the FCR was populated with all the tracks all the time, the Radar Position indicator did not speed up, and it worked exactly how I said it would. Because I changed Radar 22 a long time ago to fly with the F-22 and have been using it like that for over a year.
Scan time is the same on FCR. I have tried this change about a decade ago in FF and also in BMS4.
-
If I am not wrong and as far as I remember : the DB values you are talking about are only used by agged units.
IMO, Molni is right.
EDIT: I was talking about Ground Radar sorry.
-
This post is deleted! -
but this shows that they DO have effect.
No way!! That’s Photoshopped!!!
Isn’t it funny how you’re told you are wrong, and when you explain how to achieve the result and ask your accuser to check it out so they can see for themselves and they refuse to because “they already have decades ago”!?!?!?!?!
Don’t be dismayed, it happens a lot!! https://www.benchmarksims.org/forum/showthread.php?30875-falcon-bms-cfg-moddified-to-earn-fps/page3&highlight=bms+config
C9
-
well could be DeeJay’s case.
Anyway Mortesil I’m sure u noticed, u have a rudder input issue, just in case.
Edit: I forgot to mention that the new app looks awesome….
-
A few things to note:
First video (You can skip to about 1:00) - Stock configuration. Notice the Altitude Range on the FCR. Watch WHEN the tracks get updated on the FCR screen, every time the Beam Position indicator passes the track it gets updated. Jamming targets are never identified.
Second Video - Notice Altitude Range. ALL tracks get updated every time the position indicator reaches either end of the scan. Jamming targets are intermittently identified, in the correct position (5% position variance left in).
The values have effect. There is a cleaner way to implement an “AESA” type radar, but this shows that they DO have effect.Khöm, you changed beam parameters not just sweep time…
So you want to say sweep is just graphics but data definesd the sweep time? We can try set to lower to test it. You changed more than one value which makes impossible to judge which is work.