Shahdoh

Look in your description.lua file for these entries and others like it: {"Bf-109K-4_KIL_CROSS", 0 ,"Bf-109K-4_DIF_NJG",false}; {"Bf-109K-4_KIL_CROSS", 1 ,"Bf-109K-4_Bump",true}; {"Bf-109K-4_KIL_CROSS", 2 ,"Bf-109K-4_spec_NJG 11",false}; {"Bf-109K-4_KIL_CROSS", DECAL ,"Bf-109K-4_CROSS",true}; change the decal line (last one) to: {"Bf-109K-4_KIL_CROSS", DECAL ,"empty",true}; Empty in that part should blank out the decal that is being applied. That may or not be the one you are looking for. If not, try it on others where the word DECAL is in the line. Good luck

Is probably a decal that needs to be set as empty like the bort numbers. Would investigate that unless you can see it in your photoshop. Then its on a layer that needs to be edited/deselected.

Yeah, from the server side perspective, have not seen anything like it. Goes from over 900 ping to a steady 140's once he is in an aircraft on the server.

Sweet!

Did they change the spec layer or something in the last 1.5.3 Update 2 patch? All of my sabre skins, both default and custom have changed. The shiny aspect is quite a bit different from previous versions. This apparent change ONLY affects the Sabre.

Think I got it, maybe couple minor touchups here and there:

Since 1.5.3, It appears they have changed the Sabre's brakes so they are not overbraking. The Y saturation settings I have provided in the OP are now no longer needed and should be set back to 100. The curves and inversion for Saitek rudders are still valid. /Salute

I have seen this issue as well in MP. Carrier warehouse works for the host/server, but clients in MP can load anything they want.

First L39 Skin Thought I would try my hand at a fictional racing skin for the L-39. Think I am getting close on the main scheme, details and decals yet to be added. Let me know what you think, thanks

No, i have not, just seen this thread as I was researching while working on a L-39 skin and thought I would post what I have found. If they have fixed it, that is great!

Just got the L39 so just found this thread. I noticed this same problem on mainly the P51 skins and pretty sure I have found the solution but it can be a rather tedious one. When you have the same aircraft, but there are different (extra) items in the description.lua, it confuses DCS and causes the corruption. The fix is to create a standardized description.lua for all skins for that aircraft. If one aircraft has it, they all need it. But you say, "Its default, it should be there!!" and your right, it should but the fact is it does not. I found this fix when I hosted the Mustang race. we had around 30 aircraft registered, most of them custom skins and at first we experienced a lot of skin corruption issues. After making sure all description.lua had the same entries, in the same order and all clients had updated files, we never had skin corruption errors again. below is an example with the Mustang skins: Here is the corrected/standardized description.lua from my Miss America Too skin: Compared to stock Voodoo skin with corrected description.lua

I at first was worried about the blank name users, but SLmod does deal with them ok. One thing to check out is why the name is blank. I have seen them blank from the server perspective, but when cross referenced by a client machine, there is actually a name there that is usually "Player". But, not all clients with the name "Player" show up as blank names. Dealing with them by there ID has been working in my experience on the VA.

Chemtrails, he forgot to hit the reverse button to push it out instead of in... Silly pilot...,:music_whistling:

Under the ..\saved games\dcs\config folder is a file: serverSettings.lua Open this file (preferably with the free utility Notepad ++) and look at the following settings - ["advanced"] = { ["event_Role"] = true, ["allow_object_export"] = false, ["pause_on_load"] = true, ["event_Connect"] = true, ["event_Ejecting"] = true, ["event_Kill"] = true, ["event_Takeoff"] = true, ["pause_without_clients"] = true, ["client_outbound_limit"] = 0, ["client_inbound_limit"] = 0, ["event_Crash"] = true, Particularly the Pause on load and pause without clients, make sure they are set as you want them to be. Valid values are either true or false. Editing .lua files with either wordpad or standard notepad is usually a bad idea. Notepad ++ is the safest bet. These settings are usually set from within the UI, but one reason or another may not set correctly. This is the most direct way of verifying what the server is set to do. Good luck

Do note, anytime there is a DCS update and there are changes to the types of weapons used. This will generally break missions that use a limited supply system. The mission then has to be updated by 1 of a couple ways. 1. Delete the warehouse file from within the mission (*.miz file is really just a zipped file, just set your compression utility to open .miz files). When you open up the mission in the editor, DCS will rebuild the warehouse file from scratch with default settings. You will need to go back in and reapply any changes. 2. On any airport with a limited supply set, change it back to unlimited. Once all are set to unlimited, save the mission. This should reset the warehouse file as well. Then go back in and reapply your changes. if this option does not work, use option 1. /salute

Try this, have the airport have a limited supply, say only like 10 or so. That is what the airfield has stocked, when it drops below that, supplies come from the warehouse to replenish the 10 (or whatever). If warehouse is destroyed, the airport can no longer be replenished, and with a small supply there, will soon be out. Also make sure the speed and amount of replenishment per cycle is set appropriately. Just a guess really, but I think worth a shot.

Yep, working great on the VA. Thanks Codefox!

Last time we were using Servman, it broke and couldn't get it working again. Someone have a link to the working version of Servman then? Much appreciated.

Looking to add ping limitation to SLMOD. Anyone have a way to do this? Thanks

have you tried a very basic mission?

Sounds like someones version or mods out of sync. Since no one can connect to server, would suspect that first. Something on that machine that is not on the others and they need, so it will not let them in, more then likely something in the mission.

So far, build 74 working well here. Thank you!

Actually, I use those on the server as well. Seems to work well enough.

There are some settings that increase the network bandwidth DCS uses that can help, particularly on servers with a lot of clients. These settings are highly recommended by the larger servers like the 104th, 373vFS(Blue Flag) and the Virtual Aerobatics. http://www.virtual-aerobatics.com/forum/viewtopic.php?f=14&t=1841 Good luck!

Ok, Slmod chat log shows the output from admin commands were suppressed, but am seeing that they are not. Clients seeing the -admin commands as typed on build 72.