All Activity

Just for curiosity sake in case this comes up for others, why did you have the "force_cross_eye_recovery_tool" entry in there in the first place?

Hi i made new version with more options in case you are interested

У них сейчас работа по земле не совсем работает как надо, недолет. Если выставить QFE цели, то появляется индикация "ОТВ", при минимальных значениях дальности, причем нижняя риска зависит от QFE цели. Изменение QFE цели на QNE приводит более лучшей точности, но отключается "ОТВ" даже у самой земли. Если не выставил QFE как у цели и текущий QFE ниже высоты цели, у тебя постоянно "ОТВ" и применить оружие не можешь. В англицкой ветки это писали и горят, что исправят. Сейчас точно можно только НАРАми работать, с бомбами, если не делать пикирование под 70-80 градусов не попадешь. И в видео у Вакс - посмотрите, он сбрасывает не по метке, а по линии шпаги, сделайте расскрадровку видео. Вообще хз как у них работает, я потратил кучу времени в чем баг у них, приблизительно понял, но уже там ребята запостили этот баг. Если не исправят, запощу багрепорт заново, жду патч.

Even more - it stopped working for me completely. Now I need to set Game Options - measurement units to METRIC + Avionics to NATIVE + MiG special option Cockpit to Default to get full aircraft in its original form. Any other combination and I get either altimeter in Feet (in Metric setting), speed in Knots and some unrealistic English letters in HUD. Either Full RUS or Full ENG, not ideal that I need to change units of measurement between Hornet and MiG but other than that I will learn this limited Russian

The clearance for your landing is Runway 08. That doesn't exist, it's 07 but in either case, it's the opposite direction to where the C130 lands. So if you land on 07, then turn left at the end, it triggers the end of the mission.

definately supply the logs that BN has asked for; but also check out

I know I'm late to the party, but... DCS works well enough with a good bit of tinkering; be advised of Linux's 80-button input limit as per the kernel - I'm not sure if Lutris (the recommended method for installing) fixes that. Otherwise, suggest following guides like https://github.com/budderpard/DCS_Standalone_on_linux/blob/master/README.md

У их, у вирпиловского Прайма частично сделано, как надо, у них курок откидной двух позиционный, который если дальше нажимать уже нажимает гашетку, отжатие гашетки не возвращает, нужно пальцем возвращать. Функционально похож, но внешне нет, почему сделали для Прайма, а не для реплики ручек Су/Миг - хз.

You also need basic NS 430 module.

I think there is a version of OXR toolkit that does this?

It's over 74m for Nimitz class.

I have the NS 430 for MiG29 installed and have it googled on in the mission editor, still isn't in the cockpit, I've even changed the date to 2023 in case that was a problem, but nope, still no NS 430

Hi, can you attach your dcs log and dxdiag we can have a look for clues. thanks

A man can dream....but after all this time, and considering the rate of development of third party software in DCS, this is very likely a pipe-dream at this point.

I have done it on the Germany map as well. Its weird as there is nothing definite as far as I can make out that causes or stops it happening.

Hello pilots, I am starting this topic because i recently changed my vr headset to psvr2, and now having performance issues. Before i was using quest2 on link cable but with magicall tool called OTT(Oculus Tray Tool). In OTT i was using option called fov reduction, set to 0.8. It actually crop the image so performance gain is huge. Our eyes anyway don't see that outside region of 20% (differ from person to person 10-20%, someone is ok with 0.9, someone with 0.78...,ipd and head shape are reason). Question no 1: Is there a way to make and implement such tool for psvr2 and other steam displayport headsets? Question no 2: Am i wrong or ott was directly forcing dcs world to crop image before rendering? If yes than it means that ED left opened that option so it is easy for developers to help us here

We have already the option of choosing a fully realistic INS or a non realistic one that requires no fix taking. No fix taking being the non realistic option and brings the INS in line with how it worked in the FC MiG-29A. Could ED consider something similar the SPO-15LM? Example: Default - [Fully realistic] [User option] - Legacy FC3] As with the INS option, this would be naturally be enforced by the mission creator.

Ciao Pluto, cosa intendi per disinstallato tutto? il software steam, steam vr e osasis?

Hey! I've got Intel 13900k and it shows totally different DCS perfomance with motherboard main profiles. Motherboard Asus Z790, it has two predefined profiles "ASUS Advanced OC Profile" and "Intel Default Settings". "Asus OC" - DCS runs great, fine and smooth. "Intel Default Settings" - DCS has constant stutters and instability in perfomance. "CPU bound (rendering thread)" often appears. And that level of stuttering literally different on every other game launch. For my main working apps (video editing, CG) I need "Intel Default Settings", because "Asus OC" profile works not so great with these apps. I tried to make both motherboard profile as identical as possible in bios, but that didnt work. All cores are unparked. Any tips how to make "Intel Default Settings" work with DCS? If dcs.log file is needed, I'll upload it in couple of days.

You are welcome buddy ! I understand your situation without DCS I would be crying big time! Luckily there are so many helpfull and very knowledgeable members here so that can basically help us with anything especially VR! Let me know how it is going!

They would have to pass under the Øresund bridge, which has 57m of clearence. That might be an issue (I have no idea how tall the superstructure of a modern carrier is).

Dopo avere letto un post precedente ho provato sti driver, sapevo che avrei fatto una cazzata, infatti il mio reverb poi risultava acceso ma completamente nero, fortunatamente ho disinstallato tutto, riavviato il pc e tutto e ritornato come prima, l unica cosa che ho fatto e cambiare posto al connettore sulla scheda video.... mai seguire il primo consiglio che leggi... Tanto il mio reverb continua a funzionare anche aggiornando windows 11....

Especially in a training context, being able to plan specific failures is crucial. Procedures like a flameout or electrical failure can be practiced most realistically that way. It would be nice if ED provided that — it can’t be that hard. Since there’s already a randomized failure mechanism, it should just be a matter of the user interface.

Hi ASC. You don't have a contact option on your website (nor, you know, the other things that are required in the EU, but that's besides the point). Hence, the only way I can possibly send you a heads-up is this forum, as odd as that is. I just wanted to let you know what I just pre-ordered the C130J. However, I did that in the ED store. I am kinda assuming that you get the same revenue no matter where stuff is bought, but on the other hand, there are loads of people claiming "support your local DCS developer (by buying on their website)". I don't know which one it is. I would have happily bought on your site, but you seem to only offer Google Pay and various credit cards? Much like many, many people and primarily Europeans these days, I don't have a credit card; only a VISA Debit card, which very likely would not have worked. Also, I prefer some sort of abstraction/proliferation stragegy with credit card numbers, and as much as I generally despise Paypal, they are still my go-to method. Please consider adding Paypal in the future, should you desire more sales on your own website. Best regards.

On behalf of all the other voice actors, congratulations on an outstanding performance that has greatly enriched both campaigns. Good voice acting alone doesn’t make a great campaign — but even the best campaign loses a tremendous amount of immersion if the voice acting isn’t right. In both Arctic Thunder campaigns, you’ve set the bar.