I have been having numerous application lock-ups and having to reinstall Vue from my the original CD and then install the 4.12 Full Update. Unfortunately there is no one area where the problem exists. It's happening often and using virtualy every part of the application. I have tried it on numerous systems with the same results. e-on tells me they cannot repeat the error on their systems.

The most consistant problem is using the material editor and opening the function editor. After a few steps it locks up. and sometimes I have to reinstall the App.

Is anyone else having this problem?

On what platform you running your Vue? What do you mean by "lock-ups" ... comp freezes up? But freezing up wouldn't cause you reinstalling the software! What sort of computer you trying it on? (system info's). If it can be solved through Vue, I'm pretty sure someone from this forum will have an answer. But, if this problem is caused by something else, above info's will be helpful to point out the problem.

Judging by the title of the post, I presume Ace_Face is on Mac OS X, nish ;o) Cheets

Well, i am on Mac too - but i don't have this problem. Maybe because i am still on 10.1.5 and not under 10.2.x This will change soon, i plan to switch next week, to get a complete new class of problems :-)) Have you switched OpenGL on or off? It should be off (even when i don't have a problem with OpenGL on)! Maybe you give us a little more information (memory, disc space etc). Would be helpful.

As I stated in my title my platform is Mac OS X. I'm running 10.2.5 it doesn't matter what computer system because I've tried it on a G4 Cube 450 MHz processor, a G4 Dual 867 MHz processor tower, and a G4 Dual 1.25 GHz processor tower with the same results. I'm using Vue 4.12 with Mover 4. I've tried it with and without Open GL, and I get the same results.

Many times the applictation will freeze and I have to "Force Quit" (Vue is in red). and some times I relaunch Vue and the default screen doesn't show up and when I try to open a scene through the menu the dialoge box is blank and all the standard scene previews are missing and my personal scenes are missing. In addition many of the interface features don't work, so I end up reinstalling from the CD and following up with the full update.

Granted I am creating some very large scenes, but I expect Vue should handle it. At least e-on says it should in the manual.

Try looking at this thread for an example of my most persistant problem.

http://www.e-onsoftware.com/Support/ShowMessage.php?id=1051031530&stage=-1&chooseCategoryPage=&categoryName=&category=&subCategory=&superCategory=

Ok. The e-on thread does not really say much. Sometimes i have problems when i click too fast. Then Vue does go in an endless loop and i have to shut it down. That is not your problem. Fatal errors i only get when i am using imported objects with a lot of facets. Trees or splashes for example which have more than 500,000 facets. Then i "receive" indeed a lot of crashes or fatal errors. You can check it with your file sizes. My maximum scene was around 600 MB big, but had only around 10 Mio polygons. As i said, imported 3DS-trees let Vue memory quickly "explode". Before Vue 4.12 the limit even was around 200 MB so we are a big step further. Let us know. I am nearly sure that something like this is the problem.

Okay, this is easy to fix, but I'm not at my computer right now so I may not remember what all is involved... But try this: When you have one of these lock ups, which tend to happen with high polygon counts, here is what I've found to be the problem. A corrupt vue.env file. Here's where you clued me in... When you restart after a crash your default screen is missing and you are forced to load or new from the menu... only the atmosphere's and personal scenes are all missing. This happens AFTER a crash, or perhaps an aborted render. vue.env is a HEAVILY written to file. If something goes wrong while writting to it, Vue fails. Once corrupt, Vue will no longer work. Look at it this way... the vue.env file is sort of like the preference files under Mac OS 7.x-9.x, and by replacing it your get a fresh new Vue without the reinstall. I believe this is a Jag issue, as I didn't have this problem at all under 10.1. To repair, after a crash simply pull vue.env off the original CD and replace the corrupt one in your Application folder. I took a clean copy of vue.env and put it on my hard drive. I then copy a fresh vue.env into the Vue folder (I can't remember exactly WHERE in the vue folder it is) any time I start a new project. I haven't had a crash since.

wabe,

the large files I'm having trouble with are around 1.5 to 2.7 million polygons. However this doesn't explain how with only one object (a sphere) opening the material editor, then opening the function editor and the third operation vue crashes. the poly count in a file with a ground plane and a sphere is quite low. I will conceed that the larger files are more unstable, but isn't that unacceptable for non beta software? Have any of you reported these issues to e-on for correction? If not I think we OS Xers need to do so in order to clean up the bugginess.

BTW I have also noticed a bug with the hypervue dialogue. You can't see more than 14 computer IP's added and there is no way to resize or scroll the dialogue.

runwolf,

I will try replacing my vue.env file to see if that works. Let me run through that so I understand. I rreplace the vue.env with a fresh "original vue.env" file each time I create a new scene? Can I do that before I try to launch on of my existing scenes to correct the issue?

