Renderosity Forums / Vue
Welcome to the Vue Forum
Forum Moderators: wheatpenny, TheBryster
Vue F.A.Q (Last Updated: 2024 Dec 13 6:58 am)
Subject: Vue 4 pro - teething problems......
I check e-on's site everyday as part of my daily routine on the internet. I do as you have said since you mentioned this in an earlier post to make bkups before doing an upgrade. I do have the latest update to Vue Pro installed. Thanks for lettings us know that e-on is reading our post with our problems. That makes me feel a little better that maybe something may be done to correct our problem that is causing the slow down in Vue Pro and the hard crashes some of us are getting. :o( I really like all the extras that Vue Pro has to offer but when it doesn't work then it becomes a nightmare and that is when people get agravated and voice their opinion with the software, especially when we feel we are being overlooked with what a few think is our problem and not a problem in the software. :o) This thread should prove it is a software problem and not a USER or hardware problem. Since I now feel we are being taken serioulsy I will back off on my replys and post and hope that we have accomplished something and maybe our problem can be looked into and corrected. I want to thank everyone that did take time to speak up and only wish more would do the same. If we don't let e-on know we will never get the problems solved. Thanks everyone for letting me speak my mind in this thread.
ïÏøçö
No gebe that build I dont have and can not get it becasue it says The update archive is corrupted or truncated. Please download it again. I keep getting a corrupt download so it is hard for me to update when that happens. :o( This is with the full update which shows is 24.1 MB's but I am only downloading 20.6 MB's. I will try the Incremental update to 4.51 but the full update needs looked into and fixed.
ïÏøçö
I just now downloaded the update and was able to get the full download of 24.1 but when installing the update still getting the error "the update archive is corrupted or truncated. " I thought I had hit pay dirt when I saw I was getting the full download. I will wait and eat breakfast with everyone and hope it is ready then. gebe I like salty breakfast also but will have Country Ham with my eggs to get the salt. It is sure hard on blood pressure but OOOOOOOO how good it is. :o)
ïÏøçö
I'm as English as you can get, well short of wearing a horned helmet and going round in a longboat laying waste to Northern Europe, and I have to say it's coffee for me! Oh yeah, and a croissant, followed by a fresh baguette, some very lightly salted butter and goats cheese. I tell you; if the French know anything, it's how to have breakfast!
John
I downloaded the full beta update this morning and it ran perfectly. I was able to open VuePro and mess around a bit and so far so good. Unfortunately, I'm off to work :o( but I plan to put it through it's paces this weekend. Fingers crossed and hoping for the best. -Lin
I installed the update. Was working on a project that so far has a tree with apples (spheres), a fence, a terrain and a directional light. Was moving the position of the light and it crashed. Whole screen went white and it then closed down. I tried to do a print screen while this was going on so I could post an example, but I got an out of memory error message saying it couldn't complete the task. So maybe it goes back to the memory leak thread. Only other programmes I had open at the time were OE and MailWasher. Back to the drawing board, eh ? :-( Gill
Gill
You may have a memory problem. Have you tried to give more virtual memory to the HD where Vue Pro is? You can find it in the System properties-->Advanced--->PERFORMANCES--->PARAMETERS There again click ADVANCED--->MODIFY You should have at least 1536 as an available maximum size for your virtual memory on that HD. On the other side, you have not much ram either (512 is very little). Vue Pro needs lots of memory.
Gill:
Sounds like you're running this on a computer that is a multi-purpose machine. I wouldn't say just Outlook Express and Mailwasher, and I don't know what Mailwasher is but it sounds like it is either a virus scanner or spam filter, which cause more trouble than they are worth.
While I would never suggest you should have to run Vue all by itself on a machine, I would say that you should probably have a dedicated machine for graphics/video apps or your asking for trouble.
Also, what OS are you running?
-Tim
I've run a multi-purpose machine for as long as I've been doing artwork and I've never had any trouble like VuePro with any app that I had, once the dust settled. This includes Poser, Lightwave, Bryce, Photoshop, Painter and others, not to mention Vue 4. The whole point is windows compliancy, not dedicating a machine to it. If it was only supposed to run on it's own machine, that should have been in the product recommendation specs, so people not willing to do so, would know not to pay $300-500 for it.
And I hope the dust will settle on VuePro at some point, and it will be the stable application it can be in the environment it's designed for. They did it in Vue 4, they should be able to do it in VuePro. But with all due respect Timoteo, putting it on a dedicated machine or one is asking for trouble is a notion that should really never be heard in Windows.
Here's hoping...
ShadowWind
Mail Washer is simply a programme I use to check my mail before downloading it in OE so I can delete virus and spam while it's still on the server. I have it running all the time my computer is switched on and it never causes other programmes to crash. I use Win XP I have no trouble running any other 3D app while not only MW and OE are running but often many other programmes too. I've even had THREE Bryce windows open at once, each one rendering a different scene! I have neither the money, space, nor inclination to buy another computer solely for using Vue. Also, Gebe suggested that I may have a resource problem. I do not. I can use any other programme without that problem occurring - it only happens with Vue. Plus I checked in the manual under System Requirements and I quote: "This is why we feel that running it on a 512MB, 1GHz Pentium 4 computer or better is best suited" so the comment of "On the other side, you have not much ram either (512 is very little). Vue Pro needs lots of memory. " is wrong. Anyway, I used to use D'Esprit on my old computer with only a 550 mhz processor and just a MINISCULE 64 MB RAM!!! Sorry if I sound terse but trying to blame users computers instead of the software, or suggestions of buying another computer for sole use is just a little too much now ;-) Gill
Gill
I think Vue needs to do some home work and really explain to its customers what it does need if that be the case anyone who buys Vue should first go and load up with ram. To many things being blamed on something that I don't feel is to be blamed. Notice I said I. Just my opinion. :o) I had 512 MB's Ram when I first got Vue Pro. All I heard was you need more Ram. I now have 1.5 Gig and it still is slow or crash's and to be honest can not tell a bit of difference with the use of Vue Pro. I will not buy more. I have ran a memory check on each strip of Ram to make sure it is not bad, so I know the Ram is good. I haven't had time to try the new upgrade yet so maybe there will be something in it to help me from the crash's. Will see in next couple days. but seems some are still having problems. :o(
ïÏøçö
The only time that Windows should crash due to high memory usage is if it runs out of virtual and physical memory. So Gebe's suggestion of upping the virtual memory page size may alleviate a lot of the high polygon problems some are experiencing, and I have done that in mine. The slow response after a bit of time if you are constantly adding things to the scene could also come from this as well. After all, the more swap space it uses, the slower it's gonna be, because the hard drive is nowhere near as fast as RAM. If it crashes because of high polygons, then that is a completely different error that may be fixed by more physical RAM, but also should be looked at at e-on as well.
I think there is some confusion when I and other say Resources. Resources are not where windows stores the code, 3d model and texture data, etc. Resources are things like requesters, menus, static items that the program uses upon request. For instance, when you call up a menu, that menu is allocated in the resource table. When it is done, it's yanked from the table. The resource table is a locked size area within the windows protected zone. It has protocols as to how to allocate, write and delete resources from that table. No matter how much physical or virtual RAM you have, it still only has a fixed length. This table is used by all the programs in the system that uses interfaces. The reason this table doesn't fill up on it's own generally is that you are only using one application's interface at any given moment. Now, if a program is not deleting and thus freeing memory in that table when it does one of the interface functions, than it is leaking resource memory. When that memory fills up, it leaves no other room for any other program or itself to be able to send menu, requester information to windows. Therefore, you get all that craziness. Now if the table gets overflowed, than it can and will crash Windows. Normally programs protect against that by putting in checks for whether a certain resource can be allocated or not. If it cannot, then it usually throws a message that says, "Out of Memory" error. This does not always mean out of physical/virtual memory (though it can), but it can also mean out of Resource Memory that again is finite and not part of the main memory stack. Therefore, no amount of memory is going to fix the problem if this is indeed the error, as it seems to be based on what has been said.
I have not had a chance to play with Vue Pro since the update, so I don't know if this has been fixed or not, although I am losing hope after Gill's post, but I will let you know what I discover. And I will be the first to applaud E-on for a job well done if they fix this.
ShadowWind
Absolutely correct. Also, I have never seen Vue use all of my physical memory -- not even close ... at least according to TM. Would it still use the page file anyway? If so, is that normal?
I wouldn't think so. I know that when I use After Effects, I can sit there and watch it "chow down" on my gigs of RAM as it renders frames into the RAM preview.
Thanks,
Tim
PS> I have installed the update, and played with Vue for about 15-20 mins (max). So far, no crashes or real slowdowns. 
On machines with more than one physical drive; I've often got an increase in speed, and a decrease in page faults, by moving the swap file to a drive where Windows does't reside. After all you're going to have apps making temp files, browsers caching web stuff and Windows paging memory, all simultaneously on one drive. Also if your secondary drive is newer than your primary, it's likely to have better access times and be in better shape fragmentation wise.
John
Privacy Notice
This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.
iloco, I even don't need to do that, because e-on's people reads regulary (all the time) the posts here. And believe me, I know them since version 1, they never sleep and always are listening to their users. This is how gillbrooks psd problem in the first post could be solved immediately. Understand that it is difficult for them, if not impossible, to look into a specific problem if it is not repeatable. They are always working to give satisfaction to everybody. This is true, these are not just words. Go regulary to e-on's site and see the newest update. First of all, always get the FULL update, not the incremental. I had problems with incremental and will not do it again. Second, before you install an update, create a new folder, call it "mybackup" and copy in this new folder all the files sitting in your Vue Folder. Add to this new folder the following folders: ENVIRONMENT and MODULES. That's what I do every time a new update is available. Especially if they are betas. I only trust to my own backups. If ever the update makes things worse for you, just put back everyting from your saved folder. Just go and have a look there right now to make sure you have really the latest update:-) www.e-onsoftware.com. After that, continue posting here in this same thread. Makes things easier. Thanks!