Mon, Dec 23, 5:30 PM CST

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: About Vue Infinite9...???


greatlights ( ) posted Thu, 10 February 2011 at 9:58 AM · edited Mon, 23 December 2024 at 5:26 PM

When I was training  with Vue infinite8 it was not feeling lost.I've updated to Vue Infinite9 but when even loading a terrain 256x256, the terrain is huge, I really wonder why?

Must I resize the terrain every time?

Thank you for your technical help


Rich_Potter ( ) posted Thu, 10 February 2011 at 10:04 AM

Vue 9 uses real world measurements, so the terrains come in bigger than in previous versions of vue, gives more realism with accurate distances i believe.

Rich

http://blog.richard-potter.co.uk


bruno021 ( ) posted Thu, 10 February 2011 at 10:47 AM

Nothing has changed, check the terrain size in the numerics tab of the object manager. Still 25x25 meters, or 256x256 meters depending on your internal units.



greatlights ( ) posted Thu, 10 February 2011 at 11:23 AM · edited Thu, 10 February 2011 at 11:24 AM

Quote - Nothing has changed, check the terrain size in the numerics tab of the object manager. Still 25x25 meters, or 256x256 meters depending on your internal units.

But loading an ecosystem is a problem 'cause I must be  in dynamic population: it takes too much time for a preview 😕


bruno021 ( ) posted Thu, 10 February 2011 at 12:19 PM

Is the ecosystem scale the same than in Vue8? maybe this parameter has been changed...



greatlights ( ) posted Thu, 10 February 2011 at 2:59 PM

Isn't there any one who's working with Vue Infinite9 who could help me?


bruno021 ( ) posted Thu, 10 February 2011 at 3:21 PM

Did you check ecosystem sizes in Vue8  and 9? Are they the same?



greatlights ( ) posted Thu, 10 February 2011 at 4:45 PM · edited Thu, 10 February 2011 at 4:46 PM

Quote - Did you check ecosystem sizes in Vue8  and 9? Are they the same?

1/ When I load a simple 256x256, I get a huge terrain so I have to use dynamic population 😕 So a preview can take even 1 hour or more!

2/ I have the same basic atmo but ... 😄

3/Not the same settings between Vue8 and Vue9 for a same ecosystem 😕


bruno021 ( ) posted Thu, 10 February 2011 at 5:18 PM

Well, didn't answer the question. If the ecosystem size is smaller = more instances, which can lead to your problems.



greatlights ( ) posted Thu, 10 February 2011 at 6:14 PM

Quote - Well, didn't answer the question. If the ecosystem size is smaller = more instances, which can lead to your problems.

The vegetation seems to be more far with Vue9 😕


ShawnDriscoll ( ) posted Thu, 10 February 2011 at 6:38 PM

Just reduce the density of your ecosystem and then adjust the scale of your plants.  Vue 9 and Vue 8 are different animals.  Save your own ecosystems for Vue 9 once you have them adjusted to your liking.

www.youtube.com/user/ShawnDriscollCG


lior ( ) posted Fri, 11 February 2011 at 9:29 AM

Well, so far, I have to say that the jury is out regarding the latest version of Vue.  

  • Conflicts using older materials, both terrain and plants.  For instance, bring a tree created in Vue 7 or 8 into 9 and the scale is minute.  Leaves on the ground look more like leaf dust!  Tree barks look tiny and repetitive. 
  • Not only is scaling an option.   A bump value set to 0.200 in 8 is loaded at 0.900 in 9.  Too high a bump value makes textures look awful.
  • Ecosystem distribution is wrong.
  • Also on the subject of materials – they all have a gamma correction of 2.2 making them unnaturally dark.  This can be overridden of course, either for each and every texture in the materials lab or in Post Render Options but not everyone will be aware of this.  It looks bad on content creators such as myself as customers want to just buy and load a material and not have to fiddle around with it to get it looking right!
  • Memory issues….again.  No change there then!   Seriously, a single terrain loaded with an ecosystem material and my resources dropped below 25%
  • The option to right click on the Select Render Area icon doesn’t work (how did they break THAT???)

One must assume the scaling issues must be linked to the fact that they’ve changed Vue’s internal unit size from 0.1 to 1.0 but that doesn’t explain the bump problem

I’m sure I’ll be adding to this as I use it more…….

UPDATE: Seems the problem causing memory usage  has been found and will be fixed in the next update

UPDATE Nov 13th:  ATMOSPHERES

Something else that seems to be incompatible with anything made in Vue 8 or older…..
EXAMPLE: Pic below is my ‘End Of Day’ from my Real Skies pack rendered in Vue 8 and looking how it was intended

