4.33 Issues (Known or not)
-
-
Focal,
That’s awesome
Didn’t know the actual fuzes inside the bomb could be damaged vs just the pylon, ect. Once again impressed by the level of detail.
-
Focal,
That’s awesome
Didn’t know the actual fuzes inside the bomb could be damaged vs just the pylon, ect. Once again impressed by the level of detail.
new since 4.33
How much G did you pull before the release sequence? In 4.33 damage is better implemented and over-G can cause faulty fuzes and in worse cases even hung stores.
-
Also JFYI, Maverick sensors (head glass) can and will be damaged if exceeding a certain speed limit within rain… Makes it more interesting now yea?
-
Also JFYI, Maverick sensors (head glass) can and will be damaged if exceeding a certain speed limit within rain… Makes it more interesting now yea?
Lol come on now! That’s just too much hahaha. Really makes me smile that all of this is at our fingertips now vs 4.32 it’s like a dream sim. Again I say, this is not your fathers Falcon 4.
-
Hello everyone,
I just had time to fly with F-18 on 4.33. But i also had some issues. I took images of problems. Unfortunately wasn’t able to record video. Biggest problem is glitching F-18 on the carrier. I practicing landing and takeoff on Carrierlanding mission in TE. I was Sting11. Basically F-18 glitched under the carrier a little. But problem solved when i took the hook up. Another problems are ATC problems. These problems happaned to me and also other planes. Tower says “descent altitude xxx etc.” and after that it is saying “orbit for spacing”, but the planes are not changing their aproach course. So its doesn’t cause a problem with traffic but i just wanted to report that. 3rd problem is about HUD, some of the indicator are not fitting in. They are overflowing. Also HUD is generally too bright. BRT switch doesn’t do the effect that i want to. I can’t even see something on the HUD sometimes(even when i dont look at the sun, or when the sun is at my 6 o clock). I didn’t have much time to test properly F-18 but these are the issues that i found. Here the some of the images that i took:
-
im experiencing an odd bug in the SP Tiger Spirit campaign. munitions not exploding when they hit the ground. tested with general purpose bombs, cbus, laser guided, gps guided, you name it.
Every single time i enter 3d world, the first place i drop bombs, they explode (no matter how many i drop), fast forward few minutes later, and EVERY single bomb i drop afterwards (corect procedure, tried zero time fuze and so on) will NOT explode. It will impact the ground and nothing happens. Is the Tiger Spirit campaign maybe bugged?would appreciate any help. thanx!
Papaedit: same bug in rolling spirit campaign and in TEs
i must be cursed or something… -
@mhm:
Hello everyone,
I just had time to fly with F-18 on 4.33. But i also had some issues. I took images of problems. Unfortunately wasn’t able to record video. Biggest problem is glitching F-18 on the carrier. I practicing landing and takeoff on Carrierlanding mission in TE. I was Sting11. Basically F-18 glitched under the carrier a little. But problem solved when i took the hook up. Another problems are ATC problems. These problems happaned to me and also other planes. Tower says “descent altitude xxx etc.” and after that it is saying “orbit for spacing”, but the planes are not changing their aproach course. So its doesn’t cause a problem with traffic but i just wanted to report that. 3rd problem is about HUD, some of the indicator are not fitting in. They are overflowing. Also HUD is generally too bright. BRT switch doesn’t do the effect that i want to. I can’t even see something on the HUD sometimes(even when i dont look at the sun, or when the sun is at my 6 o clock). I didn’t have much time to test properly F-18 but these are the issues that i found. Here the some of the images that i took:
known issue…will not be solved before 3 to 4 weeks
-
-
nope, not over g-ing. but problem is not releasing munitions, its the kaboom part once bomb reaches the ground!
-
nope, not over g-ing. but problem is not releasing munitions, its the kaboom part once bomb reaches the ground!
Fuses can be affected by over g now too… caught me out once or twice.
-
nope, not over g-ing. but problem is not releasing munitions, its the kaboom part once bomb reaches the ground!
1. Over G = increased risk of bomb fuze being damaged, as has already been pointed out.
2. Insufficient Arming Delay = bombs don’t have time to arm before they hit the ground/target.Next time it happens check your Max G since RESET in the bottom left corner of your HUD and see just how many G’s you have pulled. G limit is in your LOADOUT screen.
-
taotoo, Darkman thank you! thats it, the damn over G. now i can continue getting my ass kicked in campaigns.
-
Not a big thing, but I noticed that the F16 Aggressors can no longer equip AIM-7’s, while the regular Block 30/32 still can carry them on 3/7 pylons. Would be nice if the next update gave the AGRS the -7F/M again, preferably on 3/7 and 2/8, like it was in 4.32.
-
Has there been a change to squadron supplies? On a day two OCA strike, I noticed I had been loaded with 600gal wing tanks and an ALQ-131. Upon investigation, I saw that my squad is out of 370gal wing tanks and ALQ-184 jammers. Completely out! The wing bags I can kind of see, though I never jettison them I guess if my wingmen are scattering them all over Korea they would start to deplete (but still hard to believe we would be completely out of them). But the jammers? Those should only be lost if the aircraft is lost, and we’ve only had a couple of those. Osan’s ammo dump is fully intact and no evidence of any stores being destroyed on the ground. I’m at a loss of where all my supply has gone. Any idea what’s going on?
-
Hi guys.
Well today i was checking/testing the beautiful skin by Burak of VFA-103 for F-18D and i found this issue, see below:These 2 specific “things” are related with the landing gears! When i retract them, they simply disappeared. When i drop them, they appeared!
Checked this also with the default skin of F-18D.
Can we have it fixed in the 1st update?
Thanks in advance.
Nikos. -
Hi guys.
Well today i was checking/testing the beautiful skin by Burak of VFA-103 for F-18D and i found this issue, see below:http://i8.photobucket.com/albums/a40/neystratiou/VFA-103_skin.jpg
These 2 specific “things” are related with the landing gears! When i retract them, they simply disappeared. When i drop them, they appeared!
Checked this also with the default skin of F-18D.
Can we have it fixed in the 1st update?
Thanks in advance.
Nikos.did you test with default install without skin mod ?
-
did you test with default install without skin mod ?
Affirmative dear friend.
I checked in default Korea theater with NO extra mods/skins! Only clean BMS 4.33.
My only add ons are the ITO theater and now the Ikaros theater that is an extracted via zip file, so it is under control of no affect my installation.
Please take a look and you will see it, in model F-18D Hornet.
Nikos. -
Ok I’ve seen this problem like three times now. All MP missions with basic 4.33 install. I use TARGET for programming of my WH setup and a very slightly modified BMS-full.key from the default 4.33 install. I never saw this problem with 4.32. I am not sure what triggers it as I can go full MP flights without seeing this problem or I can see it a few times in a single flight. Other than BMS itself the only programs in use are Teamspeak, TrackIR, MFDE in server mode, G15Viper to display DED on the G13/15, and TARGET. The exact same software I was using on 4.32. BMS is running in windowed mode with a separate computer/monitor displaying extracted MFDE displays.
The problem is that it seems the window focus can change at some point and for some reason this changes how BMS sees commands given via the WH/TARGET. Two examples are if it happens after landing and I try to turn on my NWS that doesn’t turn on NWS but changes HUD intensity. Trying to talk (I think it was on VHF) didn’t trigger the VHF transmit button but acted like TMS down and changed my SOI. Hitting alt-tab then mouse selecting BMS fixes this problem until it decides to change focus again. Very odd.
-
Sounds like reverso-buttono problem from out of order devices. I think you’ll find that these mixed up controls are exactly 32, 64, 96, etc. button numbers apart.