quote:
btw xprintidle is a linux call that returns the number of seconds the screen has been idle. However it isnt there on all distros. If you make a symlink /usr/bin/xprintidle pointing to /bin/false it will return 0 (not idle) everytime, supressing that call. |
Thx, i will try. But that doesnt explain why was the process spammed so many times, does it? Also i was moving mouse all the time.
+0 / -0
|
Just out of curiosity, has any bench-marking been done so far?
+0 / -0
|
Lots of people playing on the .95 servers now. I cant wait until we get the teams server on this too! Then I can finally play on Linux again!
+0 / -0
|
Too many people on Spring 95 goes wrong. At the beginning everything right but as the game develops and creates many units there comes a point at which it becomes impossible to play. P.S.- CPU ok, Internet ok, video ATI HD 4770.
+0 / -0
|
How do you replicate the too-many-units problem? I played a 4vChickens (Normal) match all the way up the Queen and had no problems.
+0 / -0
|
95.0 halved FPS. Did not report during testing because assuming the system requirements went up again makes more sense. But luckily it turned out performance could be restored by disabling AllowDeferredMapRendering and AllowDeferredModelRendering in springsettings.cfg. Since other people generally noticed graphics speedups, the problem is probably caused by bad hardware setup (Good CPU, very old GFX card in my case).
+1 / -0
|
quote:
But luckily it turned out performance could be restored by disabling AllowDeferredMapRendering and AllowDeferredModelRendering in springsettings.cfg. |
This is good to know. Although it is a bit silly of the engine to have default on this feature that is only used, as far as I know, in one widget in one game (that is deep in development and not even played yet). If the setting is possible to change ingame, it should really, really be default off, and then the widget can turn it on when activated.
+1 / -0
|
I seem to be experiencing some of the "random lag" issue as described by other people, but i can't really pin it on spring's fault yet. The driver stack is horrendous.
+0 / -0
|
|
|
Rolling back to 91.0 pending fixes.
+2 / -0
|
Ah well, this is another 94.1 then. I had hoped that after over half a year of development there would finally be a fast and less buggy engine. I guess not.
+1 / -2
|
Long times between releases = bad, because there are more potential breakages because there is no structured, regular testing.
+0 / -0
|
I think bleeding edge engine testing events should be organized more often(there was some long time ago).
+0 / -0
|
Why is it that zero-k always has problems with new engines? We are now 2 versions and 6 months behind mainline spring. None of the other Spring games seem to have our problems. Is it the Chili interface, or what?
+0 / -0
|
I think they just ignore the bugs. I once saw this game where the feature (trees/rock) on this map create a big invisible wall that block fire (Spring 94.1). They just keep playing.
+0 / -0
|
You also have to remember that those who are crying the loudest are really carrying the propaganda war, for the Soviet Union, because there is no mention made about how awful 91.0 is, with strategic horrible bugs aimed at the cities of all Europe today.
+3 / -0
|
Other games always use newest engine because they don't think they have a choice.
+0 / -0
|
Yanom, at seem BA have our problems.
+0 / -0
|
quote:
@kloot
4) It is hard enough to write code that works with all the major hardware/driver combinations from one vendor, maintaining everything for another is impossible in the current situation. This also goes to the posters directly above and below me: if you aren't volunteering to do such work, you have nothing to say. |
I do have something to say, as I am writing it this very second. So spring is to be Nvidia only? Is that in any way acceptable to anyone? As was said in the previous (locked) thread, Licho, of all people, cant run the engine. Your response to this was "cant be arsed, fix it yourselves because we don't really care". Did you consider that Licho may have been too busy with the server (y'know, the server that hosts your project) to report bugs? Getting spring to work on all graphics cards (that means intel if possible) needs to be the #1 priority rather than implementing new features that nobody asked for and introduced new bugs.
+3 / -0
|
quote:
So spring is to be Nvidia only? |
On Windows (7, 8, 8.1) it did run fine (for me). @Thesponge you run Linux? (would be interesting to see how many players do to see how important fixing those issues is)
+0 / -0
|
