The latest "official" update is 277171 (5.07) and is the only update currently available from eon, they just pulled it a few minutes ago.

Thanks will go and grab it because I can not roll back due to corrupt files from the update that was pulled. So many updates , does anyone know if the 277171 is one before the encryption stuff or does it still have it.

ïÏøçö

My prior files from Vue4 are still locked :( Putting on Moses robe & yelling from the rock "let my files go" LOL

The latest updates that "were" available: 276828 277171 277255 277859 277929 277944 I believe the problems with exporting started with 277929 (possibly 277859?, I never installed that one). In my experience I've never been successful "uninstalling" an update, I simply re-install one of the older ones (provided you saved it) and it reverts back.

The first 5.08 patch, 859, did break a few things. And the next two added to the fun. The next beta -should- be coming to the C3D mod staff, and we will take great pleasure in beating on it for you. As long as it doesn't reformat our C: drives.....

Dale....I'm passing you a HUGE beating stick and I do mean HUGE.....I'm "hoping" by them rolling back as far as they did, they were just trying to get back to where peoples cows were working & terrain buttons back in place.

Lets hope all goes well, & my files(and everyones elses) are released from encryption hell! The sooner the better I might add. It would be nice to know if I need to start restoring & redownloading items, which be seriously irritating :D

You are a gem :)

Message edited on: 08/08/2005 18:28

Just another Note, if you have Vue 5 Infinite set to check for updates it will "attempt" to get 277859, I guess they forgot to pull that one (though it doesn't appear on their site). I went back to 277255 and most of the "weirdness" is gone.

Deb; So I am, so I am.... Sapphire, to be precise (born in Sept, after all... :P ) And that's exactly what they were doing; rolling back to the last known stable build. As Christie said, once things storeside and patch side are ready to go, the download counters will be reset, and any special instructions will be placed in the store forum. sirrick; Unfortunately, that happens. A couple of files I have yet to isolate retain the last installed version number, and that number doesn't reset if you patch to an earlier build. That will keep the rendercows from running, as they will fail in the build number comparison test when they first connect... Trust me, I know... :/

Still see 277859 at e-on's website. This was the buggy one, and the one I installed the other day like everyone else. Now I'm all confused: is there a newer patch? Can't see that 277944, is that what you meant by "pulled" ?That it's not longer available? Sorry, my english is supposed to be quite good, but I'm not so sure now...lol!

Sorry for the confusion, what I meant was that sometime yesterday Eon removed the 277944 patch from their site and replaced it with 277171. Now today they removed 277171 and replaced it with 277859. Currently, the only patch available from Eon is 277859 (but this might change by the time I finish typing this :o). According to Dale's post earlier in this thread "277859" "broke a few things", and the next two (277929 & 277944) made things worse. So, if this is the case (and I have no reason to doubt Dale's comments), the latest "stable" patch would be either 277171 or 277255. Since I don't use Render Cow, I have no personal knowledge whether or not 277859 will cause problems with Render Cow or not (some indicate that it does in another thread). Again, the Patches that "were" made available are: 276828 277171 277255 277859 277929 277944 Though this might be too late for some that are having problems rolling back to an "older" patch, one thing I always do before applying a new patch is to make a backup of my entire "application" folder from within the Vue program, and if problems arise, I simply restore the backup of my application folder. The entire "application" folder is slightly under 50 Mb. Re-installing the "older" patch seems to work for me, but some here have commented that there are possibly certain files that do not get restored when you do a rollback to an older patch. Restoring the back up of the "Application" folder would make certain that "all" application files are rolled back.

ROFL, what did I say about "this might change by the time I finish typing this?"......277859 has now been replaced by 277255 on Eon's site..............

Thanks for clearing it up!