Kadin

Targanon Did you change this section: local ground_symbol_near = "ˉ" --U+02C9 local ground_symbol_far = "ˉ" --U+02C9 and further down GroundFormat = {… The labes.lua is working on my end. Most likely there is a miscoding in the file. Don't give up yet. To save time, as I mentioned before, make sure you test your file in Quick mission before you incorporate it into a mission for MP playing.

I was wondering if I am doing something wrong. I noticed that only the Spitfire has some Cold engine start up effects and none of the other prop planes including the Yak-52. Am I missing something or they are not implemented yet?

Before I posted, I did it myself again on the latest version. A few things to look into. Get the latest Labels.lua from C:\...\Eagle Dynamics\DCS World OpenBeta\Config\View. Place a copy of it in C:\Users\YourUserName\Saved Games\DCS.openbeta\Config\View. Modify it and test in Quick mission to ensure that it works. Follow the above process to incorporate the Labels.lua inside your mission. Then open (don't extract) the mission file to make sure that the Config\View\Labels.lua exists in there. Finally, make sure your Server DCS settings have Labels ON and for good measure check the box that says: Keep these settings for all missions. All this is for the Beta build...for now.

You need to incorporate your custom Labels.lua file into your Multiplayer mission, while preserving the file structure DCS recognizes. Here is how: Create your mission. Go to your Windows explorer where the mission is. Create a new folder and name it "config" . Open it, make another folder in it and name it "view". Place your customized Labels.lua file inside the "view" folder. Go to your mission file and open it. The file has an extension .miz but it is a zip file. I use 7.z app to open it. Leave it open and drag the newly made "config" folder right in it. That should do it. Clients will see your custom Labels or they can turn labels off with leftSHT+F10. Every mission needs to have this or else the server will default to Original DCS label settings. In the past, If you would open this mission again in the Mission Editor and save it, the custom label.lua would disappear but that is not the case anymore with the recent update :)

Yes and Yes

Guys, you know that the "dot" can be customized, right? You need to do a little homework but all the information is inside the Labels.lua file. Put a copy on C:\Users\YOURuserName\Saved Games\DCS.openbeta\Config\View and change settings to your liking. Of course, this same file can be incorporated into your missions so it can be enforced on Multiplayer environment.

yes, you can set custom Dot for your missions in the Server. Every client connected should be limited to that Dot system.

I would like to ask if any engine start up effects, eg. smoke, fire flashes are going to be implemented on the WWII planes

Impressed again :)

The above fix is for Single Screen/VR only unfortunately

Enjoying this amazingly versatile utility and I have a request. Would you consider adding links to the in-game manuals? Thank you, your work is much appreciated.

I had the same issue. I resolved it by copying one of the attached files to:C:\Users\yourName\Saved Games\DCS.openalpha\Config\View The labels.lua is the default one. The other is my modification. Rename it to use. Labels.lua Labels_KDN.lua

In your Nvidia panel, what setting do you use for the "Antialiasing mode"? Thank you for doing this. Very helpful.

Excellent! Thanks VampireNZ

Thanks VampireNZ. Actually, I got a modified one with no distance and grey colors (90,90,90) for "internal" usage. I was wondering how it shows in VR. I use a 4k monitor and the 2k seems to be when the actual LOD of AC start to show. So yes please post your version.

Yes, as rtimmons said. Always add/modify files in the C:\...\Saved Games\. If you have a question on how the file structure suppose to be (as in your case), look at the Main DCS installation area and mirror that.

I like the new Labels.lua. Quite an upgrade from the last one. Thank you Guys. I am attaching a modified Labels.lua for the slightly more hardcore crowd. This one has only a distance number showing between 14-25km that can easily be adjusted or eliminated. The dot is one type: ".", centered exactly on the body of Aircraft (or other target) and will show only on distances >2km. Same format for Air, ships, weapons and ground targets. PS: Place file in C:\Users\YOURUserName\Saved Games\DCS.openalpha\Config\View In case you did not know, you can incorporate the Labels.lua into your .miz file to enforce it in Multiplayer environment for everyone that connects. If you need to know how, please ask. Incidentally, it seems that once custom labels.lua is incorporated into you mission you can edit the mission in Mission Editor and resave it without having to reincorporate the labels file as it used to be the case in the past. Many thanks for that too. :) Labels.lua

...leave aside the creativity of the community mission builders that can "make believe" many situations. Our imagination is our limitation.

Well, I don't think we are comparing similar stuff. I only have one tracking device.

I don't have any issues with CV1 either. Have you check any possible environmental factors involved?

I am going to add a CON for the developers: Since they "Open that door", more people "demand" more...and yesterday!!:). Like they don't have enough on their plate already...

I am mentioning this just in case... I am using my own mission setup for Nevada and Caucasus test. Simple with only client planes to test. Nothing else. If you are testing using the "Instant action" missions that come with DCS module installation, it is a different more resource taxing environment. There all short of triggers and other vehicles and planes that coexist.

Makes you want to limber that neck, doesn't it, dburne? :)

Well, we do have to consider that we are not talking about identical map setups also: e.g. desert and sparse as opposed to forested/pasture and more urban. When everything is merged and textures brought to same technology level, there is a good chance Nevada will still end up being smoother and of course ground target ID will probably be still easier.

My performance on Nevada 2.0 is much better than on 1.5.5. When setups are as equal as they can be, I get average 45 fps in Nevada and 22 fps in Caucus on the ramp. All settings at MAX except Traffic, Lens flare and Field of view at Off. Pixel Density at 1.8 Intel i7 3970X, X79 motherboard chipset, Nvidia Titan (Maxwell chip), 16 GB RAM, no overclocking, latest NVidia drivers.