• Announcements

    • =VG= SemlerPDX

      VG Servers are Back Up! *UPDATED AGAIN* TS3 Server is back; PR and Mumble are online, Arma 3 Servers are online but still need VG specific missions and configurations, should be done before end of week...   04/15/2017

      UPDATE Sunday April 23rd:
      Most everything is back online now.  The PR Server is running, and Mumble is working.  We have not yet made PR Updates available in TCAdmin, but several more people have access to update the PR Server (including me) and there should be little to no server downtime from future PR Updates.

      I've installed a second PR Server and still need to expand the VG PR License for it - it can be used for whatever, but I called it "PR EVENT SERVER" to start.  I figured we might also want a development server for things like FastJack's PR COOP Insurgency Mission testing, and we will take care of that this coming week as well, if able.

      The Arma 3 Servers have been reinstalled, and they are running basic versions of their former missions.  They still need to be configured, but they will remain online until this happens during the week (when PITN gets time).  I've set up A3 Servers with a Steam Update button in TCAdmin, any Arma Admin can now update to the latest Arma version much faster and easier, and without needing to wait for a Head Admin.    -Sem

      Sunday April 16th 2017:
      I've just received an email from the Server Host in Germany.  They host the server that runs our TS3 and various game servers here including Project Reality, and Arma 2 & 3.  Apparently, there has been a fault with our server host, possibly a hardware failure or such, but all servers in one part of their data center were affected including ours. We do not have further details at this time, but unfortunately this means VG Servers will be down until we can regain access to our server.  We were not given a time frame estimate or specific details of what damage was incurred, and we do not know if we have lost any data that was on the server.  We've been with this host for many, many years, and we've had nothing but great connections and fast servers.  Clearly this is a rare occurrence and we need to be patient as we weather this storm. I feel particularly bad for our loyal Project Reality players who were very patient waiting for our server to get it's most recent update, and I wish I could do something immediately to fix this.  It's a sad truth that it is out of our hands for the time being as we await contact from our host, and get a detailed damage report and estimate of how long until we are online again.  Of course, I've contacted the other head administrators at VG and apprised them of the situation.  We will update you all as we get information. Thank you all for your patience and understanding!
Kaos

Current campaign

39 posts in this topic

Just set up a 4 ship sweep: me and 3 AI out of Kunsan.

Committed to the countdown screen. At 20 minutes the load flight screen showed. Then the mission screen displayed "mission in progress"

Closed the mission report screen and was back in the mission planning map screen. Checked the ATO and my flight was not listed. I attempted to setup another sweep but the result was the same.

Check Six

Asp

0

Share this post


Link to post
Share on other sites

Are you sure the runways were undamaged ? That's all I can think of.

1

Share this post


Link to post
Share on other sites
On 24.2.2017 at 8:43 PM, Kaos said:

I find the campaign too unbalanced. I agree that earlier versions were too favorable for the blue forces but now it is the extreme opposite.

Was anything changed in the last few weeks? Didn't fly as much but observed the BMS topics a bit, don't recall anything regarding balancing related changes. Might have missed it.

0

Share this post


Link to post
Share on other sites

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.

0

Share this post


Link to post
Share on other sites

I took a look at the JSTAR replay and it looks normal until around day 7 then red forces literally swamped South Korea. Just guessing: a modified trigger file?

0

Share this post


Link to post
Share on other sites

I heard of a friendly fire incident involving JSOWs, but no details on what was hit. But if DPRK made it through somewhere it's possible the situation snowballed from there. Osan's A-10s were no longer on the frontline, blue SAMs on the DMZ overrun ...

Looks pretty bad right now.

0

Share this post


Link to post
Share on other sites

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.

0

Share this post


Link to post
Share on other sites

This I think is the 3rd time recently that they have pushed hard and far into the south. I think the only common factor beyond the campaign settings is the unusual lack of pilots this year on average. Personally I vote for restart but not essential.

1

Share this post


