Jump to content

Recommended Posts

Posted

Since the previous update, most of the time, Jester just sits back there flipping the laser code's second number, and won't even lock targets.

If I eventually manage to lock something, it always misses. 

Pretty disappointed there's no fix in this latest update.

  • Like 1

I'm not updating this anymore. It's safe to assume I have all the stuff, and the stuff for the stuff too. 🙂

Posted
1 hour ago, Tomcatter87 said:

Only way to drop LGBs right now is to disable Jester, jump to the backseat, do the acquiring part, then jump to the front seat and pickle. 

By disable do you mean just not make any calls to him? Or is there an actual total disable option?

And what about firing the laser after dropping the bomb? One has to keep the laser on the target until the bomb hits

Posted
1 hour ago, cesarferrolho said:

By disable do you mean just not make any calls to him? Or is there an actual total disable option?

And what about firing the laser after dropping the bomb? One has to keep the laser on the target until the bomb hits

There's an option in the crew contract section of the jester menu to disable jester. If you just tell him to be quiet, he'll continue to do weird stuff with the LANTIRN. But hey, maybe the latest update fixes this behavior. Haven't tried yet.

  • Like 1

"Once you have tasted flight, you will forever walk the earth with your eyes turned skyward.
For there you have been, and there you will always long to return."


Check out my DCS content on Instagram

Posted (edited)

I've just tried it in MP and it worked, so I guess today's huge patch did contain some fixes (sadly the launch-bar abort switch, or the 'step' in the sound of the engines spooling down weren't among them).  Apparently HB's patch notes were late.  We're still wating for those. 

EDIT:  Correction. I just tried Operation Clay Dagger and the laser code cycling problem still exists.  I guess HB didn't release any fixes in this latest patch.  Apologies for the false hope.

Edited by JupiterJoe
  • Like 2

Intel Core i7-8700K CPU @ 3.70GHz - 64GB RAM - Nvidia GeForce RTX 3070 - Microsoft Sidewinder Force-feedback 2 - Virpil Mongoose CM-3 Throttle

Posted
3 hours ago, JupiterJoe said:

I've just tried it in MP and it worked, so I guess today's huge patch did contain some fixes (sadly the launch-bar abort switch, or the 'step' in the sound of the engines spooling down weren't among them).  Apparently HB's patch notes were late.  We're still wating for those. 

EDIT:  Correction. I just tried Operation Clay Dagger and the laser code cycling problem still exists.  I guess HB didn't release any fixes in this latest patch.  Apologies for the false hope.

 

Exactly! It seems it's a laser code error! I just tested it. 

Jester simply insists on putting the wrong laser code !!! I tried telling him the laser code but he just puts some random one.

I guess i can forget playing the next mission of the campaign i bought... 😒 😒 😒 

Posted

Ok, here is an important  update about the issue:

It seems, it might be a mission editor sort of problem.

I have the good fortune of having a friend who plays as my RIO. He quickly noticed that the bombs had an enormous code of lots of digits, something impossible.

The way we corrected it was by doing rearming and changing the codes on the bombs to, for example, 1686. After the rearming everything went normal and correct.

I suppose, as long as we ensure the code is correct on the kneeboard (4 digits, 1st digit is a 1, etc), Jester should not have trouble with it.

  • Thanks 2
  • Recently Browsing   0 members

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