Jump to content


  • Content count

  • Joined

  • Last visited

Everything posted by Kaos

  1. BMS crash reports

    Semler thanks for the reply, will follow your suggestion.
  2. BMS crash reports

    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?
  3. BMS crash reports

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

  5. VG BMS Server Group Ops

    Is this a new campaign?
  6. VG BMS Server Group Ops

    Are Red Forces getting OP again? Been away for a month with work, always miss nice events
  7. BMS crash reports

    Thank you, I was connected but not flying.
  8. BMS crash reports

    Server is acting up, suggest a restart.
  9. Current campaign

    I have been having some issues with the campaign for a few days. The most common problems are duplicate callsigns, even within the same package, which in turn messes up the flight plans (you get some other flight steerpoints). Player fragged flights not appearing in the ATO but the AI still flies them (impossible to cancel or abort). Bullseye relocating in weird positions on the map and squadrons switching back to "set by HQ" mode.
  10. Current campaign

    It makes perfect sense, I still think there is something that does not add up though. Graphics show the situation day by day from the start of the campaign, agreed it is not detailed but a rough idea.
  11. Current campaign

    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 )
  12. Current campaign

    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?
  13. BMS crash reports

    Server down, please reset callsign count as well.
  14. Current campaign

    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.
  15. BMS crash reports

    Server down
  16. Current campaign

  17. Current campaign

    TE works fine, all aircraft taxi and takeoff.
  18. Current campaign

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

    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.
  20. Current campaign

    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.
  21. Current campaign

    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.
  22. 31FW-2.jpg

  23. 31FW-1.jpg