Shahdoh

Mission Editors aware of this will set it how they want. the others.... WELL........

Version 2.5.5.32533 right? It was on that version yesterday when I got the options data. Tried to do a forced update this morning and not getting anything new.

20mm from a P-51? What mod you running?

If it is an INTENDED feature, it should be part of the Mission Editor options to include or not. That I do not have an issue with. Options are good! You can also go into that options file and simply remove those "personal" settings altogether. that way the server is not forcing an option one way or the other, IF it does not want to. Again, this should be in the ME to chose to do, just like all of the other options IMHO. But I digress, this is not Burning Skies issue, other than to adjust for if they want assistance on or off (or clean it out of the options file so its the clients option that matters).

That is probably why it is working. It is what is happening with many others.

Fly the FW190-A8 by chance? After looking at the OPTIONS file for Burning skies, found that the Anton was the only one to have assistance on. From the mission's OPTIONS file: ["FW-190A8"] = { ["assistance"] = 100, ["CPLocalList"] = "default", ["autoRudder"] = false, }, -- end of ["FW-190A8"] This is NOT set in the mission editor, yet these options are put in there from the mission creators settings. Anyone know why?

In multiplayer, some of those "personal" settings get applied if the mission creator has those settings. They CAN be cleaned out if they edit the mission options file directly or the mission creator changes his personal settings. Not sure why those type of personal settings are even IN the mission file if they are not also set in the Mission editor (which those a/c type settings are not). I have found you can just remove them without it affecting the mission, and everyone gets their personal settings as they are supposed to.

Are you using the dedicated server with the "--norender" option?

Yeah, your situation seems unique to you. For whatever reason your --norender not working the same. For many others, its the --norender option the stops the AI from functioning correctly. THis has been acknowledged by ED and they are looking at it.

It is to reduce the processing overhead of a dedicated server. It means it will not render any of the graphics. In fact, on the pure dedicated server software they recently released, there are no graphics files for it to load, so the --norender is on by default. There will be no menu or any interface all all with the program. You use a WebGUI interface that allows you control of the server instead.

Same for us on the Warbirds of Prey server, not fixed on 2.5.5.32533

There are 2 different types of weather systems already in game, but both have their issues. Now if you are talking about an IMPROVED weather system, that has been mentioned by ED as being in the works. Though that is going on several years now with no updated information...

For my experiences, random failures have been off.

Yes, have seen the same results on 2 other servers. Wake Turbulance on and lag/warping can get REALLY bad. With if off, back to normal.

They have admitted that certain things in the visuals department have gotten into the OB patch. That we are seeing certain damage that has not really happened could be a side effect of that. OR damage that should be linked to a system is not there yet, so leaves it unaffected.

Correct, when you use --norender, it should only display the DCS World splash screen, nothing else, no menu, no visuals, just the splash screen.

Integrity check safe?

Something has indeed changed, a friend of mine who flies the 109 recently had both ailerons shot off and STILL had aileron control of the aircraft. It seems that we are in the middle of transition of the old damage model and the new one and some weird things are going on. This could be a rough ride as we really can't do much until they sort out the new damage model and release it in full. Hopefully this will come soon as dealing with these problems is frustrating.

I have seen 2 other servers that had Wake Turbulance on have massive stuttering happening. They have since turned it off and things went back to "normal". It is a cool effect, but needs some serious tuning with the effect from smaller aircraft. That and the apparent connection to stuttering/warping on servers. The hit on the CPU, not sure if its on the client or server side, seems to be the culprit. Until this is addressed, I would rather fly on servers that have it off.

They HAVE acknowledged this problem and that it is apparently related to the --norender option and units that rely on visual identification as you found out. There have been several threads which I point to in my first post in this one, but here is the one where they acknowledge the bug as reported: https://forums.eagle.ru/showthread.php?t=242981

You CAN join servers with a different version SOMETIMES. Depends on if ED puts it in the code to allow it to be compatible or not (or however they do it).

Ok, thanks for testing and reporting!

And I am saying that is a NEW issue. The flames that showed up in the first 2.5.5 release where not in their correct positions. THAT was the bug that was fixed.

Can't find the thread at the moment, but I could have sworn Nineline said it was intended to apply to the AI as well somewhere along the line.

I have bad habits, in that I dont or at least rarely pre-trim the aircraft, and fly it with my own inputs on take off. This is bad, but it does let me feel more directly what the aircraft is trying to do so I put in the corresponding inputs to correct the situation. Then I trim it out once in the air. It works for me and have no trouble taking off or landing any of the WWII aircraft (to include 2 wheel landings in ANY of them without bouncing). Applying proper trim from the get go minimizes the need for more extreme inputs for sure.