Jump to content

Laser code for LTD / R can't be set when switch is safe position


Martin2487
 Share

Recommended Posts

Can't set laser code to laser designator when switch is safe position. I don't think that's accurate. For example, it should be possible to set the laser code on the ground. For comparison, LST can be set to ground. So I think it should logically be possible for LTD / R.

Link to comment
Share on other sites

Found this on the Internet:

 

4.3 LTD Laser Arming & Safety Interlocks

 

 

Laser Inhibit Envelope

Before the LTD can be fired, either manually or automatically, three sets of laser firing criteria must be met:

Laser Armed - The laser is initially commanded to ARM via the LTD/R ARM switch on the Sensor Control Panel. Full arming can only take place when:

Landing gear is up and locked

Aircraft in A/G Master Mode

Weight off Wheels

FLIR is in OPR status

FLIR is not in the default pointing mode

FLIR has valid AVMUX communication with the MC

FLIR has valid communication with LTD/R

Laser code is valid

Link to comment
Share on other sites

  • 1 year later...

Sorry for the 2019 necro. But this doesn't seem to be correct. What Drac found (in August 2019...) only explains when the laser can be fired, not when you should be able to set the laser code.

 

According to GB, you should always be able to set the code, regardless if the laser is armed or not. At least it wasn't in any of the software versions he flew, and I can't really imagine a reason why that would change. It would be a very arbitrary limitation. Setting up the laser code before take off makes a lot of sense.

 

These were my questions to him:

 

Q:

1) Can the laser be armed when on the ground?
2) Do you need to arm the laser to change laser code?
3) Is there any way you can set the laser code for the tpod before you take off?

A:
1) I think the answer is no. Memory faded on that a bit but I am 80% sure. (He later asked another pilot, who verified this, but that's already correctly implemented anyway)
2) No. You can change the code without laser armed.
3) Yes. Just change it whenever you want.

 

He also added "I did fly a different software version and I do know for a fact that several big differences exist between my timeline and older ATFLIRs. I really don’t think changing laser codes would be one of them, but I can’t be sure."

 

So my take on it is that it should be considered a bug, unless documentation clearly says otherwise.

  • Like 7
Link to comment
Share on other sites

  • ED Team
On 5/5/2021 at 2:02 PM, Bankler said:

So my take on it is that it should be considered a bug, unless documentation clearly says otherwise.

Has to be the opposite sorry, we require actual documentation that this can be done. I will look into it a little deeper, but the team works very hard to get things correct based on available information, most likely this is what we have, so we would need evidence it is different. Thanks.

  • Like 1

64Sig.png
Forum RulesMy YouTube • My Discord - NineLine#0440• **How to Report a Bug**

1146563203_makefg(6).png.82dab0a01be3a361522f3fff75916ba4.png  80141746_makefg(1).png.6fa028f2fe35222644e87c786da1fabb.png  28661714_makefg(2).png.b3816386a8f83b0cceab6cb43ae2477e.png  389390805_makefg(3).png.bca83a238dd2aaf235ea3ce2873b55bc.png  216757889_makefg(4).png.35cb826069cdae5c1a164a94deaff377.png  1359338181_makefg(5).png.e6135dea01fa097e5d841ee5fb3c2dc5.png

Link to comment
Share on other sites

On 5/11/2021 at 7:12 PM, NineLine said:

Has to be the opposite sorry, we require actual documentation that this can be done. I will look into it a little deeper, but the team works very hard to get things correct based on available information, most likely this is what we have, so we would need evidence it is different. Thanks.

Not to underestimate the team's efforts during this time, but will you consider asking your SME's?

Link to comment
Share on other sites

On 5/11/2021 at 9:12 AM, NineLine said:

Has to be the opposite sorry, we require actual documentation that this can be done. I will look into it a little deeper, but the team works very hard to get things correct based on available information, most likely this is what we have, so we would need evidence it is different. Thanks.

Do you have evidence that supports the current implementation? If that were the case I'd understand. However, faced with no evidence supporting one behavior and pilots with real experience supporting the other behavior, it makes little sense to go with the former.

 

