Jump to content

Recommended Posts

Posted

I recently updated A10 v1.1.1.1 to v 1.2.3

 

Ever since the update, my LGBs and WCMDs fail to release at the appropriate launch time. The only exception is the GBU-12. Nothing else launches correctly.

 

In the case of the GBU-12, though, no matter how steep the angle at which I set the markpoint (with laser), the weapon misses by several meters. Anybody have a solution??

 

Everything was right on the mark before I updated. I'm kind of disappointed now.

Posted
In the case of the GBU-12, though, no matter how steep the angle at which I set the markpoint (with laser), the weapon misses by several meters. Anybody have a solution??

 

It might just be the way you worded this, but it sounds to me like you aren't employing the GBU-12 correctly.

 

You can set a markpoint for your own reference, but the GBU-12 has no idea where that markpoint is. The GBU-12 needs the laser from the TGP to guide it. If you haven't setup an auto-lase in the weapon profile, you will need to fire the laser manually once the bomb is ~10secs from impact. It will then track the laser to wherever your TGP is currently pointing. Without an active laser for it to follow, a GBU-12 is just a normal dumb bomb.

 

As for the "nothing else launches correctly". We'll need more information on what you are doing and what the weapons are doing when you try to drop them.

USAF Bomber Avionics Specialist, Ret. (2A5)

 

Water-cooled i7-8700k @ 5.0GHz

Nvidia GTX1080

32 GB DDR4-3200

M.2 NVMe Drive

Warthog HOTAS

Oculus Rift CV1

Posted

Dave, you're right, I worded it incorrectly. Here's what I'm doing:

 

Slaving my TGP to the waypoint where the targets are; finding a target and tracking in the point mode; designating the object as a SPI; autolase configured already in weapon profile; selecting GBU-38 CCRP profile; following the steering cue, holding the weapon release.

 

In every instance, my GBU-38 fails to release. I'm not receiving any error messages. With the GBU-12, using the same setup, the weapon launches correctly, but even though I'm keeping the crosshairs on target, the bomb is missing every time. I wasn't having this problem before I updated. I was using markpoints for my Maverick launces and that works just fine.

 

I've gone back and flown the weapons range mission several times, and where before I was hitting every time with the GBU-38, now I can't even get it to launch, and the GBU-12 is off by several meters.

Posted

If i remember correctly, and this is going back quite a ways..lol. A-10C 1.1.1.1 defaulted the NMSP to EGI. In the newer versions, it's defaulted to HARS and needs to manually be set to EGI once the INS is aligned.

 

If you are not changing that from HARS to EGI, that will cause your JDAM situation. Before you drop any GPS guided bombs, make sure your DSMS page says 'RDY' underneath the weapon. If it says "ALN UNS" then you have an issue with your INS alignment and the bomb will not drop.

 

As for the LGB issue. The only thing i can think of is drop from a medium altitude(10-15k ft) and don't fire the laser too early. Only fire the laser once the bomb is 8-10 secs away from impact. Otherwise it will try to maneuver too much, kill it's energy and won't be able to follow the laser precisely.

USAF Bomber Avionics Specialist, Ret. (2A5)

 

Water-cooled i7-8700k @ 5.0GHz

Nvidia GTX1080

32 GB DDR4-3200

M.2 NVMe Drive

Warthog HOTAS

Oculus Rift CV1

Posted
As for the LGB issue. The only thing i can think of is drop from a medium altitude(10-15k ft) and don't fire the laser too early. Only fire the laser once the bomb is 8-10 secs away from impact. Otherwise it will try to maneuver too much, kill it's energy and won't be able to follow the laser precisely.

This is good for stationary targets, but if the target is moving, start the laser pretty soon after release or the bomb will lose the laser reflection or just not be able to adjust enough at the end.

i7-2600k@4GHz, 8GB, R9 280X 3GB, SSD, HOTAS WH, Pro Flight Combat Pedals, TIR5

Posted

Helo are you holding the bomb release down for about 2 seconds with the 38? Are you waiting for your manual release indication?

 

Also, is this a custom mission you're flying? What I've been finding is you may need to go into the mission file (.miz) and empty it out. If this is an old mission that you're currently using, and you don't know how to do it then I'll post instructions.

"ENO"

Type in anger and you will make the greatest post you will ever regret.

 

"Sweetest's" Military Aviation Art

Posted

@Yellonet - That is a good tip, but i'd still be hesitant to fire very early after release. My auto-lase is set at 10sec 100% of the time. The only time they miss anything is if i have a sloppy run-in.

 

@ENO - He'd be getting a hung store indication if he wasn't holding the release.

 

Seeing as he was doing fine with 1.1.1.1 i'm kind of ruling out the normal "newbie mistakes" here and am willing to bet money on the fact that he's running in HARS mode because that's a functionality change between versions ;)

USAF Bomber Avionics Specialist, Ret. (2A5)

 

Water-cooled i7-8700k @ 5.0GHz

Nvidia GTX1080

32 GB DDR4-3200

M.2 NVMe Drive

Warthog HOTAS

Oculus Rift CV1

Posted

I don't see how version should change startup procedure. I started with 1109 and I've been starting up pretty much exactly the same, with just a few changes to order depending on what side of teh cockpit I was looking at. As to HARS/EGI, isn't it always been the same where you had to let CDU reach 4.0.0.8, then click EGI, then click EAC? I've always done it in that order and other than newbie issue of not holding pickle, never had issue with -38s. As to the -12 not hitting target with the target in the TGP view would mean the laser isn't on OR maybe altitude too low (not sure of that one, but possible I think).

 

We can say "do X" and OP could be telling us he's doing "X", but without a track file we can really only guess what's going on.

Posted

You made me second-guess myself so i went back through the changelogs. The 'HARS selected as default' functionality was actually implemented in 1.1.0.8. So many changes since the early beta days, it's hard to keep track of what happened when anymore..lol.

 

I retract my previous bet :P

USAF Bomber Avionics Specialist, Ret. (2A5)

 

Water-cooled i7-8700k @ 5.0GHz

Nvidia GTX1080

32 GB DDR4-3200

M.2 NVMe Drive

Warthog HOTAS

Oculus Rift CV1

Posted
Still looking at corrupt mission files. If he empties the .miz out and lets the ME rebuild it in 1.2.4 it should work as its supposed to.

 

Thoughts?

 

I would agree. I always open and save mission files in the current version for that very purpose.

 

OP hasn't stated whether or not it's an old mission or if he set up a test in current version.

 

This is why I think there should be a banner at the top of the forum:"Track file or it didn't happen." ;)

  • Recently Browsing   0 members

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