Jump to content

Recommended Posts

Posted

Tested on a few missions since patch. Appears to persist in single and multi player. Am I missing something? I was under the impression the GBU 24 has slightly better range as well. 

 

I get the DLZ, release about midway, the bomb falls way short.

Release angle is zero, auto lase is set to 15 seconds.

GBU24 borked.trk

  • Like 1

Computer: I7 12700K OC 5.0 All Cores, EVGA 3070TI FTW 3, MSI Tomahawk Z690 DDR4 WIFI, 64 GB Corsair DDR4 3600 MHz, M.2 NVME 3TB

Gear: Virpil T-50CM2 Mongoose Stick, CM3 Base, CM3 Throttle, Logitech Pedals, HP Reverb G2

Modules: F-15E, F-18C, F-16C, F-14, A-10C II, AV-8B, M-2000C, Mirage F1, F-5, AH-64D, MI-24, KA-50, Nevada TTR, Syria, Persian Gulf, Falklands, Sinai, Afghanistan 

Posted
19 minutes ago, Fulcrumkiller31 said:

auto lase is set to 15 seconds

Here's your user error. A GBU-24 needs to be lased right from the start, otherwise it won't know where it's going and will just glide ahead. It should probably be falling long, but maybe it sees the laser and does something stupid trying to get at it. The increase in range is in large part because this bomb is smarter than older LGBs, so it needs to see the laser in order to compute its trajectory.

Posted
29 minutes ago, Dragon1-1 said:

Here's your user error. A GBU-24 needs to be lased right from the start, otherwise it won't know where it's going and will just glide ahead. It should probably be falling long, but maybe it sees the laser and does something stupid trying to get at it. The increase in range is in large part because this bomb is smarter than older LGBs, so it needs to see the laser in order to compute its trajectory.

I will test that out, and report

Computer: I7 12700K OC 5.0 All Cores, EVGA 3070TI FTW 3, MSI Tomahawk Z690 DDR4 WIFI, 64 GB Corsair DDR4 3600 MHz, M.2 NVME 3TB

Gear: Virpil T-50CM2 Mongoose Stick, CM3 Base, CM3 Throttle, Logitech Pedals, HP Reverb G2

Modules: F-15E, F-18C, F-16C, F-14, A-10C II, AV-8B, M-2000C, Mirage F1, F-5, AH-64D, MI-24, KA-50, Nevada TTR, Syria, Persian Gulf, Falklands, Sinai, Afghanistan 

Posted (edited)

Still fell well short. Tried again and waited until I was halfway through the DLZ, it barely had enough energy to hit the target. 

GBU24 borked2.trk

 

Edited by Fulcrumkiller31
  • Like 1

Computer: I7 12700K OC 5.0 All Cores, EVGA 3070TI FTW 3, MSI Tomahawk Z690 DDR4 WIFI, 64 GB Corsair DDR4 3600 MHz, M.2 NVME 3TB

Gear: Virpil T-50CM2 Mongoose Stick, CM3 Base, CM3 Throttle, Logitech Pedals, HP Reverb G2

Modules: F-15E, F-18C, F-16C, F-14, A-10C II, AV-8B, M-2000C, Mirage F1, F-5, AH-64D, MI-24, KA-50, Nevada TTR, Syria, Persian Gulf, Falklands, Sinai, Afghanistan 

Posted (edited)

Definitely something wrong with GBU24, it is falling way too short, I had a drop with auto lasing set at 12 sec, and when lasing started the bomb was falling short so it did catch the laser but it couldn't reach the target. (released inside DLZ)

I was planning to test too, I'll do it when I have time.

Edited by Furiz
Posted
11 hours ago, Dragon1-1 said:

Here's your user error. A GBU-24 needs to be lased right from the start, otherwise it won't know where it's going and will just glide ahead. It should probably be falling long, but maybe it sees the laser and does something stupid trying to get at it. The increase in range is in large part because this bomb is smarter than older LGBs, so it needs to see the laser in order to compute its trajectory.

I can’t find any documentation stating the GBU 24 needs laser energy immediately. In fact I read the opposite.

 

either way it still doesn’t work !

Computer: I7 12700K OC 5.0 All Cores, EVGA 3070TI FTW 3, MSI Tomahawk Z690 DDR4 WIFI, 64 GB Corsair DDR4 3600 MHz, M.2 NVME 3TB

