All Activity

It's just a warning that the ATT/HÖJD autopilot has disconnected, in this case due to said "heavy manoeuvring". To get rid of the warning you press one of the 3 autopilot buttons (pressing ATT or HÖJD might trigger the warning immediately though, if the reason for it disconnecting is still there), or you can pull the "SA" circuit breaker and then push it back in as a more nuclear option.

Btw, it works the same as in other RU modules such as Mi-24

Sorry guys its gone off the rails.

Hello, I'm experiencing regular stuttering every 1-2 seconds, both in the air and on the ground. I suspect it might be due to a demanding CPU campaign scenario, but I'm uncertain. My GPU utilization fluctuates, dropping below 50% regularly too, which cases FPS drops, although the pattern isn't as consistent as the stuttering. I am playing on triple screen, and 2x Winwing DDI as cockpit screens, also I am using PS3 eye camera as face tracking via OpenTrack. AMD Ryzen 7 5800x3D RTX 4090 64GB RAM game is on the SSD disk Win11 Thank you very much in advance! Best regards Ivan dcs.log

Thanks for your feedback, I see you already thought of many of the problems it will bring, too. I think, the solution cannot be only one track - there must be at least two. 1. A pure graphic test, maybe on marianas 2. A CPU test, with lots of ground units driving on the road. (can be caucasus) The graphic test ideally not only runs with one set of settings. But I cannot say what would be the best approach for that. I once programmed a small tool, in which I configured a set of different graphic settings, and the tool automatically set this, started DCS, run a track, recorded the performance and wrote it into a file. I had the mode to run all combinations of the configured settings (which can take veeery long time). It showed, that all settings did not interfere with each other, the drop of performance was per-setting. With this knowledge, I changed it into the way, that all settings are tested, but not all combinations (With one default from which the other change). This gave me the possibility to generate screenhots, to that it became visible, how it looks like, when changing things. My goal was to compare it with the next dcs version. Then, an update, and my tracks did not work any more and I stopped doing this. The point is there there are infinite ways of testing. I just think DCS should go into the race with something. To find out, how settings, count of units, even some modules, weather, etc. influence GPU and CPU.

To whoever in the ED team reads this, we all only ask that real, honest consideration is given to this topic and that a proper dialogue is opened. MV (and MV2) were created at some point in the past, exactly why i do not know. but they were created for a reason, and whether by intent or not MV2 is critical to making liveries. passionate and talented skinners produce work for free to enrich the player base and add value to the overall product. It saves ED time, and money. it saves 3rd parties time and money, again leading to a better product. Comments about "we made skins before modelviewer" are not helpful. Ive seen many skins from that era nad they are nowhere near the level of quality achievable now. The F5 competion debacle proves this point, skins of the current expected standard require MV2, or access to the 3D model and a licence for Adobe Substance. We all appreciate the desire to protect IP but it is a sad fact that stolen 3d models are availabe within days of a launch and encryption hasnt changed that. We all enjoy and respect the product that ED provides or we wouldnt be so upset and without access to MV2 for any future encrypted modules, the whole game will stagnate and lose players. ED, you may disagree with me or choose to dismiss my observations. But without high quality skins, mission and campaign makers will not continue because they can only make missions for skins that ED provide, forcing ED to use expensive dev hours to pump out nation, year, squadron and mission appropriate livieries. The nature of the player base is THAT WE ARE ALL NERDS. So are ED programemers! they wouldnt last programming such minute detail if they didnt have a love for it! The demand that the buttons in cockpit have "the right clicky noise" or the correct fuel burn rate for the altitude and temperature. The correct colour red for the squadron badge. Skins are not an afterthought, they are an integral part of the experience. Putting time into getting MV2 to load encrypted skins is a priority and ignoring that now will only lead to ED having to spend money downstream of the problem which wil lbe more expensive than fixing it now and allowing the huge free content community to flourish. Please ED, work with us and let us help you. Fish

