=VG= SemlerPDX

Okay - I've gotten to the bottom of this all. Seems that asshole SemlerPDX made the original account, and paid the original $55 annual license fee (if I am reading this correctly). Sorry, I don't remember such things after a year, and I have no one to blame but myself for not getting the correct login info onto the login sheet we use. Simple solution: pay the fee and reinstate the TS3 server. Eazy peazy. Only problem is I cannot afford this today, or tomorrow, or next week. My daughter turned 18 last weekend, and her Mom and I got her a new laptop and split the cost - on top of that, she graduates High School in a few months, and I've just booked a flight/hotel/car so I can get out there for the weekend and attend the ceremony. Basically, I'm over a thousand dollars in debt in less than a week here, and I can't pull the $55 out even though I very much want to pay my share for VG. UPDATE: Thanks to Double_13 for taking care of this! I've paid the bill and will apply the license now. VG TS3 will be up shortly. Anyone who appreciates the VG TS3 and can afford to chip in a little bit, please use this paypal link to my account and I will use the funds to pay the license fee as soon as it is enough. The total cost for one year is $55. There is no discussion here, we cannot use a non-profit license, and we need at least 64 slots. This is what we need, it's what we've had for years. Paypal funds on the front page have already been spent on the website costs. As we all know the list has not been cleared since the new website went live, possibly an oversight, or possibly to track the generous folks who have helped to pay for this awesome new website, so I must take up a special donation for this fee. Do not donate to the PayPal link on the front page for this TS3 License collections attempt - use the link below, or I will not receive the funds I need to pay it. IF you donate to this link, please also post up below with your name and the amount paid so I we can track the progress in THIS thread. DONATE - (Special - goes directly to TS3 license fee through SemlerPDX) GOAL: $55 (US) Received: $55

Okay. Just checked it and saw you flying... assumed it was okay. BMS Server restarted to last autosave.

I just found out that it's our TS3 annual license that needs to be renewed. Us "Administrators" in VG have access to a page with the login info for all our services, but TS3 VG login info is missing. I've contacted the other VG Heads and we'll get it sorted asap - BUT the TS3 could be down for a day (at least). Feel free to use the VG Refugee Lounge Channel in the TS3 Server run by our Brother Clan, L.A.M.B.s (nopryl). TS3 login info and password can be requested at their site for anyone who is a not currently know to LAMBS. TEMP TS3 VG Refugee Lounge: http://www.nopryl.no/smfprod/index.php (Follow all VG Rules in LAMBS TS3, violations or disruptions to our friends will be dealt with harshly)

Mumble should be fixed now. Report up if it is not (merged the thread, best to just use this if it happens again in the future)

Can't wait till programming wiz's like you and your students can make any old classic game work in that dual-screen VR tech!! One reason I won't drop $600+ now is that only 2 games I own would work halfway decent in VR (DCS and Elite:Dangerous) but both trade their awesome resolution for a blurry "difficult to look at" set of in-game UI's and menus. Unfortunately, I've already heard that they haven't made enough on this first generation of VR to consider designing or improving the system for a second generation of VR devices... but here's hoping!! Hope you and your students have fun with that, Badploy!!

PR SERVER IS UPDATED /locked

Don't worry about it, Poffadder's got it covered, like I said. But on the issue of RDP, you have access to the info page, you can fix that issue with the root login. Just a reminder.

He wrote up in the chatbox, best place to check for current events info when there are no posts on a subject. Also, I only contacted our PR Server Manager (Poffadder) yesterday afternoon, and still waiting for a reply. Was going to make a post regarding this, but seems like you beat me to the announcement so I'll write it here: We are waiting for our PR Server tech Poffadder to update the server. Be patient please - no one expected this update that came out of nowhere, couldn't even find details about it on the PR website (post is virtually hidden in a changelog post deep in their forums). Because of the new client side automatic updates, all clients are already updated but the server requires a manual update of the files. We will get this done asap, and we appreciate your patience during this downtime. We are a small community, and many of us have gotten busy with life or careers and this of course takes priority over our game time. We do share the delegation of duties, but at times, there are certain things that only the person most familiar with a task is the go-to fixit guy for the job. We operate this way because doing something the "right way" is more important than getting something done very fast, and while it's frustrating to have to wait to play a game here, this method ensures we don't run into problems with incorrect methods, overwritten config files, or lost banlists, and other such issues. Again, thank you for your patience - I will post up when I get a reply from Poffadder. Cheers!

