FuY

F1EE, latest open Beta, Get to Altitude and stabile flight. P/A engage, ALT engage, CAP engage After flying ~20 minutes (sometimes more and sometimes less) in autopilot @ stabile altitude and subsonic speed. the autopilot over corrects or oscillates resulting in the Autopilot disengaging. after that the trimm is all over the place and the autopilot becomes unusable. This might be a realism feature. but it could also be a bug. F1EEautopilot.trk

Title says it all. see miz. and trk. file for details. short summary: ~ below 82% Aircraft weight AI can maintain reasonable speeds @ reasonable altitudes without using AB. ~ between 83% and 87% total aircraft weight AI struggles noticeably with maintaining Aircraft speed. essentially using AB continuously. ~ above 88% total weight AI cannot maintain any practical speed @ any reasonable altitude. Aircraft used is Mirage F1CE. f1_bug1_aispeed.miz f1_bug1_aispeed.trk

On the issue regarding Apache Engine 2 not able to start "normally" I know someone has already made a post about it. but i got some more detail. Workaround: If (map) temperature is above 36°C... Impossible to start the Apache ! If temperature is between ~26°C and 36°C Start up 1. engine normally, Throttle to "FLY" check for Ng > 95% (1. ENG), this could require some collective as well. Start 2. engine. If temperature is below ~ 26°C "Normal" Startup. -10: "Sufficient IPAS air is required for a suc- cessful 2nd engine start. Ensure the APU, external air source, or opposite en- gine at 95% NG is supplying sufficient IPAS air." essentially bellow ~26° the APU can provide enough IPAS no matter the Ng of the 1. engine. this is what we expect as normal behavior. however, +~26° the APU no longer provides enough IPAS so you need IPAS coming from the 1. engine (95% Ng) (why can the APU start 1. engine but not the 2. one ?) and @ +36° neither, APU or 1. Engine @ 95% can provide enough IPAS so you cant start the 2. Engine @ all.

that´s not it. you can look on targets below you (cluttered by ground returns) and @ 0 relative velocity. 80% of the time the radar works as expected and simular to the hornet. the other 20% it takes up to 20 sec for a look independent of relative velocity and other variables. I fly a lot of Hornet and Viper. The hornet does not have this issue. From my understanding its a bug within DCS that has been reported multible times and always been flaged as "correct as is" yet no explaination has been given why this is not "just" a bug.

Since it is now taged as "correct as is" can we get an explaination why it is so ?! Given the troubled history of the viper i still tent to think this is a bug. but ofc if SME´s have, for example confirmed this behavior it would be nice to know.

jupp. a friend of mine showed me a clip in which he could not look onto another Viper @ 1nm-3nm above the horizon for 30 seconds. 95% sure its "just" broken.

Is this supposed to be this way ? Viper: Hornet: (since its kinda hard to see... the moment i lock him up was also the 1. time i had my HMD hovering over him)

I just did a 2100 NM, HI/LO/HI Strike with tripple bag, 4x mk82snakeeye and 2x Magic II I never droped anything but the 4 bombs @ the target which was 1050 NM away from my starting postion. after flying back i still had 500 KG of fuel. There was no wind on the map. Are you sure this is realistic ?

Hey, I´ve gotten into an Argument with someone surrounding the accuracy to pull coordinates from ATFLIR and Lightning II at reasonable standoff distance to then deploy JDAM´s on that self targeted Location. In DCS it is quite simple and accurate to deploy a JDAM on a coordinate that has been determined by the TGP, even at long range and low altitude, which would make the process of how the TGP determines where its looking at less precise in the real world. My question is: How accurate is the representation of the TGP in DCS when it comes to self targeting practicality. Is self targeting JDAM´s with ATFLIR and Lighting II standard practice IRL or is DCS in the way they represent this method to generous and accurate? Sources to your answers would be nice. Thank you.

