new 98er Develop Version crash

Iam crashed 2 times, cant play.

Infolog

http://pastebin.com/3kCfUYA3

nuu spreng_llll ninja. Also try removing AtiHacks = 1, I'm on ATi and I do fine w/o this option.

[20:19] spreng_llll i think i got rid of microstutters by setting workerthreadcount=0 and workerthreadspintime=0

What this mean spreng

Lastly we done some test with around 28 people. 2 matches desynced but first map was folsom dam deluxe 4. it desynced at 50mins and the second desync was around 30mins on this huge map with around 28 people.

In a normal 10vs10 from what i seen, desync happens much less then on 91 which is great. It may just take much longer to happen doe.

maybe he meant that by accident, this game occured in a row of 98 engine games. Dunno how they switched to 91 for only one game?
http://zero-k.info/Battles/Detail/336371

I don't want to sound insensitive or diminishing the work of the Devs. And I am grateful that the Devs is make this wonderful game. And I appreciated all their hard work and I would understand if due to circumstance that certain problems can not be addressed.


that said. I don't think it's reasonable to expect people to change driver to fit the game. As long as they are running the latest driver, I believe, it's common sense for the game to be changed to run on the latest driver not the other way around.


As I shall repeat, I loved what the Devs have done and grateful for their contribution. But telling people to change their driver when they are running the latest one is just backward. It may work as an stop gap solution but Surely the Devs must already be making changes to the games or engine's codes to accommodate the ATI driver or at least tell the players how to provide better information so the Devs can fix the problem.


I'll thank the Dev again for making and improving the game. But I think we would appreciate it more if the Devs shed more light on what's being done to address this issue. I ,and most players, would do what we can to assist the Devs tackling this problem. But we need more Guidance on what to do to provide the Devs with more useful information.

Xivender,
GoogleFrog meint, dass es an den Grafikkartentreibern liegen könnte. Also zieh da mal neue rauf, wenn dann der Fehler immer noch kommt muss es jemand nach mantis reporten.
Ansonsten kam noch die Idee auf, dass es vielleicht was mit Gras zu tun hat... also das annimierte Gras, nicht das andere... ;)

und setz mal das GrassDetail= X und AtiHacks=0
in der config. Geht aber auch in der ZKL config oderso. Und chili chat bubbles deaktivieren

I have ATI but I'm highly incompetent, I set my grass detail from 7 to 0, I don't like doing things so this better not happen again damn devs how you break your own game without even adding anything

Danke Chesti und GoogleFrog,
Komisch dass es mit dem Grad Probleme geben könnte....Ich habe nichts verändert und das läuft all die Jahre so.

Ich werde nachher mal die Grafikkartentreiber updaten und dann schaun wa ma ob es läuft.

Ich bin im Game drinne gewesen, habe meinen Commander ausgewählt und platziert und nach so 20 , 30 Sekunden ist er dann abgestürzt.

Das Schließt für mich ersteinmal ein Grafikkartentreiber-Problem aus,
aber ich werds versuchen und dann berichten obs hingehaut hat.

Not all ATI's are alike, so it would be good if people who are not perfectly competent also were able to produce useful information. At least, the infologs.

quote: I have ATi, probably competent enough, but.... I have no issues with latest engine. What am I doing wrong?

Maybe it's something that you do right. The prevalence of AtiHacks=1 in infologs of ati people experiencing issues seems to suggest that option is common; it might be actually contraindicated for 98+.

I'll check if it's one of ZKL defaults.

IIRC having ATI != having AtiHacks