Below, I made an almost identical scene in Vue 9, loaded the atmosphere and rendered.  This is NOT how it was intended to look !

November 18th – surely this can’t be right ??

One terrain with simple ecosystem loaded into scene (dynamically populated)

Gill Brooks


ShawnDriscoll ( ) posted Fri, 11 February 2011 at 5:49 PM

On my 32-bit system, I just paint the eco only where it needs to be in the camera frame.  No Out Of Memory errors.  For an entire island jungle shot, I would need a 64-bit system with 8GB RAM or more obviously.

www.youtube.com/user/ShawnDriscollCG


gillbrooks ( ) posted Fri, 11 February 2011 at 6:14 PM

The terrain size has increased x10. In previous versions it was 28x28 yds - now it is 280x280yds.   

In reality, the only time you would leave the terrain size at 28yds would be for a detailed foreground area - so it does save having to size up the terrains for you background work.

If you really WANT your terrains to load in at the smaller size my suggestion would be to load a terrain, size it down to what you prefer and save it as a .VOB.  You can then load it into your scene but you would need to go into the terrain editor and reset then create a new seed otherwise all your terrains will be identical.  In my opinion, it is much easier to resize a terrain.

Material scale is hit and miss due to the resizing of the internal unit from 0.1m to 1.0m.  If using a material created in and older version you will probably need to scale it to fit - don't rely in Vue doing it automatically - especially on bitmap based materials.

It has always been a better option to use dynamic population on large scale terrains and vue 9 now handles it much better than previous versions. You may need to tweak the scale and density but that has always been the case.

As a vague, general guide, if you want to reproduce similar to older versions you need to SCALE UP by 10.  An example ecosystem 'Forests and Green Fields' - in vue 8.4 the scale is set to 0.228 and it vue 9 it is 0.024 - approx. 1 tenth of the scale.

The opposite of that rule applies to atmospheres.  The problem regarding atmospheres not appearing correctly can be resolved by dividing the aerial perspective by 10.  In the case of the example above, it was originally set to 10 so bring it down to 1 and it will appear as it should.

When Vue 9 first came out I saw posts suggesting resetting the internal unit back to 0.1 but this has little or no effect.

 

Gill

       


lior ( ) posted Sat, 12 February 2011 at 10:26 PM

Quote - Well, so far, I have to say that the jury is out regarding the latest version of Vue.  

  • Conflicts using older materials, both terrain and plants.  For instance, bring a tree created in Vue 7 or 8 into 9 and the scale is minute.  Leaves on the ground look more like leaf dust!  Tree barks look tiny and repetitive. 
  • Not only is scaling an option.   A bump value set to 0.200 in 8 is loaded at 0.900 in 9.  Too high a bump value makes textures look awful.
  • Ecosystem distribution is wrong.
  • Also on the subject of materials – they all have a gamma correction of 2.2 making them unnaturally dark.  This can be overridden of course, either for each and every texture in the materials lab or in Post Render Options but not everyone will be aware of this.  It looks bad on content creators such as myself as customers want to just buy and load a material and not have to fiddle around with it to get it looking right!
  • Memory issues….again.  No change there then!   Seriously, a single terrain loaded with an ecosystem material and my resources dropped below 25%
  • The option to right click on the Select Render Area icon doesn’t work (how did they break THAT???)

One must assume the scaling issues must be linked to the fact that they’ve changed Vue’s internal unit size from 0.1 to 1.0 but that doesn’t explain the bump problem

I’m sure I’ll be adding to this as I use it more…….

UPDATE: Seems the problem causing memory usage  has been found and will be fixed in the next update

UPDATE Nov 13th:  ATMOSPHERES

Something else that seems to be incompatible with anything made in Vue 8 or older…..
EXAMPLE: Pic below is my ‘End Of Day’ from my Real Skies pack rendered in Vue 8 and looking how it was intended

Below, I made an almost identical scene in Vue 9, loaded the atmosphere and rendered.  This is NOT how it was intended to look !

November 18th – surely this can’t be right ??

One terrain with simple ecosystem loaded into scene (dynamically populated)

Gill Brooks


 

***After reading all what our friend Gill said,  it seems that all the ecosystems packs bought at C3D...would work easily till Vue8...but not easily with Vue9... !!!


MNArtist ( ) posted Fri, 18 February 2011 at 10:45 AM

Just chiming in that this is a MAJOR frustration, and really disappointing. I've been with Vue since v5, and while the stability of v9 is much improved (especially over v8.5), the whole scaling/bump issue is making me insane. 5 years of purchased content that must be adjusted now, depending on how it's being used. And god forbid you mix content that was developed for Vue9 and earlier versions.


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.