Quoting: GuestRuns just fine so far on Mesa (r600g, latest kernel & Mesa, everything on max, vid card radeon 6950). I'll give radeonsi a go later (kaveri system).

Interestingly, though the scores are quite close, Mesa has the edge on fglrx: higher min, higher average, though lower max, fps. I know that's not exactly detailed data (e.g I don't have timings for every frame from the benchmark), but it's encouraging nonetheless.

When you run the benchmark, the game writes interesting stuff into its log file, like best 10% fps, worst 10% or something along these lines...

View this comment - View article - View full comments

Quoting: Guest

Quoting: GuestHave you power governor set to "ondemand"? It's old, well known power management bug on Linux. Set the governor to "performance".

I doubt ondemand can cause pauses of several seconds, and it has been changed/fixed in a relatively recent kernel, too… (was it 3.12 ?)
In any case I’m playing with ondemand and it’s working fine. (I have tweaked a couple settings but in another game I measured the effect and it only changed the FPS very slightly.)

For whatever reason (I can't remember to ever have touched it), it was set to powersave, and ondemand is not even in the list of available governors. I set it to performance, the only other option, and in a short try I did not get the pauses.

But to be honest, I cannot understand that. Even with all 4 cores set to minimal frequency, the game should be able to at least play some sound. And it even happened in the menues!

View this comment - View article - View full comments

I got stops for 1-5 seconds, during the game and even once in a menue.
Anybody else experienced that?

View this comment - View article - View full comments

That's a cool idea, we're going to have a glance at the game, and they can iron out bugs. I'm going to check that out.

View this comment - View article - View full comments

Quoting: turolEveryone please read The Case Against Insensitivity. TL;DR: case insensitive filesystems break very badly when you're not an american speaking english. The only reason windows is case insensitive is because Microsoft is stuck with it because of bad decisions made 30 years ago.

Really worth reading.

View this comment - View article - View full comments

I don't know where I read about it, but I quickly applied.
I was taken in in a later push of many people.
They had 34 games for Linux back then.
Dumping Windows was a ten year old dream of mine at that time.

Now they've got 766 games for Linux.
I deleted my Windows installation in April.
A dream has become true.

Happy birthday.

View this comment - View article - View full comments

Quoting: ImantsHow can case insensitivity create bugs. I am programmer for about 8 years and only case sensitivity was causing bugs for me. Not only in file name but in string compression and in dynamics case sensitive languages like python where you accidentally name one variable in different case and all your program sops working. So I am now just curious how case insensitivity could create bugs?

Neither case sensitivity nor insensitivity should create bugs on their own.
People not caring for rules of their system(s) create bugs.

I like the variable example: IMHO, the programmer has made a mistake, and the systems shows him that he did. He created a bug by not adhering to his system's rules. It is very easy to avoid and very easy to fix.

Of course, the file case sensitivity is a bit more complicated: People do adhere to their system's (Windows' ) rules, make the casing up out of thin air for whatever reason, and such create bugs when the stuff is ported to other systems. A thing that comes very natural - writing a string the same in two places (code and file system) - is not done, creating bugs. Non-portable code is less good code. Writing the same file name twice in different casings(*) is sub-optimal.

(*) Is "casing" the correct word?

View this comment - View article - View full comments

Quoting: Guest

Quoting: Eike…

So you’re advocating making things more difficult "just because". "People should do this", "Programmers should do that"… Yeah right. And then there’s reality.

Nope.

Calculating file names such that the casing can be done wrong is - obviously - more difficult than just comparing two strings. I don't know if you're programmer, but comparing strings straight is the most natural thing to do.

And I'm yet to read about the problems an end user would have with a file system (opposed to file open dialogs) that work this quite natural way.

Sorry, neither "Yeah right" nor "And then there’s reality" seem like arguments to me, while I have given some of them.

BTW, would you please cite where I've told people (not programmers) what they should do? Unfortunately, I cannot remember having written such things... I do remember having written about what end-users really need and what they don't need. Unfortunately, you didn't answer any of that...

View this comment - View article - View full comments

Quoting: HeimdallSeriously, some Linux "features" make it stupidly difficult to work with. It seems to be on purpose, much like the Gnome developers who "know" better than everyone else.

NO normal user needs case sensitivity in their filesystem, and in most situations, it is a hindrance for adoption and porting on Linux due to the additional headaches introduced by it. For example, anyone who runs programs from WINE could see how annoying this can be.

It should be optional, like in HFS filesystems.

Seriously: The problem stems from a real unnecessary "feature" of Windows that people unfortunately got used to.

The end user probably does not care at all for the case sensitivity of files. As long as he can load what he saved, which is up to the file open dialogs (those should select files case insensitive, at least as long as there's no case sensitive match), he's fine with case sensitivity as he's with case insensitivity.

Programers got obviously used to type file names in code according to the position of the moon, their fingers or whatever, instead of according to what the file is named. Which is quite odd, as every good programmer should be trained to do things not hush-hush, but right.

Yes, this all results in a porting problems - until programmers learnt to do this right as well. But no, this is neither hard to do nor a problem of Linux.

BTW, I'm not one of those who think that Linux is perfect in every aspect. But in file casing, Linux IMHO did a quite reasonable thing, and programmers should do the same. Which is, as already stated, even easier for them: They don't need to typ the file name twice in different casings, they can just copy and paste the name from one place to the other, which will automaticyll result in matching casing. It's that easy.

View this comment - View article - View full comments

Quoting: n30p1r4t3I love gamingonlinux
[...]

I love Aspyr
[...]

And yes I realize this is late :)

It's never too late for love. ;o)

View this comment - View article - View full comments