You are asking for evidence that something CAN be done, when it has been arbitrarily limited already (if you don't have evidence for said arbitrary limitation).


Edited by Jak525
  • Like 4
Link to comment
Share on other sites

Laser codes can definitely be set on the ground or air, both LST and LTD, same with IR marker and IR marker pattern.  The UFC just has LTD above LST, and entry is fairly straight forward, colonize and enter the code and the Enter.  Codes range from 1111 to 1688, with only 1511-1688 being useful for LGBs, the lower codes - I believe - are more suited for helo's and their weapons.  This is to say you could set something lower than 1511, but it would be impractical, and I have never seen it tasked or used - not sure exactly what <1511 is used for, never had the chance to use it - it definitely accepted the input.  Laser codes are mission critical, so it must be set prior to takeoff to minimize risk of error, and even still there are errors in codes and IR marker / Trg laser.  Similar to A/A radar presets, which have now been fixed.  

  • Like 1
  • Thanks 4
Link to comment
Share on other sites

4 hours ago, Jak525 said:

Do you have evidence that supports the current implementation?

 

I'm going to take a guess and say it's the system schematics documentation, but the only thing I can understand from it is that you can't arm LTDR on the ground.


Edited by BarTzi
Link to comment
Share on other sites

I'm going to take a guess and say it's the system schematics documentation, but the only thing I can understand from it is that you can't arm LTDR on the ground.
Sure, you can't arm the laser, that doesn't mean you shouldn't be able to change the frequency though.
  • Like 2

The vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord.

CVW-17_Profile_Background_VFA-34.png

38" AW3821DW, Z370 Aorus Gaming 7, i7-8700K, 3090 FTW3 Ultra, 64GB DDR4, 960 Pro, 970 Evo Plus, WD Gold 6TB, Seasonic Prime Platinum
Super Taurus throttle, Combat and T/O panels, TM50 base, Hornet grip w/extension, TPR, 3 MFDs

F/A-18C, AV-8B, F-16C, JF-17, A-10C (C II), M-2000C, F-14, AH-64D, BS2, UH-1H, P-51D, Sptifire, FC3

Link to comment
Share on other sites

1 hour ago, Harker said:
2 hours ago, BarTzi said:
I'm going to take a guess and say it's the system schematics documentation, but the only thing I can understand from it is that you can't arm LTDR on the ground.

Sure, you can't arm the laser, that doesn't mean you shouldn't be able to change the frequency though.


I agree, which is why I think they should ask their SME about this.

Link to comment
Share on other sites

  • BIGNEWY changed the title to Laser code for LTD / R can't be set when switch is safe position

@Mo410 great info, thanks. Could you explain one more thing that is bugging me with a Hornet's laser - does it really works that way yhat after bomb drop with auto lase the LTD/R switches off and pilot has to manually switch it on with every bomb?

Link to comment
Share on other sites

Respectfully, let's not derail this thread any further, since this is rather important QOL change. When we have two people who used the system explain to us that this can be done, I don't think this thread should be tagged as 'no evidence'

  • Like 1
Link to comment
Share on other sites

8 hours ago, Foka said:

@Mo410 great info, thanks. Could you explain one more thing that is bugging me with a Hornet's laser - does it really works that way yhat after bomb drop with auto lase the LTD/R switches off and pilot has to manually switch it on with every bomb?

Yes unless you select trigger laser, then it remains armed. Used to be an overheat issue with some pods, but no longer with the newer ones, but the logic remains.

 

Always do MALT check, master arm, A/G mode, Laser, TDC assigned to correct display. 

  • Thanks 2
Link to comment
Share on other sites

On 5/11/2021 at 6:12 PM, NineLine said:

Has to be the opposite sorry, we require actual documentation that this can be done. I will look into it a little deeper, but the team works very hard to get things correct based on available information, most likely this is what we have, so we would need evidence it is different. Thanks.

 

Respectfully, now we have three experts (GB, GB's Hornet pilot friend, and Mo410) confirming that the code can be set on the ground. All respect for the team (they are heroes... the amount of bug fixes in the last patch is absolutely insane!), but I'm curious to hear what documentation they could possibly have that claims the opposite

 

Because it doesn't make much sense to arbitrarily make something impossible just because documentation doesn't explicitly say that you can do it. With that reasoning, you could for instance argue that you shouldn't be able to use rudder trim if below 1400 lbs of fuel, unless the documentation explicitly says that you can do this (or any other arbitrary limitation).

 

Unless you have documentation claiming you can't set the code on the ground for the OFP that is being simulated, or any other OFP for that matter, maybe it should be accepted that it's simply an assumption from the developer who wrote the code for this system in the game. Nothing strange about that (if you don't know, you have to guess, should happen all the time!), but that doesn't mean it's correct.

 

Cheers! 🙂

 

(Sorry for the messy look of the first image! Didn't want to display names on anyone without clear permission)

 

LaserCodeDiscussion.png

LaserCodeDiscussion_2.png


Edited by Bankler
  • Like 5
Link to comment
Share on other sites

Exactly what Bankler said. Here's a way of looking at it:

 

You're making a pasta according to a recipe. You add sausages, which were not in the recipe. You are told it shouldn't have sausages. A few chefs, who were there when the recipe was made, even say it shouldn't have sausage. It wouldn't make sense to say they need specific evidence stating it should not have sausage. Rather, no sausage should be the default until proven otherwise, not the opposite.


Edited by Jak525
  • Like 2
  • Thanks 4
Link to comment
Share on other sites

  • 3 weeks later...
  • 1 month later...
  • ED Team

I will run it by the team again, but as stated we do need to see evidence, I will take a look myself also, but we are in no rush to change something without having some evidence first.

 

Thanks

smallCATPILOT.PNG.04bbece1b27ff1b2c193b174ec410fc0.PNG

Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status

Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, HP Reverb G2

Link to comment
Share on other sites

I'm going to start sounding like a broken record, but I'd like to again point out that, unless there's documentation that explicitly states that something cannot be done, then common logic (it can be done in all other comparable aircraft) and witness testimony (three people with IRL experience) are the next best things.

The laser arm switch is a consent switch that allows the laser to be fired, it doesn't remove power from the entire relevant system, when in SAFE.

  • Like 2

The vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord.

CVW-17_Profile_Background_VFA-34.png

38" AW3821DW, Z370 Aorus Gaming 7, i7-8700K, 3090 FTW3 Ultra, 64GB DDR4, 960 Pro, 970 Evo Plus, WD Gold 6TB, Seasonic Prime Platinum
Super Taurus throttle, Combat and T/O panels, TM50 base, Hornet grip w/extension, TPR, 3 MFDs

F/A-18C, AV-8B, F-16C, JF-17, A-10C (C II), M-2000C, F-14, AH-64D, BS2, UH-1H, P-51D, Sptifire, FC3

Link to comment
Share on other sites

  • ED Team

@HarkerI'm sorry, but I can't agree with you. With that logic we can go far beyond any reasonable state. Like BIGNEWY stated above, we are investigating and we need something before making the change.

Also, I didn't want to point that out, but in the attached conversation there is one thing that makes me think twice before using it.

 

There is already information to proof other point of view, so I suggest to wait and see what the result of the investigation would be.

Thank you for the discussion!


Edited by cofcorpse
Link to comment
Share on other sites

8 minutes ago, cofcorpse said:

@HarkerI'm sorry, but I can't agree with you. With that logic we can go far beyond any reasonable state. Like BIGNEWY stated above, we are investigating and we need something before making the change.

Also, I didn't want to point that out, but in the attached conversation there is one thing that makes me think twice before using it.

 

There is already information to proof other point of view, so I suggest to wait and see what the result of the investigation would be.

Thank you for the discussion!

 

If you do have information that points to the current implementation, then I have nothing more to say. It was never pointed out to us, so I wrote my comment in that context, plus the conversation that was presented.

Also, thank you for the reply and I appreciate the update. It'll be interesting to see where the investigation leads.

The vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord.

CVW-17_Profile_Background_VFA-34.png

38" AW3821DW, Z370 Aorus Gaming 7, i7-8700K, 3090 FTW3 Ultra, 64GB DDR4, 960 Pro, 970 Evo Plus, WD Gold 6TB, Seasonic Prime Platinum
Super Taurus throttle, Combat and T/O panels, TM50 base, Hornet grip w/extension, TPR, 3 MFDs

F/A-18C, AV-8B, F-16C, JF-17, A-10C (C II), M-2000C, F-14, AH-64D, BS2, UH-1H, P-51D, Sptifire, FC3

Link to comment
Share on other sites

  • ED Team
4 minutes ago, Harker said:

If you do have information that points to the current implementation, then I have nothing more to say. It was never pointed out to us, so I wrote my comment in that context, plus the conversation that was presented.

Also, thank you for the reply and I appreciate the update. It'll be interesting to see where the investigation leads.

I'm afraid you understood me wrong. We don't have any actual information, it was stated above. But it is already done, we used available information and logic, and to change it we need something solid.

I can't agree with "unless there's documentation that explicitly states that something cannot be done, then common logic (it can be done in all other comparable aircraft) and witness testimony (three people with IRL experience) are the next best things"

There are a lot of examples where common logic fails due to different reasons, and experts make wrong statements due to wrong questions or other reasons.

 

So, let's wait and see the conclusion.

Thanks!

Link to comment
Share on other sites

 Share

  • Recently Browsing   0 members

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