[diamondgeezer]

OK, so  I'm wondering, just out of curiosity, what kind of proportion of the community can't get FS Open to work? I mean, those that complain do so quite loudly, and that's understandable given that the rest of us are playing highly uber-ised game nowadays. So yeah, there you go, have a vote why not.

[TopAce]

you told you weren't interesting in this.
I voted fish, despite of that, I don't know what do you mean under it.

It quits sometimes, sometimes when I am not playing FS_retail.

[diamondgeezer]

Originally posted by TopAce
you told you weren't interesting in this.

But then you pointed out that the SCP team might find it useful. And I had a few minutes to kill while my pizza cooked.

[Solatar]

Never had any problems running it.

[Lightspeed]

Doesn't work here... But that's no miracle with my compy

[kasperl]

Originally posted by Lightspeed
Doesn't work here... But that's no miracle with my compy

ditto.

i do remember getting something around 3.4 to work.
but then i reformated and forgot to save that exe.  and now, i really hate you guys for having spec maps and stuff.

[Fineus]

It works fine on my machine. For those it doesn't work on - might I suggest they post their specs and at what point it all falls apart for them in this thread?

It might not be to useful right now, but if we're going to hit the widest possible audience with the SCP, we should make sure it works as universally as possible!

[Goober5000]

Version 3.4 is still up there, along with all the others.  See http://fs2source.warpcore.org/exes/.  As for spec maps, they can be disabled with the -nospec command line.

The only serious crash bug I know of is the double-Y press when targeting debris.  Avoid that, and you should be fine.

[RandomTiger]

Anyone who answers no should report a bug in bugzilla if they havent already done so.

http://fs2source.warpcore.org/bugzilla/index.cgi

Its come to my attension there are some people who have problems but dont report them properly, god knows how they expect us to fix them if we dont even know about them.

If you put a bug into bugzilla there will be a perminent record thats easy to find. And its much more likely something will get done about it.

Technically fs2_open should work on any system (except win95) and if it doesnt its likely to be a problem with the code which needs to be fixed.

[Fineus]

Random, if you want to make a short post pointing out the bug reporting process and how it'd help people sort their troubles out - I can stick it up for you

[Sticks]

Just so everyone knows, I don't think my -nospec command line parameter made it into 3.5.5

If someone can validate that for me, that'd be great

[RandomTiger]

Originally posted by Kalfireth
Random, if you want to make a short post pointing out the bug reporting process and how it'd help people sort their troubles out - I can stick it up for you

Dont have time at the moment but thats a very good idea, anything that makes the process easier is good. Will do when I have a spare moment.

[Black Wolf]

Originally posted by Lightspeed
Doesn't work here... But that's no miracle with my compy

Couldn't have said it better myself.

[EDIT]A thought.

How much of FSO, apart from the new sexps and flags, will really break compatability? Would it be possible to release some sort of stripped down FSO version, something that has none of the more complex codes that are likely to be causing the bugs and high system requirements, but maintains things like new sexps, flags and suchlike? Would this be a pain in the arse? If not, I think it could all but solve the compatibility issues with new camps and old comps - you'd have all the functionality of FSO, in a package that, hopefully, would be no more buggy or resource intensive than the original.

Keep in mind though, as a non coder, I could very well be talking out my arse here...

[Goober5000]

Originally posted by Black Wolf
a pain in the arse?

The biggest system-requirement monster is DX8, but we can't un-merge that.

As for general bugs, most of the features (such as specular stuff) can be disabled using command-line flags and such.  Other bugs are due to random programmer errors that would show up in any version.

[Nico]

Originally posted by Kalfireth
It works fine on my machine. For those it doesn't work on - might I suggest they post their specs and at what point it all falls apart for them in this thread?

It might not be to useful right now, but if we're going to hit the widest possible audience with the SCP, we should make sure it works as universally as possible!

It messes from the start with me
From the pilot selection screen, everything is slown down, laggy, and there's an awful static noise. It just stops during the loading between two interface screens, everywhere else ( in-mission included ), it does that thing. Which makes the game completly unplayable .

[Goober5000]

It slows down quite a lot for me in hi-res, but I don't have any problems in low-res.  It's something that began after the DX8 merge.

[RandomTiger]

Until we sort of the rendering system it will be slow on DX8. Essentially we merged DX8 too soon. However if we hadnt merged it when we did it might not have ever happened because the code paths were diverging too much.

Lesser of two evils, we will sort this out, it just takes time because it is very complicated. Rush it and it will just be full of bugs.

[CP5670]

Works fine for me, although as others have said, it has been somewhat slow since the DX8 merge. Still, I have been using this more or less exclusively over version 1.2.

I do sometimes get some strange lag effect with the mouse, however, where the cursor takes much longer than usual to react to the mouse movements. This comes up on game startup once in a while but gets fixed if I play a mission or restart the game.

[RandomTiger]

Is that just DX8 that it happens in?

[CP5670]

I did not notice it in the older DX5 versions anyway, except sometimes in multiplayer with 1.2.