All Activity

она неправильная я бы сказал

Today is another one of those days where I pull out my Quest 3, start DCS on an i9-13900K and a 4090, and think to myself, "Today, it's just going to run smoothly..." - and I'm disappointed again. And the same loop over and over again. And I check the VD settings, check my TP-Link Archer BE550 6GHz settings, check the VD settings on the Quest, and the floor stutters like crazy during flight. I've already noticed that the movements of a wireless mouse can cause performance drops. In my frustration today, I unplugged the wireless USB transmitter on the Corsair mouse, even turned off my phone next to me to see if that might be the cause... no effect. The strange thing is, every now and then, out of the blue, I have a latency below 40, buttery smooth turns, everything is fantastic. And then, after a few hills and cities, just when I thought "FINALLY!"... it starts all over again. Rarely has a piece of software combined with hardware frustrated me so much. I've tried the smallest settings, the lowest bitrates, the fewest tasks in Windows—just about everything. The same problem remains: the cockpit looks and moves like I'm on the live set of Top Gun, and the entire scenery reminds me of my Amiga 500.

Yes, that could be it too. Someone else had a similar problem once. I've just corrected the description in the User files.

Previously, I used the grab button for the lever shown in the picture, after which the helicopter would rise into the air. The readings on this device also change (second screenshot). Now the grab button does not work to grab the lever.

Os dejo el enlace a un podcast de Motor y al Aire. Se trata de una interesante entrevista a uno de los propietarios de Aerges. Espero que os resulte interesante. https://www.ivoox.com/127-aerges-creando-aviones-digitales-audios-mp3_rf_155630619_1.html

boohoohoo hearing about the tragic story of the ah-6j mod makes me sad still, great video though

Yea but its impossible to taxi the corsair with 10 kts wind on the ground. Carrier or Airfield.

Ineed it does, but always precision factor PGM drops from 5 to 2, and the harm still finds the target with pin point precision. There must be something wrong with F-16 HARM system, and how it shows up the precision number. harm_HAD_max_PGM2.trk Simple mission attached as well. a2g_harm_accuracy_test.miz

That's exactly what you can do right now with Combined Arms.

Dear lefuneste01, I have recently activated the new PSVR2 eye tracking mod together with quad views and it works great, as it is for others: However, I've discovered that quadviews is not really working with SSAO because of a graphical glitch where the inner square is visible. This has been experienced apparently also by other users with other headsets, like the PIMAX. I've installed reshade to try to enable a SSAO shader through there, but although I can make other shaders to work in VR, just like you show in VREM, specifically the SSAO shaders do not work. I can't really make out from the first post or the rest of this thread if SSAO shaders through VREM are working in quadviews. So my question is: can I enable SSAO with quadviews, using VREM? Thanks for all your work man.

Рус явно нужно сильней обдирать, особенно рычаг тормоза: Ну и даже МиГ-21 в игре не настолько ободранный как например тут:

Никто не забывает. Обсуждался частный случай.

Amazing! It really comes alive with the upscaling. On the other hand, the AI is terrible at colorization. It just guesses the colors and usually guesses wrong. anyhow, it’s definitely worth watching

The problem with optimization is that every person plays on a different rig. If I remove the statics, it will run well for those with a lower end pc but will look plain and uninteresting for those with a good one. I’m defo not overpopulating the base, only the vicinity of the player. I can’t possibly offer and maintain several versions with different levels of statics. I need to draw the line somewhere. my theory is, if it runs OK for me, on my old laptop, in VR, then everyone must be able to run it. if you check my video, there are a few settings you can use for populated missions such as lowering the lod factor a bit. It does miracles. oh and there’s been that bug since ED moved texture loading to a different thread it struggled and stuttered, several people reported it - so again, it’s not the mission that should keep adapting every month to the current state of dcs and the player’s settings. It’s the other way around. I know tone doesn’t come accross in writing, I’m not saying this in an offensive nor in an offended, defensive way. I’m just saying what my experience in dcs and the mission editor has been like over the past 10 years.

Вообще,при разговорах об состоянии кабин, забывают что ЛА проходят регулярные ремонты, где лкп восстанавливается. Вообще самые реалистичные кабины - у последних модулей от ЕД. Самая идеальная кабина это у Ми24, у25 вообще отлично смотрится. Тут прям идеал.

Almost done with autopilot series. Master the pitch/roll autopilot, how it works with trim and the mysterious “compensation sensors” so you can fly and kill better!!!!! This should answer any questions and turn you into the machine of death!! https://youtu.be/KKJv8dDBEgU?si=DofWfL16PUbJ_ZN3

20 летние выглядят лучше… Такая облезлость, как у Томкета, один раз только мне попадалась на 60 летнем аэроплане. Если для Томкета это норма, то ладно. Это удивляет. Если немного вернуться в тему этой темы, то хорошо, что демонстрируемая кабина МиГа выглядит лишь немного б/у. Мне нравится. Или кому-то хочется её сильнее ободрать?

To be fair, you probably wouldn't taxi like that on a carrier in the first place. Aircraft would be moved to the launch positions by the flight crews.

How'd you get the picture of the lightning strike in the first post? That shows a lightning strike with scattered clouds instead of the overcast required in the legacy weather system.

