How do I increase TPOD visibility range?

I post this here, but I might be a DCS wide question. Just noticed it while flying the 18.

How can I increase TPOD visibility?

As you can see in my screenshot, I can clearly see this island (Abu Musa) visually, yet on my right DDI the TPOD is only just coming in visible range (I took the screenshot as soon as the island edge became visible).

As the TPOD can zoom in extremely far, I'd expect it to be the other way around. TPOD view distance > eye sight

My settings:

Viewing distance: Extreme

Preload radius at maximum (not sure if this helps though)

In cockpit:

I have FLIR image activated

Screenshot taken in VR (zoomed in)

The litening has a range of +/- 40 nm before it can see something. So even though your viewdistance let you see it, the POD itself won't show anything farther than 40 nm (maybe 42-43 but you get the point) ;)

Hehe those are two different answers :P

So is it true that the TPOD can only "see" as far as ~40nm? Or is this a bug? :)

IDK as far as real life is involved, but in DCS that's how it works

I post this here, but I might be a DCS wide question. Just noticed it while flying the 18.

 

How can I increase TPOD visibility?

 

As you can see in my screenshot, I can clearly see this island (Abu Musa) visually, yet on my right DDI the TPOD is only just coming in visible range (I took the screenshot as soon as the island edge became visible).

 

As the TPOD can zoom in extremely far, I'd expect it to be the other way around. TPOD view distance > eye sight

 

My settings:

Viewing distance: Extreme

Preload radius at maximum (not sure if this helps though)

 

In cockpit:

I have FLIR image activated

 

Screenshot taken in VR (zoomed in)

What happens when you go to the narrow view(at image you are in wide)?

Still cant see the island?

What happens when you go to the narrow view(at image you are in wide)?

Still cant see the island?

Wide or narrow does not make a difference when it comes to draw distance

Wide or narrow does not make a difference when it comes to draw distance

So what you are telling me is that you still cant see it.

Very well.

So what you are telling me is that you still cant see it.

Very well.

I don't think you get my point :)

About 2 seconds before this screenshot was taken, the island was not visible on the right DDI. I was able to see it visually (through HUD) long before the TPOD picked it up

I don't think you get my point :)

 

About 2 seconds before this screenshot was taken, the island was not visible on the right DDI. I was able to see it visually (through HUD) long before the TPOD picked it up

Yeah i know.

Your post was very clear.

Wasn't aware of the issue,because i have never activated t pod more than 30 nm away from target location.

+1 weird

The A-10 tpod visibly was way better. The image from Hornet's tgp is not very good, especially in the night. Hope it's WIP still...

I post this here, but I might be a DCS wide question. Just noticed it while flying the 18.

 

How can I increase TPOD visibility?

 

As you can see in my screenshot, I can clearly see this island (Abu Musa) visually, yet on my right DDI the TPOD is only just coming in visible range (I took the screenshot as soon as the island edge became visible).

 

As the TPOD can zoom in extremely far, I'd expect it to be the other way around. TPOD view distance > eye sight

 

My settings:

Viewing distance: Extreme

Preload radius at maximum (not sure if this helps though)

 

In cockpit:

I have FLIR image activated

 

Screenshot taken in VR (zoomed in)

I've noticed the same issue before now. I assumed it was just some level of detail thing with the game engine as you can be waiting for a while for objects on the ground to start rendering in the TPOD view too.

I've noticed the same issue before now. I assumed it was just some level of detail thing with the game engine as you can be waiting for a while for objects on the ground to start rendering in the TPOD view too.

True, but (enemy) ground units can be seen as soon as ground is rendered. In fact, the farther away you are, the easier it is to detect ground units. When you get closer, other ground objects and clutter become visible (are rendered) and make it more difficult to find your target.

I know.. sort of cheating ;)

True, but (enemy) ground units can be seen as soon as ground is rendered. In fact, the farther away you are, the easier it is to detect ground units. When you get closer, other ground objects and clutter become visible (are rendered) and make it more difficult to find your target.

 

I know.. sort of cheating ;)

Yeah, there's some strange inconsistencies in there. I think I noticed it the most when I was setting up quick test missions and noticed static objects i'd put in as my targets were rendering almost last of all.

Has this been fixed yet?

I'm still seeing this as of the latest OpenBeta. Any chance we can get an update on this?

Has this been fixed yet?

 

I'm still seeing this as of the latest OpenBeta. Any chance we can get an update on this?

Wondering if there's a file we can change somewhere that will increase the LOD / draw distance for the TGP

The A-10 tpod visibly was way better. The image from Hornet's tgp is not very good, especially in the night. Hope it's WIP still...

Waaaay back in the initial release of A10C Warthog (beta 1 I think) the digital zoom on the lightning resulted in really low resolution in all modes at extreme range, IIRC this was particularly pronounced in the FLIR modes, as they presumably simulated a lower resolution output for that sensor as compared to the CCD sensor in the pod.

ED changed this quickly and explained that they felt the images were too degraded. My understanding was the math was correct on the initial version, the pixel count was correct and the digital zoom behaved as expected at long range; in other words the images looked like crap at really long ranges. As a side note: there was (as recently as four or five years ago) some vestiges of this original code commented out in one of the sensor .LUA files.

I've never personally seen real TGP footage at these extreme ranges but it would certainly be interesting to see how crisp/clear of an image the sensors can create, presumably there is a lot of digital trickery in the real sensor processing to clean up images.

It seems obvious that what the OP is seeing is a bug or engine limitation and I know my point is a bit OT, my apologies. However it would be interesting to know if ED is revisiting a more realistic TPod limitation for the Hornet and other new modules vis-à-vis digital zoom and it's real world limitations.

If the distant texture popup effect on the tpod DDI screen could at least be reduced by maybe blurring it or something..

Still.. I find it strange that my eye sight visual range exceeds the tpod maximum range by such a large margin (see screenshot in my OP)

If the distant texture popup effect on the tpod DDI screen could at least be reduced by maybe blurring it or something..

 

 

 

Still.. I find it strange that my eye sight visual range exceeds the tpod maximum range by such a large margin (see screenshot in my OP)

Sent from my Redmi K20 Pro using Tapatalk

FLIR page visibly rendering

Hello All,

I wonder if this is how it works in real life, I have not seen this effect so far in videos...

Is FLIR page rendering limited to 45 nautical miles on purpose? Is it a bug or work in progress?

My settings:

I got the same problem.

Interesting

I got the same problem.

Yeah, so, if we assume that the slant range for our TGP is about 40 nautical miles - and that assumption is based on public information for AN/ASQ-228, I was not able to find this for our TGP - then it kind of makes sense, however, would it not just be blurry and not rendered at all?

I mean the effect is very poor, looks terrible, to be honest. I guess I would need to see the real-life recording from 28000 feet MSL to find out.

So, I am not about the range itself but about the graphical representation of it.

This has nothing to do with the TPOD's performance. The ~43 NM rendering range is a limit imposed on all optical sensors in DCS. That limit was set some time ago, in order to limit the performance impact of using such sensors.

It's annoying to see at times, but none of the targeting pods we have in DCS should be able to be useful at that range anyway IRL, so at least we're not losing anything in terms of capability.

I also addressed this some time ago in this thread

https://forums.eagle.ru/showthread.php?t=252421

Although I don't mind the limited viewing range of the tpod (as long as it is accurate), seeing the ground suddenly render (popup if you will) is a bit of an immersion killer imho.

Would be nice if it were to render a bit more gradually