[IPAndrews]

Hmmmm. I don't think it is actually. BHX is is getting ready for a release soon isn't it? In which case I'll need to submit it

Soonish. I would prefer if it worked with the the build shipped with TBP though, and TBP likes to ship with SCP release builds.

[pecenipicek]

all my sound problems have been fixed by taking out the card. maybe the card is fuxxored, so... anyways, all works properly now.

(i'm on the motherboard sound now. AC'97 )

[karajorma]

Hmmm. That errror where all the in-mission text turns into |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| seems to be back. In the debug build at least.

[Wanderer]

Karajorma, just sort of a check... what graphics card do you have? And do you have OpenGL & env mapping in use?

[karajorma]

Radeon 9800. OpenGL and env-mapping turned on.

[pecenipicek]

i got an interesting bug here, it looks like the bounding boxes when targetting from the hud get sorta... well, not around the target anymore. maybe its the fov bug, but i doubt it.

its a bit annoying, and get more noticeable with bigger ships in distance.

[Wanderer]

Ok... that figures. It seems that the problem(s) appears only with that combination (ATI card & OpenGL & env).. Or rather i got it on that setup and few others have gotten it too. The problem (and related other graphical issues) is not limited to this particular build. But it seems to exists with ATI cards on all builds when OpenGL env mapping is used.

[taylor]

i got an interesting bug here, it looks like the bounding boxes when targetting from the hud get sorta... well, not around the target anymore. maybe its the fov bug, but i doubt it.

Got a screenshot?  It just sounds like the old FOV bug based on your description.

Ok... that figures. It seems that the problem(s) appears only with that combination (ATI card & OpenGL & env).. Or rather i got it on that setup and few others have gotten it too. The problem (and related other graphical issues) is not limited to this particular build. But it seems to exists with ATI cards on all builds when OpenGL env mapping is used.

Doesn't surprise me all that much.  I'm trying to come up with as much info as possible to redo the FBO code in a better way.  The real problem right now is that I'm not actually sure that it is the FBO code that is the problem.  It could be envmapping in general.  Unfortunately there is no way to test this in the current code.  I am going to put out a new test build later this week to verify just this issue though.  I'll try and get some FBO changes in there at the same time, but it is pretty much to spec as it is now so I'm not quite sure what to change since you don't really get that many options with it.

[ME$$ENGER]

Ok... that figures. It seems that the problem(s) appears only with that combination (ATI card & OpenGL & env).. Or rather i got it on that setup and few others have gotten it too. The problem (and related other graphical issues) is not limited to this particular build. But it seems to exists with ATI cards on all builds when OpenGL env mapping is used.

Yup, that's the starfield corruption I mentioned in the May 17th CVS build thread (the text corruption being a part of it). Every single person that encountered this problem so far is using the R300/R350 line of graphic cards. $10 on this is an ATI OGL driver issue.

[pecenipicek]

Got a screenshot?  It just sounds like the old FOV bug based on your description.

also, the build crashed whilst trying to take the 4th screenie. i was annoyed. greatly. how to fix it?

[S-99]

I've had that happen for me before. It always happened using a nonstandard resolutions above 1024x768. I noticed the same problem when i was trying to play fs2 on a widescreen tv, yes the game eventually crashed for me too. It should be as simple as going back to a standard fs2 resolution as opposed to nonstandard, and then it should be fine.

[pecenipicek]

it didnt occur with 9th may karajormas build in the same res. 1280x1024

[S-99]

That doesn't seem to matter too much. For me it happened when i was using the 3.6.7 official build during december.

[pecenipicek]

look, it never happened before, not with 3.6.7, not with any other build other than this for me...

[taylor]

look, it never happened before, not with 3.6.7, not with any other build other than this for me...

Are you using -fov?  If you are then that's the reason it's so noticeable.  It's not new though and happens with all resolutions and whether you use -fov or not.  Using -fov only makes the problem worse.  Every version that has used HT&L has done this same thing.

[pecenipicek]

yes, i'm using -fov.

i got it on 0.39. guess thats making it worse, but i never noticed it until now...

were there attempts to fix it, and is it even known what exactly is causing it?

[taylor]

were there attempts to fix it, and is it even known what exactly is causing it?

Yes and yes.  Properly fixing it isn't simple in the current code though, and trying to shoehorn new code in hasn't worked out so well.  The problem is that lines (and the original graphics engine for that matter) use an orthographic projection, where FOV doesn't really affect anything.  The normal models (the basic "space" scene) and all are rendered with perspective projection, where FOV plays a big role.  The problem with the current code is that it's not terribly easy, since it was never an issue until we went HT&L, to project from a 3D perspective view to a 2D ortho view so that we can make everything line up.  I've been working on it but fixing this is a the bottom of the priority list right now.

[S-99]

Hmmm.. ok, like i said. It's one reason i stick with standard resolutions until the nonstandard work better. Among the fov being screwed up other stuff happened like a ctd everytime i played(3.6.7 build technically you can ignore it's problems we're at 3.6.9 now and comes different problems, just saying i had a similar problem once).

[taylor]

Actually, non-standard resolutions are supported now, just like the standard resolutions are, and are no longer considered an experimental feature.  The only thing that doesn't work right is widescreen resolutions.  I only use 1280x960 at this point and don't have any issues, other than the FOV thing, but that affects all resolutions.

[S-99]

That's good to hear actually. I'd kill to play in widescreen and now i can stabily. But wont the fov thing also throw off the targeting  cross hair on what you target?