@Morat Uh yeah. DCS's supersampling setting is always added on top of what you set globally with SteamVR. You were going crazy high per eye. In my case i never do SS settings in a game (DCS is at 1.0), i always go with SteamVR at 150% (which has one global setting plus one specific setting per game where you can add another factor to slightly finetune the global setting). My current global setting in SteamVR is ~4100x4200 per eye. Before using Quad Views and eye tracking you could see this directly in DCS's log file. Now with Quad Views enabled, it looks a bit different and shows the Quad View resolution outputs with DLSS: 2025-08-22 15:41:25.297 INFO DX11BACKEND (18664): Use DLSS preset 'K' 2025-08-22 15:41:25.350 INFO DX11BACKEND (18664): DLSS successfully initialized, 836x852 -> 1668x1700 2025-08-22 15:41:25.350 INFO DX11BACKEND (18664): Use DLSS preset 'K' 2025-08-22 15:41:25.385 INFO DX11BACKEND (18664): DLSS successfully initialized, 836x852 -> 1668x1700 2025-08-22 15:41:25.385 INFO DX11BACKEND (18664): Use DLSS preset 'K' 2025-08-22 15:41:25.419 INFO DX11BACKEND (18664): DLSS successfully initialized, 732x744 -> 1460x1488 2025-08-22 15:41:25.419 INFO DX11BACKEND (18664): Use DLSS preset 'K' 2025-08-22 15:41:25.454 INFO DX11BACKEND (18664): DLSS successfully initialized, 732x744 -> 1460x1488 One very important tweaking option for DCS is having an autexec.cfg in Savegame/DCS/Config: options.graphics.stereo_mode_use_shared_parser = false disable_write_track = true no_device_hotplug = true force_cross_eye_recovery_tool = false DLSS_Preset = "K" HUD_MFD_after_DLSS = true And why are you setting sharpening to 0.2? Go much higher! I'm at 1.0 Just in case here are my DCS settings (for graphics and VR only): ["VR"] = { ["bloom"] = true, ["box_mouse_cursor"] = true, ["custom_IPD"] = "62", ["custom_IPD_enable"] = false, ["enable"] = true, ["enableHMDMask"] = false, ["handOffsetX"] = 0, ["handOffsetY"] = 0, ["handOffsetZ"] = 0, ["hand_controllers"] = false, ["hand_controllers_debug_draw"] = false, ["hand_controllers_joint_throttle"] = false, ["hand_controllers_type"] = 0, ["hand_controllers_use_stick"] = false, ["hand_controllers_use_throttle"] = false, ["interaction_with_grip_only"] = false, ["mirror_crop"] = false, ["mirror_source"] = 1, ["mirror_use_DCS_resolution"] = true, ["msaaMaskSize"] = 0.33, ["openxr_eyeGaze"] = true, ["openxr_quadView"] = true, ["pixel_density"] = 1, ["pointer_use_type"] = 0, ["prefer_built_in_audio"] = true, ["use_mouse"] = false, }, ["graphics"] = { ["AA"] = "DLAA", ["BlurFlatShadows"] = 0, ["ColorGradingLUT"] = 0, ["DLSS_PerfQuality"] = 3, ["DOF"] = 0, ["LODmult"] = 2, ["LensEffects"] = 3, ["MSAA"] = 2, ["SSAO"] = 2, ["SSLR"] = 1, ["SSS"] = 1, ["Scaling"] = 0.66, ["ScreenshotExt"] = "jpg", ["Sharpening"] = 1, ["Upscaling"] = "DLSS", ["anisotropy"] = 4, ["aspect"] = 1, ["box_mouse_cursor"] = true, ["canopyReflections"] = 1, ["chimneySmokeDensity"] = 10, ["civTraffic"] = "", ["clouds"] = 3, ["clutterMaxDistance"] = 690, ["cockpitGI"] = 1, ["defaultFOV"] = 69, ["effects"] = 3, ["flatTerrainShadows"] = 0, ["forestDetailsFactor"] = 1, ["forestDistanceFactor"] = 1, ["fullScreen"] = false, ["heatBlr"] = 1, ["height"] = 1200, ["lights"] = 2, ["maxFPS"] = 120, ["messagesFontScale"] = 1, ["motionBlur"] = 0, ["motionBlurAmount"] = 1, ["multiMonitorSetup"] = "1camera", ["outputGamma"] = 2.2, ["preloadRadius"] = 150000, ["rainDroplets"] = 1, ["scaleGui"] = 1, ["sceneryDetailsFactor"] = 1, ["secondaryShadows"] = 1, ["shadowTree"] = false, ["shadows"] = 4, ["sync"] = false, ["terrainTextures"] = "max", ["textures"] = 2, ["useDeferredShading"] = 1, ["visibRange"] = "Ultra", ["volumetricLights"] = 1, ["water"] = 2, ["width"] = 1200, }, 13900K and a 4090.

Ive got this running pretty well using the latest PP software. There are some issues to work out but my first question 1) DFR and pimax eyetracking is awesome. It actually calibrates no problem and tracking seems almost flawless even when lifting up the headset to type something, it seems to track perfect after putting it back on. 2) The question is the square in the center of the FOV when using DFR. I thought this was just in the mirror window I didn't realize it was visible in the headset. I wish it would go away, it looks like a debug feature to check if DFR and eye tracking is working. Are we stuck with it? Why does it exist (what causes it) why dont I see it in the dcs menu? if it cant be removed can it be reduced? I find it pretty distracting. Thanks!

I had the same question. Glad its not required to be online after paying for it. Thanks!

Trialled it, surprisingly liked it (my first heli), but definitely not buying it until...

Would love to have the ability to fly a F18/F16 in sim mode while non pilot friends are in vehicles in combined arms. Would really bring things together.

DCS Apache seems to have the most unstable 'stability' system of any aircraft in the sim - surely it can't be that bad IRL? Have also shelved the Apache till it behaves like an aircraft with a actual 'stability' system.