Thanks to all for your help.
Tom

Tom, You should be in contact with technical support about this. I suspect that since its happening on so many machines that there is some other common element like a modified setting or an installed, conflicting app that's causing this problem and maybe interrupting some processes in a way that Vue doesnt like. I normally have Vue 4 running on Win XP Pro, but I have an old G3 running Mac OS X 10.1 and havent had any problems (other than the G3 being rather pokey...). Best regards, Lynn Fredricks e-on software

Tom, i think big polygon objects are the problem. That takes so much internal memory that the whole application becomes very instable. It then crashes even on operations which have nothing to do with the trouble causing object. Mostly my crashes come when i am saving files. But i only had to reinstall the application 1 times. Lynn. Problem is, that if you don't use objects like that, you will not run into that problem. On the other hand they are so big that they can't be sent via e-mail. If you want me to, i can record some of my biggies to a cd and send that to you, so that you can test it. The question wether an application can have bugs or not is a very theoretical one. Software like that is so complex that it simply is not possible to test all cases. And don't forget, in 90% of my uses it works well. Don't forget that even every operating system - which has a lot more central position - does have bugs and you have to live with that. Finally. Vue on Mac is in fact a version 1 - it's a brand new portation to this operating system. So we all should help e-on to make this successful. In our own interest.

Lynn,

I have posted some of my problems on the e-on support website and had discussions via that medium with Steve Bell. However, they ususually end up without actually resolving the issues and e-on is unable to repeat the error. I think wabe is right that we are working on much larger and complex scenes which must be pushing Vue to it's limits.

BTW I hope e-on is testing on more current systems and versions of the OS X (ie. 10.2x) a G3 Beige running 10.1 is not the same animal.

Wabe,

I understand and agree that Vue is new to the Mac and I am trying to give feedback to e-on in order to make the app better. My frustration is that I am now having to look at other software to get my work done, and I don't want to use another app. I like Vue because, in my opinion, it's the best to make great scenes for architecture. Vue's abilities are incredible and network rendering for animations makes it even more powerful. Quite frankly, I don't know why e-on isn't charging more for their product.

With that said... I really wanted to see if others were having the same problems and get a discussion going to solve the issues. The more feedback we give to e-on the better the product and (I think), the better e-on will be able to do their part.

Thanks again to all, more suggestions are welcome.

Tom

Yeah, it was a no brainer to ask about the Platform. But, since I have not much clue about Mac, I didn't realize the title. That means I can't help you here. However, I very much agree with runwolf; the type of problems you are facing ... sounds to me, the problem is caused by run time environment.

Tom, i agree with you that a discussion is good and helps all of us to make Vue better. It would be a big help if you can give a little more information about the scene(s) you have trouble with. Otherwise for me it is like operating with long sticks in heavy fog. Maybe you make a screenshot and/or a rough render so we can see something. From time to time, when i definetly want to finish a scene and Mac Vue is not able to, i switch to a windows machine in the office. Maybe that is a possibility for you too (of course not our machine in our office :-)) ). Before spending money for new software perhaps it makes sense to spend money into a windows machine as an add-on. That offers you as well some "windows" to software that is not available on a Mac too. I found that there is no danger to switch completely to Microsoft, but sometimes it helps.

Yea, changing Vue.env solves my problems every time so far. (Goes and finds a tree to bang on.) I'm probably over-reacting, but it works. And I've PARTICULARLY noticed that problems happen MOST OFTEN in the material editor when you get three or more screens deep. (Such as opening the ME, opening Bumps, opening something else.) The material editor seems the most crash prone aspect of Vue on Mac, but anytime vue crashes, for whatever reason, I always replace vue.env. Michael

Not to worry, my example of using Vue 4 on a G3 is not indicative of our testing -- Im in sales, not an engineer -- I dont get one of the shiny new muscle Macs. If its just a matter of high polygon count and not specific issues of specific types of imports, then it should be easy enough to test. We have volumes of models to experiment with internally. Ill discuss with the engineers. Best regards, Lynn Fredricks e-on software

If I may add my two cents worth in here. I had upgraded to OS 10.2.5 from 10.2.3 and had numerous problems that nobody seemed able to reproduce, including the Beta testers over at Apple. It wasn't just with Vue but also with Bryce, Lightwave, safari, and my email. The solution was for me to reformat my system and go back to 10.2.3. I'm sorry for your problems, but I am certainly glad to hear that I'm not the only one who was having them.

Has anyone tried the new 10.2.6 upgrade?

I'm going to try this week and post my results.

I have a deadline on Tuesday. Hope it works : |