Shuenix Posted February 24, 2021 Posted February 24, 2021 (edited) I get the autolase fail sometimes. I wonder if I am doing anything wrong. Here are a trackfil from latest fail: https://www.dropbox.com/s/0i5n5we0cc3fq6v/4YA_Syria_Capture_Bases_BLUE_v25C-20210224-180238.7z?dl=0 Shuenix Edited February 24, 2021 by Shuenix
Ramsay Posted March 2, 2021 Posted March 2, 2021 On 2/24/2021 at 5:33 PM, Shuenix said: I get the autolase fail sometimes. I wonder if I am doing anything wrong. It usually happens when you haven't setup the weapon profile/auto-lase correctly. I see you setting up auto-lase in the profile but am not sure it "took" correctly i.e. was loaded to the current weapon profile. Unfortunately as it's a MP track, I can't take "control" and check the profile after it failed. i9 9900K @4.8GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 11 Pro x64, Odyssey G93SC 5120X1440
ED Team BIGNEWY Posted March 2, 2021 ED Team Posted March 2, 2021 As mentioned above double check the settings on the weapon profile. I have not been able to reproduce this unless the profile is incorrect. thank you Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal
Tippis Posted March 2, 2021 Posted March 2, 2021 (edited) Also, remember that depending on how you select your weapons (direct selection on the DSMS vs. specifically activating a profile vs. cycling through them on the HUD), they may use the default settings rather than the profile you've set up. The default won't autio-lase, so that would be my first go-to guess: you're sometimes selecting the weapons delivery profile you've set up, and sometimes you're accidentally selecting the weapon with default options instead, and this is causing the intermittent behaviour. Edited March 2, 2021 by Tippis ❧ ❧ Inside you are two wolves. One cannot land; the other shoots friendlies. You are a Goon. ❧ ❧
Shuenix Posted March 2, 2021 Author Posted March 2, 2021 Does it mean that multiplayer tracks is no good? The error is rare, I think I have had it 3-4 times. My guess is that it is 1 out of 30-40 times. I am flying the A10 a lot and have dropped a lot of GBU's, so I am familier with it. I am pretty sure the settings where OK. I do know that changing via HUD can cancel the settings, but it shouldn't give the "Autolase fail" right? I will post if it turns up again. CU
Tippis Posted March 2, 2021 Posted March 2, 2021 As a general rule, it shouldn't, but I have had instances where the settings got mixed up by switching back and forth between profiles, and that might contribute to the issue. It's as if the swap-out doesn't quite clear previous settings (or only some of them) under certain circumstances. And of course, a mix of settings can quite easily lead to the the thing simply not being configured properly and might cause the issue where, as mentioned earlier, it doesn't quite “take”. ❧ ❧ Inside you are two wolves. One cannot land; the other shoots friendlies. You are a Goon. ❧ ❧
ED Team BIGNEWY Posted March 2, 2021 ED Team Posted March 2, 2021 I had another look at the track, it looked to me you made changes to the profile but did not select it? I could be wrong. I wasnt able to take control to check it in this track. Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal
QuiGon Posted March 3, 2021 Posted March 3, 2021 (edited) Just in case: Apart from weapon profile issues, auto lase can also be caused by extended flaps! Speaking from experience Edited March 3, 2021 by QuiGon Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit DCS Panavia Tornado (IDS) really needs to be a thing!
Shuenix Posted March 4, 2021 Author Posted March 4, 2021 Just had another one. Four GBU10's only weapons on the wings. Flaps up and gear up, checked settings twice, firm press on release button (TM Warthog) and I have no reason to believe there is a fault there. If I am making an error, I don't have a clue what it should be. https://www.dropbox.com/s/k0sm5tntmx2nc7o/4YA_Caucasus_Capture_Base_v136B-20210304-120622.7z?dl=0 See you up there
Shuenix Posted March 4, 2021 Author Posted March 4, 2021 Ran the repairtool and tried again. Same error again with GB10. Mods: Scratchpad and SRS. Had the eroors occasionaly before both mods.
ED Team BIGNEWY Posted March 4, 2021 ED Team Posted March 4, 2021 Still unable to reproduce here, can I ask you to check this mission, target at waypoint 1 make sure you are editing the active profile. autolase test.miz Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal
QuiGon Posted March 4, 2021 Posted March 4, 2021 3 hours ago, Shuenix said: Just had another one. Four GBU10's only weapons on the wings. Flaps up and gear up, checked settings twice, firm press on release button (TM Warthog) and I have no reason to believe there is a fault there. If I am making an error, I don't have a clue what it should be. https://www.dropbox.com/s/k0sm5tntmx2nc7o/4YA_Caucasus_Capture_Base_v136B-20210304-120622.7z?dl=0 See you up there I watched your trackfile and couldn't see anything particulary wrong that might have caused the autolase fail. I noticed that you were playing on a multiplayer server though, with some scripted JTACs being active. That reminded me of some cases where I too got the autolase fail and wasn't sure why, because for me it seemed to always happen when another player in my vicinity was already lasing on the same laser code. I wasn't able to definitely check that, but maybe there is some conflict that causes a autolase fail in the A-10C if there is already another laser active in the vicinity and on the same laser code? Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit DCS Panavia Tornado (IDS) really needs to be a thing!
afof Posted March 7, 2021 Posted March 7, 2021 Autolase fail can happen for a few reasons. No point/area track which is the case for your fail. your tgp is slaved to stpt but not tracking so the laser can not fire. you can tell by the large cross. always make sure you have a point/area track. other reasons are related to the countdown timer which is what the autolase is using to determine when to fire. for example, shooting a mav before dropping a bomb means the auto lase will try to use the mav timer and that will cause a fail. make sure the timer shows the predicted fall time and not counting down for other weapons. lastly, there are other rare reasons that i could never figure out but there is a failsafe way to prevent a fail. watch the tgp at the bottom next to the laser code, if you have a flashing A next to the code the laser is not ready to fire. and on another note, as others have suggested, dont edit or select weapons directly through the DSMS page. instead use the profile page and hotas DMS commands to select profiles. 1
Shuenix Posted March 7, 2021 Author Posted March 7, 2021 On 3/4/2021 at 3:05 PM, BIGNEWY said: Still unable to reproduce here, can I ask you to check this mission, target at waypoint 1 make sure you are editing the active profile. autolase test.miz 9.17 kB · 3 downloads I am afraid I got the fail again. When I read afof's post, below. I am getting confused. What am I excactly doing wrong? I edit the weapon, checks it and parameters looks good and saved. What is wrong?
afof Posted March 7, 2021 Posted March 7, 2021 to be less confusing, your tgp is not tracking anything so it cannot lase. you need to press TMS up with the TGP as SOI before you drop the bomb.
Nealius Posted March 8, 2021 Posted March 8, 2021 20 hours ago, afof said: and on another note, as others have suggested, dont edit or select weapons directly through the DSMS page. instead use the profile page and hotas DMS commands to select profiles. This sounds like a bug. Surely selecting through DSMS or HOTAS shouldn't affect whether autolase works or not, right? When using GBU-54s I select them through the DSMS due to the reported bug of them not guiding correctly when selected through HOTAS, but that's an old report and I haven't seen any updates in regards to whether it's been fixed or not. Last night with my first attempt to drop GBU-54s with auto lase, point track, no flashing A, selected through DSMS, they failed to lase. 1
afof Posted March 8, 2021 Posted March 8, 2021 (edited) 3 hours ago, Nealius said: This sounds like a bug. Surely selecting through DSMS or HOTAS shouldn't affect whether autolase works or not, right? When using GBU-54s I select them through the DSMS due to the reported bug of them not guiding correctly when selected through HOTAS, but that's an old report and I haven't seen any updates in regards to whether it's been fixed or not. Last night with my first attempt to drop GBU-54s with auto lase, point track, no flashing A, selected through DSMS, they failed to lase. Selecting through DSMS should not affect autolase if set up correctly, it's just a bad habbit since it opens a big window for user error. I think the bug with selecting through hotas is not about guidance but about CCRP invalid problem. By failed to lase do you mean an autolase failed message appeared or just that the laser never fired. for autolase to work you need a solid A, if it's flashing or doesn't appear at all you wont get autolase. iv'e yet to see autolase fail with a solid A. anyway for the case of the author it is a user error. Edited March 8, 2021 by afof
Nealius Posted March 8, 2021 Posted March 8, 2021 6 hours ago, afof said: Selecting through DSMS should not affect autolase if set up correctly, it's just a bad habbit since it opens a big window for user error. I think the bug with selecting through hotas is not about guidance but about CCRP invalid problem. By failed to lase do you mean an autolase failed message appeared or just that the laser never fired. for autolase to work you need a solid A, if it's flashing or doesn't appear at all you wont get autolase. iv'e yet to see autolase fail with a solid A. anyway for the case of the author it is a user error. I don't believe I had an A at all appear. I distinctly recall setting lase time to 15s, but I may have missed the auto lase on/off.
Shuenix Posted March 11, 2021 Author Posted March 11, 2021 On 3/7/2021 at 2:57 PM, afof said: to be less confusing, your tgp is not tracking anything so it cannot lase. you need to press TMS up with the TGP as SOI before you drop the bomb. Thnx, did not notice that.
Shuenix Posted March 11, 2021 Author Posted March 11, 2021 On 3/8/2021 at 10:49 AM, afof said: By failed to lase do you mean an autolase failed message appeared Yes, thats the case. ED must know what triggers that fail, right? In that case it would be nice to know what could trigger it.
Shuenix Posted March 11, 2021 Author Posted March 11, 2021 On 3/8/2021 at 6:55 AM, Nealius said: This sounds like a bug. Surely selecting through DSMS or HOTAS shouldn't affect whether autolase works or not, right? . Exactly my thoughts.
QuiGon Posted March 11, 2021 Posted March 11, 2021 On 3/8/2021 at 6:55 AM, Nealius said: This sounds like a bug. Surely selecting through DSMS or HOTAS shouldn't affect whether autolase works or not, right? You're wrong. If you select weapons directly on the DSMS page they will get activated with default settings (meaning no auto lase), whereas when you use your HOTAS you don't select weapons, but the configured weapon profiles, which are then being used (with autolase if you have configured such a profile). Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit DCS Panavia Tornado (IDS) really needs to be a thing!
Tippis Posted March 11, 2021 Posted March 11, 2021 2 hours ago, QuiGon said: You're wrong. If you select weapons directly on the DSMS page they will get activated with default settings (meaning no auto lase), whereas when you use your HOTAS you don't select weapons, but the configured weapon profiles, which are then being used (with autolase if you have configured such a profile). ^ This. Note that the even DSMS itself makes a distinction between going into the profile menu and activating one of the setups listed there, and picking some random dangly bit hanging off one of the pylons. It's really more that activating profiles through the DSMS is such a faff that you almost always want to do it via HOTAS instead. 1 ❧ ❧ Inside you are two wolves. One cannot land; the other shoots friendlies. You are a Goon. ❧ ❧
QuiGon Posted March 11, 2021 Posted March 11, 2021 1 hour ago, Tippis said: ^ This. Note that the even DSMS itself makes a distinction between going into the profile menu and activating one of the setups listed there, and picking some random dangly bit hanging off one of the pylons. It's really more that activating profiles through the DSMS is such a faff that you almost always want to do it via HOTAS instead. ^ This as well! Or to put it in some other words: If you select the weapons directly from the stations on the DSMS main page, you won't be able to use your autolase weapon profile. If you instead go to the profiles subpage of the DSMS mainpage, you can activate your autolase profile (provided you have created one before) and use autolasing. Using the HOTAS does the same thing, it cycles through your weapon profiles. Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit DCS Panavia Tornado (IDS) really needs to be a thing!
Recommended Posts