All Activity

Fixed, I should not post over the phone. Thanks mate

J-10A/B and J-11B/J-15 are probably doable too.

(Btw, you put white colored text over white background, rather unreadable, at least for people with the bright theme)

I have updated to Beta 2.9.5 and I fly mostly warbirds. I have noticed that the effects for Cannon / Gun Fire for both the F4U-1D and the P51-D are not working - AND Not showing up in the "Effect Monitor" The rest of the effects seem to work Does anybody else have the same issue?

Ну значит только вы и FAB999 от имени всего российского комьюнити ответственны отстоять честь отечественной оборонной радиоэлектронной промышленности

Связка экрана и линзы расклеилась наверное. Должно быть видно на выключенном шлеме даже. Пара таких дисплеев с линзой по-моему около 100 евро стоит на Али + найти где делают. Вроде кто-то постил тут или в VR теме ссылку даже когда-то.

sicuramente andrà così .. mio spero sempre in Indiafoxecho Sarebbe un sogno …. @Indiafoxtecho IFE non arrabbiarti Anche un macchi 202 …

does it happen to you? If so are you using VR and which Hz rate do you use? then what is it and why am I not suffering as much? EDIT: I was just in a MP session on through the inferno and I had lowered my Resolution of the G2 and it was near perfect the entire flight. the Frametimes were below 7.2ms on GPU and 6.0 on CPU and I had a near perfect flight time going to WP2.. I looked out the sides and seen no stutter, nor spikes when airborne. I use the fpsVR Counter.. the point I am trying to make is maybe you put too much on your PC can handle.. or something else is amiss..

Yeah... this is very good, maybe perfect. SnapViews["P-51D"] = { [1] = {-- player slot 1 [1] = {--LWin + Num0 : Snap View 0 viewAngle = 54.750000,--FOV Cockpit Zoom 54.750000, OEM 80.000000 "P-51D" viewAngleVertical= 0.000000,--VFOV hAngle = 0.000000,-- (Snap View)/(Cockpit panel view in)(-30°) vAngle = -30.00000,-- Cockpit View Angle -30.00000, OEM -9.500000 x_trans = 0.124000,-- Cockpit View In_Trans 0.118000, OEM 0.120000 y_trans = 0.060000,-- Cockpit View Up_Trans 0.060000, OEM 0.059000 z_trans = 0.000000,-- Cockpit View Rt_Trans 0.000000, OEM 0.000000 rollAngle = 0.000000, cockpit_version = 0, [13] = {--default view viewAngle = 40.000000,--FOV Cockpit Zoom 40.000000, OEM 80.000000 "P-51D" viewAngleVertical= 0.000000,--VFOV hAngle = 0.000000,-- (View Center)/(Cam View Dn-Slow)(-30°) vAngle = 0.000000,-- Cockpit View Angle 0.00000, OEM -9.500000 x_trans = 0.124000,-- Cockpit View In_Trans 0.118000, OEM 0.120000 y_trans = 0.060000,-- Cockpit View Up_Trans 0.060000, OEM 0.059000 z_trans = 0.000000,-- Cockpit View Rt_Trans 0.000000, OEM 0.000000 rollAngle = 0.000000, cockpit_version = 0, Give it a try. Bowie

Description: Recent feedback from the DCS general channel indicates that DLAA (Deep Learning Anti-Aliasing) is adversely affecting spotting spots. Some users, including me, report difficulties in identifying aircraft at 2-3 nm on 1080p and 1440p displays, particularly during dogfights and bombing runs. This suggests a significant issue with DLAA’s current implementation. This issue isn’t observed with DLAA off or when using MSAA. However, DLAA is still preferable, given the performance and graphical boost. DLAA applies a neural network-based upscaling and smoothing process that can blur or misinterpret fine details, such as the pixel-sized spotting dots used in DCS for target acquisition. This blur effect becomes more pronounced at lower resolution. The performance degradation is resolution dependent, as noted with better results at 4K as some users reported in discord. Request: I ask for the addition of an option to bypass DLAA’s effect on spotting spots. A toggle to disable its influence on these elements would improve visibility and accuracy. I appreciate your consideration of this request. Thank you.

Yes. I’ve got a pcie card coming today to see if having a designated usb system for the screens will help. It’s a Hail Mary but hopefully it will be the solution.

Good Afternoon, Like the title says, my game crashes at this step regardless of what aircraft, mission, server, etc I'm using. I'm able to get into the game and use the mission editor, but trying to actually start anything results in this outcome. Attached is my crash log. This is on a brand-new (clean formatted) and fully updated windows 11 install with a brand new DCS install. The only module I have currently enabled outside of the default free ones, is the hornet. I have ran memtest and verified that my RAM is fully functional. I'm on the Latest BIOS drivers and NVIDIA drivers. Page file is system manged. Both the Saved Games, and the main DCS folders are exceptions in windows defender. This computer with the same hardware, used to work flawlessly a few months back. Please let me know if you need more information. dcs.log-20251016-205211.zip

Читателей посылаю )))

I would have to check, but what I just tried in the main menu was configuring both F-5E (FF) and MiG-29 throttles directly one after the other, and the throttle settings of the former always overwrote the throttle settings of the latter. There is a direct connection between those two throttle settings

Сидите в польской библиотеке и смотрите методичики в читальном зале?

Thank you @nibbylot @Rudel_chw and all the others that have given their time to bring this awesome update to this great Naval training aircraft for DCS!!! Bravo Zulu for all your hard work folks!!!

I’ve tried the in-game comms a few times but always end up back with external stuff since it’s easier to manage, especially in bigger groups or multi-server sessions.

ED seems to be quietly tweaking the ATP in updates. We've noticed some minor changes that aren't in the changelog. I'm really liking it. It would be nice to have an option to speed up the BIT for cold starts. -Ryan

Damn that makes me feel old! Having spent a bit of time operating out of Laage with the German Mig 29's

Or 33 calendar days, whatever comes first. Thankfully there are devices for automatic diagnostics.

Нет.

Aircraft like the J-10, J-11B, Su-30MK, Gripen, EA-6B would all be nice additions as far as AI assets.

Hey all, thanks for the information very informative. I do have my curves currently around 25 in the set up. But I think @GTFreeFlyer gave me the answer. I am a "stick" rudder- twisty-guy. This, in tandem with a flight model thats a bit touchy, is probably whats causing such a big pendulum effect when I apply rudder - at least in a straight line. While banking it really doesn't cause an issue. Just on strafing runs especially as dive speed picks up over 300 knots. Anyway, thanks again. Maybe this will be fine tuned by the Devs in time for the new Reflected Campaign thats due out soon. Well, maybe soon.