[GepardenK]

Hi,
I installed FSopen by using Tureys installer and the GOG.com version of freespace 2.
Everything works fine except for 3 irritating problems, hopefully some of you guys know what to do.

1) Ship textures are messed up. A few looks fine, but most of them looks very buggy as you can see:
   

2) Parts of the background (including some stars and most notably the sun) seems inconsistent with the rest of the background. So when I am moving around, the sun will actually "fly" over the  screen faster than the rest of the background, like its changeing position. This seems to happen with subspace nodes and targeting boxes aswell. Unless i point directly at the targeted ship, the targeting box will be posisionet beside the ship instead of on it. Like this:
     

3) Lastly, some objects go invisible if they are near the edge of my screen. This does not happen with larger objects like capships, but smaller things like fighters, asteroids and projectiles just disappear. It’s like the engine don’t bother to render them. Unlike the other problems, this happens only at the higher resolutions.

Here`s my specs. Note that the game runs absolutely fluid on all resolutions:
- Vista 64x
- NVIDIA GeForce 8600M GT
- 4GB RAM
- T8300 Intel core duo
(I am playing on a 16:10 monitor, in case it matters)

thnx

 
   

[Herra Tohtori]

Hi,
I installed FSopen by using Tureys installer and the GOG.com version of freespace 2.
Everything works fine except for 3 irritating problems, hopefully some of you guys know what to do.

1) Ship textures are messed up. A few looks fine, but most of them looks very buggy as you can see:
   

Might be retail textures being used on new models, which doesn't work in most cases due to different UVmapping. Or vice versa...

This might be caused by messed up MediaVP's, or lack of -jpgtga tag which is only a problem with older builds since newer builds include that by default.

What mediaVP's are you using, and what FS2_Open build is in use? (I'm guessing 3.6.8zeta on the part of MediaVP's and 3.6.9 official build on the build part, but assumptions are rarely correct...)

2) Parts of the background (including some stars and most notably the sun) seems inconsistent with the rest of the background. So when I am moving around, the sun will actually "fly" over the  screen faster than the rest of the background, like its changeing position. This seems to happen with subspace nodes and targeting boxes aswell. Unless i point directly at the targeted ship, the targeting box will be posisionet beside the ship instead of on it. Like this:
     

3) Lastly, some objects go invisible if they are near the edge of my screen. This does not happen with larger objects like capships, but smaller things like fighters, asteroids and projectiles just disappear. It’s like the engine don’t bother to render them. Unlike the other problems, this happens only at the higher resolutions.

Here`s my specs. Note that the game runs absolutely fluid on all resolutions:
- Vista 64x
- NVIDIA GeForce 8600M GT
- 4GB RAM
- T8300 Intel core duo
(I am playing on a 16:10 monitor, in case it matters)

thnx

Both issues are caused by widescreen resolutions on older (FSO 3.6.9) builds and are corrected in recent builds.

I suggest you go and grab the latest nightly build from the Nightly Builds forum and give it a spin. If the mapping issues persist, then we know it isn't the lack of -jpgtga causing it ('cause the build I linked to has it activated by default), so then we can start troubleshooting your mediaVP department.

The build should fix both widescreen issues though.

[GepardenK]

Ok, thanks

Yes, I was using the 3.6.9 build. I tried that new nightly build, but It gives me a -jpgtga error when I try to launch the game.

I managed to fix the texture problem (new unofficial driver for my card did it), but the widescreen problems still presist.
Any idea on how to get the nightly build to work?

[Jeff Vader]

Just click Ok. 3.6.10 builds enable jpg/tga textures by default and they do not actually even have the Launcher option for them for that particular reason. That's why the Launcher will rant at you if you've ticked jpg/tga textures on with 3.6.9, then suddenly swithc to a 3.6.10. But clicking OK will remove the flag and allow you to continue.

But strange. The "wandering suns" and the likes should be a thing of the past with 3.6.10 builds. Granted, the HUD and the interface art are of course stretched, but at least the background elements should behave well.

You could, of course, do the following:
- Select a debug build with the Launcher (an FSO .exe with the file name ending in "debug" or "-d").
- Run it until you get to the Main Hall.
- Quit.
- Find a file called fs2_open.log from your \freespace2\data folder and post it here as an attachment.

