So, for some reason my computer refuses to load vue files once they reach about around 180mb...has anyone else had this problem, and is there a way around it?  Sometimes I've turned my computer off for the entire night, and then found that it would load, but other times no.  I find this very frustrating, since it forces me to hurry along a picture for fear that it won't load the next time I try.  My computer is brand new, I have a quad processor, 4 gigs of memory, etc...so what's the problem?  Anyone have an idea?

Thanks, 
Frank

You did not mention your system setup.

It sounds as though Vue is not saving the file as it should.  This can occur with large files and frequent changes within the application, which can cause a bad write to file.  Saving the file frequently and doing a Save As once in awhile as a backup is the only current remedy I am aware of.  

You should should certainly contact e-On Tech Support and perhpas send them a sample of the file so they can have a look-see as to what the problem might be.

I'm using windows vista, but that usually hasn't given me any problems.   As for saving often, I usually Save As every time to avoid these problems...the thing is, sometimes this has happened and the file has eventually loaded, but only after I've left the computer off all night.  So, at least in those instances, I don't think it's a bad write to file.

Anyway, thanks for your advice....

Well, it could be that Vista is writing to disk during a Hibernation.  If that occurs that can cause the problem you are describing.  You may want to stop Hibernation and perhpas shutdown Power Management during rendering and other long disk writes when using Vue. 

Hmmm, that sounds promising....I often find that when it goes into hibernation while loading a similar problem occurs....how exactly do I disable hibernation?

From Help and Support

To change power management settings

1. Click to open Power Options.
2. On the Select a power plan page, click Change plan settings under the selected plan.
3. On the Change settings for the plan page, next to Turn off the display and Put the computer to sleep, choose the display and sleep settings that you want to use when your computer is running on battery and when it's plugged in.
4. Click Change advanced power settings.
5. On the Advanced settings tab, expand the category that you want to customize, expand each setting that you want to change, and then choose the value that you want to use when your computer is running on battery and when it's plugged in.

Suppose that you frequently use a mobile PC to give presentations, and you want the display to stay on during the presentations. Consequently, you also want the mobile PC to stay awake while you give your presentations.

 To keep the display on during presentations

• Expand Display, expand Turn off display after, click On battery or Plugged in, and then click the arrow to change the setting to Never. You can also type the word Never in the box.

 To prevent the mobile PC from going to sleep during presentations

• Expand Sleep, expand Sleep after, click On battery or Plugged in, and then click the arrow to change the setting to Never. You can also type the word Never in the box.

1. Click OK, and then click Save changes.

See Also

• What's new in managing power settings
• Choose low and critical power levels for your battery
• Change, create, or delete a power plan (scheme)

Thanks so much for your help, keenart!

I've had a similar problem in V6I in XP (just had one case yesterday). I also do frequent "save as" and sometimes, when it gets big, a file just refuses to open again (it stays loading indefinitely). I contacted e-on support the first time this happened (a few months ago) but they couldn't help. I don't have any solution, so if you find one, I would be very grateful. Thanks!

EDIT: oh, and by the way, I have no hibernation nor standby mode activated, so it's not that, at least not for my case.

Several have been having trouble with materials not saving as selected and files not retaining saved information, and this is probably linked to your problems as well.  Currently I do not have any more information but do know that more than a few dozen on this Forum are having this problem. 

Microsoft has made some security changes to the way 64 bit systems and the file structure behaves so it may well be that these new security measures are not currently compatible with the way Vue saves its current file structure.  Most that have the problem have had 64 bit systems whether Vista or XP.  I guess time will tell as to whether this is going to become a greater issue.

I don't think it's that Keenart - I was having the same issues when I was using x32(XP).  The pic I'm working now has been a nightmare to get together :(.  I'm having to create the terrains separately & save as .vobs in order for them to retain the texture I originally put on them.

The most recent issue is prior to rendering the mat is OK - once I hit the render button the terrain quickly changes to a UV mapped rock imported from Poser and other materials decide to scale back up to 1 from where I had them.

