Jump to content

Recommended Posts

Posted

Make sure that the laser is fireing. The L symbol should be flashing until impact. Drop bombs in ccrp or ccip. Make sure that you have enough altitude so the bomb have time to track properly. Oh, and only use gbu-12 or gbu-16 ofc.

  • Replies 271
  • Created
  • Last Reply

Top Posters In This Topic

Posted

Same situation for me. Both 12s and 16s fail to ride the laser beam.

It seems that the issue that the laser spot remains locked at the initial TGP point is still valid.

My Hardware: ROG Strix X570-F Gaming - AMD 5600X @ 4.7 ghz - G.SKILL TRIDENT 32GB DDR4 3200 (14-14-14-34 CL) - GigaByte 3080ti OC 12gb - Corsair MP600 Force 1TB - 2 x EVO Nvme 500GB - Virpil Warbird Base T-50CM2 and TM Throttle + Trackhat + G25 + AOC AG271QG 27"

My Modules: JF-17, F-16C, AV-8N/A, F-18C, ASJ37, MiG-15Bis, MiG-21Bis, Fw-190D, Bf-109K, P-51D, F-86F, Ka-50 III, UH-1H, Mi-8MTV2, NS430, FC3, A-10C, Mirage 2000C, L-39, F-5E-3, SA342, Spitfire, AH-64, Mirage F-1CE.

My Maps: Nevada, Normandy, Persian Gulf, Syria, South Atlantic.

Posted

In 1.5.8 Beta TPOD is working great for me. Set up lase code to 1688, find target with TPOD, set to arm, make sure it's on lase (not marker or anything else), hit fire, arm bomb, drop with ccrp. I use the left mfd for the TPOD so I can see the DMT. Don't move the TPOD or it will default back to SAFE and lase will stop.

  • Like 1
Posted
Same situation for me. Both 12s and 16s fail to ride the laser beam.

It seems that the issue that the laser spot remains locked at the initial TGP point is still valid.

 

Ensure that You did not do the same fault like I...

Bomb fuzes must be set inorder to make the bombs explode.

 

It seems that there is a bug that makes the 1st bomb released explode despite the Fuzes set to Safe, Thus You get an impact on the first bomb run.

But when dropping the next bombs, they do go to the intended new target, but does not explode and thus You might interprete that they did not hit Your target, but hit the first target instead, since it´s the only point smoking.

| i7-10700K 3.8-5.1Ghz | 64GB RAM | RTX 4070 12GB | 1x1TB M.2. NVMe SSD | 1x2TB M.2. NVMe SSD | 2x2TB SATA SSD |  1x2TB HDD 7200 RPM | Win10 Home 64bit | Meta Quest 3 |

Posted
In 1.5.8 Beta TPOD is working great for me. Set up lase code to 1688, find target with TPOD, set to arm, make sure it's on lase (not marker or anything else), hit fire, arm bomb, drop with ccrp. I use the left mfd for the TPOD so I can see the DMT. Don't move the TPOD or it will default back to SAFE and lase will stop.
I have done exactly as you just said and all ten bombs failed to find and track the laser. The laser fired for sure. Pretty sure nothing wrong with my procedures.
Posted

Personally I've only gotten it to work thus far with the LST having direct view of the laser to hold a lock - so dive bombing - while it loses lock when going beyond its field of view - level bombing.

 

Then again, I've only tried doing it thus far with the TPOD and no use of the DMT, will do more testing once 2.5 hits.

Posted (edited)
I have done exactly as you just said and all ten bombs failed to find and track the laser. The laser fired for sure. Pretty sure nothing wrong with my procedures.
Never mind. I had it set to trnl. Not lasr.

 

Can someone quickly explain mrkr and trnl for me?

Edited by noisy_lightning
Posted
Never mind. I had it set to trnl. Not lasr.

 

Can someone quickly explain mrkr and trnl for me?

 

MRKR = Marker = Ranging laser to get distance information.