[Herra Tohtori]

What Lobo said... If you just click OK and make sure you're running the new executable, then the widescreen problems definitely shouldn't be there.

Driver problems are annoying... Just for future purposes - which drivers were you using, and which ones fixed the problem?

[GepardenK]

I was using an older Nvidia 176.60 (64x) driver, now I`ve changed to a edited version of 180.70 made to support my laptop card (by laptopvideo2go.com)

Ok, I have partly fixed the Sun problem by playing under a 4:3 resolution. However, the entire game now feels a bit stretched as I use a 16:10 monitor. I dont mind the HUD, but now we`re talking the ships aswell.
Still can’t get that nightly build to work though. The -jpgtga error is always there, and when I load a mission the game crashes:

Errorlog attached

[attachment deleted by admin]

[General Battuta]

If I'm not terribly mistaken (I haven't had much practice at reading errorlogs), you're running a debug build. Pick a build that ends in -r, not -d.

Actually, maybe I'm just wrong.

[Jeff Vader]

If I'm not terribly mistaken (I haven't had much practice at reading errorlogs), you're running a debug build. Pick a build that ends in -r, not -d.

I told him to, in the hopes that we'd see his fs2_open.log.

Ok, I have partly fixed the Sun problem by playing under a 4:3 resolution. However, the entire game now feels a bit stretched as I use a 16:10 monitor. I dont mind the HUD, but now we`re talking the ships aswell.

That would be because the drivers now stretch the image to fullscreen. There should be some driver options that retain the aspect ratio (resulting in black bars on the sides of the screen). Perhaps you could also try the Recommended build for Windows users linked in my signature.

The -jpgtga error is always there,

Hmm. Try the following: open the Launcher, select the 3.6.9 build, untick the jpg/tga textures under the Features tab, Apply, then reselect a 3.6.10 build.

I was using an older Nvidia 176.60 (64x) driver, now I`ve changed to a edited version of 180.70 made to support my laptop card (by laptopvideo2go.com)

Ok, I have partly fixed the Sun problem by playing under a 4:3 resolution. However, the entire game now feels a bit stretched as I use a 16:10 Errorlog attached

fs2_open.log, please. Not errorlog.

[GepardenK]

Thats right, I was running in debug mode, just to see what happens. But the problem is the same in normal mode...

EDIT:

Cant find a fs2open.log., its just not there

That unchecking of the jpgtga box did it actually. I can run the .10 build just fine now, which means playing in 16:10 resolutions whitout the sun problems, thus fixing the stretched ships aswell. Seems like all my problems are solved, thanks! 

[Jeff Vader]

Well, it should have been in \freespace2\data\ after running a debug build. But if everything works, there is no longer need for it.

[General Battuta]

Random off-topic question: is there any way to disable damage lightning so I can step getting the flickering-white-faces bug?

[pecenipicek]

yes, its known as "Download newest nightly build and download the most recent MediaVP's"



i had that problem with 3.6.8 MVP's without the 710 patch vp's i believe. upgraded to 3.6.10 beta's and didnt see that problem ever again.

[Jeff Vader]

i had that problem with 3.6.8 MVP's without the 710 patch vp's

Ever thought about getting the patches?

[pecenipicek]

i had that problem with 3.6.8 MVP's without the 710 patch vp's

Ever thought about getting the patches?

emphasis on had. one of the 710 patch vp's was to fix that specific issue. the first 3.6.10 came out a week after i got the patch sooo...

[General Battuta]

yes, its known as "Download newest nightly build and download the most recent MediaVP's"



i had that problem with 3.6.8 MVP's without the 710 patch vp's i believe. upgraded to 3.6.10 beta's and didnt see that problem ever again.

I'm using the 3.6.10s and the newest nightly, but I still have the problem.

[Jeff Vader]

Drivers?

[pecenipicek]

might be the geforce M8600 itself too.


i had the striping bands of doom on some of my models with the env from alpha thing earlier..

[General Battuta]

Drivers?

I think they're the newest Catalyst drivers, but I could check.