Shahdoh

Hmm, no way to really beef it up that I have ever seen/heard about without some serious hacks. Doubt they are doing that.

Looks a bit "gamey" to me. /shrug

Heheh, maybe left(put) the invulnerable tag on it? :music_whistling:

Heheh, yeah, maybe, that was dawn when the picture was taken. They still need to fix it! ;)

Have had no problem knocking the A8 out of the air with the Mustang. In fact, thought it went down rather easily.

Open beta update 2.5.5, even after a repair after the update, the exhaust flames for the Spit are out of place: Even from inside:

F8? Not seeing it in my mission editor, or did you mean the A8?

The color is customizable in the full RGB spectrum for both sides. You set the 2 sides to the same value and you remove that aspect.

Yeah, something in your settings seems off. When you moved the trim wheel in your track, the stick did not move at all in reaction to the trim adjustment. When I took control and did it, you could see the stick move in reaction and the nose come up. In fact, at your test power settings, I only needed a slight amount of trim (barely off zero) to get level flight. When I took control with your settings, it went from the level flight to snap rolls because of the high speed stall from too much elevator. Another thing I noticed, but had nothing to do with your trim, is that it showed you running on only the L (left) magneto. Not sure if that was just a track inaccuracy or you had it set that way. If so, you are loosing power. Set it to both for best performance.

Viff, Thanks, that worked until we started using the "-w" option to have separate configurations for multiple servers. Now that there is a serversettings.lua in their own folder, the dedicatedserver.lua in scripts is no longer working. Do we need to create a scripts folder inside the new configuration folder? (-w Server1 -> ..Saved Games\%DCS_Dedicated_Server%\Server1\Scripts???) In any light, this would all be MUCH easier if these server settings where made available in the WebGui and then stored in the one place that makes sense, the serversettings.lua.

Well, I understand it is not as simple as layers, but used it as more of a descriptive aspect of what seems to be happening.

That is also possible with the labels customization. You have full RGB range of color you can set to either Neutral, Axis and Allies labels. Set them all the same and there is no distinction. The BIGGEST problem with labels is that they are on the very foremost layer displayed, which means you can see it through your airframe, clouds, sun glare, EVERYTHING. If they could just move the label displayed to the same layer that the object is actually on, it would solve this problem. Apparently this is not that easy for whatever reason, or you would think they would have done it already.

I'll stand by my statement that you should rarely need aileron trim. If it is because you are not switching tanks, you are not learning from your mistakes and that is on you. If you want the best from the mustang, you have to keep it balanced.

Lua is a pretty simple code, and the code in the label.lua is already laid out for you, you just need to adjust some values to your liking. The biggest thing wanted to point out was the need for a code specific editor like Notepad++.

Good link! And take note, files with .LUA is a type of code. Do NOT use standard notepad/wordpad or any other word processor to edit the file. They can put in invisible control characters that will mess up in the LUA code. As it says, use NOTEPAD++ (Free download/use) or similar text editor suitable for program code.

I am not aware of any post to link to you on that regard, but I am sure if there is one, someone will point it out. I am busy today or I would post some info. If no one else has pointed it out, will try to get something together in the next couple of days.

Good point, you want to trim rudder to center the ball. Rarely will you need to use aileron trim.

Labels can already be made to whatever custom range you desire and also if you only want 1 type of target. This can also be implemented on MP servers IF they choose to do so, so there is nothing to add in this respect. The capability already exists. What WOULD be a MAJOR improvement for the labels is if they were to set the label to the same "Layer" as the object it is representing. Thus, if behind the "Cloud layer" or "airframe layer" it would not be seen. People disagree on the view distances all the time, but as long as there is a graphic system that allows for an a/c to be seen at 15+nm WITHOUT labels, I will set the label file to match that so those WITHOUT that type of system have a chance of seeing the same thing.

Rotaries are indeed a great way to set up trim as it matches what is actually in the aircraft. I do not have the extra axises on my setup so I use a hat switch. With very brief pushes I can get fine enough trim inputs to settle the mustang. One thing to remember though is that even the real mustang must be watched as she is not the type of aircraft that can be flown hands off for extended periods of time.

Discord complicated? hardly for a user. Now if you want to setup a server, there are a fair number of options for security and things you can set it up to do. But for the client, its just setup your input/output device and join a server. Not much more to it.

Its not so much that you can cheat with gun convergence, but that you have to turn off integrity check to allow it. That invites OTHER cheats to happen. Not that it should be a huge problem, but its a problem nonetheless unfortunately.

Using the Dedicated server with the -w SERVER option successfully but it does not seem to be reading the serversettings.lua file for the server description (or ANYTHING for that matter the first time you run the option). And yes, we have a seperate serversettings.lua in each of the folders for the -w options. There is a description in the file, but nothing is displayed in the MP server list, it comes up blank. I have seen no way to put in the server description in the WebGUI. Yes I know that we can put it in the Mission description, but that is a separate thing. We need to be able to have a server description modifiable via the WebGUI or at least have it read from the serversettings.lua. Along with that, the PLAYER name for the server as well should be available for modification.

This affects the B-17 as well as other future WWII aircraft (P-47) dropping this ordinance. Would be great to see this added/fixed.

If set to a joystick switch that is NOT spring loaded, it can be set on pretty easily, But this is a configuration choice. Still curious about the lack of consequences for keeping the starter on indefinitely.

It would be a bug that you can keep the starter on continuously. The starter's Booster Coil, as pointed out by Yo-Yo, provides the initial ignition that I mentioned in a previous post. Again, this is not intended to be on full time, that is why you switch on the magnetos which will provide full ignition capabilities and provide full power rather than the limited ignition and resulting lessor power from the booster coil.