Autolase Failure???

[Injerin]

I've played a few multiplayer missions (Operation Talons Reach being one of them) and no matter what I set my GBU-12's too in the profile I instantly get an Autolase failure as soon as I release the bomb. I set my profile to CCRP, autolase-on and 10-15 laser fire time, I'm normally drop them from 10,000 to 15,000 feet. I have even went and played DRAGON's weapon training and have no problem, the GBU-12's work as intended. I've even tried manual laser fire and it still doesn't work ( in multiplayer games).

 

Has anyone else had this problem? Or can someone please point me in the right direction? Not sure if its a custom mission setting or maybe in my key bindings with game/sim settings in my A-10C module?

[NoCarrier]

I've even tried manual laser fire and it still doesn't work ( in multiplayer games).

You sure you have the laser even on? Keep in mind it's a separate switch to arm it.

[ENO]

Recently I've noticed that my laser code has defaulted to 0000 instead of 1866... (the old stock code) I'm wondering if there's an issue with yours? Check your code at startup and make sure it's programmed through weapon profile.

 

I've been getting code mismatch errors though- so it may be something different.

 

Also, any chance that you have something else prohibiting the laser from firing? Refueling door open by any chance? (long shot but that caused someone else some issues with laser firing as well...)

[Injerin]

I've checked my laser codes through-out. I usually change my codes (1644) via INV and through my TGP so I'm not locking on to friends lasered targets. Its really wierd it happens right as soon as I release the GBU-12. I even seen my GBU-12 do a cork screw to the ground and making radical direction changes like my laser is spinning around lol (as I'm in level flight). And yes I have the laser switch set to arm :lol: Like I said I have tried other missions off-line and everything works properly. Its just the 2 latest missions i've played on-line that it gets screwy. I will be testing more in the morning.

[ENO]

Wonder if the mission builder needs to empty out the .miz file? I've found a bunch of screwy behavior between versions.

[Fakum]

I know this is an old thread, but I experienced a problem last night with this. I had setup a profile for Auto Lase, 10 seconds. Setup 4 targets in a row as markpoints, rolled in on the 1st one with no issue at all,,, turned back in on the 2nd target, as soon as I released the bomb, I got the yellow auto lase failure on both MFCD's,, tried a couple more times with same results. Cycled power off/on to both TGP and laser switch,,, no resolve?

 

So 1st bomb off the rail lazed fine, after that, no good?

[ENO]

Wonder if the laser got masked? Did you enter a turn to keep LOS for the pod or did you just fly straight? What altitude were you at?

[Fakum]

Target did get masked when I eventually turned about to make another run. Was at about 11-15k feet. I tried resetting SPI etc, even went back around and created new mark points on a straight run, even dropped altitude as well a couple times. nothing seemed to be able to eliminate that issue.

[mhe]

Never tried if it makes any difference, but you might have switched from laser to IR pointer with DMS right short? Never tried if autolase is able to override it if you set the TGP pointer to IR, but it's worth a try I think?

[ApoNOOB]

Maybe this is related: On the new version in MP I had twice a problem with my lase. The lase was on, I used it for a while and it worked. I use a different lase code in MP, it was set up in the DSMS inventory, TGP and latch on. One drop was both times successful when the problem occurred.

 

Now after a time when I pressed the lase button, the laser would activate for a few seconds (like without latch) and deactivate. When I switched from LSR to BTH it would stay on, but the bomb would not track.

 

I remember something from way back, that some stuff like the MAVS (?) could get hot and you should turn them off IRL, but this was not modded. Was there maybe some change that I need to turn off my lase/TGP after a while that I am not aware of?

 

The tracks would be of MP games and very long, also I was not able to replicate the problem. Anyone?

 

 

edit: Just to clarify, i didn't use auto lase.

Edited February 20, 2014 by ApoNOOB

[The_Pharoah]

I had an issue with autolase my last time out as well - had set everything up as per usual ie. autolase, latch off, 10 sec, GBU-12..was >FL100 but as soon as it dropped, I got the autolase failure. This was on a server.

 

How do you clear the autolase failure again?

[Fakum]

Never tried if it makes any difference, but you might have switched from laser to IR pointer with DMS right short? Never tried if autolase is able to override it if you set the TGP pointer to IR, but it's worth a try I think?

 

I can not rule that out as a possibility,, I will run the mission again and see what happens and keep that in mind,,,thanks

[Fakum]

I had an issue with autolase my last time out as well - had set everything up as per usual ie. autolase, latch off, 10 sec, GBU-12..was >FL100 but as soon as it dropped, I got the autolase failure. This was on a server.

 

How do you clear the autolase failure again?

 

I never had the issue until recently, so I never knew how to clear it, still dont know yet,,,

[The_Pharoah]

yeah its really crap, because you can't do anything until you clear it ie. it blocks out both MFCDs which is horrible.

[Fakum]

Well. I do hit the acknowledge button, that at least clears the message, but doesn't fix the problem

[Lusik]

It has just come to my mind... Have you tried to set the TGP to 'L' or 'B'? I think you cannot get the laser to fire unless you that is set. I haven't tried this and I won't have time today but give it a shot.

[The_Pharoah]

It has just come to my mind... Have you tried to set the TGP to 'L' or 'B'? I think you cannot get the laser to fire unless you that is set. I haven't tried this and I won't have time today but give it a shot.

 

didn't realise that - maybe thats it. Will give it a go this weekend.

[Fakum]

In my case, I never changed that after the 1st successful run, I cant claim I did not inadvertently change it without my Knowledge either,, I will find some time over the weekend to run the same course,, thanks

[MatzWarhog]

I've noticed a few autolase failures recently, and can't remember if I read it here or saw it on YT, when you set your cross to your target in the TGP, at the lower portion of the screen, the word "Align" will have a flashing "A" like [A]lign (no brackets, but the "A" there is flashing). Barely slewing (any movement) of the Pod, and the "A" becomes solid as in "Align", no flashing "A". After I started assuring the "A" was solid, I have yet to experience "Auto-lase Failure" again. Not sure what's happening or why, but this fixed my issue entirely. HTH

 

Matz

[Fakum]

Thanks for pointing that out, I did see that "A" flashing as well after I recieved the message. I took a run last night in same mission, the difference was, I encountered the same problem with the 1st pickle,, I just walked away at that point, but you have now given me something more to consider,, thanks

[howie87]

*Howie's TGP 101*

 

The flashing A means the TGP is in Area track mode but within a few degrees of being masked if I remember correctly. In Point track mode you'll get a flashing P instead. Obviously when it's in inertial track mode (INR) you can't fire the laser because there is no line of sight (it's blocked by the fuselage/stores). This might be the cause of the autolase failure

 

