4.33 Issues (Known or not)
-
Autonomous approach is a silent intermediate segment until joining the “FAF” (to borrow instrument approach terminology). It says I know how to get to the final approach point myself, shut up until I get there and then take over as normal. Like Mav says the initial to overhead landing is quite incompatible with a self-vectored approach as you won’t fly to the “FAF” and land normally and incur the same treatment as you flew a standard approach and went overhead tactical as you’re vectored to final.
You might get lucky asking for landing at approximately the perch position and ATC confuses the latter half of your overhead as arriving normally.
-
Would it be safe to say, that by waiting until on final after the OHB, and then calling in Autonomous approach, will allow you to land w/o the go-around call or getting bitched at by ATC?
Sorry for the question, but I’ve actually found ATC vectors work quite a bit better than in 4.32 and haven’t really messed w/ Autonomous approaches except in emergency situations. I’m flying out of Osan and don’t really need the OHB because of the E/W orientation of the runway.
-
okay you missed one important point, well actually this one is not documented enough probably
When you request autonomeous approach, that means you are not vectored
BUT , when you are in a final lined up position, the TOWER CLEARS you to LAND ….if you dont land after that, and you perform a break for instance…then you are considered like rejected landing and explused from queue…
In case you want to make break approahc like this, you must indeed ask autonomeous landing when starting break , not when you will be in a position to be on final from ATC POV…
got it ?
Could it be feasible to add a tower command to turn on the lights, without an approach? At night time with no moon, it is hard to find the airport with no NVG in OHB formation in the city, so we turned on the lights with autonomous approach. Then after the break, the lights go off again, and then we had somebody have to do a go-around anyway due to not finding the runway, but then they also had to request autonomous approach during all of this.
-
Well the thing is a bit messed up, or the sequence is written somewhere and we missed it.
We where on a break. The lead asked for autonomous before the break, we never show lights going on or off. They where off all the way.
I asked for land option 1 but still lights off. I cancelled and asked for autonomous still lights off.
In the mean time ppl where landing, I was number 4. -
ok enough
-
dont ask autonomous approach before the break else you will be kicked of after beeing cleared for landing.
-
airbases lights are working fine. your report is very isolated… try yo reproduce with reliable pattern
-
-
We have a problem with IVC server/client. Background - in our online squadron we work with human ATC who is using the F4Awacs tool from the OSC. In 4.32, the ATC only connected as client to the opened IVC server and transmitted via F1,F2 and F3 to the pilots in the game but is not committing to BMS. In 4.33 we used the same procedure but as soon as the pilots are in the 3D world the ATC can only hear them but cannot transmit into the game or is not heard. On the IVC server window you can see that the ATC is transmitting/pushing the buttons but nothing is heard in the 3D game. We have tested the communication with the IVC server/client only without launching BMS - everything is fine. When the pilots then launch to the UI it still works but when in 3D, the connection to the ATC is lost and he can only listend to the pilots on all frequencies (UHF, VHF and Guard).
Any idea what the issue can be? Why is it working on 4.32 but no longer in 4.33?Thanks,
EuKeule -
Any idea what the issue can be? Why is it working on 4.32 but no longer in 4.33?
Yes, it worked in 4.32 but it’s no longer the case in 4.33.
You need to have a flight your ATC can commit to (AWACS or JSTARS are perfectly fine), he can stay in 2D but must be on board.
I personally tested it with my squadron and it worked like a charm, so no big deal after all… -
BMS Manual p251-2 Radio Filter.
-
Thank you for this advice. This is what I was looking for.
We setup a “IVC Client.ini” with the commandline “outsiders = all”, as recommended in the manual. (For human ATC and Pilot)
But unfortunately it is still not working, so anything else to consider? -
Hi everyone.
I noticed an issue when i turn my TGP on, both in TE or in campaign. So when i want to turn TGP on i lean my head to see the OSB, i hit it and then the screen darkens for a little fraction of second, like while taking a photo with a camera, and when I lean my head backwards, outside a caopy i see something like a cockpit frame as if it appeared when my head was forward. And this frame moves outside with my head movement. This makes a TGP impossible to use. It happens also with WPN page when I carry missiles which can display any kind of video on the MFD.
I have NVidia Geforce 660, intel i-5, windows 7, and FaceTrackNoir.
Please help me -
First of all thanks to all the people who have worked on BMS and especially on the new update, you made me very excited again!!!
I would like to point out a few things that I ran into when trying out the f-18:
-Wings fold / unfold graphical issue.
When doing multiplayer, I sometimes can’t see the wings of my co-player unfold. He sometimes can’t see the wings of an E-2 unfold, while I can. It is sometimes and I have not been able yet to isolate the problem better. We have the same graphics settings, but his card is different.- Hud display does not fit in the hud (F-18)
This has already been mentioned but I don’t think there was a response, so I’ll just confirm it. The sides of the hud display are clipped because they don’t fit. I believe there is a track-ir related work-around. Too bad for people who don’t have track-ir I guess.
Thanks again, now I am going to send in some tank bats to the front manually and provide cas :):):)
- Hud display does not fit in the hud (F-18)
-
okay you missed one important point, well actually this one is not documented enough probably
When you request autonomeous approach, that means you are not vectored
BUT , when you are in a final lined up position, the TOWER CLEARS you to LAND ….if you dont land after that, and you perform a break for instance…then you are considered like rejected landing and explused from queue…
In case you want to make break approahc like this, you must indeed ask autonomeous landing when starting break , not when you will be in a position to be on final from ATC POV…
got it ?
So in conclusion:
If you want to do an overhead approach you are fine during the day, just call for autonomous after the break (near the perch seems to work).If you want to do an overhead approach at night, you are maybe out of luck since it can be hard to find the field without the lights.
So I would say: unless a command is added to have the lights switched on, only do overhead breaks during day, and use straight in approaches at night?
Sounds workable to me
-
Does emergency Landing help solving this problem? I know it’s a trick that someone would like to avoid to keep it as real as possible, but if it works as some years ago it will solve this problem
-
So in conclusion:
If you want to do an overhead approach you are fine during the day, just call for autonomous after the break (near the perch seems to work).If you want to do an overhead approach at night, you are maybe out of luck since it can be hard to find the field without the lights.
So I would say: unless a command is added to have the lights switched on, only do overhead breaks during day, and use straight in approaches at night?
Sounds workable to me
I mean, just request the autonomous approach twice, once at 29 miles and once after you pass the threshold, it’s not that bad.
-
@Bellc09:
I mean, just request the autonomous approach twice, once at 29 miles and once after you pass the threshold, it’s not that bad.
Can do that too I guess, you’ll just get the “go around contact ATC for vectors” call as you pass over the numbers at 1500 ft to the break.
-
Can do that too I guess, you’ll just get the “go around contact ATC for vectors” call as you pass over the numbers at 1500 ft to the break.
Yeah, that’s exactly what I do. Once I’m lined up at the initial, I press T to call up the menu, as soon as the tell me to go around, call for a second approach. Wham, bam, thank you ma’am, cleared for landing on short final. The queuing with AI can be weird, because it’s not designed for the overhead, but if all else fails, declare an emergency
-
Hi everyone.
I noticed an issue when i turn my TGP on, both in TE or in campaign. So when i want to turn TGP on i lean my head to see the OSB, i hit it and then the screen darkens for a little fraction of second, like while taking a photo with a camera, and when I lean my head backwards, outside a caopy i see something like a cockpit frame as if it appeared when my head was forward. And this frame moves outside with my head movement. This makes a TGP impossible to use. It happens also with WPN page when I carry missiles which can display any kind of video on the MFD.
I have NVidia Geforce 660, intel i-5, windows 7, and FaceTrackNoir.
Please help meI found out what to do, it is because i use nvidia 3d vision. When you plan to switch TGP on, you must first temporarily switch 3d off (default ctrl+t) and after tgp on, turn 3d back on.
-
Greetings guys
I have a problem with annoying AWACS massage spam in 2d map when im preparing for a mission,it keep on saying the same 2-3 massages all over and over again and dont whant to shut up.Is anyone notice that thing or is just my problem?.
Anywey BMS 4.33 is on new level now,damm is so beautiful,if someone tells me i be play sim like that when i fly FIgthter Bomber 24 years ago haha,cheers all. -
I found out what to do, it is because i use nvidia 3d vision. When you plan to switch TGP on, you must first temporarily switch 3d off (default ctrl+t) and after tgp on, turn 3d back on.
Sorry for bothering you again, guys, it seems like it didn’t help.
I turned 3d vision off globally. Now every time I want to use tgp or wpn page, when I click dedicated OSB, I get what I had mentioned earlier. Here is an example. In Tactical Engagement I pressed TGP. The image darkened for a fraction of a second and after that a canopy frame appeared. Next the same when i hit WPN page. Any clues what to do?EDIT. This what you see, moves with my head movement, outside a canopy. Sometimes after the click the image gets totally black and only interior of a cockpit is seen.It depends on what I currently see in a virtual cockpit when i click the OSB.
-
Ive got an issue with the Tomcat on the carrier. I’ve made my own TE to ty to run the F-14 from the carrier, part of a 2 ship. It loads 4 mins from STP 1 arrival time, cant start on runway. With me so far? Here’s the fun part. Within 1 min of me being placed in the pilots seat the jet rocks back and forth & drops to the deck smoking or explodes. I tried restarting the TE, same result. Tried switching aircraft position. Same result. Tried changing mission clock time closer to TO, same thing. When i viewed it from the exterrior I see one of the MLG collapse, the jet rocks to that side, then the other side collapses.
Ok. Maybe I did something. Deleted the TE & crafted another. Different location. Tried all 4 listings for the Tomcat; the A, B, Agressor A, & the D. Start at taxi time-4 mins from TO. Again within a few seconds my jet nails the tarmac. It only happens to my Tomcat, no other flight member has that issue. For sanitys sake I tried the Hornet launch and trapping again, the Hornet has no issue for me in this reguard.
Im thinking of having the Hanger Queen tagged OOS for carrier ops until further notice, pending a test flight from an airbase may cause all wings of Tomcats to be grounded until further notice.
Ideas?