Jump to content

Recommended Posts

Posted

Hi there is there any chance to setup LANTRIN auto lase time for different then 10 sec,

Thanks

303 & Friends discord

 

Hangar :

 

JF-17 Thunder, F-16C Viper, I-16, Christen Eagle II, F-14 Tomcat, Supercarrier, WWII Assets Pack, F/A-18C Hornet, AJS-37 Viggen, Spitfire LF Mk. IX, F-5E Tiger II, M-2000C, MiG-15bis, Bf 109 K-4 Kurfürst, Fw 190 D-9 Dora, F-86F Sabre, Flaming Cliffs 3, P-51D Mustang, A-10C Warthog,SA342 Gazelle, UH-1H Huey, Mi-8MTV2 Magnificent Eight, Black Shark II, Persian Gulf Map, Normandy 1944 Map,

 

 

Posted
Hi there is there any chance to setup LANTRIN auto lase time for different then 10 sec,

Thanks

No, the lase time is fixed to start at time to impact +10 and to stop at time to impact -4. You need to laser manually to achieve that.

 

I don't think so, but why would you like to do that?

Sometimes a longer lasing time can be necessary, e.g. when attacking a fast moving target, so that the laser needs more guidance time to catch up with the target.

Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit

DCS Panavia Tornado (IDS) really needs to be a thing!

Tornado3 small.jpg

Posted

During development of the LANTIRN, I watched probably all GBU delivery video available. Almost all used manual lasing. And I remember maybe only one or two in POINT, the rest in AREA.

My observation is that auto lase works quite well in DCS for stationary targets when the pilot is precise in following the release cues from the LANTIRN.

Krzysztof Sobczak

 

Heatblur Simulations

https://www.facebook.com/heatblur/

Posted

Not sure if you coded it that way, but also the point track does not always work, and especially not at buildings. Had it multiple times that the point track looses its designation when passing over the target.

I would assume, that the software just can't seperate good enough between target and background when the target gets quite big or boarders are not so good seen...

 

Anyhow, I need to say that the lanterin integration is done absolute awesome!

First time in DCS that I really feel like looking trough a POD...

 

BTW: I also don't use autolase. The Tomcat is a two man ship, so you have the big advantage that you can concentrate 100% on the POD while you still have a pilot to fly and watchout for possible threads...

Steam user - Youtube

I am for quality over quantity in DCS modules

Posted

Thank you for these kind words. I'm glad you like the LANTIRN smile.gif

 

Yes, you described it precisely. The object you want to POINT track must be of a proper visual size - not too small and not too large. It must be easily identifiable - the background can't be cluttered with other hot objects. So it will lock on a single building or a tank in a field. But it may be unable to initiate POINT on a building in a city or a vehicle hiding in an urban area. The pod monitors track quality continuously, so you may successfully start tracking, but then the track may be dropped because the view has changed. The pod will automatically switch to a wider FOV when the tracked object becomes too big to fit the frame.

Krzysztof Sobczak

 

Heatblur Simulations

https://www.facebook.com/heatblur/

Posted
The pod will automatically switch to a wider FOV when the tracked object becomes too big to fit the frame.

 

Really? Never noticed that. Rather it felt dropping the PT when the object becomes too big.

So is this implemented already?

Steam user - Youtube

I am for quality over quantity in DCS modules

Posted

I can only concur with viper, the LANTIRN implementation in DCS is absolutly stunning and feels incredible real! Not just the visuals, but also the pod behaviour feels much more realistic than the A-10s TGP, because the LANTIRN is much more susceptible to environmental conditions and not as reliable (thinking about point tracking here). As you said Super Grover, point track is very rarely used IRL, because it's not as reliable as tracking the target manually in area mode.

 

:thumbup:

Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit

DCS Panavia Tornado (IDS) really needs to be a thing!

Tornado3 small.jpg

  • Recently Browsing   0 members

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