All Activity

Windshield ventilation / anti-fog would be my guess.

well a lot of us have been fine using the G2 so at least that much lol (in other words it far worse in the g2 vs the super)

How are you connecting the Quest 3 to VD? Do you have a dedicated access point? Look into connecting your Quest 3 directly via an ethernet cable to see if the problem still exists.

If your controls allow, you can also make turns on the ground by splitting the throttles. Similar to how a tank turns; Leave one propeller at idle while powering up the other propeller. Hope this helps.

also with the FPS counter, it says CPU limited ... what it means is not really that the CPU is limited; rather DCS just can't use any more CPU processing power... which is different, it will likely be the case that some CPU cores will still not be fully utilised, faster individual core performance will help some... but ultimately you will as @Hiob says be limited by something... a couple of things that *WONT* change the CPU limited status, is making sure that DCS does not use core 0/1 (which is what windows uses by default) and the same with other DCS performance related processes like your VR stack or voice attack , beyond that other than a CPU with faster cores not much can be done by us

Well, I agree with you, didn’t wanna “argue in the contrary”, we’re here for the same goal. It’s just that sometimes people consider bugs things that are not bugs (not just in the Corsair, in all modules). Opening (yet another) thread saying this thing flies 200mph at max power and is severely underpowered is not gonna help anyone, devs are just gonna disregard it. It is frustrating because I would also love this module to shine, not just because I’ve paid for it…but because I truly love this aircraft. And to be clear, I also think it flies slower than it should.

Да его уже никто не даст, так что на этом можно только поставить точку

Any idea what the highlighted portion is?

No, we weren't using DCS. We used FS2024 or 2020. Whilst I tried a variety of manoeuvres, all just felt a little slow in their reaction speeds and as a result, felt less natural. As mentioned, with the cost, space issues and required tweaking involved, taking the risk that it "might" be possible to dial it in seemed a bit of a jump too far. In addition, I know someone who had a DOF3 and eventually sold it on.

Я думаю он имел в виду игровую опцию, которая позволяет при холодном старте сразу иметь выставленную инерциалку. Т.е. при включение ИКВ и НАВИГАЦИЯ будет стразу готовность навигации.

Why be so dramatic? They are not abandonware. Persian Gulf, Caucasus, NTTR are all feature complete but still receive tweaks and bug fixes. thanks

Regarding headlights, the problem is more complicated than that: In a war zone, an armored column traveling at night will primarily use NVG or infrared devices to avoid turning on their headlights, which would make them visible from miles away, especially when faced with aerial reconnaissance vehicles (drones, helicopters, planes, etc.). It is therefore normal for columns to travel with their lights off on DCS. Outside a war zone, however, they would turn on their headlights normally. Also, it might be more interesting if ED added an adjustable "Lights on at night" option: true/false (default: false). Regarding brake lights, I believe some vehicles have them (but probably not all models). However, I find that this is clearly not a priority for ED; I would still prefer if they added many new units. At ED, you have a model with 2 animations: "intact" and "destroyed". The explosion allows you to make this transition between the 2 animations (this hides the texture change) A ship can sink in 10 hours. A ship can sink in 2 hours. A ship can sink in 18 minutes, like the Lusitania. By convention, in most video games, when a ship is destroyed, it sinks in 1 minute. It's true that it might be interesting to extend this duration of the sinking for rescue operations, for example. Perhaps add a slider option to define the sinking time? Or something relative to the damage ? We can already adjust that. There's an option to adjust the dispersion time during an attack. Personally, I often set the dispersion time to 3 seconds, so it looks like everyone is swerving (panic), then pulling themselves together and continuing on the road without stopping.

PG, Caucus, Normandy (all of them), NTTR: all abandonware. ED specifically said that NTTR will never get an update.

I've done that with VAICOM Pro, but again this is dependent on the mission. Sometimes Jester is happy to "set map marker 1 to fixed point" and other times he just plain ignores you. v6, boNes

Tom Kazansky said: Please note that the Oasis driver only works with Nvidia GPUs. I don't know if support for other GPUs is planned (or possible). YES, they are working on making the driver work with AMD.

Yes again. I encounter a problem. I need to blow up a bridge in the beginning of a mission. I want it to look like the bridge is under repair. But the explosion in the beginning of the mission kills the static diggers. Since static can't move, can't be made immortal, and can't have late activation. I can't have the diggers where i want them.

兄弟，现在wmd7吊舱指定ls6滑翔炸弹偏差也太大了吧。已经很久很久了，别让老外看笑话啊……

Или особенности восприятия?

Can you reproduce in simple single player mission?

Заметил такую особенность работы освещения в ночное время. Луна кажется делает свет от источников еще ярче, в то время когда без луны они становятся более тусклыми. Вот пара скриншотов Вот яркость источников света когда ночью слегка подсвечивает луна А вот яркость источников света, когда ночью луны нет либо почти нет (низко над горизонтом и тусклая) Кажется должно быть наооборот чем меньше глобального света тем отдельные точечные источники должны быть контрастней, если не вдаваться в другие подробности. Настройки графики на скринах на макс.

Likewise happened to me last night. Dropping a GBU-12 from the starboard front CFT station in level flight in the external view (viewing from port). Heard a clunk and the jet shook from side to side. By the time I landed the engine on that side of the jet was dead.

There are some elementary things to understand. a) you will Always be limited by something. No matter how potent your hardware. b) wether it is your GPU or CPU at any given time is circumstantial. It depends on scenario and settings. c) VR puts much more strain (relative) on the CPU than 2D d) if you haven any fps-limit enabled, it can muddy the waters. Depending on which kind of fps-limiter you use (in game or external) it will be enforced either by the CPU or the GPU, and will be reported as the limiting factor accordingly. E.g. the default in-game fps limit is set to 180 if I’m not mistaken. If your GPU AND CPU could deliver more frames, it would be reported as CPU limited. If you would on the other hand enforce a lower limit, say 120 fps via the nvidia driver, it would be reported as GPU limited.

I have some mura in my Super. But it is little. It is no problem. I have to look for it. So, I don’t think about it. My old Reverb G1 and my Sony PSVR2 has much more. Much more.

Bulgaria camo, circular roundels please.