ebabil Posted July 3, 2023 Posted July 3, 2023 Hi When I try to deploy durandals, the azimuth steering line is shown on the side of the HUD and doesn't align with the designated point. I don't see it with other ammunition. Is it a bug? 1 FC3 | UH-1 | Mi-8 | A-10C II | F/A-18 | Ka-50 III | F-14 | F-16 | AH-64 | Mi-24 | F-5 | F-15E| F-4| Tornado Persian Gulf | Nevada | Syria | NS-430 | Supercarrier // Wishlist: CH-53 | UH-60 Youtube MS FFB2 - TM Warthog - CH Pro Pedals - Trackir 5
dorianR666 Posted July 3, 2023 Posted July 3, 2023 4 hours ago, ebabil said: Is it a bug? yes, its completely broken. i tried designation via "3." and later via tgp, both failed this way: cdip too (here selected via autoacq aft) but it happens with other weapons too here is mk84 with chute, designation is on the right side but asl on the left 3 CPU: AMD Ryzen 5 1600X GPU: AMD RX 580
ebabil Posted July 3, 2023 Author Posted July 3, 2023 thanks for the support. I hope it will be addressed soon FC3 | UH-1 | Mi-8 | A-10C II | F/A-18 | Ka-50 III | F-14 | F-16 | AH-64 | Mi-24 | F-5 | F-15E| F-4| Tornado Persian Gulf | Nevada | Syria | NS-430 | Supercarrier // Wishlist: CH-53 | UH-60 Youtube MS FFB2 - TM Warthog - CH Pro Pedals - Trackir 5
NightstalkerNOR Posted July 3, 2023 Posted July 3, 2023 I had the same issue flying just now. Dropping to low altitude fixed the line on top of the designated target. I believe I was below 400ft AGL just above treetop height. It's logical to me that these bombs work like that considering they immediately drop a parachute to align with the ground before launch, but I am not sure if they are supposed to though... Try flying at treetop height
NightstalkerNOR Posted July 6, 2023 Posted July 6, 2023 On 7/3/2023 at 9:54 AM, ebabil said: Hi When I try to deploy durandals, the azimuth steering line is shown on the side of the HUD and doesn't align with the designated point. I don't see it with other ammunition. Is it a bug? Have you tried my suggestion above?
shagrat Posted July 6, 2023 Posted July 6, 2023 (edited) Flying at treetop level shouldn't be required to get a ASL on the target in AUTO mode. It should work the same at 50ft, 500ft or 15,000ft. Especially it should not jump from one side of the HUD to the other (happened to me). I could reproduce that weird behavior. This pretty sure looks like a bug. Edited July 6, 2023 by shagrat 2 Shagrat - Flying Sims since 1984 - Win 10 | i5 10600K@4.1GHz | 64GB | GeForce RTX 3090 - Asus VG34VQL1B | TrackIR5 | Simshaker & Jetseat | VPForce Rhino Base & VIRPIL T50 CM2 Stick on 200mm curved extension | VIRPIL T50 CM2 Throttle | VPC Rotor TCS Plus/Apache64 Grip | MFG Crosswind Rudder Pedals | WW Top Gun MIP | a hand made AHCP | 2x Elgato StreamDeck (Buttons galore)
Sirbum Posted July 6, 2023 Posted July 6, 2023 (edited) with the durandales you have to be less than 750 AGL. I posted this same bug in this fourm a few weeks back, and was told about the 750 AGL. Another words anything that is retareded needs to be dropped low in order for the line to work correctly. Is it intended this way? not sure but it is how it is Edited July 6, 2023 by Sirbum
shagrat Posted July 7, 2023 Posted July 7, 2023 (edited) vor 9 Stunden schrieb Sirbum: Is it intended this way? not sure but it is how it is Why should the ASL to help you steer TO the target if the TGT diamond is outside the HUD be working different in the F-15E than in any other of the western aircraft (A-10C, F/A-18C, F-14, F-16C especially)? Btw same behavior for retarded or none retarded ordinance in all other aircraft. The ASL is provided to help the pilot align with the TGT point and is independent from height. Especially weird (and wrong) is the fact the ASL is sometimes jumping sides... Just think about a run-in through valleys in mountainous terrain, trying to align and pop up over mountain ridges with your steering cue (ASL) all over the place while evading terrain. This is a bug, not intentional. Maybe also related to this: https://forum.dcs.world/topic/329347-asl-wind-correction-incorrect/ Edited July 7, 2023 by shagrat 1 Shagrat - Flying Sims since 1984 - Win 10 | i5 10600K@4.1GHz | 64GB | GeForce RTX 3090 - Asus VG34VQL1B | TrackIR5 | Simshaker & Jetseat | VPForce Rhino Base & VIRPIL T50 CM2 Stick on 200mm curved extension | VIRPIL T50 CM2 Throttle | VPC Rotor TCS Plus/Apache64 Grip | MFG Crosswind Rudder Pedals | WW Top Gun MIP | a hand made AHCP | 2x Elgato StreamDeck (Buttons galore)
Mistermann Posted July 7, 2023 Posted July 7, 2023 Had this happen with my group last night with GBU-10's and GBU-12's. Super frustrating but feel much better now that I see this threads. Will see if I can reproduce and get a track. System Specs: Spoiler Callsign:Kandy Processor:13th Gen Intel(R) Core(TM) i9-13900K - RAM: 64GB - Video Card: NVIDIA RTX 4090 - Display: Pimax 8kx VR Headset - Accessories: VKB Gunfighter III MCG Ultimate, VKB STECS Standard, Thrustmaster TPR Pedals, Simshaker JetPad, Predator HOTAS Mounts, 3D Printed Flight Button Box Video Capture Software: Open Broadcaster Software (OBS), Video Editing Software: PowerDirector 365 Into The Jungle Apache Campaign - Griffins Kiowa Campaign - Assassins Thrustmaster TWCS Mod
Bosun Posted July 7, 2023 Posted July 7, 2023 I've also noticed that my unguided ordnance, spawning on a single player with 0 wind, 0 direction at all altitudes, will not reliably strike within a mile of target until I get below 10,000ft on Auto. I think the Auto-mode may need some work.
INDY69 Posted August 20, 2023 Posted August 20, 2023 I have the same issues with Auto and CDIP releases. This picture is after ASL fails in Auto I swap to CDIP.
DST Posted September 1, 2023 Posted September 1, 2023 With the bugged ASL most of the time in every AUTO bombing mode (guided or unguided, with or without Tpod or Laser) and the sometimes bugged CDIP-pipper behaviour it seems like there is not a single AG delivery method that is actually working properly at the moment. I really think RAZBAM should have baked this module a bit longer in in the oven, or at least should have communicated clearly from the beginning, that those systems do not work properly. Instead there are tutorial videos for all this stuff that don't mention any bugged behaviour, I myself had the impression, that this basic Air Ground stuff is implemented and working, that is why I bought the module. RAZBAM's take on "early access" is still a great annoyance and disappointment for me, something I never had with any other ea module, especially not ED's modules, where there was always clearly communicated what is implemented and working, and what is missing and will be completed in the future. I7 8700K 3.7 GHz 32GB RAM NVIDIA RTX 3080 Rift S
INDY69 Posted September 1, 2023 Posted September 1, 2023 (edited) DST that is the most frustrating thing about this module imho. There should be at least 1 consistent method for A/G employment (lvl, dive, or loft in AUTO or CDIP) with non-coordinate dependent weapons. The bombing triangle is very simple to calculate if you know where everything already is in the environment (not true in the real world), especially no wind with a known altitude and airspeed at release. Ah well, patience is a virtue.... hopefully they stop working on liveries and fix this major problem soon. Edited September 1, 2023 by INDY69
WizzRD Posted September 2, 2023 Posted September 2, 2023 10 hours ago, DST said: With the bugged ASL most of the time in every AUTO bombing mode (guided or unguided, with or without Tpod or Laser) and the sometimes bugged CDIP-pipper behaviour it seems like there is not a single AG delivery method that is actually working properly at the moment. Well, it´s working "properly" for me as I´m dropping bombs left and right with no problems. Thus it´s certainly nothing that´s as easy to fix as a bug that everyone sees/ has and, most importantly, can be reproduced.
beacon Posted December 17, 2023 Posted December 17, 2023 On 9/2/2023 at 9:41 AM, WizzRD said: Well, it´s working "properly" for me as I´m dropping bombs left and right with no problems. Thus it´s certainly nothing that´s as easy to fix as a bug that everyone sees/ has and, most importantly, can be reproduced. stillnot fixed when i select the cbu97 asl line is over target but bombs never hit the target
WizzRD Posted December 17, 2023 Posted December 17, 2023 2 hours ago, beacon said: stillnot fixed when i select the cbu97 asl line is over target but bombs never hit the target I have to admit that I havn´t dropped a single CBU-97 in the F-15E - until today. As this also (like the BLU-107) worked fine for me you really should provide the good folks at RAZBAM a short track file of what you are doing, so they can check and maybe fix whatever the problem might be.
beacon Posted December 18, 2023 Posted December 18, 2023 14 hours ago, WizzRD said: I have to admit that I havn´t dropped a single CBU-97 in the F-15E - until today. As this also (like the BLU-107) worked fine for me you really should provide the good folks at RAZBAM a short track file of what you are doing, so they can check and maybe fix whatever the problem might be. ill test tonight i forgot to set the height to 1200ft
beacon Posted December 19, 2023 Posted December 19, 2023 i just used the cbu97 and added the height. i never bombed so many targets. was a long flight and works only with the cbu97 . blu107 just does not work with the asl line
Deano87 Posted December 20, 2023 Posted December 20, 2023 I've had zero problems deploying the BLU-107 in both Auto and CDIP. The one thing that made all the difference for me was changing the BOT (Bomb on Target) Option, This is found in the top right of the AG armament page after you've set up the ripple of the BLU-107. What this does is change the point in the ripple that the HUD symbology is targeting for, by default it set to CTR which means the jet is trying to give you release info for the center of the string of bombs. This causes many problems with bombs that have a very short fall time, like the BLU-107 or any of the retarded bombs. Changing this setting to 1, which means the jet is giving you aiming symbology for the first bomb in the string makes everything much more predictable. I've had no issues since changing this setting. Of course if you're using Auto mode you should place the target point at the beginning of the runway, not the center. Proud owner of: PointCTRL VR : Finger Trackers for VR -- Real Simulator : FSSB R3L Force Sensing Stick. -- Deltasim : Force Sensor WH Slew Upgrade -- Mach3Ti Ring : Real Flown Mach 3 SR-71 Titanium, made into an amazing ring. My Fathers Aviation Memoirs: 50 Years of Flying Fun - From Hunter to Spitfire and back again.
Burner1111 Posted January 5, 2024 Posted January 5, 2024 (edited) Very new F15e flyer, learning weapon deployments. I cannot deploy BLU-107 at all in both Auto or CDIP, it fells very very short! Seems like calculation of release is off or the bomb opens the parachute and rocket too early. TPOD is correctly designated, lased but even with CDIP it does not work (piper on the beginning of the runway). Also in the end of the runway, it fails. I used the BOT=1 but no joy. I cannot find any good instructions nor limitations, if I'm deploying these wrongly. Does somebody have the same issue? Is it bugged? Edit: i think the issue is with the release countdown, as it releases before reaching to the correct distance. e.g mk82 slicks or airs are releasing correctly, near on top of the runway. tried CDIP with mk84 air, worked. so, for me it seems blu-107 is bugged. Edited January 5, 2024 by Burner1111 Intel Core i7 9700k, MSI MEG Z390 ACE, 2 x 16GB HyperX DDR4 Fury, RTX 2080Ti, Corsair PSU RM750, Samsung SSD 970 Evo Plus + SSD 860 EVO (DCS), NZXT CPU cooler Kraken X62, Fractal Design R6 black. Thrustmaster Hotas Warthog, Thrustmaster F-18 HOTAS, RealSimulator FSDB-R3 Lighting, Sim Gears F-16 ICP LT, 3x Thrustmaster MFD's, TrackIR5, VoiceAttack+Vaicom PRO, DCS UFC app in Samsung 10" tablet.
Recommended Posts