4.33 Issues (Known or not)
-
Nope as I said this also kills my input from the G13 which is run from the Logitech software and not TARGET. The only thing I need to do is alt tab and re-select BMS 4.33 and it works again. So TARGET and Logitech are still running just fine when the problem occurs. It is just that 4.33 isn’t seeing it correctly for some reason.
Ok I am cautiously optimistic that I found the culprit here. It hasn’t been a full week yet and the last time I had thought I had found it for some odd reason it took a week to come up again. Just for pure irony’s sake it came back the very first flight after I claimed it defeated…
So the problem is indeed somewhere between TARGET and BMS but it is a very specific problem. You have a few ways of delivering keyboard commands to TARGET. Two of the ways are pulsed commands (where it just needs to see the input and the length of the input isn’t a factor) and non-pulsed commands where you might need long presses to get a job done ala TMS up, NWS button, IFF in/out, UHF/VHF transmit, etc. etc. Well it looks like the kicker is if there is any modifier on a non-pulsed command that particular modifier can get stuck in the on position which is why all of the commands after are thrown for a loop. Something about alt tabing back to BMS 4.33 would cause it to be un-stuck and things would be fine until another modifier would get stuck via a un-pulsed command containing a modifier.
I looked back at my 4.32 TARGET file and sure enough there weren’t any non-pulsed commands which had modifiers. I have done a lot of MP flying since the hopeful fix without issue but as I said earlier Murphy timed it well last time so this time it is hopefuly optimism of a real fix.
-
I am not sure if it was mentioned already (this thread has 55 pages) but I want to post a little bug:
F/A-18C and her loadout. There is no possibility to have 2 x Mk83 on one pylon:
https://upload.wikimedia.org/wikipedia/commons/b/b3/F-18C_VFA-81_in_flight_during_Gulf_War_1991.JPEG
http://www.mawdecals.com/creightonsmodels/HornetsNest/Ordnance.html
-
Hi,
for training purposes I placed in a TE some Jangwey frigates and blocked them in place in open sea (KTO on 4.33.1). These are not visible in SEA mode but only in GM mode (KF-16c 52).Added a second task force but I let it free to move this time and regularly is detected in SEA mode but invisible in GM (and tbh i sould have tried also GMT but I didn’t).
-
Hi guys.
Well I don’t remember if we post that issue in the past, so my apologies if yes.
Still in version 4.33 U1 when we select at T.E. builder an airport to take off, we get the nearest one instead of the chosen one.
See below photo where I click on Seoul airbase and I got Suwon airbase:
I hope in the next update to be solved this.
Thank you.
Nikos. -
Regarding the TGP and auto-lasing: I’ve had a few occasions where the TGP lases for the entire TOF, rather than just the 20 seconds I have it set for. I’m dropping in CCRP with a bomb TOF definitely longer than lase time. When I pickle, the laser fires as normal until bomb release, but instead of shutting off until 20 seconds pre-impact, it just stays on. I’m trying to determine exactly when it happens and I think it may be tied to dropping within the bracket rather than holding pickle until the release cue falls. I have yet to confirm that however.
That is actually a feature and not a bug sir. Read the manual for the tgp and you’ll see what I mean by that
Sent from my SM-G900F using Tapatalk
-
Hi guys.
Well I don’t remember if we post that issue in the past, so my apologies if yes.
Still in version 4.33 U1 when we select at T.E. builder an airport to take off, we get the nearest one instead of the chosen one.
See below photo where I click on Seoul airbase and I got Suwon airbase:I don’t think it’s a bug either.
The point you click on the map when adding a flight or package is supposed to be the target.
The departure airbase depends to the squadron assigned to the package. If you chose a squadron that was placed on seoul, then your flight will depart from seoul.
You must of course place squadron before creating package for this to work correctly -
That is actually a feature and not a bug sir. Read the manual for the tgp and you’ll see what I mean by that
Sent from my SM-G900F using Tapatalk
If it’s a feature then why was it fixed in U1?
@U1:
Fix for Auto lasing sometimes kicking too early after LGB drops.
From:
https://www.benchmarksims.org/forum/showthread.php?26567-Falcon-BMS-4-33-U1-Full-Installer
-
Here Iron Fortress Campaign at autosave shows wrong intel; the north had already invaded and now blue forces pushing back north: no “imminent invasion” as start of campaign was Pohang to Kunsan the rest overrun.
Same campaign I hit Red airbase Kimpo
get court-martialed because some of the components are still listed as blue:
something is wrong there.
-
Video tutorial from friend cougar56th adding the F-16C 52+ HAF cockpit to the default database. for correct RWR AN/ALR-93 (V) 1
it is good to be fixed in feature BMS 4.x version
-
The EA-18G’s hard-points are completely FUBAR. The EA-6B’s hard-points are fine, though.
-
Was there any change in 4.33.1 regarding LGB dropped in pairs? I used to do this often and it used to work in 4.33 and before (if I remember correctly), but now the first bomb is accurate, but the second isn’t. Is it done by purpose? What’s the best way (if any) to drop LGBs in one pass?
-
Was there any change in 4.33.1 regarding LGB dropped in pairs? I used to do this often and it used to work in 4.33 and before (if I remember correctly), but now the first bomb is accurate, but the second isn’t. Is it done by purpose? What’s the best way (if any) to drop LGBs in one pass?
No problem from my end. Possibly the laser is cut out before the last LGB impacts,so that would be the first thing to look at.
Could you please give more info on the release settings ? -
The configuration is rather simple - I have two bombs and drop them both in pair (with one release pulse). They should impact in the same moment therefore, but only one of them impacts on the target.
-
The configuration is rather simple - I have two bombs and drop them both in pair (with one release pulse). They should impact in the same moment therefore, but only one of them impacts on the target.
How are you confirming one hit ?
Are you using the weapon external view , or ACMI ?
What does the debrief show ? 50% hits ? -
I base on debrief show. It shows 50% hits.
-
Does the debrief say the first one destroys the target, or damages? If destroyed, the sim might register the second bomb as a miss cause the target is already registered destroyed ?
-
It should register hits after the target is destroyed as being ‘damaged’. Shouldnt be misses.
-
Dunno if it has been posted - I do not see it for 4.33 U1: The waypoint 2 bug is still there in TEs:
When you plot a flight, there is always an unnecessary waypoint offset until the flight heads to its destined target/mission area:This also leads to AI flying offset before heading towards enemy positions e.g.
I recall this was not the case in 4.32 and older Falcon versions.
Correct me if I’m wrong. -
Dunno if it has been posted - I do not see it for 4.33 U1: The waypoint 2 bug is still there in TEs:
When you plot a flight, there is always an unnecessary waypoint offset until the flight heads to its destined target/mission area:This also leads to AI flying offset before heading towards enemy positions e.g.
I recall this was not the case in 4.32 and older Falcon versions.
Correct me if I’m wrong.you ar wrong this is on purpose.
DeeJay will explain but this is like in real life
-
It should register hits after the target is destroyed as being ‘damaged’. Shouldnt be misses.
Didn’t know that, thanks!