All Activity

The skill in the F-16, F-18, and other more advanced planes isn't in the bombing itself, it's in bombing more heavily defended targets, in worse weather and/or at night, while still being able to keep SA on other threats or respond quickly to support calls. Doing all of that also takes skills, just different ones than the MiG-29 requires, in the same way that manual dive bombing in the MiG-15 or F-86 requires different skills in the opposite direction. For any generation of planes, there are easy missions, hard missions, and impossible missions. The next generation of planes makes easy missions trivial, hard missions easy, and impossible missions hard, and they have their own impossible missions which would be completely suicidal in earlier generations.

TDC Depress no response and with correct elevation can't lock target.Have u really fixed it?My dear ED. 222.trk Or your test team are useless.My bro.

LastMissionTrack.trk

Да, это ваще круть! Очень удобно!

You shouldn't let that stop you. You can have a lot of fun shooting down enemy air targets with the practice weapons. The smoke rockets make it easy to tell if you've hit the target. You should also re-enable the Damage and Failures sections in VNAO_T45.lua. I copied part of the A-4ec's Damage section into the T45's Damage section since they should be somewhat similar.

@Calvin.Pimax Hey Calvin. I tried again tonight and it ran excellent just like last night but this time it did crash. I was hoping there would be a correlation between good performance vs not as good performance as an indicator if it would crash or not. Seems like not. It did run about 30 min this time before it crapped the bed. Not sure why all of a sudden its running better but I'll take it, but it still seems likley to crash. So I guess I still need supports help. The ticket number is #111697

Have you tried deleting the FXO and Metashader 2 folders in your DCS Saved Games folder yet?

I kind of like the challenge of bombing in the MIG because in the F-16/F-18 it takes no skill at all. In the MIG you actually have to develop skills, but it is not on a crazy difficult level like bombing with the warbirds (WW2). The MIG-29A Fulcrum strikes a perfect balance.

Парень, ты меня подловил... Чувстовать себя, сопричастым (в какой то мере) - это приятно. Не так ли, serg_p? Так я это и сделал! Форум я читаю, когда я не могу чего-то найти в руководствах или чего-то не понимаю. А я пишу в случае, когда нашёл проблему или её решение. Форум, как ты понял я не читаю. Но информацию получаю. Например из этого интервью: Конечно их мало. Было (Eagle Dynamics - 1991-1992 Андрей Масалович Так начинался Flanker).Но то, что их сейчас мало из вышеприведенного интервью не следует (таймкод 2:52). Имея отношение к программированию, я на своём опыте знаю, что времени и ресурсов всегда не хватает. А вот это печалит. Может быть помочь ребятам? Например EA могла бы передать часть работы сообществу? Или сделать часть кода открытым? 1С так делает. Говоришь разработчики форум почитывают? Но, мы слишком далеко ушли. Я ответ на свой вопрос нашёл. Спасибо за внимание.

DLAA, works best in VR for me. Gives the sharpest image close up and at a distance.

I can’t remember when I last bought a module now. A bit late though, there’s not many I don’t have but anyway. I remember too well having an update just before Christmas, the proverbial tailwheel fiasco. I pissed and moaned for months about it along with others, a fair few of us were testing and giving feedback but it took forever to have it put right. I wish I’d have known how to roll it back to pre-update, anything to have it as it was. It wasn’t a lotta fun for a while. Thankfully it was sorted eventually. It could be argued that an accurate model of the Mos shouldn’t have any AI to manage radios etc, never mind fly by wire. The trouble with that is flying it on our own leaves a few things to be desired. It was promised in some form but the wind took that whisper with it I think? Personally, I fly it loads, mainly for pleasure, loading it up on a server now and then for some rocket and cookie shenanigans. It all works pretty well for me (ignoring my dodgy targeting) but it does need a bit of tinkering. The EA idea doesn’t really work for me, pretty early (in the real sense of the word) after release I thought it wouldn’t be long til we could, ya know, mark some targets like some of the Path Finder boys did in their Mossies but we just can’t have em somehow? I’d prolly pipe down if we got some though the novelty would soon wear off, or would it . Then it’s what about those wipers… Maybe ED should open up the doors a bit for the people that obviously have a passion and a talent for modding. A quick scan around the Modding threads and you’ll find Modders banging away for years on projects. Can’t they be brought into the fold somehow? Helped along a bit? Maybe I’m being naive but I’d have thought working with the people that are building bits specifically for DCS already, before they’re earning anything, would be of help to the whole community. Look at stuff like the Lancaster project, give those lads a few tips or tools and help them work and well all have Lancasters too. Then… we’re really gonna need those TIs . We’d have more being worked on, more releases maybe and I don’t think anyone’s out of order expecting modules to be completed and maintained. We need Maintenance Units for all modules , maybe eh?

Some of the commands for the pilot are showing doubled and orange.

