Kaos

Semler thanks for the reply, will follow your suggestion.

21 minutes ago, CobaltUK said:

I doubt it is server related. Its a rare event  (for me maybe 1 or 2 times a year and always after my pc has been on for a LONG time)  and looks like maybe a memory leak taking consumed memory close to the max 4gb available to 32bit bms. Just a guess though.

I have had this message for a while, as it happens only on the VG BMS server I thought it had something to do with this server. Maybe a setting on my side?

I get this message and then BMS crashes, is it my system? (does not happen on other servers)

Nice!

Just now, =VG= SemlerPDX said:

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

Thank you, I was connected but not flying.

Server is acting up, suggest a restart.

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.

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 )

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?

Server down, please reset callsign count as well.

I have been playing regularly for the past week and would like to point out a few things:

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.

Red air seems to have an unlimited number of planes, re supplies and repairs are extremely quick for red forces. (for example: destroyed airbases are back to 100% in half a day)

I am unsure that this campaign can be won even with constant human controlled flights and surely look like it has been designed with that concept in mind.

This is not a complaint just an observation.

Server down

Payback!

TE works fine, all aircraft taxi and takeoff.

I will try a TE offline and see what happens. I will post the results.

Just did a flight out of Kwangju airbase, two flight package with all AI controlled aircraft. No issues, all aircraft taxied and took off as expected.

3 hours ago, Brain said:

Where did you last see him? Did he make it to the runway and hold short?
Last patch there was a bug with wingmen stopping on the taxi way for no good reason.

I did a few flights out of Kunsan, the wingman stops on the parallel taxiway and never reaches the holding point. This happens for runway 36, not sure if the problem is there when runway 18 is in use and could be a problem for Kunsan only as I have never seen this happen at other airbases. All planes are there when joining the flight airborne; my guess is a broken or missing taxi path to runway 36.

I planned a package with 2 flights in it, I was the only human player, and all AI controlled planes never got airborne. All stopped on the taxiway. There were some

AI generated flights as well on the taxiway not moving. This happened this afternoon.

Also noticed callsigns+9 for all flights. I read up on it and the solution is to reset the callsign count using Mission Commander.

14 hours ago, CobaltUK said:

Situation critical. 

 

Looks bad! 

Haven't played much this month, my job kept me away from home for a while; the few times I played the weather was just fine, no problems and perfectly playable.

I thought about trying the new 3D models and the new skins but did not do it knowing the compatibility problems it would cause. Either way it is fine with me.

Cheers

15 minutes ago, =VG= SemlerPDX said:

Restarted to last autosave

Thank you

Server down

4 hours ago, Brain said:

Did any of you ever play R-Type on Gameboy? It only has 6 levels but the difficulty increases significantly. Once you learn how to use the Force (that probe thing on front of your ship, not a Jedi reference) it's all about tackling different situations the right way. Eventually you'll reach level 4 which has you flying through tights corridors while near indestructible things fly at you. YT link for those interested.

Played the arcade version, I believe it was called Last Resort. Cool game

Server down, set RESCAP (allow me the joke )

On my last flight a few days ago I was flying with CobaltUK and both had issues with the game. My flight plan had a few extra steerpoints in it that were not supposed to be there, his flight plan was different than what was planned and resembled the flight plan generated by the AI when you first add a package. The coordinate system in his case was totally off as he was getting wrong distances from the steerpoints. On my screen a memory usage warning message appeared a few times ( BMS using 98% of allocated memory, have never seen that before. I restart the game after each flight to prevent memory leak so I doubt it was a problem on my side) 

Problem with the process running on the server(memory leak or memory hogging sort of thing)? Corrupted save file?