Jump to content

Belaja smert

Members
  • Posts

    38
  • Joined

  • Last visited

Posts posted by Belaja smert

  1. I already posted this to the tech support forum, but hey, maybe this will get more attention here.

    ---

    I went through the old threads concerning TCP/IP -play, but found nothing that was similar to this problem.

    Background:

    - I have played several TCP/IP battles against this opponent before, experiencing no problems.

    - Both have 1.02 CDV version

    - I have 512kbps ADSL, opponent has 525kbps cable modem

    - My machine was acting as server

    - Scenario we played was Pershotraveneve Ridge

    Problem:

    Everything was going smoothly, until we both hit 'go' after turn 13. After that I saw normal video playback but my opponent froze in the 'completing upload' screen for a while and then received 'connection lost' message. We tried again from the autosave, same problem. So we decided to back up a couple of turns, starting again at turn 11. Strangely when we hit turn 14 -> connection lost.

    Has somebody experienced this same problem? Could the scenario be "broken", causing the crash? Amount of data being transferred can't be the problem, since this is a small scenario, we have fought larger ones before.

    I have save games of both the original attempt and the re-run on my hard drive. I'm willing to mail them if someone would like to give it a try.

  2. I went through the old threads concerning TCP/IP -play, but found nothing that was similar to this problem.

    Background:

    - I have played several TCP/IP battles against this opponent before, experiencing no problems.

    - Both have 1.02 CDV version

    - I have 512kbps ADSL, opponent has 525kbps cable modem

    - My machine was acting as server

    - Scenario we played was Pershotraveneve Ridge

    Problem:

    Everything was going smoothly, until we both hit 'go' after turn 13. After that I saw normal video playback but my opponent froze in the 'completing upload' screen for a while and then received 'connection lost' message. We tried again from the autosave, same problem. So we decided to back up a couple of turns, starting again at turn 11. Strangely when we hit turn 14 -> connection lost.

    Has somebody experienced this same problem? Could the scenario be "broken", causing the crash? Amount of data being transferred can't be the problem, since this is a small scenario, we have fought larger ones before.

    I have save games of both the original attempt and the re-run on my hard drive. I'm willing to mail them if someone would like to give it a try.

  3. Originally posted by Battlefront.com:

    The previous post

    Being one that is working 24/7 in software industry, I have to admit I'm with BFC. Nothing is ever *perfect*, when talking about software, that is a contradiction in terms.

    Should there have been more tweaks and updates and 3D-models? Sure, but not if those would mean future delays. The way I see it, CMBB is the most accurate and fun-to-play simulation to date.

    The only wish I have concerning the CM2, is _completely_ moddable units, if only for the public's sake. It should be *relatively* easy to accommodate these changes in the future engíne. I mean moddable graphics, values and specific characteristics.

    BTW Hortlund is using the word "fanboy" in an offensive manner, not one to encourage discussion, not to mention debate. Labeling your opponent is a cheap way to secure "victory" in debate.

  4. Originally posted by Admiral Keth:

    Actually, what I'm intending to do is put a new field in the database called "spoiler". The reviewer can place their spoiler information in this field during the review process. There will be a small link or graphic next to each review which, when clicked, will then display the spoiler. This Scenario Depot feature should be available in the next couple of weeks.

    Excellent! Thank you, Keth.
  5. T-34 was called "Sotka" by finnish soldiers. Sotka is a finnish name for a species of waterfowl. "Sotka" originally meant Goldeneye (in form "sotkas") (Buchephala clangula), however, by end of 19th century it had turned to mean Scaup (Aythya marila), Tufted Duck (Aythya fuligula) or Common Pochard (Aythya ferruginea). T-34's nick "Sotka" originates from a steamboat Sotka. One jaeger, when seeing the T-34 for the first time at June 1941, said that the tank "rolls like Sotka boat".

    T-34 Sotka

×
×
  • Create New...