I think I can confirm it's using the baro altitude for ranging, or something at least: If you dive at the target, laser on (symbol on HUD), then Active Pause and turn the pressure adjustment knob on your altimeter, the range indicated on the scale on the left side of the HUD moves as you turn the knob. I tested in ISA conditions (1013 hPa), and had to turn the pressure knob to about 1007 hPa to get the range scale to match what I calculated with trigonometry based on altitude and map distance. But on the other hand, I had to turn the pressure knob to about 1045 hPa to get the pipper to match where the bombs actually fall. (Active Pause is incredibly useful for figuring all this out.) Some assumptions I'm making: The slant range itself should only come from the laser; that should measure the straight-line distance from your plane directly to the ground under the pipper, which is the slant range. That should not be affected by the altimeter setting or anything else. And I'm assuming the HUD scale should be showing the slant range. However, the weapon ballistics, which means how the weapon flies through the air and where it will actually impact, should depend on the baro altitude, as that is a measurement of air density, which will affect the flight path, and hence where the pipper should be drawn on the HUD. So it does feel like something should happen when I turn the altimeter pressure knob, as that will make the system think I'm in thicker or thinner air and that the weapon will fly in a different arc. It seems like there has to be some cross-communication between these systems, because drawing the pipper in the right place on the HUD needs both the slant range and the baro altitude, and as the baro altitude changes, that moves the pipper, which should move the point the laser is shooting at, which will change the slant range, which will also move the pipper. I assume that programming all of this so it actually works, draws the pipper in the right spot for all the different weapon types, and does so within whatever tiny fraction of the minimum-spec CPU slice they're budgeted for, is a huge pain in the butt. Kind of amazing that it works as well as it does!

Located on the front-left vertical panel in the cockpit, below the Landing/Taxi Lights Switch, there is an Indicator Light Intensity Switch which controls the brightness in cockpit of the warning lights, autopilot lights, target designator lights, etc. I would like to bind this function to my device, but I can't find a key item for this switch in the key bindings settings. Please let me know if this function is listed under a different name. Otherwise, has this key binding been omitted from the settings? I'm aware I can use the mouse to click it, but I specifically want to bind it to a peripheral. Good luck!

I mean maybe your wrong? We can hold onto hope and their subject matter experts say, no this is just how it works?

It just seems there are two factors it takes into account 1. following the target with pre designation 2. movement of pipper compared to pre designation You can tell pipper isn’t exactly moving normally after pre designate. I had a time I pre designated a moving vehicle on a road, the vehicle made a sharp 90 degrees left turn after the pre designate. I put my pipper on it ( within the 10 second limit) and my bullets we’re just the tiniest bit off.

Thanks for your reply. The HSD appears a bit jittery compared to the other displays. It seems even harder to read when the Pixel Density is low. I had set this option to 1.0 in the DCS options and increased the Foveate Resolution to 180% in the QuadViews Companion App. Due to a recent DCS update issue, some of my settings were reset, and with QuadView turned off, the HSD had become extremely difficult to see. The issue has been resolved for now. Thank you very much.

It shouldn’t care about altitude setting, the only methods of air to ground ranging are laser and radar altitude, it does. It use radar. Understand once the laser is activated (dive of 10 degrees) it stays on for 30 seconds no matter what. And will afterwards stay off for 32 seconds no matter what.

