Shahdoh

Great news, Thanks Grimes!

Update, issue has been resolved. It was an extra firewall protection in place by the server provider. Once that was routed correctly, server is visible to all. The new Virtual Aerobatics Public Server is now online, enjoy!

We have ran into a problem with getting the server to show on the master list. I know, you have heard this one before but I think this is different. Server is running Windows 2012 Server R2 Standard. 32 Gig ram running at 4ghz. DCS starts up fine. The issue is that it does not show up in the master server list unless you connect directly via IP or have connected remotely to the server with RDP. If you have, then it will show in the master list for about 10 minutes (but only you, no other client can see it, unless they also connect direct ip first). Get out of DCS or not log in via RDP for about 10 minutes and the server will no longer show in the list. Any ideas what is going on here? The mission is the same being used on another server just fine. We are trying to upgrade to better hardware/network but have ran into this issue. Thanks for any insight you can provide.

It appears to be a bug, though DCS log does identify the issue with this message: WARNING NET: mizInfo too big, cutting short the server desc... WARNING NET: mizInfo still too big, cutting out the player list... I have been able to clear the error and get the player list to show by moving all of the briefing to the tasks in the mission editor. If I left any part in the mission briefing area, I would get the error and player list would not show. Seems to be mainly affecting very large missions.

As long as both have access to the Internet, then yes, one machine can connect via direct IP to the other. The internet is still required initially for license verification. So, not really a lan only solution, but still pretty easy to setup. Just start a new server, Public or not, just set a password and the other can either select it from the list or direct via IP. As far as interaction between pilot and instructor in the L39, I hear it's working better then ever except for a bug where lag on 1 machine or the other can cause damage to the aircraft. Good luck

Yes, Slmodv7_5_072 fixed the dropped character issue for us on the VA server. Though we are still seeing some other issues. Clients with the name "Player" come up blank "" on the server. Other clients see the correct name just fine. When using ID #'s for either kick or ban, if its a 2 digit id, it will at least sometimes apply the action to the wrong person. Example (-admin id kick 24 will kick the person with ID #2, if repeated, it then kicked another client, but not 24). Collisions/kamikazi actions with a Mig 29 report the action as the Weapon = "Mig 29" instead of kamikazi. This applies a different punishment level than is intended. In our case, weapon use is treated severely so the poor Mig 29 pilot gets kicked/banned just because he was involved in a collision. Thank you!

Pretty sure its the texture not saved with the proper mipmaps. When saved properly, there are varying sizes of the texture to match up with the different lod images (varying degrees of detail based on distance). If the proper mipmap texture for that lod (read distance) isnt there, looks like its defaulting to a standard or last loaded skin.

Updated to SLmod release 52 (current as of 19 Feb 2016) and the bug is gone. Characters not being dropped any more.

Do you use limited armaments via the supply system? Updates that change weapons generally will corrupt the warehouse file on missions with limited supplies. Missions that use unlimited settings generally do not see the problem. If you do use limited munitions, set it to Unlimited for all bases, save it, then reset the limited values you want and do a final save. Good luck!

Correction to what has been happening on the VA. Server sees all characters in chat, nothing is cut off, but still need to add the extra character as if it was. All clients connecting in are having the last character in chat dropped and slmod commands from the client/admin need the extra last character to execute properly. I have been on multiple other servers, and seen it fine on an SLMOD controlled server and also the dropped characters. On the 1 non-slmod server I visited did not have the dropped character problem. Looks like I was running SLmod a couple revisions old so will update on next refresh and report what happens.

My admin commands are being suppressed, if I enter the extra character to complete the command since it is cutting off 1 character.

Yep, seeing the same issue on the VA with 1.5.3. Exactly as described above. Actually, watching DCS chat, DCS appears to be dropping the last character on any chat sent..... Maybe not related to SLmod at all??

If you are looking for a bit slower start, take a look at the Virtual Aerobatic server. It is a non-combat server where you can get the hang of MP without the threat of being shot down. We have Air to air refueling, learn to fly formation with other pilots and in general get a good feel about MP without the immediate threats. Then when you are ready for combat, the 104th is one of the best!

Nice skin Snowsniper! Have not been able to test the scripts in 1.5.3 mp just yet, hopefully this weekend will be able to try it out.

Something strange happened on the VA today (6 Feb), it dropped all connections but still showed it as online and available. I have since restarted the server. Pretty sure have seen Ka-50's sling loading ok so hoping this is just a weird glitch that cropped up.

Unfortunately, the function the script relies on is still not working. B(

There are 6 Cargo's approximately 4.5 miles south of Mozdok along the rivers edge. The number is minimal atm due to number of objects in mission affecting public server visibility (at least at time of creation). Enjoy!

Have looked at the mission settings, and have not seen this setting there. Only other place is the client setting. I made the change and had others confirm that it was working. So, no clue as to whats up now. If you know what the setting is in the mission, please, point me to it and will look again. Thanks

On the Virtual Aerobatic server, we have since changed the setting to Large on the server machine (1.5.2). Users are now able to see that setting, or any lesser setting they choose on their client.

Found an issue with the autoadmin system with it recognizing collision versus weapon use. A F-15 and Mig 29 collided. The F15 pilot was correctly assigned points for the collision. The Mig 29 pilot was credited with a weapons hit/kill and subsequently banned for it. It registered as this in the SLmodstat.lua: Issue has repeated itself, again with Mig 29 involved. Mig 29 classified as the weapon instead of just a collision.

ah ok, thanks

WC, I might be wrong, but I think its just that the Beta UID's are different then the live server UID's. I just added the new ones to the old admin list and its working fine. Now will see when the admins switch back to the live client instead of beta. /salute

I have been hosting the Virtual Aerobatic Test server (till we get the dedicated one back up and running) and have had NO memory leak issues. Server has stayed up for over 12 hours at times and has not used more than 6.5 of 10 available gigs of ram. Granted, not much going on mission wise, but practically every aircraft is available and server sees a near constant 10-25 clients connected at any one time. Version 1.5.2 update 1

Jumbik, The tanks WILL show up with limited weapons but as I tried to explain earlier, its a case of a corrupted\not up to date warehouse file for the mission. All mission files (*.miz) are just zip files. Open it up with just about any compression software (Pkzip, winzip, etc) delete the warehouse file from the mission (it will not have an extension). Open up the mission in mission editor (DCS will rebuild the warehouse file with current data. You can now see all available munitions, tanks, etc and set limited supply as you desire. Salute, Shahdoh

Have seen at least something similar on the Virtual Aerobatics server where we use supply system to restrict munitions. When there is an update and new items (weapons, fuel tanks, etc...) are introduced, they either do not show in the list and even sometimes corrupt the information due to changing id numbers or something. I reset the file by deleting the warehouse file from the mission.miz. DCS will rebuild that information when I open the mission in the editor and then I can set the restrictions I want again. Shahdoh, Virtual Aerobatic Server Asst. Admin