All Activity

Ми-8Т с грузом в Афгане на 5000? Имею сомнения на счёт груза, ну или заправки на 40 минут.

I don't have a problem with doing that, but I have deleted that folder a couple of times myself and it always gets recreated.

Керосин не посчитал. Итого в зоне на 3000м в штиль с включёнными ПЗУ: 8706+2080 10786КГ. При максимально допустимом 11400 с ПЗУ. Все должно взлетать, вне зоны только без ПЗУ.

Hi. Just to let you know. The nvidia 5080 is awesome. I get over 140 fps with all settings on high at 4k Very happy with the gpu.

Maybe that one if you would be so kind thanks

Посмотрел по номограммам. Вне зоны. На Н=3км 10600 кгс, в зоне Н=3км 11600кгс. С включёнными ПЗУ меньше на 200кгс.

I just checked and don't have that folder. I only have C:\ProgramData\WindowsHolographicDevices.

Hi Akiazusa, Here I am, I've done what suggested and it, more or less, works. Generally speaking the "dedicated" ARK.lua to be put into .miz woks but with the following. 1) Despite using Russian names in the ARK.lua file (in the plate I would like to see Russian names), the names are translate in English. I understand that this is due to the me setting the cockpit in English in the "special" setup, but it would be good to have this "exception" to the setup and keep original Russian names. I'm also thinking to change the cockpit setup to default, but I need a bit more time to learn and know the cockpit to be able to use it even with Russian text. 2) The callsign labels are out of scale due to character font failure and, either they are not shown, or are too big and with a different font from the channel name (AFD name/location). Regarding point (1) I was thinking to comment (clear) line 4 of the ARK_MAIN_page.lua, but I would like to have your advice/suggestion on this point. Regarding point (2) I don't know really what to do: I have difficulties to identify the proper lines into the ARK_MAIN_page.lua; more, in the file ARK_usefull_definitions.lua there are info on fonts and dimensions. But I don't want to touch to those if not sure (or more sure, or less blind...) of what I'm doing. In ant case, thank you again for your support. For the moment I don't mark as solution, just in case we can fix these points.

@ASW could it be this....check out my thread...

Может. Если в дкс не может, тем более пустой, значит это баг.

I stupidly deleted C:\ProgramData\Hololens and now I have a lifeless headset with no driver. If anyone could upload said file/folder or offer some assistance I would be hugely grateful. VR is on its last legs with me. Cost..hoops to jump through...cost to performance ratio. Never ending drama. But my wallet stays closed forever to anything related to that company!

Sounds great, but do I read correctly that there will be no more HUD (AN/AVS-7) without NVG's??

Guys using the Honeycomb Bravo - do you get full functionality in DCS? All buttons map, all levers and trim wheel work as you'd expect?

Can you attach a longer log file that covers the period of this occurring, the one attached here is very short. The log shows you have parked cores, and are still on Windows 10. Windows 11 will better support your hybrid CPU and scheduling. Core parking can be disabled via the ParkControl software, can’t comment re: Windows 10 though. Log analyzer indicates disabling actually cores for that for Windows 10…but that won’t necessarily fix your issue.

Schau mal ins DCS Winwing Unterforum! Da muss man in irgendeiner lua erlauben/erzwingen, dass screen Export auch während VR funktioniert. EDIT: Hab mal den Link rausgesucht.

Hi, steht auf Seite 61.

Der Schalter ist an der linken Throttle ein 3-pos Schalter. Wird praktisch mit dem kleinen Finger bedient. Vorn-alle Lichter an, hinten - alle Lichter aus.

Glad to answer any questions coming my way ^^

По сложности, да, он, скорее сложнее чем те же А3хх где в целом нужно семь кнопок нажать для запуска. Оффтоп, но жаль что Ту-154 так никто и не сделал для современных авиасимов. ПТ для FS9 был легендарным. Я тогда правда был слишком мелким, чтобы его толком освоить

Despite the leading modes were changed to RL the aspect ( angle) arrow will not appear . It appears only during lock from RL main modes and indicates only DIRECTION of target velocity or angle ( not speed ) so it doesn’t change its length.

Not exactly the same problem as the others that reported the ModelTimeQuantizer: ANTIFREEZE ENABLED issue, it sounds like. These are not some temporary stutters, these are 5-15 second long stops. Outside the freezes, it is theoretically 200fps-ish (for that particular flight that I'm using as an example). Confirmed that the issue reproduces even at Low graphics settings. Also, increasing RAM to 96GB does not change the repro. nullImage of CPU usage during the freeze. Confirmed that during the freeze, almost all threads are idle. The only really threads active is one that calls into Visualizer.dll, and another that looks like the sound thread. Almost no other threads are active during the freeze period

Wo werden den die Positionslichter bei der Hornet angeschaltet ? Aus dem Handbuch werde ich jetzt nicht schlau wenn ich bei der Stratprozedur die Drehknöpfe links am Schubhebel einmal , Position und Formtion , sowie den Schlater Strobe auf BRT stelle, blinkt trotzdem nichts, wenn ich die Maschien s elerb starte .. Den im handbuch beschriebenen Schlater "Außenbeleuchtungshauptschalter" finde ich nicht udn ist auch so nirgends beschrieben . Was übersehe ich oder mache ich falsch , denn stelle ich im Missonseditor die Maschine am Abstellplatz mit "Triebwerk an " ab , blinken diese Lichter ?

Unasked for moza thoughts: * you can mount it backwards, just remember to save your profiles with inverted x and y axes * you can box the amount of movement available for each profile eg the default fa18 will only push forward a few degrees so as not to slam into a centre mfd. That rules for cockpit builders except the default startup requires it to slam violently into all your precious kit unless you lift it out beforehand.

In DCS, the data for the Magic 1 missile comes from a variant before early-to-mid 1980s, whose seeker head used ordinary glass that hardly transmitted infrared light above 3 μm. Even with a liquid-nitrogen-cooled seeker, the end result would still be similar to the AIM-9B. However, the modeling uses a seeker head with magnesium fluoride, which is opaque. It should have similar performance like AIM-9D/R-13M

Tor M1 E band MK23 E-F / MK 50 VAR BAND G-H band SA8 C band MK37 SA-6 Tracking C band / Fire X band MK 37 SA-3 LOWBLOW TR (I band) / P-15 MK 37 C band SA-11 SR - MK23 TEL-MK36 When engaging the SA-11, fire from 25,000 feet in DIRECT mode, with a loft of 60-70 degrees. When you see the SA-11's smoke, fire and then dive to evade.