fisadev

I'm not assuming that, it can be very well a problem in the litening magnification. Which again, is a separate issue from how good the resolution is on its digital zoom.

@NineLine My post that was merged here, was talking about something different to what most people are discussing in this post: - I was reporting that the sniper has less magnification than the litening - Here people are debating about the resolution of the sniper vs litening Magnification is how big things are seen. Resolution is related to how much detail you can see. They're of course related, but they're two different things that can be right or wrongly simulated independently. Regardless of the resolution debate (very valid!), I still think there's also a separate issue with the magnification, because AFAIK the sniper should have equal or greater magnification than the litening.

You have absolutely no evidence to sustain that. It can absolutely be a bug.

As I already told you: being a newer pod with better optics, it would be expected that the Sniper would have greater zoom. There would be no reason to reduce the digital zoom capabilities to a point where it has less overall zoom than previous generations of pods. If older generations of pods could get that level of digital zoom, newer generations will obviously use at least that much digital zoom, if not more, coupled with the better optics.

Again, that doesn't mean the Litening would have greater zoom. The Sniper can have digital zoom too (in fact, the XR mode is a digital zoom). Both have optical and digital zoom, and the Sniper is a newer pod with more powerful optics, so the most logical thing would be for it to have greater zoom overall (for instance, same level of digital amplification over a greater optical zoom, would yield a greater final zoom).

Ivandrov: I can imagine that's the case, but that doesn't explain why the Sniper would have less zoom than the Litening, it should still be the other way around.

[this was merged here from another thread] Litening pod in max zoom (TV, MAN RNG knob all the way and expand active): Sniper pod in max zoom (TV, MAN RNG knob all the way, and TVXR active): The ATP is known for having way more definition than previous generations of pods, so this doesn't make much sense. Am I missing something? One thing I noticed is that in TVXR, the MAN RNG knob doesn't change the zoom, it's always at 1.0X. Maybe that's the reason and it should be able to go to 4.0X like in the other modes? The same happens in IR, with an even greater difference in favor of the Litening. Thanks in advance for the help!

Hi! I've been working on a tool to manage DCS and SRS servers. It lets you start/restart/stop, edit configs, upload missions, download tracks, and even configure automatic health checks that keep your server up and restart it when it crashes, etc. All with a very strong focus on making things simple: installation is just running an exe, configuration is just there in the ui, etc. It started as a simple script for myself, then evolved into a nicer web ui, and then I decided to share it with the world and so put some effort into making it super easy to use. It has some overlap with the DCS Server Bot, obviously. But I really don't like the idea of administering servers via Discord chat, and wanted something far more simple than what the bot provides (too many extra things to install, configure, maintain, etc). Downloads, documentation and more: https://github.com/fisadev/dcs_server_manager/

Oh! Thanks for the info, I didn't know the real thing wasn't roll corrected. Sorry for the noise then, marking your answer as solution

The more the head is rotated in the Apache, the more the icons marking stuff in the ground get misaligned (waypoint, radar targets, shots markers). This short 15s video demonstrates the issue very clearly. It happens on all missions and settings, under VR (can't test it in 2D), and as far as I can tell to everyone (seen on youtube videos, friends, etc). Couldn't find a reported issue about it, sorry if it's been reported before. I can also provide a sample track, but it's super easy to reproduce: you just have to fly with a waypoint and tilt the head, and the alignment clearly breaks.

fisadev

Hi! I wanted to share a very useful discovery that at least in my setup, helps me fix the F10-map-related FPS drops when they happen. This doesn't prevent the FPS from dropping when using the map, but fixes it when that happens. Most of you are probably already aware that doing alt-tab can get your original FPS back, but it's unreliable at best, and sometimes it just won't fix it at all no matter how many times you do it. Well, I think I found out why: even if you alt-tab, if any screen (including the VR headset) is showing any pixels from DCS, there's a high chance the drop in FPS isn't fixed. So you have to make sure absolutely no screen is showing any part of the game at all, including the VR headset if you are using one, to get your FPS back reliably. In my case, that means doing two steps: 1) Alt-tabbing to another full screen app. Not just any app, but a full screen one. I just use a cmd.exe window in full screen mode with F11, which I always have opened anyway when flying because of some home made scripts I use for a button box. 2) Switching to the desktop mode of Virtual Desktop (which I use for the VR headset), getting out of VR mode, so DCS isn't rendered in the headset anymore. In the case of VD, you can do that with a VR controller or with the Shift+Windows+D keyboard shortcut (while DCS isn't in focus, otherwise DCS "eats" the key presses. But after step 1 DCS is already out of focus, yay). Those two steps guarantee that no screen, desktop or VR headset, is trying to show any pixels from DCS at all. And that seems to do the trick, I get my high FPSs back every time when doing this, 100% reliable in my case at least. Hope that's the case for others as well!

I found this bug today too. I was trying to record a tutorial video for the radar, but all targets were jamming me, even an I-16. It made no sense, until I realized it was the active pause that was causing the jamming.

FTR is good enough alternative to something 99% of the players can't simulate (a force feedback stick). Not even close to asking for something to be less realistic just because the realistic version is too slow for someone's taste, man.

Not useless, he's right. If everyone starts just posting stuff they "feel" could be different, the real bug reports will get lost in an ocean of noise. It's in the best interest of everyone to prevent that.