MoleUK

I'm not necessarily arguing for disabling IC, just pointing out that one of the games biggest servers had it off for 5 months. The world didn't end. And why would disabling IC lead to more cheating, when we've already established that the IC doesn't seem to stop cheating? It just stops some forms of cheats but not others. Lots of games let you decide whether anticheat is enabled, that's not very unusual. This is not a ranked MP game or something, with any kind of ingame currency or progression to hack your way through. There are already people exploiting known bugs and mechanical quirks to their advantage. Like zooming in/out in track-IR to make the current dots pop much bigger. You won't stop that behavior, and you probably shouldn't base the entire MP experience around those people. At least imo.

I think I saw this bug listed as fixed in a changelog previously, could have reared it's head again. iirc last time it had to be ticked off in the special menu or it would render while invisible.

Unfortunately so. And some users regularly take advantage of known exploits that pass IC for as long as they possibly can (See: Viggen high altitude performance before it was fixed). Or the new chaff jammer toggle trick that's just been publicised. That'll likely be widely abused for weeks/months before it's fixed. There's always something. I just enjoy the game and do my thing.

God I miss the clear canopy mod as well. The baked in reflections on the Huey/Hip remain godawful, and it's been a year since the IC change made the fix to that problem no longer viable. ED really should have copied over some of the quicker autostarts for a tickbox option for each module as well.

When has the IC ever stopped cheaters? When IC was enabled I saw a couple hackers caught on ECW. One was teleport ramming while invulnerable, the other managed to hack the weaponry. They weren't flagged by IC, they had to be manually caught and banned. You'd have to ask the staff if they had a surge in cheaters when IC was disabled for those 5 months. From the outside nothing really looked any different, and from what I've heard the IC really isn't very sophisticated at all. It's just a small userbase so there's less people with the incentive to work around it. It's in the past tense because the moment ED added the spotting mod to the game, the IC was re-enabled. Disabling IC had no negative impact on the player numbers while it was in place.

ECW ran with the IC disabled for 5 months almost to the day so people could continue to use the spotting mod after it failed IC. It remained one of the most (if not literally the most) populated MP servers in DCS for that entire 5 month period. Players don't enjoy being blind, even in MP.

Yeah the dots are only rendering some of the time and at certain angles. The more ground units there are in the mission the more this becomes a problem. Longstanding bug, which has complicated the whole spotting discussion from the beginning. There seems to be a limited number of dots, and ground units seem to be shared with air units for that number. It might be that in VR because it's rendering them twice (or potentially 4x in quad view) it's hitting that cap quicker than in flatscreen.

О, а модели пехоты должны исчезать с небольшого расстояния? Я предположил, что это шаг оптимизации, а не ошибка, но решил проверить.

Была ли проблема со 100 точками воспроизведена внутри компании? Я продолжаю сталкиваться с этим, и пятна перестают отображаться и начинают исчезать, когда я перемещаю камеру. Я считаю, что в виртуальной реальности ситуация хуже и, похоже, связана с количеством наземных юнитов в миссии. Как только вы превысите 100 наземных единиц, воздушные точки начнут исчезать. Возможно ли, что стереовидение или четырехмерное изображение приводят к тому, что система точек перегружена количеством точек?

ECW Suffers badly from the 100 dot bug so you don't get the dots at all there sometimes. Try it on other busy servers and you don't always see the same problem. Until the bugs that make dots de-render are fixed, people are not going to see the same things on their systems.

@BIGNEWY Just to confirm, dots are still disappearing or not rendering at all at times. Did a flight on ECW PG which had a ton of ground units present, so it's likely the 100 spot bug. This is going to make it difficult to give any accurate feedback while dots continue to not render properly at all times.

The transition points have always been awkward with spotting dots, that's something that hasn't ever been fully fixed afaik. 3nm was often a point where users would complain about their appearing/disappearing instantly, a smoother transition would be ideal. And yea in my experience quad view with 1.0 as a centre focus really seems to squash down the dots. I really don't entirely understand why, perhaps the developers could look into why it's tilting things.

Do not confuse allocation with usage re: vram. DCS will allocate all the vram immediately. But actual usage will vary a good bit, and the chinook remains an absolute hog for vram. Though vram alone likely isn't the only reason the Chinook is a performance hog mind. I think ED found a relatively good sweet spot for visual fidelity vs performance with the Hind (and even then it wasn't exactly light on the system), every ED release since they seem to be pushing things too far or optimising too little.

