MoleUK

Это была проблема, по крайней мере, 3 года, но в большей степени это проблема для VR-игроков, поскольку это может привести к переполнению памяти в мета-ссылке. Блокировка положения F10 и сохранение масштаба помогает уменьшить проблемы, как и использование мода пустой вешалки для пользователей VR. Но это не устраняет проблему для всех. Вероятно, здесь имеется более одной ошибки.

Can confirm that they are broken in MP atm. Frontgunners and sidegunners. Sometimes they open fire for a while, but they inevitably get busted.

See if this helps. Dump these in your saved games folder for DCS. Saved Games > DCSOpenbeta > Liveries > Cockpit_FW190_A-8 > Default https://www.dropbox.com/scl/fi/902tnu4hjr6bd1gahjtyc/id_13_D_FILTR.dds?rlkey=09asektjkq007a76c1f4c00qz&st=fphc6qh0&dl=0 https://www.dropbox.com/scl/fi/73ehptgjyt2375r8nq5w7/description.lua?rlkey=7zedyax014asqeoisdk1vdse5&st=y0sgi0xs&dl=0 It will clear up the canopy and may help reduce/eliminate the flicker. Passes IC.

Of course it's unrealistic, the entire zoom function is unrealistic. You don't actually want realism though. You don't want to sit through hours of briefings and debriefings before and after you fly. You don't want to have to quit the game every time you die, instead of hitting respawn. You don't want to go through a court-martial whenever you accidently friendly fire something. Because you don't want actual realism, you want an approximation of realism. Actual realism isn't very fun, not even in this game that we play. And it is a game, there's an easy way to tell. Join a multiplayer server quick, get in a jet and hit '. You'll happily see all your air kills, ground kills and deaths listed. And your score for the videogame you're playing right now. I understand that some people would rather scream "It's a simulator not a game!", but it's very much both. And given that we don't want actual realism in this game that we play, we settle for many approximations to best enjoy it. To make it more fun. The current VR spotting approximation isn't fun or accurate, at least imo. So it fails on both counts. Spotting can literally never actually be 100% accurate to RL even if you wanted it to be, due to playing with pixels on a screen, rather than looking through a glass canopy and atmosphere. But it would be nice if this particular approximation were tweaked a bit again, which it appears it will be eventually. Hopefully for the better.

DLAA definitely doesn't help yeah (especially in motion). I've tried various different resolutions, both with and without DLAA. None lead to the same ease of spotting as flatscreen atm. Particularly as you can zoom out in flatscreen and make the dots immediately 'pop'.

Unfortunately it gets more complicated due to various AA and upscaling techniques. DLAA and quad view for example. I can't get dots to appear as well in VR as they do in flatscreen period atm. I can just zoom out in flatscreen and get dots to immediately 'pop' far better than they ever do in VR. Yes, I can only speak to the experiences of myself and others who I talk to. It has had an effect, and not a good one. It's true, I can't stand debate. I run away from it and can't engage at all. It's so easy to die. And realistic too. So let us disable accounts upon death, this is reflective of reality. If the aim is realism, when a pilot dies then naturally you must you die. Game over. Unless of course the aim of gameplay is more than merely realism. Perhaps the aim of the game is some level of fun as well as a touch of realism. But no, that can't be right. Sarcasm aside, the aim of the game is FUN. If you insist on rules that almost no others enjoy, what do you think happens to the game? It dies. Because you drove away all the other players. I think we can agree that nobody wants this outcome. At least I hope so.

Ok, force spotting to be just as bad in 2d as it is in VR right now and watch what happens to the playerbase. There is 'realism' and there is 'fun'. Currently I have neither. Dying shouldn't be easy in the first place, so forcing it to be bad for everyone would be the best natural choice. Therefore let us make it so you can only die once per 24 hours, and then be locked out from further play. This is a bit more realistic. Though really we could argue for permanent consequences. There are hundreds if not thousands of possible software/hardware setups for VR, which is why this one size fits all approach is somewhat self-defeating. Of course there is one approach that potentially addresses all this (dynamic scaling), but it has been ruled out as a solution for whatever reason.

This would be a great thing to have, even just as a keybind. The way the mouse moves/displays in VR has always been jank, and it would solve a lot of frustration. Personally I have to switch to F10 to find the mouse cursor a lot of the time. And while that's not ideal for me, for other users with F10 performance issues that's not really an option at all.

The problem is that the new VR spotting has taken the fun out of things for a lot of us. It's currently a lot easier to spot in flatscreen than it is VR, that can be tested fairly easily by swapping between the two on the same settings on some spotting mission tests. I assume that the changes were not made with the intention that VR players should find it far harder to spot than flatscreen players, but that is the state of the game for a lot of us atm. For me if I can't see a damn thing (as things currently stand) it is no longer a fun experience period, as a result I have stopped playing almost entirely. I understand that some people may enjoy the reduced spotting, but from my perspective I would rather those players have an option to enable that playstyle for themselves rather than force the current lack of visibility on everyone else.

It's mostly a reason for ED to invest the time in doing it. And yeah the Apache was always very rough for VR as well. It's remained a performance hog ever since release, so I have come to accept this as the new norm. The Chinook demands have only cemented that. Doesn't mean there won't be optimisations that arrive, but unless something drastically changes the Vram and general horsepower requirements are only going to keep escalating. Unfortunately Nvidia has been stingy with vram for generations of GPU's and seems unlikely to change much there, so a lot of DCS users are going to suffer in the meantime.