I had DCS Crash 2 times just hiting the previous dtc binding key. I opened kneeboard moved to the proper page, hit previous dtc binding and DCS crashed. 2 times same error. Wonder if this is a bug and where is the best place to report it Here is the stack trace from the log. And the F10 marker plan i had setup. 2025-09-26 02:20:50.637 INFO EDCORE (Main): try to write dump information 2025-09-26 02:20:50.915 INFO EDCORE (Main): # -------------- 20250926-022051 -------------- 2025-09-26 02:20:50.916 INFO EDCORE (Main): DCS/2.9.20.15384 (x86_64; MT; Windows NT 10.0.26100) 2025-09-26 02:20:50.917 INFO EDCORE (Main): C:\Jogos\DCS World OpenBeta\Mods\aircraft\AJS37\bin\AJS37-Avionics.dll 2025-09-26 02:20:50.919 INFO EDCORE (Main): # C0000005 ACCESS_VIOLATION at 00007fff5d54b2dc 00:00000000 2025-09-26 02:20:50.920 INFO EDCORE (Main): SymInit: Symbol-SearchPath: 'C:\Jogos\DCS World OpenBeta\bin;', symOptions: 532, UserName: 'varbe' 2025-09-26 02:20:50.921 INFO EDCORE (Main): OS-Version: 10.0.26100 () 0x100-0x1 2025-09-26 02:20:50.930 INFO EDCORE (Main): 0x000000000008b2dc (AJS37-Avionics): RadarMaterial::Init + 0x2CBC 2025-09-26 02:20:50.931 INFO EDCORE (Main): 0x0000000000115eba (AJS37-Avionics): cockpit::AJS37::NavigationIndicator::initialize + 0x2CCA 2025-09-26 02:20:50.931 INFO EDCORE (Main): 0x0000000000115c84 (AJS37-Avionics): cockpit::AJS37::NavigationIndicator::initialize + 0x2A94 2025-09-26 02:20:50.932 INFO EDCORE (Main): 0x00000000001de75a (CockpitBase): cockpit::avDevice::setUpdateHandler + 0xCBA 2025-09-26 02:20:50.932 INFO EDCORE (Main): 0x0000000000233a6e (CockpitBase): cockpit::avDevice::performClickableAction + 0x5E 2025-09-26 02:20:50.932 INFO EDCORE (Main): 0x00000000004009b7 (CockpitBase): cockpit::avSyncable::update_entity + 0xCC57 2025-09-26 02:20:50.932 INFO EDCORE (Main): 0x000000000085840d (DCS): SW + 0x23C1DD 2025-09-26 02:20:50.932 INFO EDCORE (Main): 0x0000000000b53ddb (DCS): SW + 0x537BAB 2025-09-26 02:20:50.933 INFO EDCORE (Main): 0x0000000000a623c0 (DCS): SW + 0x446190 2025-09-26 02:20:50.933 INFO EDCORE (Main): 0x00000000000c253a (WorldGeneral): ActionDispatcher::process_ + 0x7A 2025-09-26 02:20:50.933 INFO EDCORE (Main): 0x00000000000c2056 (WorldGeneral): ActionDispatcher::dispatch + 0x16 2025-09-26 02:20:50.933 INFO EDCORE (Main): 0x00000000000c5b80 (WorldGeneral): TimedActionBuffer::feedEventsUpTo + 0xF0 2025-09-26 02:20:50.933 INFO EDCORE (Main): 0x000000000000430f (World): wSimTrace::CommandsTraceDiscreteIsOn + 0x1DF 2025-09-26 02:20:50.934 INFO EDCORE (Main): 0x0000000000004aa2 (World): wSimCalendar::DoActionsUntil + 0x262 2025-09-26 02:20:50.934 INFO EDCORE (Main): 0x0000000000a6d1fd (DCS): SW + 0x450FCD 2025-09-26 02:20:50.934 INFO EDCORE (Main): 0x0000000000a6ced4 (DCS): SW + 0x450CA4 2025-09-26 02:20:50.934 INFO EDCORE (Main): 0x0000000000a90809 (DCS): SW + 0x4745D9 2025-09-26 02:20:50.934 INFO EDCORE (Main): 0x0000000000a44cf4 (DCS): SW + 0x428AC4 2025-09-26 02:20:50.935 INFO EDCORE (Main): 0x0000000000a46333 (DCS): SW + 0x42A103 2025-09-26 02:20:50.935 INFO EDCORE (Main): 0x00000000025b8d0c (DCS): AmdPowerXpressRequestHighPerformance + 0x1097D08 2025-09-26 02:20:50.935 INFO EDCORE (Main): 0x00000000010dac82 (DCS): SW + 0xABEA52 2025-09-26 02:20:50.935 INFO EDCORE (Main): 0x000000000002e8d7 (KERNEL32): BaseThreadInitThunk + 0x17 2025-09-26 02:20:51.822 INFO EDCORE (Main): Minidump created. F10-map markers plan Scooter 3-3 _ Coragem.ini

Mostly looks fine. There are a couple of blips, but I'm assuming that the dcs log file and the CSV file are for two different runs? Was curious if showed up in log for matching timestamps. I've attached a couple of screenshots from blips. The blips coincide with high App CPU timings as well. I noticed you're running Through The Inferno for this, so possibly it's just loading a bunch of stuff in, or scripts, at the time which are triggering this. I see you're running both Quad-Views-Foveated and the OpenXR Toolkit. Do you have Turbo mode enabled in either of those? Turbo mode will throw off frame timings (it'd skew the numbers in this csv report as well). Quad-Views-Foveated has it on by default...except for SteamVR which you're currently using. Overall though looked ok. How's the "feel" in general when you play? I wouldn't get too hung up on a blip (.1% frametime if this is what it's based on) if the game is smooth and you're just chasing a number which is an outlier (especially if due to to something like TTI). EDIT: I don't use fpsVR so can't comment as to what it displays to you, or how it calculates it's numbers.

Do not say it known issue.If it already known issue,why no fix?

I'm so grateful to ED.LastMissionTrack.trk 111.trk Really Cool HUH? Do not say it known issue.If it already known issue,why no fix?

After confirming "check" or arming the injection seat, RIO asked me to close the canopy so I closed and confirmed with my "check". Then proceeded other checks... I could not recall that RIO would close the canopy for me in the assist startup.