TRNL = Training Laser = Training only use (haven't actually checked if this emits anything at all or is just a function to get familiar with the procedures during training)

Posted
MRKR = Marker = Ranging laser to get distance information.

TRNL = Training Laser = Training only use (haven't actually checked if this emits anything at all or is just a function to get familiar with the procedures during training)

Thank you.

 

Just realised the Pocket Guide has been updated since I last downloaded it so I have just read through the section for the pod. Glad the Sensor Select hat can be used to control the pod, will make a huge difference.

 

Hopefully for the other people above saying they had issues they also had TRNL selected rather than laser.

Posted
MRKR = Marker = Ranging laser to get distance information.

TRNL = Training Laser = Training only use (haven't actually checked if this emits anything at all or is just a function to get familiar with the procedures during training)

 

TRNL: Training. No laser beam is fired but the TPOD behaves as if it is.

 

MRKR: Marker. It is a low power IR laser beam used to mark spots on the ground for ground troops. The beam can be seen with NVG. This beam cannot be used to guide weapons.

 

LSR: Laser. This is the high power laser beam used for weapons guidance. It cannot be seen with NVG.

 

LRNG: This is laser ranging. It fires the high power laser for 3 seconds in order to get precise range to target.

  • Like 1

"Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning."

"The three most dangerous things in the world are a programmer with a soldering iron, a hardware type with a program patch and a user with an idea."

Posted

Are the HOTAS controls for the TPOD described in the Pocket Guide working on any DCS version right now?

" You must think in russian.."

[sIGPIC][/sIGPIC]

 

Windows 7 Home Premium-Intel 2500K OC 4.6-SSD Samsung EVO 860- MSI GTX 1080 - 16G RAM - 1920x1080 27´

 

Hotas Rhino X-55-MFG Crosswind Rudder Pedals -Track IR 4

Posted
Are the HOTAS controls for the TPOD described in the Pocket Guide working on any DCS version right now?

 

Yes they do at least in 1.5 beta.

 

For the added functions to work You must be in HTS mode.

| i7-10700K 3.8-5.1Ghz | 64GB RAM | RTX 4070 12GB | 1x1TB M.2. NVMe SSD | 1x2TB M.2. NVMe SSD | 2x2TB SATA SSD |  1x2TB HDD 7200 RPM | Win10 Home 64bit | Meta Quest 3 |

Posted

Thanks for the heads up.

" You must think in russian.."

[sIGPIC][/sIGPIC]

 

Windows 7 Home Premium-Intel 2500K OC 4.6-SSD Samsung EVO 860- MSI GTX 1080 - 16G RAM - 1920x1080 27´

 

Hotas Rhino X-55-MFG Crosswind Rudder Pedals -Track IR 4

Posted

Does the slave mode work for the pod? If I set an A/C LOS using the DMT, then pull up the TPOD, it doesn’t snap to the DMT designated spot. Is it something procedurally wrong on my end or not yet implemented?

Posted
TRNL: Training. No laser beam is fired but the TPOD behaves as if it is.

 

MRKR: Marker. It is a low power IR laser beam used to mark spots on the ground for ground troops. The beam can be seen with NVG. This beam cannot be used to guide weapons.

 

LSR: Laser. This is the high power laser beam used for weapons guidance. It cannot be seen with NVG.

 

LRNG: This is laser ranging. It fires the high power laser for 3 seconds in order to get precise range to target.

 

Appreciate the correction.

Posted

Sometimes I cannot toggle between AR/PT - why ?

| i7-10700K 3.8-5.1Ghz | 64GB RAM | RTX 4070 12GB | 1x1TB M.2. NVMe SSD | 1x2TB M.2. NVMe SSD | 2x2TB SATA SSD |  1x2TB HDD 7200 RPM | Win10 Home 64bit | Meta Quest 3 |

Posted
Does the slave mode work for the pod? If I set an A/C LOS using the DMT, then pull up the TPOD, it doesn’t snap to the DMT designated spot. Is it something procedurally wrong on my end or not yet implemented?

 

COuld be a bug.

"Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning."

"The three most dangerous things in the world are a programmer with a soldering iron, a hardware type with a program patch and a user with an idea."

Posted (edited)
COuld be a bug.

 

Does the slave mode work for the pod? If I set an A/C LOS using the DMT, then pull up the TPOD, it doesn’t snap to the DMT designated spot. Is it something procedurally wrong on my end or not yet implemented?

 

Along the bug I posted above with AR/PT not toggling, I also see this..

 

Seems not to work:

1. Aircraft HOTAS Control Mode (TDC)

This TDC control mode, which is the default mode, is available when the TPOD is displayed on either MPCD. In this mode TDC control is assigned to the aircraft’s sensors (INS/DMT and IRMV) and not to the TPOD. The TPOD is slaved to the aircraft’s command LOS ( A/C CMD LOS), the aircraft’s selected target point. If no A/C CMD LOS exists, the TPOD sensor head is caged to the boresight position (depressed 2º in elevation). Otherwise the TPOD is locked on the aircraft’s target.

Any TDC command will be ignored by the TPOD and instead will be obeyed by the selected aircraft sensor. TPOD sensor head will not move from its caged position until an aircraft target has been designated.

The TPOD is using this control mode when the legend next to PB14 displays TDC.

 

The problem is that the TPOD does not move to the DMT / MAV Line of sight.

 

Seems to work:

2. TPOD Slew Control Mode (TDC)

This mode can be selected by clicking on the PB14 when the TPOD primary display page is displayed. The TDC legend is underlined (TDC) to indicate that this is the operational TPOD TDC control mode. Clicking on TDC will return to the default mode (Aircraft HOTAS Control Mode) and remove the underline.

In this mode the TPOD captures all TDC commands. If the TPOD was in SLAVE mode, it will automatically select AR track mode. When the TPOD designates a target, this target becomes the aircraft’s selected target (A/C CMD LOS) and all aircraft sensors are automatically locked to it.

This seem to work as described.

 

Seems not to work:

3. TPOD HOTAS Control Mode (HTS)

This mode can only be selected by double clicking the [sensor Select DOWN: HUD Scene Reject/TPOD] HOTAS button in less than 0.8 seconds. The PB14 legend displays HTS to indicate that this is the TPOD TDC control mode. To exit this mode, either double click on [sensor Select DOWN: HUD Scene Reject/TPOD] HOTAS button or click on the PB14 to select any of the other two modes: TDC or TDC.

In HTS mode, the aircraft TDC and Sensor Select Switch are controlled by the TPOD. The TPOD obeys all TDC commands and can be controlled by the SSS HOTAS switch, but any TPOD target designation is not considered an aircraft target designation and thus cannot be used for an attack run.

 

Apart from being able to control the TPOD via HOTAS commands, it works exactly like TDC mode and sets DMT / MAV Line of sight, where it according to the description, shouldn´t set DMT / MAV Line of sight.

 

Regarding the AR/PT bug, what I see is that PT automatically is selected when the TPOD cursor is moved over an AI object. Pressing PB20 does nothing.

Moving the TPOD cursoe over static objects does not change mode from AR to PT.

 

 

FinnJ

Edited by fjacobsen

| i7-10700K 3.8-5.1Ghz | 64GB RAM | RTX 4070 12GB | 1x1TB M.2. NVMe SSD | 1x2TB M.2. NVMe SSD | 2x2TB SATA SSD |  1x2TB HDD 7200 RPM | Win10 Home 64bit | Meta Quest 3 |

Posted (edited)

Hi there !

 

I don't know for you, I tried the TPOD in 1.5.8 beta, and for me the display looks very blurry/fuzzy. I checked my graphic settings, instruments resolution is set to 1024. Do you have the same problem ?

Edited by flo57100
Posted
Hi there !

 

I don't know for you, I tried the TPOD in 1.5.8 beta, and for me the display looks very blurry/fuzzy. I checked my graphic settings, instruments resolution is set to 1024. Do you have the same problem ?

 

Yes, same for me, very difficult to see something :(

MSI Z97 Gaming 5 - Intel I7 4790K - Artic cooling freezer 7 pro rev 2 - GSKILL 32 Go - SSD Crucial M5 120 go - SSD Crucial 2To - HDD western digital caviar blue 1 TO - Gigabyte GTX 1070 Gaming G1 - Windows 10 home 64 bits

Posted
Hi there !

 

I don't know for you, I tried the TPOD in 1.5.8 beta, and for me the display looks very blurry/fuzzy. I checked my graphic settings, instruments resolution is set to 1024. Do you have the same problem ?

Yes, same for me, very difficult to see something :(
You both have not accidentally changed the focal point / focus setting have you? Mine is perfectly clear.
Posted
You both have not accidentally changed the focal point / focus setting have you? Mine is perfectly clear.

 

Look at this vidéo

at 1.22

MSI Z97 Gaming 5 - Intel I7 4790K - Artic cooling freezer 7 pro rev 2 - GSKILL 32 Go - SSD Crucial M5 120 go - SSD Crucial 2To - HDD western digital caviar blue 1 TO - Gigabyte GTX 1070 Gaming G1 - Windows 10 home 64 bits

Posted

To engage the HTS mode, which can only be done via HOTAS, you must double click the [sensor Select DOWN: HUD Scene Reject/TGP] button for less than 0.80 seconds.

"Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning."

"The three most dangerous things in the world are a programmer with a soldering iron, a hardware type with a program patch and a user with an idea."

Posted

Zeus, thanks again for the update. Reading in the manual the Marker function is supposed to flash the laser 3 times a second when activated. Was testing last night on multiplayer, was a constant beam. I know its WIP, just bringing to your attention. Thanks

  • Recently Browsing   0 members

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