Textures do not show on SVN

[w03]

I am running SVN on windows Vista, and textures do not show correctly on almost all vessels and a few planets. This results in everything looing pitch black. (However, the ox and certain planets show their textures correctly)

Example is below.

[klauss]

Um... I've been fiddling with the config file, and my config has a few technique changes that I tried to leave out of the commit.

Maybe I messed up in one commit?

Lemme check...

EDIT: nope... doesn't seem to be the case.

Can you go back a few revisions and find which one broke it?

[w03]

I actually have two copies of SVN, and both have the problem. One I just checked out a few days ago, and the other I checked out around 5/10/10. My oldest SVN copy showed the problem after 2 or 3 revisions (all on the same or next day).

[klauss]

Please, I don't experience the bug, I'll need you to svn up your oldest SVN checkout to a revision that doesn't show the bug. To the newest revision that doesn't.

Ie, if you do svn info:

Code: Select all

claudiofreire@klauss:~/src/vegastrike/trunk/vegastrike$ svn info
Path: .
URL: https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/vegastrike
Repository Root: https://vegastrike.svn.sourceforge.net/svnroot/vegastrike
Repository UUID: 9476613a-4e0a-0410-bcee-947800e9c4d1
Revision: 12834
Node Kind: directory
Schedule: normal
Last Changed Author: klaussfreire
Last Changed Rev: 12834
Last Changed Date: 2010-08-04 21:37:36 -0300 (Wed, 04 Aug 2010)

My repo is @12834, so I'd "svn log | less" to find the previous revision number (not necessarily 12833 btw) - which in this case IS 12833, so "svn up -r12833", make, test. And so on and so on.

A bit of a pain, I know. But it's the way to find the bug.

You can look at the log and discard revisions that don't seem to be relevant, like 12833, which says "Better, less twitchy seeking of video streams" - that hardly has anything to do with the llama, so you could skip testing it at first, to go about faster.

[energyman76b]

I have posted the same bug back in May - and even then it was several month old... 'going back' is going to be very time consuming. I am away for work >12h a day - so not in the near future.

[klauss]

Actually, I recently found (and I think corrected) the bug.

Does it still happen aftern an SVN up, rebuild and reconfigure with vssetup?

[w03]

Sorry for the really late response... I'm so busy with high school.

I tried SVN up + reconfigure, but now I have a runtime error...

Thanks!

[klauss]

Did you run vssetup and reconfigured VS
The latest SVN needs to rebuild your vegastrike.config in /home/USER/.vegastrike

[w03]

Yes, I reconfigured vssetup, but I'm not sure if I did everything correctly. How do I rebuild SVN.

[klauss]

What error do you get if you run vs with --debug

[w03]

Ehhh... how do I run with debug? I read the wiki entry but I still don't get it.

[klauss]

$ ./vegastrike --debug >output.txt 2>&1

[nihilbilly]

im having the same problem. happens on both windows and linux.

my card is a radeon hd 2600 pro.

here is my debug output.

[klauss]

Weird, that bug was fixed some time ago.

But I do see that your drivers are failing to compile the highend shader, which might be an issue. I'll have to take a better look there.

[Rattan]

I just finished testing with a Llama after updating to rev 12922. I can see the ship. My card is an Nvidia GeForce 9500 GT. So, either the bug is fixed or it's specific to the Radeon drivers I'd guess. Hopefully that may help with figuring it out.

[energyman76b]

Hi,

I updated on 24th October, run vssetup and the bug is gone - for me.