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.
-
I post my video again about the known issue of the “Harrier-Shaking bug”.
-
it happens to me too… it even managed to flip once…i thought it was from rough landing…
-
I have not used the Harrier yet, but interesting to know that there might be a bug associated with that. I believe many issues are being addressed as I speak. But for now, we need to AGAIN, be patient with any new issues this new version has. The devs have been hard at work to give us a new sim with extraordinary features. There are bound to be issues. For now, I would say work around it and give the devs some much needed down time. Being patient thus far has proven good works come from it.
-
Harrier shaking bug is a bug known before release
it happens on weak systems where FPS are low on airbases…
this will be fixed in U1 , the tricky part is that i can not reproduce it on my rig since i can not run 4.33 below 40 fps…
-
Harrier shaking bug is a bug known before release
it happens on weak systems where FPS are low on airbases…
this will be fixed in U1 , the tricky part is that i can not reproduce it on my rig since i can not run 4.33 below 40 fps…
Thanks Mav,
Any info regarding changing the 2D pit FOV?
-
I’d like to throw in a possible texture bug. SA-2, SA-3, and SA-5 have no skins. They are just gray models. The SA-4 has a “skin” but looks like it was misapplied.
-
I’d like to throw in a possible texture bug. SA-2, SA-3, and SA-5 have no skins. They are just gray models.
Not a bug. (model don’t have textures (yet))
-
I have communication menu issue. When I call tower by typing “T”. Sometimes, number of command 2,3 are overlapped, or a command is not fully displayed.
How can I explain that? The bottom command line is half disappeared? When I chose command 2 request. I say abort landing.
I though the command has sub commands like refuling. reloading something like that. But abort landing! -
I have communication menu issue. When I call tower by typing “T”. Sometimes, number of command 2,3 are overlapped, or a command is not fully displayed.
Comms box size issue relative to your resolution. We are working on that problem (was the same in 432)
-
I have communication menu issue. When I call tower by typing “T”. Sometimes, number of command 2,3 are overlapped, or a command is not fully displayed.
How can I explain that? The bottom command line is half disappeared? When I chose command 2 request. I say abort landing.
I though the command has sub commands like refuling. reloading something like that. But abort landing!Hi there mate.
Well if you mean exactly the below situation:
Then you have probably the dpi resolution at your monitor above 100%.
Try to lower that setting (or set it 100%) and you will fix it ;).
Nikos. -
Hi there mate.
Well if you mean exactly the below situation:Then you have probably the dpi resolution at your monitor above 100%.
Try to lower that setting (or set it 100%) and you will fix it ;).
Nikos.Hi! Yes, exactly. I think you have a right solution to fix this. However, I didn’t have this problem with 4.32 version.
I think I should wait until next patch as Dee-Jay mentioned. or have to follow your way until the patch is released.
Thanks! -
Hi! Yes, exactly. I think you have a right solution to fix this. However, I didn’t have this problem with 4.32 version.
I think I should wait until next patch as Dee-Jay mentioned. or have to follow your way until the patch is released.
Thanks!That is correct. I also had no that specific issue in BMS 4.32, but now i have ;).
Since Dee-Jay said that will gonna be fixed, it will.
Until then, just keep it in mind as a temporary solution, it is confirmed by me.
Nikos. -
1. what happened to the old keystrokes; the expanded ones are different and now I am unable to figure out how to lock the target with keyboard (num lock) cursors in HAD and radar modes please advise asap.
It also appears that saved settings revert back to defaults including labels, weapons effects and messages for example. -
1. what happened to the old keystrokes; the expanded ones are different and now I am unable to figure out how to lock the target with keyboard (num lock) cursors in HAD and radar modes please advise asap.
It also appears that saved settings revert back to defaults including labels, weapons effects and messages for example.RTFM and learn to use TMS
-
Not sure if this is covered in the manual, only read ca 70 pages yet, I noticed in the UI (mission and missions schedule) the “show names” feature is not available in my install and ancient rig.
Not a big deal though. -
Since Dee-Jay said that will gonna be fixed, it will.
Dee-Jay didn’t said that it will be fixed, he said that DEV are working the problem. Maybe not to be expected for the next patch.
-
This post is deleted! -
I don’t know what is the problem, but I can’t control the view in the game via mouse or keyboard.
I tried both version 32 and 64 bit but the problem is same.
I use default full key set .And no connected joystick or other periferia on the PC except keyboard+mouse.In the advanced control menu It is work but in game not. I tried shift+4,6,2,8, and right mouse button to look around in the cockpit, but it isn’t work.
But I can use the scroll button to lean left or right
I have no joystick now, becouse it is in serviceI would like to learn the game until , but I can’t now.
PC spec:
AMD 965x4
HD4850 1gb
8gb RAM
Asrock 970ext4
USB laser mouse -
I assume you think that’s a helpful response yet frankly if you can’t help please don’t tell me to RTFM. @Mav-jp:
RTFM and learn to use TMS