The recent releases from ED do seem to be trending towards higher and higher vram requirements. This could actually be solved by offering a lower texture install of recent (if not all) modules in the module manager, a bit like steam can offer optional 4k texture pack downloads but in reverse. Not everyone needs or wants the extreme level of detail that is now on offer. User mods have shown that the module textures can be significantly shrunk while still maintaining most of the visual fidelity, and given the module manager already exists perhaps it could be leveraged to help users with GPU's that have less than 16 gigs of vram. And if ED wants to get more people to install standalone rather than steam, having this feature only available on standalone (via the module manager) might be another incentive to get users to make the jump.

Планируется ли предлагать загрузку текстур более низкого качества/размера в диспетчере модулей для более поздних выпусков модулей? Я спрашиваю, потому что последние несколько выпусков (Apache и Chinook), похоже, имеют тенденцию к необходимости использования 16-гигабайтного графического процессора с видеопамятью для работы на высоких настройках текстур без проблем с производительностью переполнения видеопамяти. Поскольку мы не можем устанавливать уровни детализации текстур для каждого модуля, было бы полезно, если бы была возможность альтернативной загрузки/установки этих модулей через менеджер модулей. Даже если бы он был доступен только при отдельной установке игры, это было бы очень полезной опцией для пользователей, у которых нет 16-гигабайтных графических процессоров. Или для пользователей, которые работают только с разрешением 1080p и т.д. и которым не обязательно требуется сверхвысокая детализация. Спасибо

Re: The terrain stutter specifically, a frame-rate cap (applied externally ie from NVCP) + low latency ultra and vsync fast was going to be my suggestion to try and fix it. But I see you've already done all three now lol. That seems to work for me and some others, but not everyone reports success. I'm assuming it's something to do with the terrain render thread getting out of sync but that's just a guess. Yes, despite skepticism from some users, low latency mode does seem to fundamentally alter something for the better. At least in VR. I would also always recommend having an external frame-rate cap, ideally set in nvidia control panel. Just set to your headsets refresh rate. Vsync fast may or may not help as well.

If it's a very regular heartbeat like stutter that appears on the FPS graph as massive FPS drops as opposed to general FPS degradation, it's worth eliminating any mods/scripts as a possibility. Could try renaming the DCS savedgames folder temporarily to see if that fixes it. If it's more like the terrain not moving by smoothly while everything else seems fine, that's a different problem entirely and is a bit tricky to try and address. Terrain jitter problem shown here:

I saw something similar to this recently. Was only getting it in track replays and SP content. Turned out after deleting the OH-6 mod, I still had mod .lua files leftover in the savedgames>DCS>Scripts>Hooks folder. Deleted the leftover mod .lua files (the loaches AI gunner hook lua can cause issues iirc) and that sort of stutter disappeared. I will say though anecdotal, I've seen lots of user reports of increased memory usage since the Afghan patch (2.9.6.57650) I think as well. I know the patch notes did list changes to the terrain render tech, so it could be related.

From the last patch: "DCS: UH-1H Huey by Belsimtek Corrected rockets placement in XM158 launcher" This is the result: Only the XM-158 pods are affected. uh1.trk

From the last patch: "DCS: UH-1H Huey by Belsimtek Corrected rockets placement in XM158 launcher" This is the result: Only the XM-158 pods are affected. uh1.trk Sorry, meant to post this in the Huey bugs section. Have now done so.

Might be useful for any of the simpit crowd. Can toggle it on/off as needed. The flickering might be due to poor lighting or being near the edge of the stationary guardian, as there wasn't flickering in the first recording before I re-enabled the guardian.

Is this still waiting on attention from ED's end?

Возможно, вам придется полностью удалить его, а не просто отключить набор инструментов. Стоит попробовать. В противном случае VD остается вариантом, который я бы посоветовал всем иметь в наличии, хотя бы в качестве резервной копии. Лично я считаю, что он работает лучше. Возможно, DCS изначально пытается запуститься в режиме виртуальной реальности, а не в плоском экране, и происходит сбой, в зависимости от того, что вы добавили в ярлык.

Отключите OpenXRToolkit, Meta исправит это в версии 69. Альтернативно используйте VD, который не страдает от этой проблемы. Кажется, что VD часто избегает этих проблем, которые создает мета, поэтому его стоит иметь в качестве резервной копии. Многие пользователи в конечном итоге просто постоянно используют VD вместо ссылки, поскольку в некотором смысле он может работать намного лучше.

Known issue. Meta should fix it with v69. Until then, either don't use openxrtoolkit or use VD which has no such problem atm.

Yes, disable/delete super carrier module. Could also try disabling others as well but I don't think that makes a difference currently. Only time I've seen the frametime a bit like that was the map drawing degradation problem. I think it's been fixed but haven't double checked: You can/could workaround it by hitting escape while on F10 before returning to F1. Hitting escape hides the map drawing which is/was the source of some degradation loop. The longer F10 was left open the bigger the degradation before it hit a reset point.

TAA is often a poor alternative. This remains true in DCS. An alternative solution might be XeSS native resolution (XeSSAA), ED would need to implement that. And long-term they probably should as it's platform neutral.

Для запуска вам понадобится официальный адаптер. https://www.play-asia.com/playstation-vr2-pc-adapter-for-pc/13/70hb33?ref=google_uk&srsltid=AfmBOorRuNmAspchzAmLfR7WNdOqNJY2xss_ysWyvEw06n_Ez-e_7qqV62w