can not reproduce Once in a while Autolase Fail.

[Nealius]

That's a really weird ergonomics design. Seems useless from a practical standpoint. 

[Tippis]

12 minutes ago, Nealius said:

That's a really weird ergonomics design. Seems useless from a practical standpoint. 

Think of it as a target-of-opportunity kind of thing: you've set yourself up to ripple off a bajillion snakeeyes with carefully planned spacing to take out this convoy… except now you find a little runt at the end that only really needs one. Select Mk82SE, pickle, and then go back to the original plan with a slightly shorter line of drops — quick and easy compared to diving into the menus and creating new profiles and/or erasing and then re-doing your original ripple settings.

[Nealius]

Ah now I see. Similar to how the Viper has two profiles in the SMS page. The Hog is just more "high context" about it and doesn't tell you.

[Tippis]

Yes, pretty much.

 

It's a pretty common theme with the Hog in general. You have a whole bunch of highly complex systems that can be set up in minute detail, and then you have a set of limited-function default-setting quick-access features to get to almost (but not quite) the same functionality. If you ever start diving into the capabilities of the CDU, for instance, you will find this kind of duplication all over the place. Often, while the “simplified” features often come with some initially frustrating limitations, once you start treating them as tools to deal with a specific situation, that simplification makes sense and the “missing” bits turn out not to matter.

 

Markpoints are perhaps the most immediate example: they're annoyingly easy to accidentally spam all over the place with a simple button mis-press, and there's nothing you can do about it. But it turns out that this is almost the whole point: you're meant to be able to just strew them across the country side, because while they function like navigation points in almost every regard, they are meant to solve a very different and much more dynamic problem that doesn't need the fine control and editing features of a regular waypoint.

[Shuenix]

Back to topic:

Do you agree, if I setup a bomb with Autolase and 15 seconds to lase and dropping from 8000 ft AGL, it SHOULD not give the autolase fail?

If you do not agree, why?
If you do agree, it must be a bug, right?

 

Shue

Edited March 15, 2021 by Shuenix
Put in AGL

[Tippis]

Well… 8,000ft feels a bit low and I wouldn't be at all surprised if it feels it simply doesn't have time to trigger and track the target properly.

 

And no, even if it intuitively “shouldn't”, that does not mean it must be a bug. It can still just be any number of user errors.

[Shuenix]

On 3/15/2021 at 11:58 AM, Tippis said:

Well… 8,000ft feels a bit low and I wouldn't be at all surprised if it feels it simply doesn't have time to trigger and track the target properly.

 

BTW. It made an error with mission Bignewy made and it was 10000 ft.

[Shuenix]

Just had one more:

https://www.dropbox.com/s/tt34sjvl7qa0sxw/4YA_Syria_Capture_Bases_BLUE_v27B-20210323-194330.7z?dl=0

[SJBMX]

Tried to watch the track, but got a ton of script errors trying to open it. The player aircraft never seemed to appear.

[Shuenix]

4 hours ago, SJBMX said:

Tried to watch the track, but got a ton of script errors trying to open it. The player aircraft never seemed to appear.

It is Syria map

[SJBMX]

Yes, I know. I got the track to load, got a whole bunch of error popups, and then the mission started playing but the player never spawned in.

[Yurgon]

I saw the player aircraft fly away from Incirlik/Adana for 20 minutes, then the track stopped mid-air without any action. But I must confess that I fast forwarded a lot because it was not obvious how long the whole thing would take.

 

A short and quick replay would be a lot better. And yes, I know it can take hours and hours to reproduce such a problem, but that's often the most important part about bug-hunting: narrowing down the problem and making it reproducible.

[Nealius]

Disregard, probably user error RE: laser not functioning when not in area/point track

Edited March 26, 2021 by Nealius

[Shuenix]

8 hours ago, Nealius said:

Disregard, probably user error RE: laser not functioning when not in area/point track

 

I will remeber to check that next time. Thnx

[vctpil]

Hi,

 

I can't get the autolsae to work.

 

15,000ft

Laser switch LASER

DSMS : set the correct profile, autolase ON, check the laser code

TPOD : point track, set SPI, check the laser code

 

The bomb drop but the laser does not come.

 

I am able to drop laser bomb with autolase OFF, laser latch ON or OFF, but the autolase ON simply does not work.

 

Any idea?

 

Thanks,

Vincent

[Yurgon]

If you could post a track or a video, that would be most helpful.

[QuiGon]

19 hours ago, vctpil said:

Hi,

 

I can't get the autolsae to work.

 

15,000ft

Laser switch LASER

DSMS : set the correct profile, autolase ON, check the laser code

TPOD : point track, set SPI, check the laser code

 

The bomb drop but the laser does not come.

 

I am able to drop laser bomb with autolase OFF, laser latch ON or OFF, but the autolase ON simply does not work.

 

Any idea?

 

Thanks,

Vincent

 

Have you set a lase time? IIRC it is 0 seconds by default, meaning it will start autolasing 0 seconds before impact, meaning it won't autolase. I recommend to set it to 10-15 seconds lase time.

[vctpil]

On 7/12/2021 at 11:27 AM, QuiGon said:

 

Have you set a lase time? IIRC it is 0 seconds by default, meaning it will start autolasing 0 seconds before impact, meaning it won't autolase. I recommend to set it to 10-15 seconds lase time.

Raaaaaaaaaaaah, that was the problem, I forgot to set the lase time, thanks a lot.

Edited July 13, 2021 by vctpil

[Yurgon]

On 7/12/2021 at 11:27 AM, QuiGon said:

Have you set a lase time? IIRC it is 0 seconds by default, meaning it will start autolasing 0 seconds before impact

 

I just came across that part in the manual. With 0 seconds autolase time set, it'll default to 4 seconds. Which is an odd choice IMO, but I guess it is what it is.

 

DSMS Settings Page for LGB:

 

Quote

Tip: For best accuracy, set this to 8 seconds before impact. If set to 0, the laser will default to firing 4 seconds before impact.

 

[QuiGon]

1 hour ago, Yurgon said:

 

I just came across that part in the manual. With 0 seconds autolase time set, it'll default to 4 seconds. Which is an odd choice IMO, but I guess it is what it is.

 

DSMS Settings Page for LGB:

 

 

I wasn't aware of that, thanks!