Useful information (docs) for Carrier Ops
-
And it is possible to start with an F-16 on a carrier. If you want to land on a carrier with a F-16, then
do it without any stuff (jettison all) and your speed should be only 160 knots. Because the landing gear are weak from the F-16. -
1./ Because it is possible.
or
2./ After a hard mission with some holes from a fire canon in your beautiful F-16, you have
serious problems on your way back over the ocean. You navigation is destroyed, you lose
fuel and the only runway in range is a carrier.
You have 2 choices.- Eject and lose your f-16
- Try to land on the carrier and save millions of US dollars.
Regards
-
1./ Because it is possible.
In BMS, sure. In the real world, not a chance.
You navigation is destroyed, you lose
fuel and the only runway in range is a carrier.
You have 2 choices.- Eject and lose your f-16
- Try to land on the carrier and save millions of US dollars.
Ejection is the only option. It takes months of training to land on a carrier in an aircraft suited to the carrier environment, it isn’t just something you decide to “try.” Not to mention the fact that the Viper wouldn’t survive the arrested landing. The arresting gear on a boat is radically different in operation than that of it’s land based counterpart.
-
+1.
-
Hello,
maybe someone can help me to solve the following problem. I use Falcon BMS 4.33 U1.
In comparision with others users, my HUD did not show all information. It seems to be, that
my monitor is not big enough.Take a look at the attachment. There you can see my HUD and the HUD from others users. In
contrast to my monitor, they can see more information.
I used a monitor with 1920 x 1080. I think, that should be enough? Can i change something, to
get more information?Here some examples:
GoodMy Cockpit: (not good)
2./ Second Question:
My Hud is sometimes to weak for different weather. I have the brightness to max, but i cannot see my hud in white clowds. Take a look. Is there a solution? I tried
in the past several colors for the HDU, but they did not really help me.3./ I take a look at several F/A-18 Ramp Start Videos. It is possible, that some switches was removed in Falcon BMS 4.33 U1 ?
Take a look at the Video at minute 3:32
The handoff offset flash in this video. If i try the same at my F/A-18, it did not flash. Or do i something wrong?
4./ I tested several starts and landings from the aircraft carrier “Enterprise”. 90% works very good with the catapult and the arresting cable.
But i have the following problems. Sometimes the catapult did not catch my F/A-18. I tried it several times and the only solution is to
reload the mission. Than it works.
Other problem. If i land on the carrier, the catapult from the landing runway of the carrier catch immediately my just landed F/A-18 . It happens
if i land to much on the left side. Then i am stucked and the carrier is blocked for other aircrafts. I think the only solution is to use the
keystroke “AFTriggerCatapult” and then my aircraft is free again?5./ I my point of view the ILS/Tacan System of the F/A-18 aircraft is a little bit buged. Or i do something wrong. That could be possible too.
If i activate the backup System and try to use several TCN Channel for diffrent situation.
Situation 1:
Carrier with TCN Channel 028X
Main System : Works with T/RBackup System : Works not. Only with “AA T/R”. And i think, AA ist only for aircrafts like a tanker?
Situation 2:
Tanker with TCN Channel 029Y
Main System : WorksBackup System : Did not work with “AA T/R”.
Works only with “T/R” ==> for Ground
For me, it seems to be, that the developer of the F/A-18 inverted both functions.
Have other users the same behaviour?
6./ Exists there F/A-18 Checklists or manuals like this?
http://www.cockpits.net/files/FA-18Cv3.0_MANUAL.pdfBest regards,
Marvel -
1. Known issue. HUD data does not fit in the HUD. With TrackIR, you can center the view, lean back then re-center. This will dynamically shrink the HUD data and it will fit better, but maybe not 100%.
2. Known issue. Partly that’s how it really is; partly because the glass background is a little to light (imho). You can recolor the glass, or change the HUD color (yellow seemed best for me).
3. Known bug. Turn on console lights. There are some missing textures with lights off. See:
4. Happens sometimes, don’t know why or how to fix it. Try another cat? At landing, sometimes you ‘hook up’ on Cat3. Use the ‘release cat’ button (default SHFT-K) to release the cat.
5. Don’t know; Haven’t tried BU TACAN.
6. Don’t know.
-
Hello,
does someone know from a “fcr-bug” ? Since the version 4.33 i have the following both problems. Maybe i do something wrong, but i used the same steps like in 4.32, and therefore i think, its a bug.
1./ The ICP-MARK Feature did not work anymore very accurate. If i have a target and i want to create a new Targetpoint with the ICP (Mark) Feature (FCR), then i get some coordinates. But they are not
the correct one. They are 5 to 10 miles away from the correct target. In BMS 4.32 this feature works fine.2./ Another annoying thing is the following. Take a look at the attachment. On the left side is the FCR. The right side a maverick camera view. The FCR did not correspondent with the maverick window.
The cross hair from the FCR is on the left side of the targets. At the maverick windows on the right side.In BMS 4.32 it works perfect. The camera is everytime at the correct position.
Regards,
-
1. Cursor Zero. ??
-
Hello,
does someone know from a “fcr-bug” ? Since the version 4.33 i have the following both problems. Maybe i do something wrong, but i used the same steps like in 4.32, and therefore i think, its a bug.
1./ The ICP-MASK Feature did not work anymore very accurate. If i have a target and i want to create a new Targetpoint with the ICP (Mask) Feature (FCR), then i get some coordinates. But they are not
the correct one. They are 5 to 10 miles away from the correct target. In BMS 4.32 this feature works fine.Did you do a Cursor Zero after switching to your markpoint ? If not, you will have the SPI offset and your cursor will be off.
2./ Another annoying thing is the following. Take a look at the attachment. On the left side is the FCR. The right side a maverick camera view. The FCR did not correspondent with the maverick window.
The cross hair from the FCR is on the left side of the targets. At the maverick windows on the right side.Or it this correct?
Regards,
Maverick has a bit of misalignement, you need to align them. Check your install folder \Docs\Falcon BMS Manuals\BMS-Training.pdf, Maverick training mission for the procedure to align them.
-
Hello,
you both are right.
1./ Cursor zero seems to be the problem. I will do some more tests.2./ After i align my aircraft sensors LOS and the missile LOS, everything was fine. Short solution
Lock with FCR, lock same target with TGP or WPN and press BSGT (OSB 20)
Page 121 from the bms-training.pdf contains the correct information.Maybe for TE builder are the following carrier pictures helpful.
Only Enterprise, Roosevelt and Vinson seems to be correct implemented.Regards
-
Yes - if it’s not there anymore, it should be.
Hello,
i tested today the balkan theater (version 1.05) and there i can find the “speed brakes” on the left side. Take a look at the screenshot.
Maybe it is possible to reimplement it in Korea?
Regards,
Marvel -
Arty add to hotlist.
Sent from TapaTalk
-
Not a ‘bug’ per se, but an incomplete feature, which I think is known to BMS devs:
@BMS:
8.4.2 Carrier trap landing
….
Fly your approach with a relatively steep slope (at least 3-4°) and with the FPM on the AOA bracket. ….
The AoA bracket and Indexer in 4.33 (U1 and U2) do not represent correct AoA parameters according to NATOPs. You will get ‘on speed’ indications that are misleading during landing.
Specifically the very upper and lower ends of the AoA bracket are outside the range of acceptable landing speeds. Also the ‘On Speed’ donut on the AoA indexer will light over a much wider range than indicated in NATOPs.
The AoA ranges in BMS and NATOPs are show below:
The bracket and lights are also ‘backwards’ for Naval Ops standards, but I think that is a known issue. Finally, per NATOPs, the AoA indexer is only lit with gear down and no WoW. In BMS the AoA indexer is always lit.
-
Also one should note that the HUD AOA bracket in the Viper is backwards from the one in the Hornet - if they didn’t make the HUD bracket match the Indexer you can get into real problems, and it a serious transfer of training problem in moving between the two platforms. The real trick is to just watch the Indexer and keep the ball lit - i.e.; be on-speed. That works for both platforms because the Indexer in both operates/indicates the same (minus some granularity/sensitivity).
I’ve learned to be able to tell a USAF from a USN pilot flying a Viper in HUD videos - a USN Viper pilot will always land on-speed; the USAF guy is always fast. Being of a Navy stripe, I always land on-speed…Fly Navy!
-
Also one should note that the HUD AOA bracket in the Viper is backwards from the one in the Hornet ……
It is noted in the chart I posted and the post itself. I’m confident this is a known issue with the Devs and am hopeful it will be fixed in future updates/versions.
…. The real trick is to just watch the Indexer and keep the ball lit - i.e.; be on-speed. That works for both platforms …
Not in BMS. That’s the point of my post. The BMS ‘on speed donut’ lights up in the wrong range of AoA per NATOPs. NATOPs shows an total indexer/bracket range of 6.9 - 9.3 AoA units. A part of the range (7.4 - 8.8 AoA units) is ‘on speed’ and the rest is ‘slightly slow/fast’ (outside the bracket <6.9 or >9.3 is ‘slow/fast’). In BMS the whole bracket range is ‘on speed’.
-
Hello,
i tested today the balkan theater (version 1.05) and there i can find the “speed brakes” on the left side. Take a look at the screenshot.
Maybe it is possible to reimplement it in Korea?
Regards,
MarvelNow its missing with the latest balkans update2 , too. Oh God how great is to keep older versions wink:
Thanks -
It is noted in the chart I posted and the post itself. I’m confident this is a known issue with the Devs and am hopeful it will be fixed in future updates/versions.
Not in BMS. That’s the point of my post. The BMS ‘on speed donut’ lights up in the wrong range of AoA per NATOPs. NATOPs shows an total indexer/bracket range of 6.9 - 9.3 AoA units. A part of the range (7.4 - 8.8 AoA units) is ‘on speed’ and the rest is ‘slightly slow/fast’ (outside the bracket <6.9 or >9.3 is ‘slow/fast’). In BMS the whole bracket range is ‘on speed’.
Actually, the bracket operating differently between the two jets is how it is in RL, so that’s not a bug…it’s just annoying. REALLY annoying…I wouldn’t really expect any “fixes” until there is an actual Hornet avionics model developed.
One of the things that may also be incorrect in the BMS Hornet bracket is that it lights only three indications - it should light in five indications; upper/lower chevron and upper/lower doughnut…you probably know that. It’s actually a lot harder to capture and maintain on-speed in this case than to do so with the Viper indexer…at least I’ve found it to be the case - a lot more sensitive. And the fact that the brackets are opposite in the two make for some seriously hard habits to break.
But the AOA ranges don’t really sound that far off…what you’re really controlling with AOA/on-speed is your pitch attitude for a given gross weight to put the hook in the wire. The actual numbers don’t really matter as much as your attitude and speed. In this case you really need to ignore the bracket - at least, that’s what I do…for both the Viper and the Hornet. The indexer always works…and you also need to hit the altitude numbers at the 180/90/groove.