I'm curently on winXP 32bit with 2GB of ram (no recent security patches have been installed) and am now having the "wandering texture" issue where objects sometimes get oddly retextured with some other texture in the scene. Haven't had that one for a long time, but after putting on that 6.5 update it seems to be back. Having a few issues modifying textures when resources are below 40% and Vue crashing when you hit the OK button (which I don't remember occuring anywhere near as often as when I was on one of the pre 6.5 patches - the one before they started playing with the radiosity). Also for some bizarre reason, sometimes things I hadn't selected in the hierarchy editor suddenly become selected after moving things I had selected in the hierarchy, meaning the second time you move what you thought you had selected, you move a whole lot more than just what you thought..... I think.... 

Also the eco systems vanish from the preview window whenever I save the file 0_o (not a serious issue, just odd and something else I hadn't noticed before). And then there's the working window screen flickering to blank all the time (the objects are still there, and the screen comes back if you select something in the hierarchy editor - again ont a major issue, just an annoyance).

Not sure if all of these issues are related to the last couple of scenes (mainly poser imports with largish numbers (maybe 10) of fairly decent sized image textures - not in my gallery here) or a more general problem, but hope it goes away (gets fixed) either way.

Flak - ditto on things becoming randomly selected after moving an item.  In addition, I've noticed if I rotate an item & then go to another item, the item I just rotated snaps back into its pre-rotated place.  This is NOT limited to Poser items - it happens with native .vobs or any other type of object.

I have 8g(XP x64) so memory should NOT be an issue at this point.  That said in watching my task mgr while rendering - Vue is sucking down memory at a rate of 1000.  It drops with every second that passes in increments in the thousand area.

Thanks for the update Debbie, that sure is not good new.  Looks as though we are going to have to send tickets to e-On once again.

Whine on:  I'm tired of sending in tickets, it's old repeating the same ol same ol.

Whine off - :(

These same bugs get cured & then return updates later :(

Yep! You are right, I have noticed that as well.  I certainly hope they get it sorted out it is annoying to find a material I created for a scene dissapear and I did not save the material seperate.  

On a lighter note, I liked the covered bridge you did.  I have been asked to paint so many of those scenes early in my career and now they are dissappearing fast.  We only have a few left in the Tri-state, the States do not want to maintain them anymore.  They sure are beautiful.

Thanks Keenart :)  I love the old countrysides myself - very beautiful and full of charm.  They are very inspirational.

Quote -
These same bugs get cured & then return updates later :(

Undates anyone ? :D

dlk30341  - what you say about that rotation thing might explain why I thought I was loosing my mind a few nights ago - I could've sworn I had rotated this building... and then whenever I looked back, it was back unrotated, so I would rotate it again... and then it was unrotated 5 mins later..... at the time I thought it was sleep deprivation kicking in, but by the sounds of it, may have just been Vue lol (that was the only time that's happened to me though)

Oh well, lots of saving, lots of restarting.

And now for a quote from an IM I received a while back that had me chuckling for quite some time  -> "one good thing about Vue is that after you crash it, it restores and reloads quickly!"

actually it was the last update when all of this started for me, but after I had used it on a few scenes I was working on I could not go back to the old patch.  It would almost be funny if it wasn't such a headache when it happens especially after hours of lost work. 

I did find a way to get several of the files back open again.  I used my Memory Manager, turned it on and watched Vue load, then deleted half the scene and then Saved As, opened Vue again, and did the same for the other half of the Scene and was able to save it, but could not put it back to gether as something was causing it to crash.  But, at least I was able to recover the work I had completed before the file stopped opening.

Typically most 32 bit 3D apps should open if they contain less than 1.99 gigs of info or less than 32,000 x 32,000 pixels, which ever parameter is met first, but in Vue's case this does not seem to be the case.  Or, it is because the Vue app is choking over the info and just not saving correctly, and the larger the file the louder the cough. 

The only time I ever tried to roll back a patch resulted in having to reinstall Vue (can't remember if that was V5i or V6i though).  I was thinking of just calling updates that roll back fixes as undates.

On the memory size stuff,  I've had 1.3GB bryce5 files that have opened up to the full 2GB of ram usage (32bit XP) fine and then happily render - bryce5 doesn't need much ram to render in, though I've never had anything above a 5000x5000 texture come through intact in anything. Vue definitely doesn't like large amounts of image based textures as far as I can tell - my most problematic scenes have that (mainly due to poser imports) as their common feature.