4.33 Issues (Known or not)
-
Can anyone check if the skyguard appears in HAS mode?
If not, is it a known bug? -
Then I’m sure your mixed controls are related in terms of ctrl-shift-alt modifiers. TARGET is notorious for screwing up key press and release for key combos. Failing that it’s some crazy buffer overflow making a pseudorandom association.
Ok just a brief reply here as Frederf had nailed it right from the start. Not a BMS issue but a TARGET issue. Posted the issue here ~> https://www.benchmarksims.org/forum/showthread.php?25951-TARGET-and-keyboard-modifiers-(shift-alt-control) as that is the correct forum for that issue if interested. If not then BMS on.
-
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.
Welp sad to say this problem came back last night right after landing in a MP mission. I thought Frederf’s advice had nailed it as after removing the three commands that used all three modifiers the problem went away for a week. I don’t see how TARGET could be the issue now as I am not using any more modifiers than I was with 4.32 and I flew well over 1000 hours in 4.32 and never saw this problem once. The only things that have changed is my key file (I use a modified bms - full.key file from the new 4.33 install), my .tmc file for TARGET (I modified my 4.32 file to match the key commands of the new key file) and 4.33 versus 4.32. The fix still hasn’t changed as all I need to do to fix it is to alt tab back into 4.33 then the commands work fine again. If TARGET was losing it’s mind and locking in another modifier I don’t see how alt-tabbing back to 4.33 would change or fix anything.
The only other thing that is even remotely related is my version of MFDE in use is newer on 4.33 than was in use on 4.32. Other than that I run everything the same as I did for 4.32. BMS in windowed mode. MFDE in server/client mode. G15Viper to display the DED on my G13. Teamspeak3, TARGET, and TrackIR5. None of the last four bits of software required any changes to work with 4.33.
Another thing I noticed that almost guarantees this has nothing to do with TARGET is that not only am I temporarily losing my ability to control the avionics via the Warthog but that the G13 that I am using to sub as an ICP also does not work when this problem crops up. That has nothing to do with TARGET at all and is controlled via the Logitech gaming software. Wonder if my 4.33 install is corrupted now somehow as I just did a MP TE which was nothing more than formation work and touch and gos and this damned problem happened no less than 6 times in that one TE. Most of the time I would see this only once in a flight.
-
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