All Activity

Why do we still not have GCI simulated in DCS? All I can do is ask for the nearest bandit and get a heading, but not any actual commands to follow to intercept. Asking for confirmation from AWACS/EWR is also useless many times as they won't respond.

I don't know what to tell you, other than that they are absolutely from a real C-130J... we recorded them over the course of 2 days after getting approval from the USAF. As others have mentioned, the planes in these videos are C-130H variants, which sound very different. I would also caution against using videos recorded using cellphone microphones as a point of comparison against what the actual airplane sounds like.

What is the degree of difficulty in flying the C-130j alone with the help of an Ai copilot?

same # -------------- 20250921-094239 -------------- DCS/2.9.20.15010 (x86_64; MT; Windows NT 10.0.26100) I:\Game\DCS World OpenBeta\bin\edCore.dll # C0000005 ACCESS_VIOLATION at 00007ffee1e74cdb 00:00000000 SymInit: Symbol-SearchPath: 'I:\Game\DCS World OpenBeta\bin;', symOptions: 532, UserName: 'hind7' OS-Version: 10.0.26100 () 0x100-0x1 0x0000000000024cdb (edCore): b2DynamicTree::RemoveLeaf + 0xBB 0x0000000000024656 (edCore): b2DynamicTree::MoveProxy + 0xB6 0x000000000003e6b4 (Effects): Effects::loadShipWakeConfig + 0x2304 0x000000000003efae (Effects): Effects::loadShipWakeConfig + 0x2BFE 0x000000000016bc11 (Visualizer): smSceneManager::DestroySceneManager + 0x11831 0x00000000001728db (Visualizer): smSceneManager::regLua + 0x61BB 0x0000000000156eec (Visualizer): smCamera_Implement::getClipRegion + 0x1CC6C 0x000000000014076c (Visualizer): smCamera_Implement::getClipRegion + 0x64EC 0x000000000015b602 (Visualizer): smSceneManager::DestroySceneManager + 0x1222 0x00000000000331e1 (edCore): ed::thread::_get_current_thread_id + 0x71 0x00000000000037b0 (ucrtbase): wcsrchr + 0x150 0x000000000002e8d7 (KERNEL32): BaseThreadInitThunk + 0x17

It is because the cause of the bug is whats called "undefined behavior". It surfaces for you in a "random" (but deterministic) way and btw changes with each DCS update.

+1 support!

No, that’s updated software with R-77 lock. I posted images above of every single stage of datalink guidance from before radar contact, after, and lock Here’s some more in search stage, guidance circle is centered

As the title says the canopy is not repaired with the rest of the plane if you jettison it or rip it off, so you're stuck with a plane without a canopy Tracks : https://www.swisstransfer.com/d/69102569-8948-4d4d-bf6b-8291d922eb52 (sorry I still don't know how to attach tracks)

Yeah, it really looks like a random mapping was used from mig29a_tex1_vvs.dds around the wind shield.

Weirdly it's not working for me. I've got the folder with that name and a couple of jpgs in it, but they don't show

Yes that’s how it should be. The “communication menu” is a relic from the Lock On / Flaming Cliffs days, and shouldn’t be used with full fidelity modules. Use the appropriate radio button instead, and everything will work as it should. The communication menu simulates talking to the ground crew. In-flight, you can’t talk to the ground crew for obvious reasons.

ED doesn't typically talk a lot about stuff that's in progress (mainly because the forums start whining "you promised"). That said, there are lots of examples of things that people had wrote off and said were never coming even when ED said "we're working on it" multiple times (Multi-threading is a great example) that eventually showed up. Yes the wait is painful and they aren't giving any details. But history shows that they often are actually "working on it" and it will eventually show up.

Okay, thanks. I'll give it another go. I thought I could adjust them anywhere once the icon had changed to the adjust icon.

Справедливости ради РЛЭ и РТЭ не боги пишут. И там встречаются ошибки и неточности.

I found a quick fix, at least, I think. It works so far for me. Go to your Pimax Device Settings - Games - Dynamic Foveated Rendering- QuadViews - and change your setting to Quality or go to Customize and change the Peripheral Area Resolution to what works for you. I hope this helps.

Hello, Today I completed the testing of the second mission, on Taxi, take-off and initial climb, it looks like this: I will now focus on the VFR Landing one, hopefully it won't take too long to make If you'd like to try it, here is a temporary link: F-104C - Training - M02 Taxi & Take-Off (by Rudel_chw).miz Once I have completed the landing one, I will upload the Set to ED's User Files. Cheers! Eduardo

Quick update for anyone with the OG Crystal. There was a recent update with Pimax. I do not believe this issue is related to the recent DCS update. I have seemed to have fixed the issue by doing the following. Go to your Pimax Device Settings - Games - Dynamic Foveated Rendering- QuadViews - and change your setting to Quality or go to Customize and change the Peripheral Area Resolution to what works for you. I hope this helps.

Yes, please... I'll try to update the quick reference I made a long time ago based on the documentation that was included. I just found out last night, already installed and tested... will take her for a spin So to be really sure, no way to have the old v1.4 pilot hud monocle (I think it was on letter I) will take the DAP also for a spin...

this? https://youtu.be/-nP52fDF_58?si=iP5zscNN9UzqlWLM&t=262

Ya, I don't remember if 256 used to even be an option (I think it was just 512 and 1024) and when they added it it overwrote the whatever had previously been selected. In fairness, they changed that section a bit ("every frame" is now a checkbox rather than part of the dropdown list) so likely they changed exactly how it was stored which reset it to default. But that's one that really should have been highlighted in the changelog IMO.

So the front-side of the canopy bow is using (seemingly random) textures that cross other visible parts. It picks up the white from textures at the nose (between the red and gray). Therefore it is impossible to get a clean look if you have a contrasting color there. https://www.digitalcombatsimulator.com/en/files/3347023/

The MiG-29A looks to be significantly higher fidelity than the F/A-18C from everything I've seen. VR is a whole other conversation. There are fidelity and performance issues unique to that interface.

I was just typing this . I managed to solve the problem. I noticed that the cockpit resolution was set to 256, and I hadn't touched it after the patch. Changed it to 1024 and everything is fine, the kneeboard is back to normal. The last patch must have forced something here. Thx too!