Gear: Virpil T-50CM2 Mongoose Stick, CM3 Base, CM3 Throttle, Logitech Pedals, HP Reverb G2

Modules: F-15E, F-18C, F-16C, F-14, A-10C II, AV-8B, M-2000C, Mirage F1, F-5, AH-64D, MI-24, KA-50, Nevada TTR, Syria, Persian Gulf, Falklands, Sinai, Afghanistan 

Posted

Have you checked at laser DED page if the code it´s correct? Now if you hot start laser code is 0 and you have to change it.

GBU-12 works fine but i tried CBU-97 on TOSS bombing and it allways fall short too, tried on tanks at waypoint 3 on Persian Gulf instant mission hot start take off, tried from differents bearings and alwais the same, so no wind problem

NZXT H9 Flow Black | Intel Core i5 13600KF OCed P5.6 E4.4 | Gigabyte Z790 Aorus Elite AX | G.Skill Trident Z5 Neo DDR5-6000 32GB C30 OCed 6600 C32 | nVidia GeForce RTX 4090 Founders Edition |  Western Digital SN770 2TB | Gigabyte GP-UD1000GM PG5 ATX 3.0 1000W | SteelSeries Apex 7 | Razer Viper Mini | SteelSeries Artics Nova 7 | LG OLED42C2 | Xiaomi P1 55"

Virpil T-50 CM2 Base + Thrustmaster Warthog Stick | WinWing Orion 2 F16EX Viper Throttle  | WinWing ICP | 3 x Thrustmaster MFD | Saitek Combat Rudder Pedals | Oculus Quest 2

DCS World | Persian Gulf | Syria | Flaming Cliff 3 | P-51D Mustang | Spitfire LF Mk. IX | Fw-109 A-8 | A-10C II Tank Killer | F/A-18C Hornet | F-14B Tomcat | F-16C Viper | F-15E Strike Eagle | M2000C | Ka-50 BlackShark III | Mi-24P Hind | AH-64D Apache | SuperCarrier

Posted (edited)

Upon further testing. The issue seems to lie with the bombs not seeing the laser when dropped from max DLZ above 15000 ft. 

With a 10 degree loft- bombs capture laser

wait a bit to around 10-12 miles bombs capture laser. 

24k ft level drop from around 14 miles M 1.2, bombs don't see the laser until they are ballistically too low to make the target (although they try).

Below 15k feet, I have a few successful hits, bombs glide like they are suppose to, but sometimes one of the two bombs never catches the laser.

Some SME feedback on discord confirms this, these bombs are pretty complicated, there is a lot more to it than dropping in the DLZ. 

 

Although I still feel like there might be some wrong behavior. 

GBU24 odd behavior.trk

Edited by Fulcrumkiller31

Computer: I7 12700K OC 5.0 All Cores, EVGA 3070TI FTW 3, MSI Tomahawk Z690 DDR4 WIFI, 64 GB Corsair DDR4 3600 MHz, M.2 NVME 3TB

Gear: Virpil T-50CM2 Mongoose Stick, CM3 Base, CM3 Throttle, Logitech Pedals, HP Reverb G2

Modules: F-15E, F-18C, F-16C, F-14, A-10C II, AV-8B, M-2000C, Mirage F1, F-5, AH-64D, MI-24, KA-50, Nevada TTR, Syria, Persian Gulf, Falklands, Sinai, Afghanistan 

Posted (edited)

I have the feeling they were not primarily made to be self lased, whats the point of letting it glide for miles when you still have to get within laser range of your own laser. Might as well drop it late then. 
 

would need to test a buddy lasing scenario (or with a JTAC) to see how it behaves

edit: did some quick research online, have to correct my statement of its use case. 
 

made specifically for low level use, should not be affected by early lasing. 
 

Was an interesting read: https://www.globalsecurity.org/military/systems/munitions/gbu-24.htm

Edited by Moonshine
Posted

"However, if the LGB guidance system detects reflected laser energy from the target designator too soon after release, it tends to pull the LGW down below its required trajectory and the bomb will impact well short of the target."  I think it totally depends on launch parameters when you should lase. good read indeed. Check out my above track.

Computer: I7 12700K OC 5.0 All Cores, EVGA 3070TI FTW 3, MSI Tomahawk Z690 DDR4 WIFI, 64 GB Corsair DDR4 3600 MHz, M.2 NVME 3TB