This work in MP or SP only?

спасибо, было супер! я так понимаю концовки 2? почему то результат всё равно 50%, хотя написано что миссия выполнена на 100%, но видимо, потому что кровожадный

Not to derail this entirely, but cold war historians have only found nuclear war plans in every warpac nation's archives. They are very well documented historically, and there were never any non nuclear ones found (cuz being historians they looked). There is a great Czech book on this (not translated), it happily includes exactly how many kilotons everything near the czech border got on 0 hour, and then how many warheads were reserved for follow on strikes as needed. I know this doesn't comport with western notions of the conventional war they wanted to fight, but it is what it is. Back to the 29, which was designed to work from highways, cuz they expected their own bases to be nuked in return 10 minutes later.

Don't feel bad, my voice doesn't sound the best either. Opinions are like asses - everybody has one.

Considering how touchy this BIT is, and the fact that you are able to get through the initial BIT (something I can only do if I unassign X and Y axis from my Joystick,) my guess would be this is just an issue with the aircraft systems as simulated rather than the FFB forces. Just a guess though.

I realize that if I have the autopilot engaged and do some heavy manuevering, these alarms might come as to alert that it might have broken, or is it just to highlight that I have something wrong? I have not felt any issues with it while flying though. Can it be reset? If so how?

LOL, seconded!

Solution: Implement Nike-Hercules so we can enjoy launch warnings over the Cold War Germany map

Please provide a track and we will review.

Все 4 пункта мимо. Прям снайпер Это не баги, это ФИЧИ, которые есть в реальном самолёте. Наверное нужно прочитать Список изменений нынешнего патча... МиГ-29: Проблемы с системой «свой-чужой» для клиентов, подключенных к миссии, запущенной на выделенном сервере. Эта проблема присутствует только на выделенных серверах.

Using FAB-500, default fuze, default timings. OPT mode , CCIP, no predesignation. At least 30º dive angle, waiting for laser ON, waiting for CCIP moving up. Bombs falling short a little less than 100 meters

Then you need natural head movement, otherwise you'll feel just like artificial cam.

Based on feedback from the team, after a cold start and AFCS check, you will need to manually set airleron trim to neutral. This might be what you are seeing. Let us know. Thanks!

Just a note from your vid and to add to DP SPaz's comment, you'll want to land along the angled deck (points out the left of the carrier) along the dashed yellow and grey line, and when you touch down on the deck, don't press the brakes, put the throttle to full power. If you miss you'll want to be able to lift off again, if you catch the hook, you'll stop, and can pull the power after. Kind of treat every carrier landing as a bolter and be happily surprised when you stop.

Except for the RBKs, I've found the weapons quite accurate when given a good bombing solution. There may be though other weapons that needs to be adjusted, I have not dropped them all. Note that some modes will be less accurate than others, like CCIP Delayed mode and TOSS in particular. Wags

Do you have real life experience with MiG-29? We have following FACTS: - SPO-15 in MiG-29 9.12 is connected to radar for blanking of forward hemisphere. - Rear is not synced. - ED agrees SPO-15 can handle MPRF in MiG-29 - Testing for radar overspill of SPO-15 device is performed at 3x the rate of HPRF of MiG-29 radar. What happens here, exclusively in MiG-29, like you insist, to prevent working exactly with HPRF despite SPO clearly being able to work with it?

I tried to run your mod / mod compilation today, DCS did not start with it in the tech folder. Did I do sth wrong or does the mod need an update after the recent patch?

Huge thanks to @Wags for a very well produced instruction video! For me it sorted out all question- marks in how to deploy ground attack weapons. Very cool that you included the DTC functions as well, atleast for me it asweared some remaining questions I had about the cartride functionality. If my mark 2.0 eyeballs is correctly calibrated, Wags seem very accurate in his bomb drops, so it can obviously be done. I better getting into my Fulcrum and start practise!