this problem has only popped up very recently but i really cant get rid of it. It updates fine and then runs, but does not remember the update for next time so that the next time i run it it wants to download the entire 111meg update AGAIN! it works ok if i sit through it, but it takes a very long time.

obviously my first thought was simply to reinstall, as before i had the game in /root/.vendetta (i use linux) but also a /home/mike/.vendetta directory, and a /usr/bin/vendetta executable which i run as 'mike' (which i know is VERY sloppy but i didn't realise it had used /root). So, learning from this mistake, when i reinstalled i removed the old directories and files and simply put the whole game in /home/mike/.vendetta, and the executable in /home/mike/bin/vendetta. Yet, exactly the same problem persists. i have write access to the directory of installation, so there should be no problem storing the updates. I could even see the size of the directory increase in size as the updates were DLed, yet it want to get them again next time.

help!!

What do you have in /home/mike/bin/vendetta? If it's a copy of the binary executable, then I'm guessing that's what your problem is; at least for me Vendetta installs & updates the binary executable in ~/.vendetta/, not in ~/bin/.

You don't have Kerio firewall, do you?

FM, I think that was a Windows issue...

dark, type df -h and tell us what it says. :P

yes roguelazer i have an 80gig disk and its not full!!

i liked beolach's idea but unfortunately when I ran /home/mike/.vendetta/vendetta as opposed to /home/mike/bin/vendetta i just got the message:
Fatal Error: Couldn't open window.

regardless of what GUI i execute it in. and obviously the /home/mike/bin/vendetta still does the same thing. what should i do? =( i can't believe reinstalling didn't fix it - ive never seen anything like this before!

I get that same error when I run ~/.vendetta/vendeeta directly; I never use it. I use ~/.vendetta/update.rlb (well, actually a vendetta.sh script that runs update.rlb, and afterwards copies the errors.log & screenies & stuff where I want them).

its really irritating - nothing works! i have reinstalled several times, i even made a copy of the media.rlb file when it had updated it to 98% so that i could copy it back every time and it would just fill in the last 2% but for some odd reason it wiped that file and made a new one!! It randomly gives me segmentation faults when i execute vendetta or update.rlb (even if i remove media.rlb) which causes me to have to reinstall again.

dont get me wrong vendetta is a fantastic game but this really shouldnt happen - it is totally unpredictable!

EDIT -- It would half make sense if updating of the vendetta executable had something to do with this - is there any way problems could continue even through reinstalls and use of the standard directories?

Do you get any specific code with the seg fault?

Does 'mike' own /home/mike/.vendetta?

Can you bzip2 up a core dump and mail it to me (andy@guildsoftware.com)?

no i dont get anything specific, but the segmentation fault problem goes away when i reinstall (leaving me with just the old problem). This whole thing started when i started vendetta windowed in KDE, causing it to crash. Is there a file it may have corrupted whilst doing this (that wouldn't be replaced by reinstalling) or anything like that? Does vendetta look at any files outside of the .vendetta directory and the vendetta /bin executable?

where does it put the 'core dump'? to be honest im not sure what it is - is it the output of vendetta from time of execution to when you quit?

thanks guys i appreciate it =)

No, it only looks inside ~/.vendetta.

To get a core dump, start up an xterm (or whatever), run tcsh if you're not using it as your shell already, type 'limit coredumpsize unlimited', then run ~/bin/vendetta, and see if you can get the updater to crash.

When the game is in a state where the next update will start a new 111MB download, can you do a ls -l ~/.vendetta, md5sum media.rlb, and cat ~/.vendetta/vendetta.lfv and show me what it says?

you will never guess what happened!! i was playing two nights ago and had to hard reset mid-game (i know this is not generally a good idea on an online game) but it has completely solved my problem!! It always succeeds in updating now and the problem has completely disppeared at least for the moment.

thanks for the help tho guys and if anyone has any idea how all this happened i would be quite interested to find out! later people =)