Sun, Jan 19, 12:25 AM CST

Renderosity Forums / Vue



Welcome to the Vue Forum

Forum Moderators: wheatpenny, TheBryster

Vue F.A.Q (Last Updated: 2024 Dec 30 8:14 pm)



Subject: Vue d'Esprit 4.06 Released


e-on ( ) posted Fri, 12 April 2002 at 5:31 PM · edited Sun, 19 January 2025 at 12:24 AM

Attached Link: http://www.e-onsoftware.com

E-on software is pleased to announce the availability of Vue d'Esprit 4.06. You can [download the update now from our website](http://www.e-onsoftware.com/Download/Vue4Updates.php).

Please note that this update is an incremental update from Vue 4.05 only. We will be releasing a full update (from any version of Vue 4) very soon.

Here is the list of bug fixes and improvements featured in this update:

  • Image mapped bumps not applied correctly on rotated objects in Object Space mode.
  • Bad shadows cast on boolean operations involving polygon meshes.
  • Now possible to animate gels.
  • Restored default system file browsers instead of custom browsers (except under Mac OS X v10.0.x).
  • Bump maps were slightly offset relative to the color maps.
  • Very rare problem when rendering polygon meshes with no thickness.
  • Anti-aliased and Receive shadow material properties not saved/restored properly.
  • Field interlacing options inverted in Advanced Animation Options dialog.
  • Mixing transparent materials with different fade out colors would produce an unexpected fade color.
  • Sunlight auto-decay not saved in standard atmosphere model.
  • Volumetric materials not animated correctly.
  • Incorrect panoramic renders in multi-processor mode.
  • The Animation File Format Options box sometimes appears for the wrong format after changing file format with browser.
  • Spherical and cylindrical mappings were flipped horizontally. Warning: mappings created with Vue 4.05 or earlier will be flipped horizontally in 4.06 (enter -1 X axis Picture scale to compensate).
  • The views tooltip did not appear when OpenGL was enabled.
  • Corrupted alpha channel when rendering to disk with anti-aliasing.
  • Objects with the "Main view only" or "Hidden" properties would still appear in wireframe mode.
  • "Sunlight masked by clouds" not restored after canceling modifications in Atmosphere Editor.
  • Strong noise would appear when rendering some imported meshes with reflective materials.
  • Crash when saving multiple objects or objects with linking/tracking.
  • Problem when using Effects brush before and after changing terrain resolution.
  • Problem when using Undo/Redo brush after changing terrain resolution.
  • Reduced the height of Stones, Pebbles and Fir Trees, and made it independent of terrain resolution.
  • Fixed Grit, Gravel and Stairs Effects brush modes.
  • Memory leak when rendering some boolean operations that involve groups.
  • Very bright highlights would sometimes appear quantized.
  • Now displays a warning when attempting to save a PICT file larger than 4095 pixels.

Mac specific:

  • Crash when using arrows with drop down lists.
  • Problem with Japanese and other "exotic" text inputs.
  • Print preview and print preferences would crash.
  • Terrain exports would crash in file selection.
  • TIFF export crashes.
  • Random deadlocks in Wireframe preview mode.
  • The scene preview did not work when the main view was maximized.
  • View tooltips could appear above modal dialogs.
  • Crash when closing sub-dialogs of the light gel material editor.
  • Render not displayed in main view when using single threaded OpenGL mode.
  • Rendering can now be aborted by clicking in the render.
  • Random crashes due to conflicting threads.
  • Tooltips would appear even when application was collapsed.
  • Dragging a file onto an open scene would crash.
  • Views not refreshed after hiding/restoring application.
  • Now uses standard Mac "File modified, save?" message buttons.
  • Drag-drop operations show a picture of the dragged element.

Windows specific:

  • PICT file format not working when Quicktime not installed.

Kudos to those who participated in the beta testing.

Enjoy!
Steve.


MikeJ ( ) posted Fri, 12 April 2002 at 6:07 PM

Cool, Steve! Just for the sake of saying it, I've been using this 4.06 [the "you know what" ;)] for a couple weeks now, and it does seem to do what it's supposed to do. I have to admit that I never saw some of those problems listed above, but I haven't seen any new ones, either. it is very stable. Vue is running very well under this new patch. Good job, Steve, and thanks. :) BUT, even though I've said this a hindred times before, I want to ask everyone who tries this to FIRST: ... In your main Vue directory folder find the "Back" folder and copy it and then paste it somewhere else on your HD. Running the patch executable will automatically create a new Back folder, but it never hurts to have extra backups. If you have problems with the patch, it's a simple matter of pasting the contents of that Back folder into your main Vue folder, to get back to your previous version before patching. And remember, this is an incremental patch from Vue 4.05. It will not work if you try to patch, say a 4.03 version for example.



Jcleaver ( ) posted Fri, 12 April 2002 at 8:08 PM

I do have a strange question. I also was using this, and now don't know if what I now have is the final release or not. I am assuming so as my splash screen no longer has the big bold red letters saying beta. I can say that Vue has been very stable for me also with this update. Kudos to E-ON!



MikeJ ( ) posted Fri, 12 April 2002 at 8:12 PM

yeah, same here. No "beta" on the splash screen. Seems to be "the real deal".



gebe ( ) posted Sat, 13 April 2002 at 1:47 AM

Great Bravo Steve, to you and all e-on! As you know I didn't have any crash or other problem either. Since the beta 6.2 I'm only working with this version and have not touched Vue 4.05 at all, except for comparison. Vue 4.06-02 ist effectively the most stable of all Vue 4 versions, atleast with Windows 98 I use. Thanks. :-)Guitta


gebe ( ) posted Sat, 13 April 2002 at 1:52 AM

In the past, in installing betas or patches, I had some fruitless experiences and putting back the content of the "back" folder was not satisfying for me. That's why, before installing a new patch, I always copy the entire Vue root content to a save place. This means, that you please also follow Mike's indication to keep a copy of your original Back folder, because some files may have changed in the modules or somewhere else. Have inexpected problems ? Put back the content of your back folder and also the saved root files. I hope you don't need to do this:-) Guitta


SAMS3D ( ) posted Sat, 13 April 2002 at 4:21 AM

Guess I better go get 4.05 first....Sharen


gebe ( ) posted Sat, 13 April 2002 at 4:24 AM

Yes Sharen, You cannot use this incremental update over another Vue version. Only for 4.05. Guitta


Lyne ( ) posted Sat, 13 April 2002 at 12:14 PM

I just can't.... bring myself to update my perfectly working current version.. espeically now that my orange trees will sink below the ground plane... :) There are so many updates it makes my head swim... one of these days if and when there is one that everyone says is fantastic and works great.... I will try it... don't get me wrong, I do love Vue sooo much... Lyne

Life Requires Assembly and we all know how THAT goes!


gebe ( ) posted Sat, 13 April 2002 at 12:47 PM

Lyne, If you have anough space on your HD, you can do what I always do insteed of taking risks. I copy my whole Vue Folder to my HD e:, then update the copy. If it works, fine. If it doesn't, I go back to the old version. Don't forget that you need to have Vue 4.05 to be able to update. If you create a copy, there is another VERY important thing to know. Vue's updates ALWAYS install on the latest Vue used. Also, if you want to update the copy, open it first, do any thing in it, then close it, then update. :-)Guitta


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.