4.33 Issues (Known or not)
-
This post is deleted! -
I think the strangest part of my problem is how there is no consistency in when it happens to give me a clue as to what is wrong. Today I was involved with 2v2 BVR setups and we worked through five setups without a single instance of my problem. Yet I can be on a landing practice MP TE and just have it happen over and over again.
-
Does your profile contain any EXEC code or similar? I’ve had scripts run well for long periods of time but seize up when running through more dodgy coding.
-
Does your profile contain any EXEC code or similar? I’ve had scripts run well for long periods of time but seize up when running through more dodgy coding.
Nothing that hasn’t been used for 1000+ hours in 4.32 without issue.
-
FYI, I did run into a problem in a MP flight, where the Warthog wasnt responding anymore. However I dont think this is BMS fault : there was no error displayed in the script, yet I couldnt stop it manually, I had to kill it, and when starting to restart Target, I had a “TM service isnt running, start it manually or start Target as admin”. I did the latter, reran the script, and I could use the Warthog again just fine in the same flight. Just scared the hell of my wingmen
Could that be a similar issue to what’s happening to you ?
-
FYI, I did run into a problem in a MP flight, where the Warthog wasnt responding anymore. However I dont think this is BMS fault : there was no error displayed in the script, yet I couldnt stop it manually, I had to kill it, and when starting to restart Target, I had a “TM service isnt running, start it manually or start Target as admin”. I did the latter, reran the script, and I could use the Warthog again just fine in the same flight. Just scared the hell of my wingmen
Could that be a similar issue to what’s happening to you ?
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.
-
Not sure if this has been mentioned in another thread or not, but figured I’d add it here. During MP campaign, during approach to Osan AB, after autonomous approach call @ 29nm, when at less than 5nm on final approach (straight in) get approval for landing from ATC. As the distance closes, I hear that another flight has been given permission to take off. Then shortly after, my permission to land has been cancelled and I’m to re-request approach approval. This has happened several times, either exactly as I described or, take off approval has been granted to a flight and shortly after, I’m given approval to land, and then approval cancelled and told to abort the approach. I guess ATC still needs some work.
-
Not sure if this has been mentioned in another thread or not, but figured I’d add it here. During MP campaign, during approach to Osan AB, after autonomous approach call @ 29nm, when at less than 5nm on final approach (straight in) get approval for landing from ATC. As the distance closes, I hear that another flight has been given permission to take off. Then shortly after, my permission to land has been cancelled and I’m to re-request approach approval. This has happened several times, either exactly as I described or, take off approval has been granted to a flight and shortly after, I’m given approval to land, and then approval cancelled and told to abort the approach. I guess ATC still needs some work.
ATC is far from beeing finished to revamo is 4.33.
however for your specific problem if you think about it, nothing we can do.
indeed in case of autonomous approach, the ATC has no way to know if you will land in 1minute or 20 minutes because you dont have a’y pattern to follow. therefore in case of autonomous aporoach you are badly inserted in the atc queue and on a busy airfield you will be kicked out from final often…
-
This kind of things also happens in ATC approaches. But I won’t complain about it anyway, it’s already surprisingly fluid as it is.
-
ATC is far from beeing finished to revamo is 4.33.
however for your specific problem if you think about it, nothing we can do.
indeed in case of autonomous approach, the ATC has no way to know if you will land in 1minute or 20 minutes because you dont have a’y pattern to follow. therefore in case of autonomous aporoach you are badly inserted in the atc queue and on a busy airfield you will be kicked out from final often…
Far from being finished I understand, saying that for my situation “there is nothing you can do” is laughable. At my first call for autonomous landing at 29 miles, yes I am an unknown variable. However, once the 5 mile call for final is requested, I am no longer unknown. As to whether or not I’m cleared to land is at ATCs discretion. Once given the clearance to land by ATC @ 5nm or less, I shouldn’t have to worry whether or not another aircraft is going to be cleared to take off when I’m on 5 mile final. That is very fixable.
-
Since you not code it, you cannot say “easy to fix”.
-
Far from being finished I understand, saying that for my situation “there is nothing you can do” is laughable. At my first call for autonomous landing at 29 miles, yes I am an unknown variable. However, once the 5 mile call for final is requested, I am no longer unknown. As to whether or not I’m cleared to land is at ATCs discretion. Once given the clearance to land by ATC @ 5nm or less, I shouldn’t have to worry whether or not another aircraft is going to be cleared to take off when I’m on 5 mile final. That is very fixable.
very fixable is easy to say ROFLMAO
I have tremendous fixes ready (dont expect in update anyway)…which prioritize the final approach queue … making abort the correct aircraft depending on their position and status…but still the interaction between take off queue and landin gqueue is EXTREMLY tricky to handle… next versions will see major improvment but declaring it is very fixable , considering i spent months means:
- i have very poor coding capacities
or
- it is not so easy after all
-
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.