Gear: Virpil T-50CM2 Mongoose Stick, CM3 Base, CM3 Throttle, Logitech Pedals, HP Reverb G2

Modules: F-15E, F-18C, F-16C, F-14, A-10C II, AV-8B, M-2000C, Mirage F1, F-5, AH-64D, MI-24, KA-50, Nevada TTR, Syria, Persian Gulf, Falklands, Sinai, Afghanistan 

Posted (edited)

Yeah saw that too. Weird how it says it shouldnt be affected by early lasing and then it states this paragraph 😂
 

This bomb is not nearly as delivery parameter sensitive as is the Paveway II LGB, nor is it affected by early laser designation.

Paveway III hurt itself in confusion 

Edited by Moonshine
Posted
21 minutes ago, Moonshine said:

Yeah saw that too. Weird how it says it shouldnt be affected by early lasing and then it states this paragraph 😂
 

This bomb is not nearly as delivery parameter sensitive as is the Paveway II LGB, nor is it affected by early laser designation.

Paveway III hurt itself in confusion 

 

Lol it is certainly odd, wish I didn’t get the immediate cannot reproduce tag. something is clearly off.

Computer: I7 12700K OC 5.0 All Cores, EVGA 3070TI FTW 3, MSI Tomahawk Z690 DDR4 WIFI, 64 GB Corsair DDR4 3600 MHz, M.2 NVME 3TB

Gear: Virpil T-50CM2 Mongoose Stick, CM3 Base, CM3 Throttle, Logitech Pedals, HP Reverb G2

Modules: F-15E, F-18C, F-16C, F-14, A-10C II, AV-8B, M-2000C, Mirage F1, F-5, AH-64D, MI-24, KA-50, Nevada TTR, Syria, Persian Gulf, Falklands, Sinai, Afghanistan 

Posted (edited)

So this is how GBU-24 behaves,

 

this track is when I lased myself, it was going to fall miles short so I activated laser, (I probably released too early but... the DLZ was ok right?) the bomb picked up and flew directly to target: gbu24 self lase strange flight.trk

 

then I let the auto lase option to do it and it didn't lase on time cause the timers were wrong: gbu24 auto lasing late.trk

 

so this must be cause of que range set too high and we get release que well ahead of time, or we have to lase 1 min early for the bomb to fly correctly, in my test it was falling well away from the point of impact.

Edited by Furiz
Posted (edited)
55 minutes ago, Furiz said:

So this is how GBU-24 behaves,

 

this track is when I lased myself, it was going to fall miles short so I activated laser, (I probably released too early but... the DLZ was ok right?) the bomb picked up and flew directly to target: gbu24 self lase strange flight.trk

 

then I let the auto lase option to do it and it didn't lase on time cause the timers were wrong: gbu24 auto lasing late.trk

 

so this must be cause of que range set too high and we get release que well ahead of time, or we have to lase 1 min early for the bomb to fly correctly, in my test it was falling well away from the point of impact.

 

Yeah same thing on my end. The bomb just takes a nose dive.

GBU24 odd behavior2.trk

Edited by Fulcrumkiller31

Computer: I7 12700K OC 5.0 All Cores, EVGA 3070TI FTW 3, MSI Tomahawk Z690 DDR4 WIFI, 64 GB Corsair DDR4 3600 MHz, M.2 NVME 3TB

Gear: Virpil T-50CM2 Mongoose Stick, CM3 Base, CM3 Throttle, Logitech Pedals, HP Reverb G2

Modules: F-15E, F-18C, F-16C, F-14, A-10C II, AV-8B, M-2000C, Mirage F1, F-5, AH-64D, MI-24, KA-50, Nevada TTR, Syria, Persian Gulf, Falklands, Sinai, Afghanistan 

Posted

I tried it with the hornet and it does the same thing, except the DLZ is much smaller. so it captures the laser. 

Computer: I7 12700K OC 5.0 All Cores, EVGA 3070TI FTW 3, MSI Tomahawk Z690 DDR4 WIFI, 64 GB Corsair DDR4 3600 MHz, M.2 NVME 3TB

Gear: Virpil T-50CM2 Mongoose Stick, CM3 Base, CM3 Throttle, Logitech Pedals, HP Reverb G2

Modules: F-15E, F-18C, F-16C, F-14, A-10C II, AV-8B, M-2000C, Mirage F1, F-5, AH-64D, MI-24, KA-50, Nevada TTR, Syria, Persian Gulf, Falklands, Sinai, Afghanistan 

