Shahdoh

“I want to go to Las Vegas”

Nope, same issue still, scripts work for the server only, not client connections. B(

Running some new tests myself atm. Fingers crossed.

We had scripts like this on the VA server, but when I last tested it, it only worked for the server, not any of the clients. Has this been confirmed working on a client connection?

That's really the main problem right now. None of the scripts that check on the clients are working atm due to changes in 1.5. As soon as they get that workingagain, then admin tools and other control scripts can be put to use again. It is a known/reported issue, trying to be patient waiting for the fix. Shahdoh -VA Assistant Admin

We finally have the Virtual Aerobatics server up and running! Give it a whirl. /salute

It is not out of the question. I used the TF-51 since it was free for everyone and to hopefully build interest in racing in the community. At one time I was thinking of having all PFM capable aircraft racing in their respective classes, but, I found out that even just the mustang took up a good deal of time for the organization part. So, I might have multiple seasons, 1 for Mustangs (or maybe props as a whole) and another for 1 class of jets, yet to be determined. I may post a survey in the coming months to see where the interest lies. 1st things 1st, need to wait till 1.5 scripting issues get resolved as the race code is currently not working.

Thank you for your interest Uthaedis. At this time, the season is over. I will be looking to start up a new season in 2016. Hopefully will have the scripting issues that occurred with 1.5 resolved by then and will put up a new post for the 2016 season. /Salute

I run a dedicated free flight server named - North American Free Flight. Linked are 3 different crashes I experienced with the server on 18 Oct 2015. Tracks are a bit large so linking the files via dropbox, hope this is ok. https://www.dropbox.com/s/00nob6rxin2dnvd/DCS%201.5%20Beta%20Crash%20log%20-%2010-18-2015-1.rar?dl=0 https://www.dropbox.com/s/00nob6rxin2dnvd/DCS%201.5%20Beta%20Crash%20log%20-%2010-18-2015-1.rar?dl=0 https://www.dropbox.com/s/60sp1rqvejukxca/DCS%201.5%20Beta%20Crash%20log%20-%2010-18-2015-3.rar?dl=0 Thank you for a great Sim

I use saitek peddles, but these settings should help out all the same. http://forums.eagle.ru/showthread.php?t=130129

I do not disagree with that at all, but atm, the simpler solution is just to increase the default. Even with the settings opened up to allow 10mbs, with 20 clients connected, am only tracking 1.5mbs activity. The power users will make the change, but that leaves a large number of people who either do not read the threads or do not dare touch files on their computer. Those will continue to see the lag spikes due to the choked bandwidth set by default. Simply increase the default and that will eliminate 1 of a few different things going on with MP connections IMHO.

Good to know, thanks.

The more people that set it, the better it will be for everyone. Really needs to be as the default instead of the minimal settings that are there now.

That is correct, create if not there, add to it if it is.

I ran into a similar issue. It seems something changed in the inventory and a new save does not seem to rectify it after opening an older mission(even previous 1.5 mission). I was able to fix it by deleting the warehouse file out of the mission archive, reopen the mission (it will rebuild the warehouse file when its not there) and then re-establish the quantities. Notice the blank names in the inventory list, that is the biggest warning that the inventory (warehouse file) is corrupt in some manner. Additional note, need to change your airports to the appropriate side as well.

Check out this thread. It started off about old missions in 1.5, but also covers issues with missions built in 1.5. http://forums.eagle.ru/showthread.php?t=147907 Basically, it comes down to mission size and how much data is being transferred to the master server, apparently. Have it too large and it will not show. Get it to where it will show and it will disappear after just a few clients show up. Shrink it some more and it will stay visible with more clients. Right now I am running a 1.5 server with 67 a/c available with 3 tankers airborne and 2 carriers and I can host 20 people with it staying visible in the list. No scripting or briefing yet, those too will change things. Good luck, Shahdoh

What were the other parameters of the mission? How many AC? How many clients could connect before it disappeared? As stated by Xcom and others, it seems to be mission size that matters most. Carriers indeed would add a substantial amount of info compared to other items in the game.

Carriers in themselves do not prevent the server from being seen. I have 2 in NAFF's current mission and it stays visible with all slots (20) full.

Like this one?

As mentioned before, seems to be how much data is being broadcast to the master server. In that light, thinking length of client names may be contributing to that factor, thus the minor fluctuations in client capacity for a set mission.

Looks like multiple issues. #1 being mission size can effect how many clients can be on before it disappears. I can concur with that, as we ran a much smaller mission yesterday and had 20 clients on and server still visible. The other issue is the duplicate name creating an event on the server. As Nelson pointed out, we specifically had 2 clients on with the same name on the server. At this point 11 people were on. Server stayed listed. Then, had those 2 players collide, triggering the friendly fire event to the duplicate name. At that moment, the server became unlisted and did not return. All this time, there were just the 11 on the server. Edit: Seems my limit on the NAFF mission is currently 11, retesting the duplicate name event issue. Edit2: Ok, disregard duplicate name issue. Retested and not able to duplicate. Apparently another had joined NAFF at the moment we ran our test. Edit3: Changed mission to 67 available a/c and 3 tankers - no briefing info, server stayed in the list at 20 out of 20 allowed. Now the Memory leak issue killing the server (10g ram) around 35-60 minutes into the mission.

Another issue that I have just been informed of, is the player names need to be unique. Specifically default users named Player. Get people to use unique names, inform "Player" how to change their name and then remove them from the server. See how that works.

Not sure either, just throwing numbers out there to see if there is any relevance. 1st day I had the mission up I was getting 10-20 people connecting, So thinking mission size or number of client slots has something to do with it.

New mission that looked like it was doing well, has dropped off the server list. Clients were around 6-10 when it happened I think. Also, I can not put in server information when creating the server or it will not show up either.