Shahdoh

Try it in darker conditions, I have seen the flames. What WAS fixed is the flames not being at the exhaust ports. If they are intended to be seen more in the daytime, that is a new issue.

Friend said if he waited to turn it on until he got in the air on the non-clipped version, it would stay on. Worth a shot for others to test.

Great! Thank you!

I understand that, but now that you have changed that one condition, I ask that you try the --norender again, because there are several other servers experiencing this issue. I would like to see if you are too, now that you have them apparently working again.

-w allows for multiple instances of the server off the same install. For testing purposes, try the --norender and see if the AI still reacts, if you get the chance please. I am curious.

For us, if we use the --norender option in MP, nothing engages, ground or air units.

Looks like rudder assist is on in that video.....

Sounds like you might be rushing her into the air. Do you pick the tail up (push on stick, or trim it to do so) on the rollout? Doing this will let it get more speed on the ground to about 120-140. From there you can relax on the push just a bit and she will fly when she is ready and should feel considerably more stable because of it. Also, do not use flaps IF you have been. If she still wants to pick the nose up, do not let her, keep it down (and use more nose down trim next time) and the climb slight till the airspeed picks up more.

Hmm, working on mine and a friends computer. /shrug Metashader refresh maybe? ps: flames are barely there in the daytime, not sure if that changed a bit, but if seen at dawn, the flames are definately there and in place instead of all over the place around the front and in cockpit.

interesting, and this was on the full install? not the pure dedicated server software?

Try it without the --norender option (full install required) and see if it works. This has been an issue reported in several other posts. This link will point to others: https://forums.eagle.ru/showthread.php?t=243137

Still doing it on 2.5.5.32299

Cool, now for all of the others to follow suit.... PS: You would "THINK" it would be pretty easy... the Nav lights would be one of the LAST things to turn off with the LOD ranges instead of being one of the first.

Can the aircraft nav lights be seen from further than 1 mile yet?

There is one already, here is the link :music_whistling: : https://www.digitalcombatsimulator.com/en/shop/

Thank you!!

Not yet, but will report asap. They did fix the exhaust flame issue with the spit (not mentioned in patch) and there was mention of dedicated server fixes, so can hope this AI issue was connected to that.

There has been a lengthy conversation on that topic in this thread: https://forums.eagle.ru/showthread.php?t=242847 Basically, ED's stance is that it did not have it, thus, it is not in game.

F2 outside view (if enabled), its the data tape at the bottom of the screen.

Have you tried running a MP mission utilizing the "--norender" command line option on 2.5.5 and if so, are the visual type AI units engaging as they should? For myself and others, this single option is what keeps the AI from working properly in 2.5.5. I am curious to find anyone who has different results to narrow the problem down even further.

Find out anything with the mission USSR_Rik?

Didnt they make the radio menu mouse clickable sometime back?

There are other reasons for engine failure than just overheating, but since we do not get a detailed report on what failed or why, we can only guess.

I understand that fully. My comment was for those wondering and want to test it out, that they could then see WHY you should not land AF birds on carriers just because they have a hook. It is why I used "THEY" in my original statement. ;)

Funny thing, this broke with 2.5.5. In 2.5.4 it was working fine with the --norender switch.