All Activity

Does this mean antenna sectors 1 and 8 are not exactly at 70 degrees but further back?

Ricordo che ero sempre legato alla VR

У меня то же не работает.

Thanks for correcting me. I was wrong! [emoji1303] Cheers! Sent from my SM-A536B using Tapatalk

Work around that may work is put a soldier unit inside and use it to detect hit. In some cases they'll sit inside so you won't see them, but they may sit on top so may or may not work.

Hey all, some feedback from the team: The detection of emitters abeam of the aircraft: the answer is it cannot do this very well. The 90 degree light doesn't correspond to exactly 90 degrees off nose, this "sector" will change both in size and location depending on power and frequency of the threat emitter. So it cannot be relied upon for precise notching. And because it relies on simultaneous reception by both the rear hemisphere and 50/70 degree antennas, both significantly off-boresight, the reception in that area is significantly weaker. They do not even overlap at 50% beamwidth like forward hemisphere channels, but actually further out. So if the signal is too weak, the 90 degree lights might not trigger at all, and the threat might just jump between 50 degrees and rear hemisphere. This is accurate with multiple sources on this.

Тут такое дело, тестировал я эту авигационную систему и в хвост и в гриву и понял, что имеется следующая ошибка: Неправильно считается истинный курс. Кто-то на туда вычел магнитное склонение, поэтому с восточным склонением ИК оказывается больше магнитного на величину склонения, а должен наоброт меньшне Дело не в джойстике. Проверьте, что кривые отклика в настройках осей джойстика не используются. на ФФБ их использовать - это вообще смертельный грех, но оказываются есть и такие )

К сожалению документы здесь не любят, всё больше по слухам и субъективным ощущениям ориентируются...

I just find changing the rate to feel clumsy especially if it has to be 125. I would change it back to 1000 after exiting DCS

agreed. with the data we have available, there are users with other brands of mice, that do not use G HUB, that have the stuttering problem. and in our case, G HUB cannot be singled out as the culprit. as far as my system is concerned, i do not have stuttering, and i use G HUB. check out this link if you have not already. https://www.wikihow.com/Change-Mouse-Polling-Rate

No The problem can still occur with GUHB off, but I have it on in order to change the polling if I need to.

No, I’m at 120 fps. looks exactly like the above example unfortunately

Try dots at 2 pixels on the options menu. I highly discourage upscalling in DCS, which is a very pixel sensitive type of experience but it can be mitigated with the dots at 2 pixels thing.

I'm having much better luck with DLAA, but running not-VR at 1440px with a 5080 doesn't require DLSS. -Ryan

Ну, такой подход оправдан, когда один самолет является непосредственным, скажем так, "наследником" другого, или когда самолет создается в сжатые сроки, "в режиме аврала", во время войны... Наглядный пример - ЛаГГ-3/Ла-5... Разработка же МиГ-29 началась в 70-ых, а в серию он пошел в 80-ых... уж за 10 лет можно было бы адаптировать блок управления закрылками от МиГ-23 под 29-ый...

Nope.

What about the official paint kit? :C

Up until recently, probably the very last update, I would make make a flight plan in the ME, and it would automatically give me a nice magenta line on the GPS. The FP and it's waypoints are no longer showing up. It happens I was using the C-101 on the Normandy map, but I don't know if that's relevant or not. I'll try it later with a different aircraft, but I know it most certainly used to work on the C-101.

Это отсюда кадры, с русскими субтитрами смотрибельно

@Flappie I double checked the rotorbrake . I move my controller (Saitek throttle quadrant) upwards. the rotorbrake handle moves downwards in DCS. Then I can start the engines. btw: maybe it will help , if you delete this axis and rebind it

Thanks, will look for the setting and check if it works. By the way, I use VR.

My sim is locked at 40fps for personal preference: hardware + fps consistency across anything that's possible to occur on screen. The ghosting doesn't get in the way of my combat. I assume it will diminish with higher FPS too as it is the nature of temporal anti aliasing. Keep in mind that is FPS dependent, which is the actual render the temporal anti aliasing is acting upon previous frames to generate the next, not "Refresh Rate" dependent. The later only affects monitors if you're running with no Vsync, which is already the standard to run without. The gif is at 25 for compression sake.

I had the same issue until I realized my mic input level in Windows was too low—boosting it made a huge difference in both VOIP and SRS clarity.

After giving it some serious thought I ordered both the throttle base and stick base off of Ebay since I already have the grips and I can't afford a Moza Hotas. I'm still very disappointed with winwing and their customer service.