Posted

PW3 are different than PW2. The weapon should fly in a "bump up" glide to extend its range regardless of laser energy and should arrive to target area (or beyond) if not guided. The weapon has an INS, barometric sensor, digital autopilot. It decides what delivery profile to do based on sensed data on release: loft-level, dive, and I think a third one. It has a break level ceiling of I think 15,000' PA.

  • Like 3
Posted
9 minutes ago, Furiz said:

In other words it shouldn't fall short a few miles?

 

Exactly my point lol. but "can not duplicate" -_-

Computer: I7 12700K OC 5.0 All Cores, EVGA 3070TI FTW 3, MSI Tomahawk Z690 DDR4 WIFI, 64 GB Corsair DDR4 3600 MHz, M.2 NVME 3TB

Gear: Virpil T-50CM2 Mongoose Stick, CM3 Base, CM3 Throttle, Logitech Pedals, HP Reverb G2

Modules: F-15E, F-18C, F-16C, F-14, A-10C II, AV-8B, M-2000C, Mirage F1, F-5, AH-64D, MI-24, KA-50, Nevada TTR, Syria, Persian Gulf, Falklands, Sinai, Afghanistan 

Posted

I know this is a bit OT but I didn't want to start another thread as my question is somewhat related.

Using The GBU 12 I'm finding my bombs are dropping seconds After countdown to release? And still hitting target...Is this normal? or something New I missed?ThankYou in advance.

Patrick

mini.gif

Posted

FYSA this has been recreated both above 15k and below 15k, auto lase and manual lasing through the whole time. Bombs will fall short regardless, fail to capture laser, or capture but fail to pull back up and hit. 

If released near the bottom  half of the DLZ the bomb has a chance to hit. I implore yall to test this for yourself! 

Computer: I7 12700K OC 5.0 All Cores, EVGA 3070TI FTW 3, MSI Tomahawk Z690 DDR4 WIFI, 64 GB Corsair DDR4 3600 MHz, M.2 NVME 3TB

Gear: Virpil T-50CM2 Mongoose Stick, CM3 Base, CM3 Throttle, Logitech Pedals, HP Reverb G2

Modules: F-15E, F-18C, F-16C, F-14, A-10C II, AV-8B, M-2000C, Mirage F1, F-5, AH-64D, MI-24, KA-50, Nevada TTR, Syria, Persian Gulf, Falklands, Sinai, Afghanistan 

Posted

The other thing I haven't seen mentioned yet in this thread but should be remembered in DCS (and may be part of the problem here): the pod lasers in DCS are basically an 8 km (IIRC) long light sabre.  If the tip of this light sabre (or some part of it between the tip and your aircraft) doesn't intersect with anything you get no reflection point and thus nothing for laser guiding bomb/missile to guide on.  If you point it at something 20 km away, the end gets suspended in air part way to target (until you close the range to about 8 km) so gets no guidance.  That would fit with some of the testing above where it seems to ignore it or the case where the laser was activated later (likely after it was in range) rather than at max range for the missile.  As was commented above, if you're trying to launch at max range from altitude you're going to be better off to have buddy lasing occurring.

  • Like 1
Posted

The 24 is such a complex beast that it's basically impossible to reverse engineer the implementation without being intimately familiar with the weapon IRL. There really should be much better documentation as to what exactly is simulated from the different profles in mode 1, otherwise it's going to require hundreds upon hundreds of drops to get some kind of testing data and try to figure out what works and what doesn't. So, in my opinion there should be a clear and comprehensive writeup about the expected implementation and from there we can determine how well it matches up. 

  • Like 1
Posted

Why is this still labeled “cannot reproduce”? 


 

Computer: I7 12700K OC 5.0 All Cores, EVGA 3070TI FTW 3, MSI Tomahawk Z690 DDR4 WIFI, 64 GB Corsair DDR4 3600 MHz, M.2 NVME 3TB

Gear: Virpil T-50CM2 Mongoose Stick, CM3 Base, CM3 Throttle, Logitech Pedals, HP Reverb G2

Modules: F-15E, F-18C, F-16C, F-14, A-10C II, AV-8B, M-2000C, Mirage F1, F-5, AH-64D, MI-24, KA-50, Nevada TTR, Syria, Persian Gulf, Falklands, Sinai, Afghanistan 

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...