GumidekCZ

HQ-16 missile is bugged again. Any AOA and G-forces have now NON! effect on missile speed and energy. At lower speed, missile almost stop slowing down and keeps its speed till missile timer countdown ends.

@NineLine Please, can the ED team finally fix the DIMM export after such a long time since the problem was reported? Many thanks.

I hope this ugly reflections will be fixed asap.

Clean drivers and settings for RX 6900 XT, latest drivers with MSAA 4x - this is terrible This is how rivers look like now, A-10C edges are also very ugly. I cant do anything in DCS to make it better.

Same issue still present - thats horrible! It ruins the game immersion!

Thanks, I was not at my PC to check correct naming. Will fix it.

I solved the problem with this:

So I had to find solution by my self (I have been foolish) And I found it. I didnt know, that "User Snap View Saving" in MISC DCS settings have effect on this problem - because it is wrongly named. It have not effect just on quick view, but also on user saved default view. So if anybody in troubles with default view angle not set after DCS restarted ... make sure that this option is checked

The WORNG descent profile reported long time ago (April 27 2024): https://forum.dcs.world/topic/347820-ai-descent-angle-wrong-calculated/#comment-5422844

WP now in feets after previous update - NICE! GJ! But INS still set to NAV instead of IFA

At the time we released Gamblers and started to fixing old Raven One, AI behaved reasonable, able to rejoin in turn and climbed without problems. Now its just ...beeeeep.... Other developers knows about it, players reported annyoing stupid behaviour months ago. Do the developers need to adjust AI lead climb profile in every new/old mission? Really? Thats what you want from them/us? instead of further tuning AI logic and may be adding some options for AI into ME?

Do you know how many of paid missions I had to tune or put there AFB restriction for AI as Lead in climb? MANY! I hate this! But Im glad I can help to campaign developers and bring players smoother flight experience. IRL pilots always need to plan the flight and choose between quick AFB climb and saving fuel after reaching cruise alt, OR to do shallow climb without using of AFB - more fuel saving when heavy loaded and better to wingmen form-up in climb, not after reaching cruise alt as in first example. So as most of DCS campaign missions - where AI is a lead, I (and many others) would like to se smooth AI flight with whatever I setup in ME (except the near stall speeds). I cant immagine, how mix of AFB with speedbrake climb can be NOT-BUG in your eyes. One good thing ED had done - get rid of the side wave glitch when AI crossing WP as mentioned in recent change log. GOOD JOB TEAM!

F-16C 152nd_Fighter_Squadron 80th_Fighter_Squadron 36th_Fighter_Squadron 174th_Fighter_Squadron 132nd_Wing _Iowa_ANG M-2000C: 2004 Tigermeet 2010 Tigermeet This results in jittery lines in F2 view:

But this method you mentioned "I will not say stupid", but it is only bypassing of the current stupid/broken AI logic (AI still have plenty of power to increase closure rate) and IRL this is very common type of rejoin called "CV Rendezvous", it cannot be instructed and hope for a mirracle that paid campaign player will do so. ED team must work harder and not searching for bypasses and workarounds.

As title says. Flying NTTR map at night is NOT FUN! DCS 2.9.8.1214.1 View on Las Vegas from Nellis direction with racing oval. nullnull

No answer regarding the funcntional bort numbers?

Does this rule mean, that bort numbers MUST be functional ???

The AH-64 weapons processor automatically compensate for wind drift AH-64__GUN_SHOTS_NOT_WINDCORRECTED.trk

George CPG very very often forgetting to do quick LASER Ranging before he fire the gun. So if you change targets from the target list, there is very high probability of wrong range data for balistic computer. AH-64_George_randomly_NOT_LASER_RANGING_FOR_GUN_SHOT.trk

Soon I will soon report two BUGs: 1) George CPG very very often forgetting to do quick LASER Ranging before he fire the gun. So if you change targets from the target list, there is very high probability of wrong range data for balistic computer. 2) DCS AH-64D Longbow Apache is missing very important part of ballistic computer calculation WIND FRIFT - If you search for AH-64 ballistics, you will find that computer compensates for: Air Resistance Gravity Yaw Projectile Drift Lead angle compensation Trajectory shift WIND DRIFT

When you have set up multiple triggererd action for group and multiple triggers in main mission trigger list - IF YOU DELTE OR ADD TRIGGERED ACTION IN LIST, OTHER TRIGGERED ACTIONS ARE RENUMBERED BUT ARE NOT UPDATED AUTOMATICALLY IN ACTIONS FOR TRIGGER IN MAIN MISSION TRIGGERS. THIS RESULTS IF WRONG ACTION TRIGGERS SET IF YOU ADD(CLONE) OR DELETE ACTION TRIGGER WITH LOWER NUMBER THAN OTHER ACTION TRIGGERS. THIS HAVE HUGE NEGATIVE IMPACT FOR COMPLEX MISSIONS - especally those produced by 3rd party developers. Thanks ED for solving this problem asap.

Now thats how look like descent profile now. From 30k at start to 12k in the middle of route - AI starts shallow dive and AI is diving steeper and steeper when closing to final descent waypoinnt - There the AI is still some 1500 feet above defined altitude. AI is able to descend to 12k only by reaching next waypoint after the descent one - here set also to 12k feet. AI_Descend_test_.miz

AI is trying to climb fast to roughly 70% commanded alt, then AI will set for shallow climb. - thats ok (can save some fuel), but never saw any mention by ED develop team about this behaviour. BUG/PROBLEM IS WHEN: When AI is passing Waypoint in climb - AI F-16 or FA-18 will make small "S" turn - Hornet AI more agresive turn. USING AFTERBURNER IS SET TO OFF - AI will use full MIL power to climb, but could be not enought, AI will increase AOA and fall into the sea. HIGH OR SLOW SPEED IN CLIMB SET - HORNET AI is unable to manage and calculate stable climb profile and by using AFB it speed in steeper climb up too much and will use airbrake with simultaneously decreasing climb angle -> AI is too slow -> AI will use AFB ->...this repeats - at VIPER the problem is simillar but F-16 AI will not deploy Airbrakes so the unstability is mainly in speed and not in climb angle. There is only some kind of sweet spot in setting of parameters for AI to climb, but no-one exactly knows what is the key to it. AI need to be able to calculate/decide for shallower MIL power climb without using AFB (fuel eficitent) or using AFB with steeper climb angle and at higher alt switch to just MIL setting. I did tests only with Hornet and Viper, but I highly suspect others AI models are affected by this bug too. From my Tacview: AI_CLIMB_PROFILE _BUG_.trk

As far as I know without additional scripts, once unit is hit, it remains hit and this condition cant be reset Thats a pitty.

Here, when set the wider FOLLOW coordinates, AI is unable to achieve it and will stay in trail till Lead do wings level. AI_outside_turn_rejoin_BUG_2.trk