Link to post
Share on other sites
4 hours ago, Brain said:
4 hours ago, Brain said:

I heard of a friendly fire incident involving JSOWs, but no details on what was hit. But if DPRK made it through somewhere it's possible the situation snowballed from there. Osan's A-10s were no longer on the frontline, blue SAMs on the DMZ overrun ...

Looks pretty bad right now.

Intel shows a sudden drop in the number of ground forces at one point and no recovery. That can very well be the consequence of the friendly fire incident. What puzzles me is the number of OPFOR planes, no matter how many are shot down it remains constant. Moreover repairs and resupplies are almost non existent for the blue side and at maximum for the red side. Try have a look at the intel graphics there might be a clue there. ( can't do it myself at this time )

0

Share this post


Link to post
Share on other sites

Intel doesn't give any details I'm afraid. You'd need to look at a lot of autosaves side by side to see what happened exactly.

IIRC somebody wasn't getting AWACS calls last week when I had a few flights, indicating Kadena was down already. This happened before even without friendly fire. You can't win a war without supplies.
DPRK on the other hand still has a lot of mostly untouched war production and has captured even more in South Korea.

If A-10s were inactive (they were not a week ago) then probably nobody took care of the engineers, fixing up all the airfields etc.

BMS simulates economy and the problems you describe are most likely a consequence of that. We may never know what tipped the odds in DPRKs favor exactly.

1

Share this post


Link to post
Share on other sites

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.

 

1

Share this post


Link to post
Share on other sites
14 hours ago, Brain said:

BMS simulates economy and the problems you describe are most likely a consequence of that. We may never know what tipped the odds in DPRKs favor exactly.

It makes perfect sense, I still think there is something that does not add up though.

14 hours ago, Brain said:

Intel doesn't give any details I'm afraid. You'd need to look at a lot of autosaves side by side to see what happened exactly.

Graphics show the situation day by day from the start of the campaign, agreed it is not detailed but a rough idea.

0

Share this post


Link to post
Share on other sites
14 hours ago, Brain said:

You'd need to look at a lot of autosaves side by side to see what happened exactly.

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

1

Share this post


Link to post
Share on other sites
4 hours ago, Kaos said:

Graphics show the situation day by day from the start of the campaign, agreed it is not detailed but a rough idea.

At first glance I couldn't find any massive dip on the Blue side.
I remember Asp was indirectly involved in the destruction of the bridges north of Seoul. This usually funnels all DPRK forces over one bridge to the east, a few nautical behind the DMZ. If CAS went wrong there, nobody would have stopped the Zerg-rush towards Osan and beyond. I noticed an alarming lack of ROK tank battalions last week as well.
I'll just assume that's what happens ... or there was just so little player participation ... but I really don't believe the latter.

4 hours ago, =VG= SemlerPDX said:

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

F-16C Blk.40 or F-16C Blk.52, 2 or 3 ship, loaded with JSOWs, tasked with AI or CAS :D
JSTARS in the last autosave should show when the break through occurred, then it's looking at some other saves from around that time.

Does anybody want to build an analyse tool for that? Basically Mission Commander with a timeline?

Anyways, took off around 0700 local, 2-ship with AI heading out to do some SEAD over Haeju. Flying out of Kunsan, active 36, wingman go stuck on the taxi. I was tabbed out in between (setting up playlist quick), might have caused it. Loadout was 2xAGM88, 4xCBU87 CEM, 2x120, 2xHeat, ECM. Met up with Canteen, took about 4000lbs and had a smooth ingress.
Using only the WPN page, the first Magnum didn't find it's pre-planned target. The second one shot in HAS connected with a FanSong to the north east.
Turned out, Haeju airbase was only defended by a AAA battalion. I made 4 quick mark points to do as much damage before any scramblers could arrive. The first 2 bombs were lofted in CCRP, 3rd bomb in CCIP, 4th bomb didn't come off, probably due to over-G. AD: 0.5s, BA: 1550
Diverted to Seosan for fuel reasons and called it a flight.

2

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now