Honestly imo there was something inbetween their v1 and v2. On the initial rollout of v1 I had fairly large dots, that slowly seemed to be degraded over several patches. This may have been due to changes on my end (quad view, DLAA), but I suspect there was some unnannounced tweaking at some point idk. Then v2 rolled out with no announcement and it was immediately noticeable that it had degraded again. Everyone seeing different things depending on their individual VR setup is a huge confounding factor. And I don't know if it can be said with any confidence that the "average" VR user was a fan of the V2 revision or not. We'd need more feedback than just forum or discord complaints/praise, as if I were just going on feedback I've personally seen/heard I'd say most people did NOT like the v2 VR spotting dots as most feedback I saw complained about lack of visibility. And i'm not sure what the "Average" VR users setup looks like right now for DCS. We will have an unusually large number of higher end headsets as people spend more on this hobby, and aside from that many users have started using quad view even with headsets without eye tracking. A lot of the feedback split I've seen between those praising vs complaining about spotting dots has come down to whether or not they're using quad view. Though that is by no means universal. And I don't entirely understand why quad view is squashing dots so much, as I have the focus area set to 1.0 so it's not upscaling. It is sharpening (AMD CAS) and doing other stuff though, so perhaps it's a quirk of the rendering. I'm assuming it's not due to something as stupid as the dots size being calculcated based on adding the resolution of the outer focus to the inner focus, due to the game rendering 4 views rather than the normal 2. Though it might explain some things if the game is overestimating the resolution you're running at when quad views is enabled. And yeah an individual setup for each headset is going to take a lot of tweaking, and every time something new and unusual pops up like quad views it might need to be factored all over again. And again for each new headset release. It's going to require a lot of upkeep, and i'm not convinced that 1: It will be done well enough to cover for settings variations, or 2: It will be done in a timely fashion. Which is why I just keep coming back to sliders as the most workable solution.

There are many exploits that are already used online, there is no avoiding that. Even the anti-cheat is faaaaaar from perfect unfortunately. I would rather we not base the entire spotting system around a few players who will abuse it. Just let me set it to what I want on my end so I can continue enjoying the game, I don't care if others will abuse it to spot me from further away than they should. Many of them abuse badly modeled radars to already do that lol. And players exploited 1080p spotting for years to do it too. As I said, there is no perfect solution. There will always be a group of players who are upset with the solution. Sliders upsets the least and pleases the most, imo. Yep. I might not like that others would abuse it, but at least I would be able to enjoy the game I bought.

Not fully, but I think things are slowly moving in that direction yeah. Frankly it just makes sense as VR headsets get increasingly higher and higher res. And more and more of them include eyetracking.

I wouldn't quite define quadview as simply a mod. At this point it's integrated into the game, I think ED understood that it's kind of integral to the future of DCS in VR. And it wasn't just those using quadview who were unhappy with the VR spotting in the previous patch. Many of us just simply stopped playing because VR spotting felt awful in the last patch. Some felt it was fine, and good for them. But trying to have a single setting that pleases both sets of customers doesn't seem very viable. If you please one, the other will be upset. I still maintain a client side dot slider (and the ability to turn them off entirely) is the best workable solution atm given all the variance in setups, so hopefully we get there eventually. There will still be some complaints from a certain % of MP PvP users, but that is a niche within a niche of the overall users, and you literally can't please everyone particularly on this issue.

Until the "off" button works, I'd recommend you install and activate quad view as this reduces dot size significantly. This was part of the problem with the previous implementation where the very small dots became even harder to spot under quad view. Whereas the current spots almost seem tuned (intentionally or not) specifically for quad view.

Huge improvement on QPro at 2500x2500 with DLAA + Quad view. Spots are not oversized, visible from a good distance. It's unfortunate that they can't be turned off for those that want them off though.

Похоже, что их отключение в настоящее время не работает для многих людей. Включение четырехъядерного просмотра и DLAA на данный момент значительно уменьшат размер точек.

Приятно слышать. Может помочь с производительностью (vram) и размером установки одновременно.

Можно ли в менеджере модулей предложить альтернативные установки низких и средних текстур? Таким образом, его можно будет выбирать модуль за модулем.

It would be nice to see this addressed eventually. Unfortunately the new slider for canopies doesn't seem to have any affect currently.

Just did a quick stress test by maxing res and increasing refresh rate while on the Chinook, UI elements are still causing artifacting/distortion with ASW in general (while everything else in the pit is actually fine) and it remains particularly bad when in combination with the rotor effect.

Might be talking out my rear end, but as I understand it this problem is caused by DCS not exposing depth buffer information for reprojection techniques like ASW to work off of. So any UI or HUD elements will end up being garbled by the rotors since it doesn't know the HUD/UI elements are supposed to be in front of the rotor blur. Afaik nothing has changed there.