Area mode is for tracking stationary targets, Point will track a moving target.

 

If you get an autolase failure, clear the warning with TMS left then manoeuvre the aircraft until you get a solid P or A and hold the NWS button to fire manually (or set latch on and press to toggle the laser on/off).

 

Also make sure your TGP is set to either BOTH or (L)aser. IR mode will not work. A flashing L symbol means the laser is firing.

 

I think being too low can also generate an autolase failure if the lase time is set to longer than the bombs time of fall.

Edited February 22, 2014 by howie87

[Fakum]

Ive never encounter any of this in the past. what I have been doing is using the laser to create mark points in the TGP, once I have the 4 targets marked, I switch from Flight plan to Mark Points, select A as my 1st mark point target, TGP SOI, China hat forward long,,, TGP is set right on target,,, come in for the run with a GBU-12 set to Auto Laze ,10 seconds, CCRP,,, line up and as soon as I pickle,, Auto Laze fail

[howie87]

You're actually use the TGP to create mark points on your CDU. You should then switch the CDU to mark point mode, select mark point A and press China hat aft long to slave your TGP to the steerpoint. Alternatively you could press TMS down long to set your steerpoint as the SPI and then press China hat forward long to slave all your senors (including TGP and Mavs) to that SPI. Please read my comment above regarding the autolase failure and possible causes.

[MatzWarhog]

*Howie's TGP 101*

 

The flashing A means the TGP is in Area track mode but within a few degrees of being masked if I remember correctly. In Point track mode you'll get a flashing P instead. Obviously when it's in inertial track mode (INR) you can't fire the laser because there is no line of sight (it's blocked by the fuselage/stores). This might be the cause of the autolase failure

 

Area mode is for tracking stationary targets, Point will track a moving target.

 

If you get an autolase failure, clear the warning with TMS left then manoeuvre the aircraft until you get a solid P or A and hold the NWS button to fire manually (or set latch on and press to toggle the laser on/off).

 

Also make sure your TGP is set to either BOTH or (L)aser. IR mode will not work. A flashing L symbol means the laser is firing.

 

I think being too low can also generate an autolase failure if the lase time is set to longer than the bombs time of fall.

 

The flashing "A" I was referring to occurs in "Point Track" mode with the CDU and UFC both selecting "Mark Point". The "A" I'm referring to, is the first letter of the word "Align", just below the target image on the MFCD. Any, very minor slewing of the pod will stop the "A" from flashing, and the word "Align" becomes solid, and I no longer have "Autolase Failures". Just clarifying my post.

 

Matz

[Fakum]

Yes, I also was referring to the A MatzWarhog is as well.

Howie,, I believe you have corrected me, I havnt flown in about 6 months, so Im shaking off some rust,, I went back and reviewed most of this matter back in Nov of 2011 at this thread:

http://forums.eagle.ru/showthread.php?t=81113

The only difference was, I never seen this yellow Auto Laze fail notice before,,, maybe because I was China Hat forwarding by mistake? I will test. thanks