Informatika és tudomány

  • axenet
    #42303
    Megvan a bibi. Folyamatosan összeomlik a szerver mint a zacskós tej, U4 problémára gyanakodnak :


    It would not be Falcon, if thigs would always run rock stable forever .....

    As many of you gents many have already noticed, we have encountered very strange and undefine-able crashes on the Redflag 3.0 server.

    But the problem we have is, that we are not certain, if the crashes are caused by the new campaign (3.0) or by Update 4 or by hacking attacks (which is farfetched though) ....

    Whereas redflag 2.3 ran for over 2 weeks rock-stable without any crashes, now things wend south.
    Every change introduced with 3.0 and different from 2.3 has been terminated as cause, as i ran same under 2.3 conditions.
    Unfortunatly there are no sound indications of errors to find as cause of the crashes at the moment, so we are forced to proceed more
    analystic and efficient.
    Meaning, that we are currently running the server on Battle for Sinai 2.1 in order to see if at least there we will see tha same problems.
    If we will, then most likely the problems are cause by Update 4.
    Usually an official update like Update 4 would not in conflicht with the campaigns we release, as those use their own filestructure independent from
    .exe updates.

    The next step would be to run the server with Redflag 3.0 under Update 3, but for now - as you all have Update 4 installed, we run BFS 2.1 to exclude or determine Update 4 as cause for our problems..


    I appologize from all pilots participating, but in the same time i ask for everyones help to participate on the BFS 2.1 server in numbers, as we need
    to "stress" the server as best as possible in order to get sound results.

    Meanwhile, in the same time, works is being done parallel in order to find the reasons.
    It is pitty imo, as RF 3.0 was my best work on a global perspective compared with anything i have done before.