All Activity

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!

Thank you very much for all the vehicles. I think we need the code for the Pantsir to be able to launch HARMs missiles at it without using the HTS pod; if it already exists, please could someone send it to me?

Check what your Cockpit Displays Resolution is set to. It had set mine to 256 (rather than 1024) after the last update. It messed with a number of things in my cockpit including the on knee kneeboard in the F-18 (although it didn't actually mess with the pop out one). May not help, but worth a look.

I had no doubt about that. Anyone who goes to the trouble of not only purchasing winwing mcdus and PFPs must have a love of heavy metal and logistics. The Herc is right down our street.

Works for me in VR. The 'hitbox' to click is a bit small though, especially as there are no other components around they could make it larger.

Mbucchia himself gave me a solution, to use steamvr beta which has a fix for a timing issue. I still didn't have time to try it. I will update here as i can

I decided not to give up and logged into another server. It's also 4YA, but it's a map of Afghanistan. There is no such problem there. Everything works fine on the map of Afghanistan.

Start by removing your mods and trying it again. Mods can have unpredictable and seeming unrelated impacts. And actually it's worth running a slow repair (with remove extra files) after you do that. And if that fails, try renaming your saved games folder as you may have missed a mod in there and a repair won't touch it.

Well the grimm reapers videos have served me well for over a decade...I will not slander them...but they're not infalable, and it is a new modual with a questionable manual IMO...but I believe the radar workings as is are incomplete or malfunctioning,not sure which ...hehe.

Guarda ti riporto quello che ha scritto un utente sul forum nelle richieste… Magari come primo step semplicemente dare la possibilità che l’intera escursione dell’Asse sia assegnato ad un comando quando arrivi al 100% esegui il comando, ch’esso potrebbe essere il carelllo ON/OFF oppure il first dent del trigger del Tedac (e con un modificatore gli assegni il secondo stage) Altra cose credo abbastanza facile sarebbe quella di dare come terza opzione il long press… in pratica nel tab Control Settings quando selezione, ad esempio il pulsante 1 di un joystick ora si ha: Pulatante1 Pulsante1_off si potrebbe aggiungere Pulsante1_long Non fondamentale perche si può sopperire con i modificatori ma i pulsanti da utilizzare non sono mai abbastanza….