Tenkom

Unforunately I'm away from home for a couple of weeks and I've forgotten the specifics. It's been a while since I did it. Check out the pdf in the first post there. I seem to remember something about the "pressed" function doing it. See chapter 5.8 in the pdf.

You can edit the lua so that clicking the trim button will only give one pulse. It means you have to keep clicking if the trim is far off. But it does help alot with fine tuning.

I noticed when using this new shortcut the SMS page didn't go into "Strafe mode" like it does when you click the top left OSB button. Is this correct?

If the HUD and TGP pointers are not in the same place that implies that the plane knows that the HUD and TGP are pointing at different locations which seems weird to me.

The only benchmark should be against the real one. Hopefully they will work on the litening to make it more like the real thing but it has nothing to do with the Sniper pod.

Let's try not to get too off-topic here. This thread is about the new pod. The focus should be on helping ED getting it as close to realistic as possible. The older pod has nothing to with this.

Seems to run contrary to the SPI is a SPI is a SPI philosophy. Why would the TGP not be pointed at the SPI? Or why would the SPI not be where the TGP is pointing?

Does anyone use ATC when landing? For me it makes everything easier except the touchdown itself. I seem to overshoot the wires more easily when using it. But I have more practice without ATC so that might get better. Especially maintaining a stable descent rate is much easier with ATC.

This is natural because if the plane is keeping level while banked that means if you level out without reducing elevator action the plane will pitch up. For the same reason you will always pitch down when you roll into the turn if you don't also pull pack on the stick.

Are you able to detect targets at that range though? Just because you can set the scale that far doesn't mean that you can see anything that far away. I haven't used GMT much at all so I don't know it's effective range.

As far as I know the JF17 is the only module that simulates canopy fogging. It's kind of cool but also kind of annoying. I hope they add an option to disable it if they ever decide to include it.

Is this for nightvision?

What I like about the mudhen is that it can carry stupid payloads without turning into a short range slug. For example it can carry 9x JDAMS. That's only one more than the hornet. But it can do that while carrying plenty of fuel, 4 amraams and still go supersonic. The hornet with 8x JDAMS can only carry 2 120s or 1 120 and a fuel tank and it is NOT going supersonic or very far carrying that.

I'm usually on one of the 4ya servers where there are hundreds of units. So probably worst case.

I was looking at this last night. I was playing with a steady fps. Used and reserved hovered around 14,5GB. They were usually very close. Sometimes USED was higher than Reserved. Does this game really require 16GB minimum of VRAM? Or is it a case of the game just grabbing whatever it can get it hands on? Anecdotally I also have a 4070super GPU with 12GB and it actually gives me higher FPS than my 6900XT but it's a stutter fest so I cannot use it. I guess this does indicate that 16GB is indeed required(for 4k high setting at least). Makes me happy about choosing the 6900xt over the 3080ti back in the day.

How do you know if you have VRAM issues? It seems to use up all my VRAM(16GB) most of the time but I still have good performance, most of the time. Sometimes it just tanks for no apparent reason but that's been the case in DCS for me throughout DCS history and all my pcs.

You can bind these switches to keys so you don't have to jump in the back. At least the Tpod and laser switches. Not that it's a big deal to jump in the back during the startup in any case.

What about the city-spanning craters?

Mavericks have been in the game for over 15 years and ED has never bothered to implement this. I wouldn't hold my breath.

I don't see your point. Everything is a compromise. You choose your loadout based on the situation. If you don't need the range then centerline FLIR is the obvious choice. You gain an amraam and the TGP is in a much better position. If you do then you go with a centerline tank. There are no worms. You simply pick the loadout that suits the situation.

Still a problem. More than 5 years later.... It is easily fixed with a simple edit to the .LUA file so there is no excuse for this. If for some reason you are actually happy with this crazy sensitivity at least add a ant-elev slow bind. It has nothing to do with realism since in RL this is an absolute analog control.

You have to align the HMD and activate the countermeasures if you have TGP or HTS you'll have to turn those on as well.

Are you asking if we have GPS? No satellites over flat maps... Are you one of those?

The reasoning behind it, as I've understood it, is correcting for INS drift. If you have several pre planned target waypoints you will only have to adjust one of them in the case that they have drifted off.

I have to push the stick gradually forward as the speed decreases from 250-190 at which point the nose starts dropping and I need to start trimming for on-speed and bring the throttle a little forward to catch the plane from becoming a brick. But it feels natural to me. The plane doesn't balloon as long as I react accordingly.