Badploy is indeed a great leader, and great team player! As you could see on his profile, he actually IS a VG Member, and is one of the oldest here (predates my own membership by several months). The WCC Clan merged with VG when they lost their friend and leader. They retain their old clan tags in homage. Other noted WCC/VG members include Sparky, StarchyDuke, and BozZz . They are all good friends and good people, and already considered VG Members for nearly as long as VG has been a clan.

done

Quick fix for that (first alt+tab back to BMS, windows task bar will likely still be on top of it) then press Ctrl + Alt + Delete to bring up that blue windows splash screen, don't select anything, just press Esc Will pop back to BMS properly.

or any public online FPS game.... Not sure who is working on this server, but it is labeled as DEV -- if they could post up here in the discussion, it would help... PITN? You got some good things coming or something?

But we cannot make a rule for every little thing. It would be very difficult to have and enforce map specific rules, on top of that. Besides the fact that I think you are confusing this humvee with something that would be used as a front line asset, and though it may be employed that way on Mutrah often, it's a paper thin defensive asset at best when used as it was designed, and might be well used as a member of a humvee group that moves soldiers around the map. Putting it into it's own group would segregate it from the other humvee mobile infantry groups, wouldn't it?

There was another area with permissions for chat specifically that I forget about often. It's fixed now.

I am not certain I'd know what to look for, but I'm happy to make those files public for anyone to look at if they would like: BMS Server Autosave Files Feb2017

I've restarted the campaign to Day 1. I didn't change anything. If one of you wants to reactivate an AI Squadron we've disabled, that is okay (I'm thinking A-10's would be smart). I don't want to alter the base save file at this time, until we are certain of what to fix here to make it better, since you all can still "fix it on the fly" and see how your fixes play out while you fly.

Again, just let me know if you don't want to continue this overly challenging campaign and want me to restart it from Day 1 with some sort of modifications. Those notes that on Day 7 is when it gets rough makes me think on how there is a trigger to bring Carrier Vinson into the campaign on Day 7 (but in our file, we've modified it so it's present on Day 1). I wonder if this could be the issue, but it hasn't been one for the many months we've been doing it this way. Just more speculation and theory.

Yea, that's whats weird -- I didn't change anything and all of a sudden, OPFOR is OP. Maybe someone messed with the frag-o near day 1 after I launched it. I'm not sure what to change, as I had a look over the Day 1 save, and things actually look normal. Squadrons we grounded to add to the challenge are still grounded, and unless the campaign itself changed with the last update, I am at a loss for what to change to fix this. Maybe I should activate the A-10's and a few of the F-18 squadrons we grounded on the next Campaign restart... Just let me know if it becomes uplayable before that time, and I'll start it over on Day 1 with a few extra BLUFOR Squadrons active. If you want me to do this now, just tell me.

Done. Callsigns cleared and campaign restarted from last autosave.

I was wondering as much. I think the base mission save needs to be modified a bit, I'll have a look at things later today and will let you all know when I have something to swap out.

Restarted (sorry for the delay, I've been away )

banned

But that does not explain why you were on our server during the 30 Day Period in which you were banned -- only because of a server error were you able to rejoin VG PR COOP due to technical difficulties we were having with our banlist, but you did not rejoin the server using the name we had banned you with, you used subversive means to sneak back onto our server via the use of an alternate name in an obvious attempt to go unnoticed and bypass the ruling of the Administration here. How are you going to explain that? You cannot. ^ I fully agree and support this decision, as I'm sure all Admins here will once they read the facts presented by TEDF. We do not need players who do not respect the rules, and we certainly do not need players who intentionally bypass the judgement of the Admins by attempting to rejoin the server during a ban period with a different name -- be sure you understand: taking advantage of a technical error with our banlist is no excuse and you knew full well that you were not welcome here for 30 days from December 18th, which is why you used an alternate name to hide.