Re: Some bad news for us all. -Very important news
Masterz, the BSP isn't a problem; Yoyorast still has his source files for the sbsp. What he is missing now is any and all tags pertaining to the mod; any contributions and such. Anything E3P0 did with the map and its assets has been [most likely] irreversibly lost.
Re: Some bad news for us all. -Very important news
well, there are no custom tags... the modifications to the bsp and all that are the main problem.
Re: Some bad news for us all. -Very important news
Quote:
Originally Posted by
StankBacon™
well, there are no custom tags... the modifications to the bsp and all that are the main problem.
No custom tags? You seem to be forgetting the Warthog modifications and the ATV.
I have an idea that MAY solve this issue, only talking to Yoyo about it though (Yoyo, check the Yoyorast forums).
Re: Some bad news for us all. -Very important news
i seriosly cant beleive this. they better get the files back
Re: Some bad news for us all. -Very important news
Quote:
Originally Posted by
p0lar_bear
Masterz, the BSP isn't a problem; Yoyorast still has his source files for the sbsp. What he is missing now is any and all tags pertaining to the mod; any contributions and such. Anything E3P0 did with the map and its assets has been [most likely] irreversibly lost.
I wouldn't say they are missing, they are still there, but in a way that makes them hard to edit. It is possible to get all the tags back in working order, it would just require a lot of time to do it.
Re: Some bad news for us all. -Very important news
Quote:
Originally Posted by
Dr Pepper
i seriosly cant beleive this. they better get the files back
You can help make sure he gets some of the files by donating 500 dollars to him
Re: Some bad news for us all. -Very important news
Well tell me if you want anything making E3pO whilst you work on the BSP.
I am guessing you can get the mongoose back If not I could model you one.
Re: Some bad news for us all. -Very important news
Ehh... I counted about 3-4 things in this thread which are just plain wrong.
Firstly, if your harddrive is surged more likely the motor or the circuit board is fried... all you'd do is put it in a clean room (falling dust is like boulders to harddrive data), replace the motor and circuit board... maybe head assembly to be safe... and read the data off.
Also surge protectors and UPS are generally a special type of powerbar... why didn't you have one of those... especially with the brownout potential (which is BAD for electronics)
Re: Some bad news for us all. -Very important news
Quote:
Originally Posted by
Freelancer
No custom tags? You seem to be forgetting the Warthog modifications and the ATV.
I have an idea that MAY solve this issue, only talking to Yoyo about it though (Yoyo, check the Yoyorast forums).
Thanks Free, I got your PM, but unfortunatly it wont be needed and maybe would not work.. first because I had XP run on my mac pro with boot camp on a partition.. I mean I installed from Leopard.. I guess this complicates the process.. + I had to reinstall several times for diferent reasons.. a real nightmare.
But this afternoon, I really thought everything was solved cause I found a build on my usb key (I totally forgot I had it on it).. it was not the very last but the one before.. I sent it to shadowSpartan.. and he said it was dam protected..
So now our almost last chance to recover these past month work (other than unprotecting the last build) can be Matooba.. I talked to him yesterday and he's got a build apprently diferent from mine and e3po's and like 2 weeks old.. I'm crossing my fingers..
EDIT: I just talked to Mat : he's build is protected like the others :( But he talked to Conure.. he told me that Conure is recoding his depro map unprotector to make it unprotrct using right file names. So he's going to make his map unprotector over just for this situation only..
So I can only hope Conure succeed in his task.. thank you so much man.
Re: Some bad news for us all. -Very important news
Well things are turning around. I hope Conure can make it happen. Well question after this little mishap are you guys still going to be protect internal beta builds?