Disclaimer: I am not pretending i could do better. I am not ranting or complaining. I am not saying ED is doing bad, in fact the opposite. I am also aware that most of what i mentioned is already in the pipeline. This is simply a: "hey, love your product, best money i have ever spent... here is what i would love to see looking forward." ______________________________________________________________________________________ 1. Performance improvements -......................... 2. Significant improvements/changes to AI. - More realistic AI flight model especially in Combat. - More reliable AI in areas like tanking and landing patterns. (I think in these areas, AI planes flying like they are glued to a rail is fine as long as it makes them more predictable and reliable) - More dynamic interaction between AI (If group A see´s a threat, it should have the option to talk to group B about it.) - Significant improvements to air defense systems. (Communication between them and better tactics like turning the radar of to defeat anti radiation Missiles) - More difference between skill levels. (A ZU-23 with the lowest skill level might shoot without good aim, it might just randomly blast into the sky, [would also look awesome].) - ATC improvements 3. Improvements to the Editor. - Better implementation of the F10 menu, options to layer the menu, maybe a better GUI. (Currently you need a 3. party script if you want a layered F10 menu, this should become standard in the Editor.) - More options for mission creators regarding AI. (Changing AI external lights or giving them certain tactical settings like low altitude lurking.) - More intuitive settings across the board. - Popup explanations about a certain setting like what does a certain ROE setting do. - More options regarding View options. (you need 3. party scrips to, for example, prohibit players on your server from seeing enemy positions via the spectator mode.) 4. More immersive Environment - Dynamic weather. - Smoother Surfaces, better mountain textures. (Certain mountains and ridges look like Lara Croft´s boobs from those older video games.) - General Audio improvements and fine tuning. - Options to turn of city- and airfield lighting. - More AI aircraft types and updates to the old textures of certain aircraft. - More Ai units from tanks to trucks to infantry. 5. Quality of life improvements. - Short cut to copy a location from the F10 map into a knee board page. (this would make it so you don´t have to constantly tab between F1 and F10 when trying to punch in a waypoint) - Better communication when procedures within a given module change. - Maybe a better GUI for rearm and refuel (When refueling, a slider to refuel external stores, things like that.) - Tanker call out when turning 6. Modules - Gib F-15E, Eurofighter, AH-64D, Mirage F1, make every SU and MiG an epic module. also... do it by tomorrow ?! To summon it up, DCS is awesome. Given what people sell in MSFS the modules in DCS are above and beyond anything else. I just hope the "World" in "DCS World" gets some more attention.

I once had like every flight in the AO ignoring their individual and unique tasks, ignoring their orbits... and immediately lining up to attack a SA2 sight. I was really spooked by it. Not only did they leave their station and went straight for the SA-2 they all 1. went in a trail and then went for that one SA-2 like a hive. that is why i used the ROE. but ofc the ROE created new problems. I dont know... but working with the AI is impossible. i had countless problems with it. some i can reproduce... some i cant. some happend 20% of the time. some happend 80% of the time. some are so weird that i dont even bother reporting them as a bug cuz i dont know how to describe it. Do you have any tip of how to deal with this ? Do i wait till the Ai is overhauled completely ? Do i notoriously report everything i observe ? Am i just stupid and it all works for you ?

So, to nail it down. 1. bug: carpet bombing task gets broken when using certain ROE settings. (I use the ROE setting to make sure these flights don´t randomly engage before their push time and they leave CAP to those who are assigned to it) 2. bug: The JDAM ripple seems to be a problem with GBU-31 and probably other types since the GBU-38 gets rippled out as expected. 3. bug: in certain formations the wing man, alto it would make sense does not ripple out ordinance together with his flight lead

Bombing tasks, F/A-18 2x2 GBU-31 4 task drooping 1 guided bomb each on 1 location each. some bombs hit some target locations twice while not hitting others. also, the rippling out of most, if not all bombs in one pass that i am used to is no longer happening. Carpet bombing tasks, F/A-18 2x2x2 MK-83 1 carpet bombing task instead of, well... carpet bombing, the AI drops one bomb after another in the most stupidest way ever. Idk where the problem is. but it must be with the MIZ. Doing the same task on an empty map the task are done the way they should be (apart from the rippling of guided bombs in 1 pass) also, i fast forward at around ~5-8x the speed idk if this might cause the problem. but there is something wrong here. if you load the Miz. Observe the 2x2 ship F/A-18 taking of from CVN-72 both flights will orbit at wtp2 till 10.30 DAY1 250-70.miz

I am still not so sure yet. but i trust you on that.

Latest update, Syria map, F/A-18 using ATFLIR, Twilight conditions ~1900 local