Topics created by marvel_master

@marvel_master

I do some more tests.
If i start a TE at 09:50 and the Takeoff Time is 09:56, then the Falcon Server
loads die fmap from 11:00 (between 10:58 and 11:02). He cannot load the 10:00 fmap. Maybe he just loaded the starting fmap from the TE and therefore the client ignores the 10.00 fmap?!

I think i can life with this solution.

Regards

@Dega:

Where do I put this in the config? I don’t see it as already existing in the falcon bms config.

And is this a MP fix only? I am having similar issues in single player campaign

workaround :

Just Host a MP session (even if you plan to fly it SP ) and apply set g_bMPMovingCarriers 1 in your cfg

the carrier will be stopped and you wont have the issue 🙂

but unfortunatly carrier will not turn head wind then…

Hello,

sometime i have the problem that the carrier drives through islands from the map. Take
a look at the screenshots.

It is possible to determine the carrier route or to stop him in online missions?

Regards

Yes, it´s a known bug in 4.34. You need to do in flight alignment after take off from carrier.

I used the X52 until a few month before switching to a X65F on W10. Currently not on my PC but I have for sure still the driver and SST software I used on my machine.
Will look up later

Gesendet von meinem SM-G930F mit Tapatalk

Thanks for your reply.

I actually suspected something the like about, but I preferred to ask, you know.

With best regards,

Hello,

i tested several bms theaters and its the same behavior. Everytime if i land with a f-18 at a carrier, the FPS decrease to 15 or less. If i fly the same
TE online, everything is fine. The fps decrease extreme, if i am 100 meters in front of the carrier. After the landing the fps return to 80 to 120 fps. But
only, if i look in front. If i look back to carrier, the fps decrease again.

I attachend some offline and online Screenshots. There you can see how the fps are.

What can i do to fix this problem? Do i have to reinstall falcon bms 4.33 U5 ?
On annother computer from me, i do not have such behavior and everything works fine.

Regards

I don’t think the is the answer you are looking for, but DCS is a much better option for what you are trying to do.
BMS is focused on a dynamic situation.
DCS is focused on scripted missions, which is exactly what you are describing.

Hello,

i know, that the BLU 107 in normal case is used in CCIP mode.

But i tested a TE the CCRP mode at FL 200 and it works. My problem is, that it not work inside a Korea campaign with the TGP mode. Only with a
TE i can drop the bombs in combination with CCRP and TGP. I do the same steps inside the campaign, but the BLU 107 dont drop.

Only if i “tms up” the runway with the FCR, the BLU 107 will be dropped inside the campaign. But not in TGP mode.

What could be the reason, that it not work inside a campaign?

Regards
Marvel

I would like to see the Longevity criteria changed though… 100 missions without getting shot down. Ok, that’s easy to do if you fly very reserved like I had to do. But I hated the fact that if you lost a wingman or a jet from within the package your score would reset. Man I do remember it taking me a couple years to get that medal.

Shouldn’t the Longevity be specific to the player only?

@Red:

I do believe that in official korea, links = roads as i have never seen a convoy or vehicules not following roads.

Well this is totally not the case.
By design and by theory this can’t be done.

one way to be certain is to check you station-ILS file. I dont have balkans installed but find the carrier you are looking for in that file and it should look something like this.

in this case 13 is the TCN, 226300 is UHF and 116300 is VHF and 11110 is ILS

USS CARL VINSON CVN70

25 13 X 999 100 1 226300 116300 0 0 11110 0

@marvel_master:

It is possible, that this feature is a little bit bugged?

Regards,
Marvel

no its not “possible”, it is sure !

Fantastic job mate !!! 😄

Yes it needs silicon lube. There is porbably some left at the bottom of the stick shaft inside the cover, remove the bottom cover and spread some of that around. Or buy some. I tried lots of different lubes but reallly the stock lube is best, either buy it or spread the existing one around.

@Agave_Blue:

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.

Great. It works. 🙂

Thanks a lot.

Best regards,
Marvel

WOW, … so many ugly and outdated 3D models …

Cheers,
LS

Its a manual bombing reticule. you set up your SMS for a manual release, set the depressed reticule to the correct setting in mils for your release profile, and fly your release profile. When the solution is reached (correct speed, altitude and dive angle, reticule on target), pickle to release bombs, and recover to straight and level.

You first need to know the ballistics data for bombs in Falcon, and you have to guesstimate a bit to use it as the depressed reticule is not of fine enough resolution for actual use. Once you have ballistics data for the bombs, you can create a table of depression setting vs dive angle, speed and altitude, to use in order to select a profile before flight.

Given its limitations, its not used much at present. Its there as a backup incase the bombing computer (the MMC) or the HUD fail, and as at present in BMS if the HUD fails both the standard and the backup reticule are not selectable, you cannot use it as a backup in BMS either.

Basically unless you specifically want to make a manual release, there are better options for pretty much every situation in falcon.

EDIT: I understand the Multi Command Handbook included in your BMS install under Docs/Operational Documents has quite a bit of information on manual bombing, which may prove of interest to you.