4.33 Issues (Known or not)
-
So far, this has been a fantastic new version of FBMS! However, there will always be some growing pains associated with new software improvements.
For one, I have found that the 2D cockpit FOV can not be changed. Since I do use 2D quite a bit during flights, I have found the FOV to be to close for what I want to see and be able to function in pit when accessing pit functions. 3D pit is fine for FOV settings but is difficult when dealing with specific aircraft functions that are much easier to access in 2D pit. Below is the 2D “in pit” list for FOV.
guidedview 0 0.000000 0.000000 0.000000 -0.000000 1.791412 0.000002 59.999996 0 23 9000 29 18000 1 27000 26 ‘HUD - up once’
guidedview 1 0.000000 0.000000 0.000000 0.000000 -15.621903 0.000000 59.999996 0 0 9000 13 18000 2 27000 9 ‘straight forward’
guidedview 2 0.000000 0.000000 0.000000 0.000000 -36.536102 0.000000 41.999962 0 1 9000 17 27000 3 ‘MFDs - backup instruments’
guidedview 23 0.000000 0.000000 0.000000 -0.000000 28.439116 0.000002 59.999996 0 24 9000 36 18000 0 27000 32 ‘up twice’
guidedview 24 0.000000 0.000000 0.000000 -0.000000 58.439114 0.000001 59.999996 0 25 9000 43 18000 23 27000 40 ‘up three times’
guidedview 25 0.000000 0.000000 0.000000 0.000000 88.439110 -0.000000 59.999996 9000 49 18000 24 27000 46 ‘up four times’In 4.32, I could change the “in pit” FOV by changing the 7th initial value to increase FOV. Like this….
guidedview 0 0.000000 0.000000 0.000000 -0.000000 1.791412 0.000002 89.999996 0 23 9000 29 18000 1 27000 26 ‘HUD - up once’
guidedview 1 0.000000 0.000000 0.000000 0.000000 -15.621903 0.000000 89.999996 0 0 9000 13 18000 2 27000 9 ‘straight forward’
guidedview 2 0.000000 0.000000 0.000000 0.000000 -36.536102 0.000000 41.999962 0 1 9000 17 27000 3 ‘MFDs - backup instruments’
guidedview 23 0.000000 0.000000 0.000000 -0.000000 28.439116 0.000002 59.999996 0 24 9000 36 18000 0 27000 32 ‘up twice’
guidedview 24 0.000000 0.000000 0.000000 -0.000000 58.439114 0.000001 59.999996 0 25 9000 43 18000 23 27000 40 ‘up three times’
guidedview 25 0.000000 0.000000 0.000000 0.000000 88.439110 -0.000000 59.999996 9000 49 18000 24 27000 46 ‘up four times’The 89.999996 field highlited in red changes the FOV for 2D pits in 4.32
4.33 has not effect on changing FOV in 2D pit. This issue may have a solution, but I can not find it. 90* FOV in 2D pit works perfect for me when accessing certain functions. Is there any additional things I need to know or do to enable this?
Also, any other small issues people might be having could be included in this thread. Been reading all of the threads with possible issues so I know what to look for and how to deal with them.
Any fix on this issue? Thanks
Yes I found one: apply same changes “to the 3dckpit.dat in ckptart folder (not the one in the F-16CM-50 folder) then it works even for the F-16CM-50.” -
Hi Folks,
Read the thread, seems a lot has been handled already….awesome, though i found a texture glitch on the Mlu model:
Its on both sides… i hope there is a solution for this…
I know this are the txtrs from Jan Has in the Balkans Theater, but with the new BMS 4.33 txtrs in Korea its same issue and only with the Mlu mdl…Thx in advance…
Grtz,
H!TEC
-
When i try to select radar alt i go from off through standby to on it doesn’t work go back to standby then on and it works. is it just me or is it a bug.
-
When i try to select radar alt i go from off through standby to on it doesn’t work go back to standby then on and it works. is it just me or is it a bug.
hw long do you wait between going from off to stdby & from stdby to on? New in 4.33 is de RDR ALT BIT test, so it takes a short while for bit test before you get an actual readout. You can see RDR ALT BIT test on the MFD test page.
Ref BMS -1 p.53 “1.2.5.1 SNSR PWR Panel”: RALT BIT is implemented and visible from the MFD TEST page (OSB#7). When the radar altimeter is active the radar altitude can be read in the HUD in the box preceded by the letter R. -
When i try to select radar alt i go from off through standby to on it doesn’t work go back to standby then on and it works. is it just me or is it a bug.
Not a bug.
The Radar Altimeter has a warm-up period of about 15 seconds from the time the switch is placed to STBY or ON
The CARA BIT is performed by depressing the OSB adjacent to RALT on the MFD test page. The BIT can be run with RDR ALT switch ON or in STBY.If the BIT is performed with the switch in STBY and the AL setting at 500 feet, the ALOW warning function will be tested.(Flashing AL on HUD and VMS if the aircraft is in flight.
During the BIT, the RALT indication on the MFD will be highlighted and then 300 feet will be displayed beneath it. The BIT takes about 5 seconds for completion -
Thanks, feel a little embarrassed now didn’t see it in manual.
-
Thanks, feel a little embarrassed now didn’t see it in manual.
To be fair,I don’t think the BMS manual goes into detail.
I’m sure Reddog and Darkman will make the needed additions -
Hi all,
I just purchased Falcon 4.0 and have successfully installed the game. I can get through the menus, however as soon as I click “Takeoff” the game completely freezes up and refuses to load.
Here are my system specs:
Windows 10 Home
Intel Core i7-4700MQ
Nvidia GT 750M
8GB DDR3 RamThanks,
Matthew -
Nvm, I figured it out using a fix in this link: https://www.benchmarksims.org/forum/showthread.php?24914-Game-freezes-after-hitting-Takeoff&p=366168&viewfull=1#post366168
-
A couple of issues with Hornets and HARMs using POS mode:
On the f-18c,
The WPN POS page only really functions correctly for HARM’s on stations 3 and 7.
If you want to use more than two HARMs, after the first two missiles have launched you won’t be able to see what you’re doing on the WPN page. Stations 2 & 8 show no prelaunch information below the LSDL, and the top half is occupied by the previous two missile’s info, so no post-launch info either. (Obviously because these are the F-16 avionics, only intended to support two HARMs)
However, if you select a steerpoint and highlight a missile type in POS EOM mode for instance, it appears to still work in the background, hand-off occurs etc…On the Super Hornets,
the WPN POS page is a bit more buggy, but again all the modes still work in the background -
Hello,
one solution for this question could be the following.
1./ Can i see in the cockpit the air brake position? In the F-16 i have on the left
side an indicator. But in the F/A-18C i did not find something similar yet. ……Regards
No - there is no indication of speed brake position in the Hornet other than a light on the upper left brow to indicate BRAKES ……
1. I thought BMS took the eyebrow ‘Brakes’ indicator in the F/A-18C away in v 4.33.1?? ……
Stevie indicates a ‘brakes’ light should be in the left eyebrow. I am certain it was in the original 4.33 release. But now it’s gone in the update (4.33.1.). Maybe it needs to be added back?
https://www.benchmarksims.org/forum/showthread.php?27947-Useful-information-(docs)-for-Carrier-Ops
-
Campaign MP issues
KTO, Rolling Fire Campaign, resuming a SAVED day CAM file. No matter if we have 2 or more players, usually the non-host players have a CTD upon exit. Either the mission freezes with them unable to do anything, OR they can just exit the mission and then it CTDs. It’s not the network going down, and I have 25Mbps up/down. Mission will be just fine with no symptoms until we exit. Host usually doesn’t crash until trying to exit BMS altogether.
In 4.32, most TEs would freeze leaving the cockpit, but campaigns were ok.
Known?
-
@NATOPS:
2.12.10 Angle-Of-Attack (AOA) Indexer. ….
The indexer only operates with the landing gear down, W-off-W, a valid ADC AOA signal and a functional ADC. The lighted symbol(s) flash if the arresting hook is up and the hook bypass switch, on the left vertical panel, is in CARRIER. The symbols do not flash with the arresting hook up and the hook bypass switch in FIELD. The switch is solenoid held to FIELD and automatically goes to CARRIER when the arresting hook is lowered or aircraft power is removed. ….
That would be a nice add. I’m pretty sure it’s not in BMS now.
-
Campaign MP issues
KTO, Rolling Fire Campaign, resuming a SAVED day CAM file. No matter if we have 2 or more players, usually the non-host players have a CTD upon exit. Either the mission freezes with them unable to do anything, OR they can just exit the mission and then it CTDs. It’s not the network going down, and I have 25Mbps up/down. Mission will be just fine with no symptoms until we exit. Host usually doesn’t crash until trying to exit BMS altogether.
In 4.32, most TEs would freeze leaving the cockpit, but campaigns were ok.
Known?
This situation seemed to improve when the host increased bandwidth settings on the server to 20480 and the 2 clients to 4096; however, it’s not completely gone away. Crashes occur 25% of the time versus 100% upon exiting campaign mission.
-
I created a TE using some Crusaders out of Kunsan (Stock KTO), and when taxiing their rear wheels do not touch the tarmac (front wheel seems fine). I can post a screenshot if necessary.
All the best, Uwe
-
Hey, a friend of mine can’t hear the ATC on UHF15 (can’t talk to the ATC, can’t hear the ATC), however we can talk on the same frequency using IVC. He is a Falcon Veteran so it’s definetly not a Noob mistake. I’ve gone with him through his Settings however I was unable to locate any mistake. Any chance that this is a bug?
-
Hey, a friend of mine can’t hear the ATC on UHF15 (can’t talk to the ATC, can’t hear the ATC), however we can talk on the same frequency using IVC. He is a Falcon Veteran so it’s definetly not a Noob mistake. I’ve gone with him through his Settings however I was unable to locate any mistake. Any chance that this is a bug?
Are you mixing channels and freqs? What tower and what freq is your bud trying to use?
Sent from my XT1080 using Tapatalk
-
Are you mixing channels and freqs? No, we both used the same Channels and the same Frequencys. We were using: Amedola, Seosan, Chongju. No luck on those Airbases. However he fixed the Problem. Will tell you tomorrow what his fix was.
-
Flying 4.33.2 multiplayer campaign in KTO. Multiple times, I’ve had my consecutive missions total zero’d out when I haven’t died/crashed, etc. Same with wingies. Moreover, successful RTB for all in the flight. Anybody see this?
-
Maybe 75% of the time when I refuel with AI wingmen, they permanently fly formation with the tanker and refuse to rejoin me…
I say “done refueling” to the tanker after I finish.
Sometimes they refuel then align to the right of the tanker permanently.
Sometimes they don’t refuel at all and align to the right permanently.
If I say “flight rejoin” or “RTB” they acknowledge, then continue to fly with the tanker.